Moonshine

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

Same thing as here?:

no log, no track. pressing and holding EXP FOV (to zoom in on your flight) will cause a CTD

confirm, just happened yesterday. i was fully expecting it to zoom in focusing on the lowest scale that shows all my flight members, instead it zoomed fully out to show every link contact. something is fishy

has to do with the missing "absolute" targeting. only "relative" targeting is modelled currently. ED is aware. lets hope this will be done rather quickly as it limits the viper to bomb drops while having direct line of sight with a TGP (lets face it, off the AG FCR you wont be accurate enough) so bad weather operations are not possible with JDAMs

has been raised here: sadly, since this bomb was added and without its proper guidance modes it aint any better / more stand off than a GBU-10. best to stay away from it

confirm, 6x singles, 300ft spacing. result pretty obvious: @BIGNEWY could you move that to the viper bug section? MK82SE_ripple-singles.trk

the ED manual or an actual one? because neither manual at this very moment describes what we currently see in the aircraft. its not only about filling the contact, its also about coloring it correctly. one does not just suddenly lose every ROE classification upon painting things with a radar. but currently we do. if the ROE tree programmed in the jet does not correlate with the one from link, one would see the symbology mipple. which we do not see either

its a bit misleading that its title is related to TWS. in the end the subject is about the whole symbology / colors and the effect of it can be seen in modes like TWS where it leads to issues due to the facts it is impossible to tell what stage of the "promotion ladder" the contact really is (system or tracked target). you really only notice you went too far if you suddenly have it bugged.

yeah the way the symbology is makes TWS really unuseable unless you disable all link symbology on the FCR dont know why ED fails to see this..

time (in zulu) when your reach the steerpoint. your current time is 17:34:01. you have 5min 17s to get to the steerpoint. now if you add those 5:17 to the 17:34:01 you get 17:39:18

the dust smoke is not displayed when using the game with Multithreading (which is now the default). start it in single thread and you will see it work. creates very awkward situations in multiplayer where some people have near 0 visibility down low and others can see everything in perfect conditions.

has to do with the implementation of absolute and relative targeting. currently we only have relative targeting implemented see more info here:

Already reported

Long standing subject, been brought up on multiple occasions see and and (especially funny that the original thread that is often referred to in this one can no longer be found anywhere)