NSAdonis85

nullGBU_MovingTarget_Training.miz After boresighting Mavs the waypoint is displaced on the HUD/JHMCS as on the screenshot until weapons have been fired. dcs.log LastMissionTrack - Copy.trk

Same thing happens for me in Syria (I and others have posted about this long ago and got ignored). Look at my A/C modules list, and the F1 is the only one that butchers frametime for some reason. Before bringing up the esc menu made it back to normal, now that just makes the frametime better.

My first question here is: do you in any way do the following: 1) change the default gpu driver profile 2) change the DCS GPU driver profile 3) have DCS added to antivirus exception (both game folder and saved games folder)

I did loooong ago, never got any reply ever.

The issue still persists after yesterdays patch. dcs.log

Yea, I know about the DTC part and what prerequisites it entails to be included, the way the F-15E and F-14 handle waypoints with naming together with the mission tab is something that would make everyone's lives more easy with this in the long run on jets that have a more complex INS system that can handle more than 9 waypoints plus 9 correction waypoints (example in my mind here is the Carousel IVA unit). I don't know if it's accurate that the JSOW/TPod slaves to the altitude given IRL. Mentioning all this in documentation would be good too, so far neither of the 3 (A-10, 16, 18) has it as far as I saw. I do own the Apache too but I haven't gotten around to learning it enough to know how this works with it, the Ka-50 has it's own similar system already. Yea, Revan is my fav SW character (with both games, never got into SW:TOR enough)

It seems so. Would be nice for the A-10, F/A-18 and F-16 to get the mission planning tab like the F-14/F-15E has tho, that would be a much better solution than this current one.

I think I know why it is happening. Both when I tell the tpod to slave to a waypoint or I waypoint designate the JSOW it gives the altitude I set in ME (FL300), not the height above sea level as you can see on the screenshot, so if I even release the weapon it just goes dumb because of the alt diff. I don't have this issue with the F-15E because of the mission waypoints tab in ME. I'm including the miz file too just for reference. JSOW_Training.miz

I will, thing is, I might have done something wrongly in the track, i wanted to just replicate the behavior, I'll rerecord it tomorrow. Is the setup errorless tho?

Topic name says it all.

Still happens in any Mirage F1 mission on Syria map. I have loaded into an F-14B, M F1CE, then Strike Eagle, made screenshots of it, including log file too. Note what happens when I hit Esc to bring up the UI in the 3rd screen. dcs.log

The tell-tale difference is in the frametime, I still have this issue BTW, altho i haven't checked it the last 3-ish patches, will report back when I check on it now.

I noticed that if I waypoint designate a JSOW it acts like a JDAM with the super low release range, but if I radar or TPod designate it works fine usually. I ncluded track and mission I used just in case. FA-18C_JSOW_bug.trk JSOW_Training.miz

The carrier cold start mission hangs on either a full or partial second stage loading since update 2.9. It hangs there indefinitely (I let it there at one time for about an hour and it didn't load in) dcs.log

Oh, so this is among the new additions to the F-16C, haven't had time to read the mini-updates thread.