LuftWolf and Amizaur's Realism Mod Poll #10: The SLAM-Poon
 

Ok guys, the long and the short of it, is that I CAN get the SLAM-ER to hit ships, using waypoints. So more or less, the a version of the Harpoon CAN be added to the P-3 for ASuW.

However, there are some problems with this.

1) I can't get it to have true waypoint and RunToEnable capability... in other words, at this point, the missile goes active as soon as its fired. It will follow its set waypoints as long as it doesn't home on anything, but if it encounteres anything along its flight path, it will start homing on it.

2) I have no idea what impact this might have on its Strike capability... at this point, it may have to be removed entirely.

My goal is to get the missile to enable on what is originally the destruct waypoint, because then it could still be used for strike (just enable the missile a short bit before the target so the radar seeker itself can home for the kill) and would more or less have full Harpoon capability then, other than a Destruct waypoint, but this is not such a big deal if it has three Fly-To waypoints on the way to the target. I think it would be nice if the SLAM-ER could be made into a version of the upgraded Harpoon, since after all, that's I think what it is supposed to be...

So, this thread really is not a poll per se, since I already know the overwhelming opinion is to have the Harpoon on the P-3, but what I do what to know from you guys is at what cost you would want the ASuW capability added.

So, throw around some ideas, if you want, especially under what circumstances you WOULD NOT want me to make the change, meaning there is too much lost in gameplay terms to add the single capability of ASuW to the SLAM-ER.

Re: LuftWolf and Amizaur's Realism Mod Poll #10: The SLAM-Po
 

Sounds pretty good. Perhaps you can set it to use infrared instead of radar guidance? That will keep it SLAM - which has an IIR seeker.

And you might want to keep the seeker's FOV small (a few degrees). That will prevent it from homing too easily on other things, and will also simulate the difficulty involved when you use the real thing for AS attack - the FOV probably isn't all that big, and is even smaller if you want magnification so you can see anything with the limited res IIR seeker for a designation.

And just for the question - what point is it to have it "enable" on the destruct waypoint if the darn thing activates a seeker as soon as it is launched.

IR seeker on the SLAM-ER is the whole reason why it was a non-functioning weapon in the first place from DW 1.0 up to 1.03... too reactive with the environment, so that's out.

In terms of the rest of your post, that's the details that I'm trying to work out...

BTW, I think I have this one by the stones the way I want to... the Terminal Homing commands required to make it follow waypoints were interfering with it ability to enable, so I did a little bit of variable swapping (Runout for RTE) and get it to enable a little bit before the final waypoint, and its working...

I just have my test build for this now with all kinds of junk in it... so I'm going to script it from the bottom up and hopefully get it to work again just right.

I want all the feedback I can get on this.

Right now, what we are going to be looking at is an Advanced Harpoon for the P-3, basically a SLAM-ER that retains the Harpoon's ASuW capability (or a Harpoon with land attack capability depending on how you feel when you look at it): land attack capability on waypoints with terrain following capability is retained from the SLAM-ER, in all other respects it will act like a Harpoon (with radar guidance) with three fly-to waypoints before enabling, but it will not have a seeker size option, nor will it have a destruct range option.

What do you guys think about this?

Happy Easter, btw! :rock:

I can imagine that if it goes active upon firing it could cause a lot of unwanted trouble in a high activity environment...

:o I'd rather have no weapon at all then.

Happy Easter!

I'm pretty sure I've resolved that problem.

I'm going to script something from the ground up the way I think it should be and let you know how it goes. :up:

Cheers,
David

Well, the long and the short of it at 9:34 EST on Easter Sunday is that its working... I had to do a bunch of extra things to get around a problem that essentially amounts to "these missile don't like time compression" only to find the only way around it is to NOT use time compression during missile testing (because it totally fudges all the range calculations and if something is a bit off with these SLAM-ER hacks, the missile is going into the sea), and I'll leave it at that for now.

So I'm going to do ANOTHER build from the bottom up, without all the unnecessary work arounds and test without time compression.

It looks like TC+missiles are bad combo in general... all kinds of things might be messed up because the game can't calculate the ranges properly (they are moving too fast to calculate with TC on), so I'm going to say here now that I don't recommend using TC with missile in the air.

Ok, maybe another build of LWAMI is around the corner after all... this one seems worth doing 3.03 for.

Any other things people want to see in a new LWAMI build that you don't think will take forever and a day to do?

Sounds very promising :rock:

Yes, I just confirmed it using DebugViewer... using TC when missiles are in the air and the doctrine requires an xyrng calculation will cause a progressive under calculation of range traveled in the order of 30% each cycle... so of course that caused all kinds of problems in this situation where I have a tolerance of less of a 1nm between the missile doing what it is supposed to and threshing around like a fish in the water.

This should be very straightforward to do properly at this point.

Ok, so the idea for this is an air-launched Harpoon variant with Extended Response capabilities.

The new SLAM-ER will:

1) Maintain the range and speed enhancements of the stock SLAM-ER over the Harpoon. The SLAM-ER has a 280km (Harpoon is about 118km) range and a speed of 548kts (Harpoon is about 510kts).

2) Have a warhead equal to the Harpoon (enough to just kill the OHP with two missiles) and due to the wide wing span have a cruising and homing altitude of 30ft (equal to the SS-N-27 subsonic stage and lower than the 50ft of other seaskimming missiles in the game, including the Harpoon) and a radar cross section of the TASM (have to lose something guys).

