Robin_Hood

Sorry to resurrect this post, but I have a question. What does the "IMU reset" procedure, described in the manual (page 282), do if it is not a kind of in-flight alignment? It does require to fly straight and level for 5 minute, which sounds like the sort of things you have to do for in-flight alignement. Also, I've tried the procedure described (INS - OFF, then INS - IMU, fly straight and level for 5 minutes), but "IM" never appeared on the TID, it kept on displaying "AH".

We have had the same experience, with the Link 4C not working after a multicrew ramp start, but working with a pilot-only rampstart. Any news on this?

Got it, thanks. I wasn't making any comparison with the APQ-120 though, I was only talking about the AWG-9 (and the above image is from the F-14 manual). Anyway, the AWG-9 is already pretty fun to fiddle around with!

Browsing again through Heatblur's manual, I came across this picture of the Pulse Search mode (page 222), where altitude returns are indicated and displayed approximately in the manner that I would expect. I am guessing then that sidelobe clutter in Pulse Search should be a thing, but is just not implemented (yet?).

Hi everyone, I hope some people can shed some light on this for me. I was wondering why there seems to be no sidelobe clutter (especially altitude returns) in PULSE SEARCH mode. I have searched but couldn't find anyone mentioning sidelobe clutter except in relation to Pulse Doppler. I understand that in Pulse Doppler, both main lobe clutter and altitude returns are filtered (MLC filter and Zero-Doppler filter respectively), and that the zero-doppler filter cannot be deactivated. However, it occurs to me that in Pulse Mode, the sidelobes should also be a problem, and shouldn't altitude returns also appear, at a distance roughly equal to the aircraft's current height? A sidelobe pointing at the ground in pulse mode would create a return, wouldn't it? Is there still some Doppler processing anyway with the zero-doppler filter even in Pulse, or some other way of filtering out aititude returns, or is it simply not implemented? Or am I missing something?

Interesting, I'll try different times and maps, but I'm pretty sure it worked alright a few weeks ago; now that I think about it, I have changed the mission start time some time ago, maybe it placed it at a different date then. I'll investigate

I would like to submit this simple mission and multiplayer track where the following behavior occurs: Initial conditions: - There is a ME-defined flight of 2 client F/A-18C and an E-2D Hawkeye - Both F/A-18C are defaulted to the same MEMBER Datalink group Behavior: - At mission start, I can initially see the other Hornet as the "B" flight member on the datalink - A few seconds later, he disappears and is replaced with a simple datalink contact from the AWACS, instead of a member or donor or even a party to the Datalink net The track file and the mission file is attached ; if I have missed something, please let me know Note: this is a very simple case that I made after seeing the problem in more complex cases (user-defined groups, custom VCS and TN, etc...) Datalink_multiplayer_test.trk test_DL.miz

I don't see this bug as "reported", so I'd like to bump this thread. Here's another track ; one F/A-18C, one train, one ground mover. The vehicule shows up on the GMT display, but the train doesn't.Trains_GMT.trk

Hope this is not forgotten, since we are getting the SA-5 also, that will have to be added to the filter.

Except that tha APU in the Hornet doesn't provide electrical power. So...

Alright, thanks, Grimes. I've been working on a modified version of MBot's ASW Script, and I wanted to have the sonobuoys work only if the hydrophones weren't lowered into the bottom. Guess for now it'll wait.

I guess testing all that on a flat terrain should eliminate any possibility of a DTED influence, wouldn't it? (Perhaps over the water, so that elevation is really constant for miles around)

Hi all, with seabed depth modelled on the maps now, I am wondering if there is any function to get the depth of a Vec2 position, like land.getHeight does for terrain elevation. getHeight gives 0 (sea level), and getDepth doesn't exist. Any thoughts?

I know 1.2 seconds (after release) is also the second option (in-flight selectable), that also works in the F/A-18C (by MFUZ = PRI, IIRC). There might be a mistake here on ED's part? Maybe this would actually warrant a bug report. There is also the backup 500 ft (IIRC) for VT fuzing (if the bomb never senses it crossed the (ground-)selected HOB, it will burst at 500 ft anyway), that I think is not modelled right now in DCS.