Im_TheSaint

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?

D4n, get good, srsly.

I think I spoted an inconsistency between the manuals and the visual model. As per pictures, the 3d model of our DCS P-47 uses the CE 13' paddle blade propeller, specifically the symmetric type with a narrow base which was indeed used on the d30 and 40 models. However the manual states a very generic Curtis constant air speed propeller of the size of 12'2". This was sometimes called the toothpick proppeler. I believe this a accuracy conflict between the manual and the 3d model. On top of this, almost with absolute certainty the manual is wrong. As the "symmetric paddle" prop has been used on models since the P47-d23RE variant. And the performance of the plane in game indicates it's being used instead of the original toothpick prop. More info for enthusiasts: The original toohthpick prop had lower proppeler efficiency, or rather, the better paddle prop had a much higher efficiency. This efficiency gap would only be enlargened with the higher HP engines which came rather quickly after the plane's A variants. From thrust horsepower calculations based on climb rate difference between the toothpick (in the manual) and the paddle prop (in the 3d model and on the actual planes), the effective thrust horsepower difference for a 2600HP engine, can come up to 400 or more more thrust horespower available (based on data used). Which is a massive difference from just a prop change. Sobert S. Johnson a P-47 ace, in his book named Thuderbolt! Talks about this prop in some praise "Never again did a Focke Wulf FW190 or a Messerschmitt ME 109 outclimb me in the thunderbolt, the new prop was worth 1000 horsepower more and then some." Arguably his claim of the new prop being worth 1000 engine HP could even be accurate. Given he was flying a 2800+ engine HP plane with an overspun turbo and higher RPM engine, given the old prop's inneficiency in harnessing this power. The new prop on his plane could have performed like having a 1000 engine HP more with the old prop.

It´s a dtc app. It works. Use it. It´s good. Let´s all thank the guy who made it for us. Link attached. https://github.com/the-paid-actor/dcs-dtc/releases

The visual

We will have one tommorow. The playerneeds to wake up.

Just watch 84f851d3c05c84721b26b3d85a58357d.mp4 The visual

RWR / other viewport exports. I have a home cockpit and I need to export my RWR and some other cockpit panels to a screen to use the F16. I used to have this line in my RWR_ALR56_init.lua : dofile(LockOn_Options.common_script_path.."ViewportHandling.lua") try_find_assigned_viewport("F16_RWR") and then in my monitor config i used this: F16_RWR = { x = 3760; y = 1440; width = 480; height = 480; } This was also possible for the DED, PLFD. Everyone who has a home pit needs this functionality. Please let me know, do you also think it belongs here and needs to be a supported feature?

Hello Ed, due to the changes to cockpit script files during the last patch, my RWR export now breaks integrity check. I have a home cockpit and I need to export my RWR to use the F16. How do I do it now? I used to have this line in my RWR_ALR56_init.lua dofile(LockOn_Options.common_script_path.."ViewportHandling.lua") try_find_assigned_viewport("F16_RWR") and then in my monitor config F16_RWR = { x = 3760; y = 1440; width = 480; height = 480; } How do I export the RWR after this patch, without breaking integrity check?

E-TF[803] Saint F16-C

Im a competetive player bro. Dont tell me to get good I did.

PLS target size and RCS size modelling. PLS missiles which dont go off the rail dumb when I have a lock PLS missiles which have correct PK/R modelling. PLS a full fidelity missile native do DCS, 120 Bs and Cs are FC3 by all standards of virtual modelling. They aren´t full fidelity. We need a full fidelity misisle. Same goes for red force. PS: C7 PLS ?!?!?!? Its a block 50 viper and a block 20 hornet game. They are supposed to have propper missiles, especially since DCS is now moving forward now. And the reason why I am begging today is that I dont wake in 2022 with meteors phoenixes and SD10s being finished fully and debugged, and 120s are still FC3 missiles.