Moonshine

@BIGNEWY any chance you could move this to a bugreport? at least mine and furiz post as while yes he did not align the helmet properly, it still is a bug

That is true, yet even with a perfectly aligned helmet the TD box is off from where it should be. The TD box as seen in the HUD does not match the actual position the TGP is looking at as seen in the TGP page. So even without the HMCS the marker vs the tgp view is off. most likely connected to the issue with excessive drift etc made a short track to showcase. - Airspawn -> so HMCS is "perfectly" aligned -> GPS is on, so i should not get much INS drift - on the first pass the deviation is minimal as i have been flying for barely 5minutes. - on the second pass the deviation is already easily visible, and im only flying for 15minutes - on the third pass i use the HUD only (so i could not have thrown the symbology location off by doing a bad HMCS alignment) - still, TD box VS point tracked location on TGP is off quite significantly. and thats after 15 ish minutes. the longer you fly the worse it gets. no alignment will ever fix that. this is also referenced here: and here: so, while you definitely MUST align the HMCS during a cold start to "not have that problem", it currently does not eliminate the problem, rather than just make it "a little less off" TD_box_misaligned_vs_TGP_view.trk

confirmed, seeing the same. yet it only defaults NAV mode to Azimuth 1, not A-A. Azimuth_1.trk

make sure the .png is written in lowercase (.png and not .PNG)

why a wishlist? was literally a report in 2021:

with GPS, Bluefor Viper at around 40m and redfor (without unrestricted SATNAV active) 100m or more according to this post: If even with gps you are getting 100+ m of deviation, then something is off as it does not match the „no more than 40m“ claim in the linked post. there is also bugreports about SPI location drifting etc.. so might be a combination of things that lead to excessive perceived drift. Pretty sure TGP sight picture would not match Hud diamond (or TD box) placement in your track either

look, i did not claim my post was "the solution as it would be in the real jet". it is just the way DCS does it at this very moment in time. reference this:

Dont turn on Mids before your alignment is complete and your time page shows „GPS“. In some cases, you even have to roll out of the hangar.

or you take the AG radar, slew the cursor over until the bullseye location of the cursor matches the bullseye location you are supposed to find and create a FCR Markpoint off of it..

as per the title, the waypoint as set in the ME seems to be off compared to what the jet will show. attached the track and a screenshot. you can see where i put the waypoint in the ME (at 0ft AGL) and you can see without moving the TGP that it starts drifting off as if the waypoint was hanging a couple meters in the air. this happens even in a point track and even with markpoints that have been created using Laser ranging first. on top of that, if you zoom in on the TD box (or the waypoint diamond), it starts jittering heavily the higher the zoom level is. TD_box_jitter.trk

Its been over a year since that bug was reported here, its pretty big of a problem if there is multiple emitters of the same type in the mission and it would be nice getting that fixed. since the old report was locked, id like to simply bump it again.

Not working for me, clean game, except SRS and Tacview. crash log attached. @Lord Vader dcs.log-20250123-163132.zip maybe its the sheer amount of contacts causing this. not getting crashes with "low" number of contacts.

we had this issue before, described here: with the lastest patch, it was re-introduced. was fine before the update on the 21st of January.

Thanks for the test, good insight. i do know that some servers/scripts dont just „shut down“ things, instead it effectively „despawns“ the units as the player moves a certain distance away. Would explain the disappearance you are describing and probably the next thing to test.

isnt that "on" or "off" thing meant to be for force sensing sticks (when set to "on") and for spring ones when set to "off"? thought either newy or nineline posted about that a while back, cant find the post just now Found it:

Not 100% sure but it might be worth exploring the case of „turn a SAM off while HTS is locked on it“. I had that happen too no matter if „trigger based SAM shutdow“ (normal ME triggers) or IADS script controlled ones like when they shut down detecting a HARM. since that self protection against anti radiation missiles is now also possible without external scripts (standard ME function) it might too cause the issue.

Might be subjective. Normally, no axis curves, gradient to „off“ (unless you use a force sensing stick) and sliders to the maximum.

No idea what was borked, full repair has fixed it. Thanks for all input and merry Christmas

Awesome, thanks, will do. Will have to wait until tomorrow though. Yeah im aware. In the past however we had an issue occurring only when cold started, not in hot or airstart. Hence why i test everything off of cold starts

I wanted to but somehow i cant upload anything bigger than 266kb anymore, even the shortest track is too big

Hm. Ill try with a clean install again tomorrow. Would be good if it is just my game, and not the update. Thanks for the feedback and merry Christmas o7

huh weird. In a previous try i dropped 4 of them, none tracked.

see title cold started, changed laser code to 1511, took off, set up laser codes in the TGP DED, laser arm on, set autolase to 15s, dropped a bomb - miss. she did not track at all. also didnt work with 1688 in previous tries track attached GBU-12_not-tracking-laser.trk edit: also tested with a fresh miz, airspawn, everything default (laser to 1688). still didnt track.

yeah been doing that for years now. still requires direct line of sight and doesnt work if the weather is bad and hence you cant see it. on top of that, requires TGP point track to generate a markpoint, which will - upon entering point track - already shift the coordinates compared to what your SEAD Page would have shown. only thing that would work is the AG FCR.

thats fine if only we could actually store the info on the SEAD DED page as a markpoint. but we cant.