Robin_Hood

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.

From the tests I did some time ago, the bombs were bursting about 1.2 seconds after reaching 1500 ft AGL for some reason, instead of immediately after reaching that height. Therefore, depending on their vertical velocity at the time, you may find them bursting between, say, 900 and 1450 ft. Which, of course, is not really helping this matter.

I think this is a reported bug that happens when the mission starts in Case 2/3 conditions and progresses through the day to Case 1 (typical of dawn/pre-dawn mission starts). The carrier only kinda changes the case and gives conflicting information. Only fix at the moment AFAIK is change the start time of the mission.

I checked quickly but didn't find a report for this (sorry if already reported). When using the new feature, USAF Aggressors is not populated at all no matter the mission date, pretty much breaking the "country" entirely.

Oh, my bad then. I used SP to do some quick tests. I tried in MP, and it works fine indeed. Thanks!

Hi, the mod looks really amazing, but I'm having some issues with obstructing objects, as per the attached screenshots. Takeoff from runway 4 on the CVN-73. Any ideas what might cause this?