Im_TheSaint

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")

Jonsky, pls test this: open game, open MP, connect to GS or some other server with integrity check but with pure scripts no. Then slot in with the plane where you have modified files. Then disconnect from the server. Then your IC should fail like mine and you have to restart. If that happens, we have the same issue. Otherwise, please send me your PFLD file Im_TheSaint#4970

That means that in terms of issue description, you have the same problem as I, or everyone else who will be running scripts of any sort, even the kind of scripts that were allowed by ED, during a big discussion and patch, on this very topic a few months ago. Se1ko I am tryint to make ed treat this as a bug and resolve it. But for now it looks like the temporary workaround is restarting DCS. Which is an unacceptable usecase.

Here are some screenshots of the process: 1. After I restart DCS, my IC is okay. I can go join a server with 'pure scripts' off. 2.) I found an F16, slotted in clicked briefing and fly 3.) Immediately afterwards. I disconnected from that server. Now, even without trying to join a new server I see that my IC is invalid. 4.) If I try to join the same server, my MP IC checker fails me:

Neither of these pieces of advice work. Even if I restart, it just happens again and again. It is clear that standard IC has changed, because if I join a server with 'pure scripts' disabled, after disconnecting from that server, my IC in multiplayer menu fails again. Try these steps to test it out, on your system: 1.) Change one of your cockpit scripts file. You can add code, or a comment. - The easiest way is to change release ammounts in your CMDS lua file. (make a backup of that file before hand btw.) 2.) Open the game anew, and go to a server with IC without 'pure scripts' required. (Growling sidewinder for example). 3.) Slot in with a plane, of which you have changed the file. E.G. Slot in with the F16 if you changed the F16 CMDS lua file. 4.) Click briefing, click fly and thats it. Now go back to spectator or just disconnect. 5.) Your base IC will be invalid absolutely disregarding that the server you just used, had pure scripts off. I believe what I am reporting, has absolutely nothing to do with ’pure scripts’. My own DCS client is telling me my IC is invalid, not the server. I havent been kicked by a server or a server refused to allow me to connect no. Instead the MP ic checker blocks me. If you test this for yourself, you will find out that mods which should not break IC, do break IC.

Visual export code such as: dofile(LockOn_Options.common_script_path.."ViewportHandling.lua") try_find_assigned_viewport("F16_RWR") or making changes to the profiles in CMDS page will result in a broken Integrity check my DED_init.lua more info here in f16 specific thread:

ED giveth, but ED also taketh away

Hello Jonsky, this is not true. About 6 months ago, mods such as these were added onto a list of mods that do not break IC. ED curated it and it was a pretty big conversation where it was decided that these shouldn't break IC. Also, this isnt a pure scripts issue. It's an IC break issue. Disregarding of sever settings. Therefore, imo this is a bug. BIGNEWY already confirmed as per the screenshot, that these mods should still work even with the new patch. I am afraid you are simply not right.

The changes that I have made, should not break IC. And therefore if a server requires good IC from me, it should work. I spoke to BIGNEWY about it just now, and he literally confirmed it. You're missinforming _SteelFalcon_

What falcon said, has no bearing on this issue. It's not a question of whether servers require pure scripts or not. The changes which I have applied should not break IC at all, because these changes are on a list of allowed mods. This was decided by ED themselves in a huge discussion, about half a year ago. I spoke to BIGNEWY today, and he confirmed that:

Integrity check is once again broken by visual exports of cockpit elements. This is a thing absolutely fundamental to people with home pits. Here i am providing a screenshot of my IC fail, and also an example of a piece of code I added to my f16 ded file, so that it renders on an extra screen in my home pit. Can I maybe change the code somehow so that it works? I am providing other examples, of my RWR and HSI files, where I added the same line for visual exporting. And then I am adding my CMDS file, where I simply edited the countermeasure release programmes.

D4n, you may be the first person I have ment, whose perspective I trully did not understand. Why would that bother you? Even if you're bad, and want to cope, (which clearly). How do you arrive at making this particular complaint. Instead of the million other things you could call unbalanced, in a simulator. (Which DUH). And the Track IR/VR tagging of players too. It was the most ridicolous thing I've ever heard. How did you even arrive at that becoming your concern?