Moonshine

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.

good to hear. will that "Sead target" also be stored for the aircraft sending it? kinda pointless if everyone gets a steerpoint but me who actually has all the data and sends the information to the other members? i think thats the bigger issue than having or not having threat rings. the thing in question was the fact that the one sending such a point does not get any way to store it for himself.

You did not understand my question, we are talking past one another

While correct, still does not explain why - after going through the process and finding a sam with TDOA (teamwork with my flight members) and then me sending it via link (stp 107 and onwards or whatever) - I as the one sending it via link do not also get the information i am sending displayed on the HSD, meanwhile all my flight members get a new „ring“. That is the subject in question. Not how rings are tied to units in the ME currently and therefore at the mercy of the mission designer.

it is fine if it "defaults" to that but currently it is "exclusively" that and that is not right. i should be able to change it, not only via DTC but also by simply changing the delivery mode from CCIP to CCRP, DTOS etc. regardless of weapons on board or not. in addition, DTC should not be the only way to manipulate the SMS and telling the jet what is loaded. manuals clearly describe how its done manually as well. somewhat of a different topic as we lack the function in game as of now but sadly directly linked to this issue.

dm sent

Unless i tell the SMS via DTC or manual entry what is equipped on the jet it doesnt know anything about weapons loaded or not. I should be able to fully manipulate delivery modes and radar modes WITHOUT having to have anything loaded. The fact we cant even manually tell the jet what stores we have is another thing not done right. somehow however the jet knows I expended all my AG munitions and yet i still can manipulate all delivery modes. I just have to have loaded up something first. This can not be correct. With that i should be able to put AG mode in, master arm to „SIM“ and the jet give me every delivery option and symbology just as if i actually had a weapon loaded. We cant even do that. The artificial barrier that the computer doesnt let us manipulate stores pages, delivery modes and radar modes is false. These are not hard linked to „no weapon no manipulation“

Its been like this for a while, wonder if thats correct. Scenario: i was flying some CAP, had only A-A weapons with me but i did have both pods (HTS, TGP) with me. While i was cruising around waiting for things to happen i thought id locate some SAMs. switched to AG mode, locked some things up with the HAD and tried to refine the position with the TGP. didnt work as it did not let me slew the TGP at all. this is due to the fact that with no AG weapons attached, the AG radar is stuck in AGR mode as the default delivery mode is set to CCIP. and we cant change the radar modes or the delivery modes at all, not even GM or GMT is possible. i doubt that is correct. as a workaround i had to use NAV mode with the HAD and TGP as then the radar is in CRM mode by default, not "hindering" me slewing the pod. wonder if thats correct because if you expend all AG munitions but were in CCRP or PRE during weapon delivery, you can continue to use HAD and TGP in AG mode no problem. i reproduced it in a short track where i was trying the same thing with locating an SA-3 using first the AG mastermode, then the NAV mastermode. track attached Cant_slew_TGP_in_AG.trk

apparently GND/AIR fuzing options are still work in progress.

it does not choose the rail based on amount of mavericks. in your case, you chose LAU-88 triple rail. if you want 1 missile only i suggest you select the LAU-117 single rail. for reference about "big" or "small" mavericks: D / H Mavericks are small G / K are big