Moonshine

@BIGNEWY why is this a wishlist item and not a bug? it was working before you guys remodeled the RWR..

Sams in DCS are rather simplistic. Only by using scripts like Mantis or skynet you can make them behave less stupid. Until ED comes up with some more in-depth modelling of an actual IADS, thats sadly how it is.

the higher and faster something is, the faster his missile will be and hence will cover the distance from pitbull to impact more quickly. thats why at very high altitude, just defending when you hear the RWR wont suffice. you have to anticipate that the enemy has fired on you already. not even mentioning thin air and hence less drag for the missile but also slower control response for any defensive maneuvers. The Amraam has some guidance capability with Datalink, so if you lose lock, it will continue to fly to the anticipated location of the contact, and, with some luck, pick it up on its own radar once active. however this is not as reliable as if you continue to feed the missile info by holding the lock until she goes active

might be related: dont think its the bombs fault but the CCIP post designate

i support that point. an option to choose would be beneficial. having switched from a "conventional" stick - that was great all around - to a FSSB did improve the "feel" of flying the viper in ways i cant explain. i just feels so much better, more agile and more responsive.

i tried to get a track from a MP server (as they save automatically) yet so far i can never open them (most likely corrupted due to the crash). @BIGNEWY could you please take a look? the "missing trackfile" tag like on this post (merge, same thing) wont help solve the problem.

indeed you are correct. you can type in all the data, as soon as you switch the release mode to CCRP (or even PRE for MAVs) the game crashes. and no, Track cant be produced as of course the game crashes before a track can be saved... here, a video: https://drive.google.com/file/d/1cNypCukWXB6bu0auxKXXw1Rf1iS1rbUp/view?usp=sharing

Yes this is also why i observed in my test, lat long was fine but elevation was couple feet off every time.

As already raised and explained by @Sadhu, the WPT data shifts when pressing TMS aft to CZ. while the coordinates stayed consistent in my test, the elevation data after pressing CZ was off compared to what the DED WPT entry says. i understand this to be the case when area track or point track is commanded as it measures true elevation, however not when the pod is just slaved to the steerpoint. Sadly the previous post was locked, so i made a new one. TGP_TMSaft_shift.trk

even if thats true, it would explain why it wont work if you are alone and have no AWACS. but doesnt explain why its not working when an AWACS is present. he is a different donor. and if the AWACS already classifies something as hostile (which would mean that multiple factors identifying something as hostile is already true), i dont think your own aircraft should overwrite that information. yet currently we lose all classification as soon as our radar paints something. even worse, on top of that, the classification also disappears on the HSD. which it shouldnt

Been discussed and raised here: sadly the post everyone is referring to in that thread is „no longer available“…

Im seeing the same as Cypher whenever i create a static template off of a flight, then load an empty map, add the static template and somehow the STNs for #3 and #4 are swapped constantly. Only manual input in the jet „fixes“ it. I made a post about it a while back. in the meantime i changed PC, completely reinstalled DCS from scratch and it still happens.

select HAS, search emitter, lock emitter with TMS Up, try to break lock (TMS aft) - not working - am i missing something? only changing mastermode or switching wpn station gets rid of the lock track attached. HARM_HAS_cant-unlock-emitter.trk

thats funny. because i just tried to see what happens in other mastermodes when MARK is open on the DED. in AA Mastermode i can still lock radar contacts and since doing that via TMS UP, it also creates an OFLY Markpoint on my current location. so the Sensor PLUS the DED take the TMS input..

it is only done via payload restriction, never used it, dont know if that even allows you to load them or not at all. there was a massive discussion years ago about 4 harms for the viper or only 2. can read it here: https://forum.dcs.world/topic/245426-4-harms-for-the-viper/ and this was the final conclusion (when payload restriction option was introduced); https://forum.dcs.world/topic/209147-viper-mini-updates/?do=findComment&comment=4769196

Depends on how the pylons are restricted via the mission editor. ED implemented an option in the ME a while back that would let mission makers choose to „disable“ the inner stations to be used for firing harms (but can still carry). Trackfile would help

as the title says; when starting cold (or in any case from the ground and not airborne) all elevation values typed into the OA page will result in the triangle symbology to be below ground. HOWEVER: if you re-enter the elevation values while airborne, the symbology is correct again. i dont know how many times ED "fixed" the OAs but it would be cool if it could actually be fixed. sorry for the new post again, but the others are all locked... track attached. you can see me overwrite the values agian as i am in the air and close to the target OA1+2 below_ground.trk

AGR_no-wpn.trk AGR_wpn_loaded+unloaded.trk

even with just guns you should be able to use the AG radar together with other sensors like a TGP. maybe you just want to do some recce? i doubt that would be done in NAV where you cant see sensor symbology in HMCS

thanks for clarifying

But what does it do if i have a steerpoint offset induced but am not in any FTT (so there is nothing to reject)? because on the TGP, first TMS aft returns to INR track and TMS aft again REMOVES the steerpoint offset.

So there is no „TMS aft“ function associated with the AG FCR cursor slewing (before a SPI has been designated via FCR as then it would just reject it again like you said)? maybe i have to reword my question if you use the AG FCR (no matter which mastermode) the cursor is on the currently selected steerpoint „slaved“. Now start slewing the cursor on the radar screen but do not designate anything. After that you want to return the cursor so it is back to the original steerpoint location. You can achieve that by pressing CZ on the OSB, but not with TMS aft. Whereas with every other sensor selected as SOI, TMS aft would do the same as the CZ button does

Not sure i understand that part correctly. So CZ is an SPI logic, not limited to the TGP. If i slew the cursor on the AG-FCR, TMS aft will not CZ the cursor back to its original SPI location (slaved to a STP). Only the OSB will do that for me. Is that intended? Because when HUD is SOI and i slew the steerpoint diamond in NAV (or any VIS mode weapon, DTOS etc when in AG mastermode) TMS aft will remove the offset induced by slewing

@itn might be related:

make sure you dont run any mods and if still having issues, run a full dcs cleanup and repair