Se1ko

I'm not saying remove IC checks, I am saying make tools for server admins that allow them to have more specific control, rather than the somewhat clumsy feature they have now, which is like using a chainsaw to slice cheese. For example; Hoggit are saying they have enabled pure scripts because there is a weapons cheat happening that is crashing their servers. Ok, fair enough, no one wants that. The problem (in as much as I understand it) is that the weapons cheat is in no way related to scripts used for cockpit display exports but anyone that has edited a script to simply display an MFD to another display in their simpit are now also kicked off for having an impure script. The only tool admins have is to either enable pure scripts or not. It doesn't allow them to look at subsets of scripts, or stop people tampering with a weapons based script, or allow the guy with a MFD viewport export that's doing the right thing to use his script while stopping the specific problem. Its either all vanilla DCS or nothing. That's what makes it clumsy, especially when you consider that DCS is very well known and regarded not in part due to its legitimate modding community. I agree with your comment on being able to break out controls and displays as a function of the game being made available. A certain other military flight sim has done it quite successfully.

Oh yes, I have been on the receiving end of people that cheat, its not fun for anyone and I applaud ED in trying to do something about it. The problem, as stated above, is that if a server wants to try and stop cheating it has to use a function of three available options that is too broad a brushstroke of script protection that denies the server to legitimate users.

That's fantastic if you have a MIP or UFC, not much help if you have a more homebrew simpit.

That is the problem. ED have not provided any server admin tools that would cater for such a need and don't seemingly have any plan to provide any. The three IC checks are so broad that in order to fix a specific problem you deny a great many other genuine users of the server that cause no harm. Have a read of Hoggits forums as a case in point.

ED, and yourself, are rather cagey when when explaining what this need is. Why is that? Why does it seem to be a big secret (beyond not wanting to share how to exploit the script file to cheat, which I can understand)? There must be a great deal many people that export views for MFD's to other screens that have don't have any ideas of trying to exploit or cheat DCS, why seemingly create a situation where you are hobbling modders that just want to get more out of the game legitimately and taken the time to do it? They are a loyal fan base of your product. Furthermore, why is this pure scripts thing so wide ranging and broad that it affects tools like Viacom, or creating export viewports? Can you not have a more targeted approach to integrity checking that looks at stopping people exploiting specific scripts that do affect gameplay as opposed to enforcing an IC that you can barely make a even a simple mod to make your life easier? As one user suggested, why not have server script tools to target specific scripts? If one was to take a cynical view, it would seemingly appear that ED are locking people out of modding in an attempt to in the future steer users to products such as export apps and MIPS that they may gain profit through partnership with....... Happy to be proven wrong (and without the mantra of "you can run a repair and ask the server admin to turn the pure script off")

First up, I do realise that sim bug fixing is a slow and painful process, however, is there any news about a fix for this at all? As someone that exports displays to a touchscreen, the pure clients thing really sours the experience. Hoggit now have "Pure Scripts" enforced (and I know that it is likely for good reasons) but surely exporting screen displays is not something that can cause an issue??? I liked that with DCS we have had the ability to create our own sim pits and make the game as realistic as possible with what resources we have.

Oh agreed, it is not an acceptable work around, but it is a beta and I am glad to be able to keep playing DCS until this is resolved. I am just wanting to add my issue to illustrate that its not an isolated problem. I am sure ED will hear a lot more of this as users that rely on display extraction to run expensive complex sim pits will have plenty to say about it:)

I run Helios and use its export function to display MFDs to a touchscreen. Nothing untoward. When I start up DCS and select a multiplayer server (in this case Hoggit GAW, which has the "Require Pure Scripts" function disabled) I will initially pass the integrity check and be able to join the server and have the exports running. However when I leave the server and go back to the Multiplayer screen I now find that I do not pass the integrity check with any server that requires it, despite having passed when I initially started the game and selected Multiplayer. If I exit out of DCS completely and restart the game again I find that I again pass the integrity checks with all severs again. So does this mean people exporting displays now have to bomb out of DCS each and every time they want to join/leave a server?

I'm not trying to stir up trouble, but as a thought: ED would have derived their version of the F16 radar perfomance from some sort of documentation that must be in the public domain? If this is so, why not release that documentation so that it can be reviewed? In commercial real world full flight simulation (level D) both customer and manufacturer would have validated flight test data of the actual aircraft performance which forms the basis of how the simulation behaves (which is checked by a series of tests known as QTGs (quality test guides))l. If an aspect of the simulation is called into question then the test flight data would be the reference point or standard by which any dispute can be argued objectively (raw data) rather than subjectively (end users opinion)? Like I said just a thought.....

Ok then, so what are these lines for in the CMDS_ALE47 LUA file?: -- Auto presets -- Threat type 1 programs[ProgramNames.AUTO_1] = { chaff = { burstQty = 1, burstIntv = 0.02, salvoQty = 4, salvoIntv = 1.5, }, flare = { burstQty = 0, burstIntv = 0, salvoQty = 0, salvoIntv = 0, }, } -- Threat type 2 programs[ProgramNames.AUTO_2] = { chaff = { burstQty = 1, burstIntv = 0.02, salvoQty = 6, salvoIntv = 1, }, flare = { burstQty = 0, burstIntv = 0, salvoQty = 0, salvoIntv = 0, }, } -- Threat type 3 programs[ProgramNames.AUTO_3] = { chaff = { burstQty = 1, burstIntv = 0.02, salvoQty = 8, salvoIntv = 0.5, }, flare = { burstQty = 0, burstIntv = 0, salvoQty = 0, salvoIntv = 0, }, }