Im_TheSaint

I understand the technical differences between the pods, tell me which one you actually prefer though Which one do you actually think is better? The zoom is so much nicer on the litening pod, and that actually makes it much more usefull for me for A2A and A2G purposes. There are very few uses of the advanced features of the SNIPer, that are both usable, and necessary, at the lower ranges it can be used for. Tell me a use case that the SNIPer can do, that the LITENING can't, I'm really curious.

Make the RWR exportable by default

Like this? 201 being my station number? @Tholozor The feeling where people from your discord group answer your public post i knew i should have kept it in the family.

I fly the 16 with my 18 friends. How can they check their STN number, i can then add it to my 16 side of DL.

You need to disable modules. You dont have to delete them. How many planes do you have? disable them all but 2 which you will fly that day. Then it works better.

After speaking to a few dozen people, im prett confident in saying that the new dynamic slot system is a failure from a performance standpoint. It crashes peoples games. Its performance tax is insane. Even people with astonishing PCs have massive stutters during the slot select screen. It's sort of game breaking. I found that deactivating the amount of loaded modules helps immensely. However this isnt scalable. If I have 3 active modules the slot system loads fine, if I have 6 it doesn't. Thats practically unscalable as most long term players use a dozen modules. And obviously doubling the amount of active modules - ergo doubling the amount of dynamic slots on the map - should not cause game crashing. A 10 fold increase should, but merely doubling? Do you understand what I'm trying to feedback here? What information do you need to recognize this as an issue?

Yes we have done that too. Does the wingman not need to press any buttons? TDOA calculation just happens when the lead induces it?

I know, that's not the problem.

How am i to induce a TDOA calculation as a wingman? The lead is supposed to tms up an emmiter on the had page, and then tms left long, what is the wingman supposed to do?

RWS has a bug where you can get set the bar scan setting to do more than 4 bars, and the radar does behave accordingly. Steps how to replicate: Go to A2A Master mode. Go to TWS (by TMS right long). Cycle the bars setting to 3 bar scan. Switch to RWS (by TMS right long) - Notice RWS is now set to 3 bars. Which should be impossible. Cycle the bars setting - See bars go to 5, 7, 9, etc. Fix by going back to tws, cycling bar scan to 4 bars, and go back to RWS. Should be fixed.

Whether you prefer to boresight your mavericks in flight or on ground, there is a bug somewhere between the targeting pod and the mavericks. In your hud the maverick symbol and the tgp symbol will be on the same place, but in the MFDs you can see that they are looking at different places. Making targeting impossible. I think this is part of a greater TGP bug, where the TGP can get confused and will look into the sky when looking at a steerpoint that has ground altitude set up. Maverick boresight does not really work.trk

can you share how you are exporting it? i forgot what the viewport name was

Just finally add these two lines of code to DCS Open Beta\Mods\aircraft\F-16C\Cockpit\Scripts\EWS\RWR\indicator\RWR_ALR56_init.lua dofile(LockOn_Options.common_script_path.."ViewportHandling.lua") try_find_assigned_viewport("F16_RWR")

It's a quality of life change that allows us to export the RWR indicator of the f16 without breaking integrity check, or without enabling exploits. It's two lines of code that you can copypaste. I want it on one aircraft in one Display, but if ED does this for enough many of the displays and indicators, they don't even need to address the poor usability of IC anymore. That has been so irresolvable for so long. This removes the main issue with it. If you as a user are exporting your MFDs, (like soooo many players out there), you are able to do so, because the MFD files on your favorite module already use a piece of code like this. I just want other major parts of the plane to do so too.

dofile(LockOn_Options.common_script_path.."ViewportHandling.lua") try_find_assigned_viewport("F16_RWR")