3) Retain the terrain following capability of the original SLAM-ER and can cruise on three waypoints, with the last waypoint being the enable point.

Any suggestions on changes to this?

Cheers,
David

Oh crap... I've been bad... :oops: :damn:

It has nothing to do with the time compression, but rather how the runtoenable is calculated... that's a design problem but compounded by the darn interface... so I need to find another way of doing a couple things...

I'll keep you guys posted. :)

Ok, well, I'm just calculating the RTE based on time in the air (I can do that here since the speed is constant and this doctrine is only for the SLAM-ER... it should work fine 99.5% of the time if I build in a small tolerance, but not so big that it makes targeting too difficult) and the whole things works perfectly together for ASuW.

I need to do some testing on the Strike capability but now it works like a radar guided Strike missile with waypoint and terrain follow capability, as opposed to a TLAM which is blind and falls on the waypoint every time.

Also, I need to make sure the fine tuning of the missile RTE calculations are good, but basically, I think it can be said that the Harpoon is now on the player P-3C. ;) :up: :rock:

Ok guys, I need to do some range-dependant error correction for my RunToEnable calculation method since it produces slightly inconsistent enable points on the final waypoint based on total range travelled... since the enable point needs to be fairly precise in order for this missile to be used correctly.

This is going to take a bit of time... so I'm going to take a break and watch some baseball, and hopefully finish this tonight or so for LWAMI 3.03.

So, what else needs to be corrected for LWAMI 3.03? :cool:

Now is your chance. :yep: :know: :)

Cheers,
David

Does the SLAM-ER ever get used in any mission or scenario? If not then sounds like the changes would be welcome, otherwise it might leave some missions unplayable.

Yes,

I just want to know if we will lose the Slam-ER.
Are we going to be able to choose between Slam-ER andéor Harpoon for the P-3?

The SLAM-ER will function differently than a TLAM, but will still be capable of ground attack.

Keep in mind, this missile has been broken in stock DW since 1.0 and up to 1.02, so there are essentially zero missions that use the P-3C in a ground attack role requiring the SLAM-ER. ;)

No, I cannot change weapons because that is hardcoded in the interface for playable platforms, I can only change their parameters, and no I can't make dubs. It's either all the way changed or not changed at all.

If I could simply swap weapons in and out, well, then this would be a whole different experience modding this game (think new playable platforms...).

As I kept bugging you about, just do something fast on the missiles and FCRs in the DB. You don't need to get them perfect. Just concentrate on the most obviously wrong and go with what's already in your brain or whatever's close at hand - anything you can input would be eons more realistic than the present state. Don't bother taking more than a 60-90 minutes on this - fast, rough at present.

At least we'd see if people even notice the difference.

So you mean the weapon effectiveness of the various missiles and the ranges of the FCR's on the ships which carry them?

Yeah, a quick temp patch job on that simply shouldn't take more than 90 minutes. Making it perfect is hard, making it better from its current state is ridiculously easy and would still be appreciated.

Just to be sure we are on the same page...

What are the "obvious" ones?

OK.

0) Set a timer on your desk for 90 minutes (use your digital watch or something). Start.
Note: My timing assumes you use an automated editor like DWEdit.

1) Start by making the SS-N-22 and SS-N-25 Seaskimming - just change the doctrine used here.

2) In fact, make all of Russian SSMs Seaskimming. I thought the altitude set was 50 meters rather than 50 feet, but either way, even the -19 (presumably at least as low as -12), -12 (100 feet), -9 (130 feet) and upgraded -2s (50 feet) are a lot closer to the missile_skim alttitude setting than the missile setting. If you are really dedicated and the game allows it, make a whole bunch of new doctrines with various seaskimming altitudes to simulate different degrees of seaskimming ability. Quickie source and another quickie source here.

3) For extra fun, try turning on ECM for -12s and -19s (a flag). They are supposed to have jammers to improve their chances of making it through (those huge missiles are more like assault drones than missiles from the amount of features they have), and it'd be kind of neat to see how it'd work out, whether the game would even recognize such a thing. :D

4) Now, head to the SAMs - AAMs can wait. Think the SA-N-6 should only have a 60% effectiveness? If not, change it. Or maybe the SA-N-9 might be good, but it is hard to believe it is 100% effective (making it better than Aster)? Change that too. There aren't that many missile entries - going through the lot of them to check on one number in each should take only 15 minutes.

5) There aren't that many planes. Notice all of them have a radar and FCR SL of 67. Since we are aiming to make it better, not perfect this time, just do a quickie. Since missiles are around "50", set small planes like fighters for 60 and the big ones (bombers) say 70-80.

6) Head to sensors and bring up the radars. Start with the aircraft's search radars. Here is a quickie source you can use for coarse alignment until the time comes for the Big Renovation. Go to the FCRs for the fighters, and understand that they most definitely aren't cutting off at 36km! For today's coarse alignment, just assume tracking range is about 60% of detection, and set the values accordingly.

7) Head to ship FCRs. It is hard to get the right data, but at least ensure that the cutoff is longer than the range of the SAM involved! Specifically, I refer to cases Top Dome, who's hard cutoff is 36km when the database says it has 74km. You might also review cases like the SPG-51, which is used to direct SM-2s (at least earlier versions with range of only 70 or so km). Adjust the FCR range accordingly.

8) Just keep on doing what you can along these lines until the timer beeps.

Thank you very much. Now let's see if anybody appreciates this. I would.

I thought most Russian SSMs where high altitude weapons with a terminal dive manuever.