Moonshine

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)

everything has been said in this and the previous comment. its pretty clear what the issue is. still wondering why this is tagged as "correct-as-is"

@BIGNEWY please take a good look at this part. It has, regardless of module, been a long standing issue and is often criticized by the community. Funny enough, ED tried to combat this with Wags FAQ videos. Yet where are they? The first (and only one) is months back. Now you might say its up for interpretation however it really looks like you cant ever follow through or even finish what you promised/started. The feedback on the state of the F-16C from @WHOGX5 perfectly shows this. Thanks for writing this out. Ive been very keen and active in the past reporting bugs etc yet the way things have been handled and how the community has been treated on these issues have lead to me (and surely others) to not even bothering anymore. ED does not primarily need new modules to get people hyped. How about fixing the long standing issues on modules and most notably the core to not make scripting, planning, organizing and flying such a hassle? one not constantly monitoring the forums to keep current on whats broken or not is in for an unpleasant surprise everytime they fly in some form or another. Somewhat acceptable if its in open beta. But its all in stable now. As a paying customer this is not acceptable and very disappointing to see.

i understand that when looking at the issues most all of the modules have in some capacity this thing seems like a low priority thing. but there is so many small things in the core game that if fixed, would make the the game/sim significantly more enjoyable.

thats already a bug report. im sure there are more older ones than that one. need to search further found more and funny enough, this one is 13 years old:

not that. i got my visibility range maxed out yet exhaust smoke and contrails only show up at a certain zoom level or distance (or a combination of both). this btw also applies to any sort of smoke plume (like from destroyed ground units).

indeed not "correct-as-is". wonder on what documentation ED is basing the current implementation on. would be nice to see this changed as @WHOGX5 described.

please uninstall mods (even the yellow MFD one) and submit a track, not just a screenshot so people can try and reproduce it. in the past, mods (even cosmetic ones) did cause some things to break. dont ask me why, spaghetti code i assume. just to be sure, best to run a clean game and submit a track on every bug report unless you want endless "missing trackfile" or "unable to reproduce" tags on your reports

Please put that in a separate report, including a trackfile of it. Otherwise things get mixed up and nothing gets done to fix either issue

same, happens with any asymmetric loadout, not limited to AGM-65

yes, no need to insert it again, just "double check" to make sure it matches what you set it as via the ME or the Rearm/refuel menu exactly, it will mess with the attack as it calculates release parameters that your bomb does not have havent tested or verified that, however the post in the viper mini update mentiones that the only fuze you can change mid air is the FMU-152 tail fuze which exists for GBU-12 and GBU-38. so changing those values should carry over to the bomb on the jet

remember, the only fuze you can adjust its settings in the jet is the FMU-152 (which the CBUs dont have). for every other fuze you need to select the desired fuze settings via the ME or via the F-10 ground crew menu. then in order to get correct release parameters based on the fuze settings of the bomb, you need to tell your jet what the fuze settings of the loaded bombs are by adjusting the values in the SMS. all you do is tell the jet what parameters the bomb has, you can not change the bombs parameters by changing the SMS values. and until we get some sort of weapon delivery planner and DTC you will have to do it manually.

so bottom line (despite it working previously) it now requires direct line of sight, bomb on coordinates is no longer valid as unless you try to hit a massive building, you wont hit anything. sad to see it changed that way and stays that way until its refined. hope it wont take months until that. its a rather core part of using those weapons in adverse weather conditions with no LOS

while i see the same thing regarding follow-on mavericks, i could not see the CMS thing. worked all fine on my end. i changed programs, i switched modes, never turning it to off and nothing out of the ordinary happened

it is what you need to do. boresighting is done at a certain distance, so anything above that distance and anything below that distance will look slightly off. only at the exact distance you boresighted will the mav and the tgp perfectly match. which is relatively hard to get right that perfectly. if anything, the very perfect boresight (without ever boresighting beforehand) of other modules seem to be a bit of "wizardry"

true. turning GPS time off and on again (or in this case ON - OFF - ON as its somehow on off per default) does not adjust the time at all