312_JS

Still an issue. Definitely not just a visual thing. Especially when you FLY close to or over 1M, the nose moves from side to side.

Sorry to hear that. I really liked it (I know I might be in a minority).

Yes, you just have to install into the new MT directory.

Massive performance increase with the MT. Thanks a lot team!

Excellent, that did the trick. Thank you. I somehow missed this file. Hate that it's all scattered into so many files.

Thank you. No luck so far, I was able to find the DCS ID, but not the Button ID.

I'll try the Model Viewer, cheers. Your example is for the INS modes switch, I'm trying to figure our the HSI modes switch (DCS ID 1256, looking for the Button ID), which isn't in the luas. It's not always 3, I learned the hard way that if the Cmd is not three digits, you need to make it a three digits. For example if the Cmd is 78, you need to ad 30 in front, not just 3.

I see. Are you by any chance aware of any tutorials on how add a missing button to the luas, please? Mainly how to find out what the ID of the control is.

Have you had any luck finding the HSI NAV/R NAV Mode selector switch, please?

Looks like the issue was the ";" at the end of the pcall function. Without it it works flawless. So my Export.lua now is: dofile(lfs.writedir()..[[Scripts\DCS-ExportScript\ExportScript.lua]]) pcall(function() local dcsSr=require('lfs');dofile(dcsSr.writedir()..[[Mods\Services\DCS-SRS\Scripts\DCS-SimpleRadioStandalone.lua]]); end,nil)

Looks like the issue was the ";" at the end of the pcall function. Without it it works flawless. So my Export.lua now is: dofile(lfs.writedir()..[[Scripts\DCS-ExportScript\ExportScript.lua]]) pcall(function() local dcsSr=require('lfs');dofile(dcsSr.writedir()..[[Mods\Services\DCS-SRS\Scripts\DCS-SimpleRadioStandalone.lua]]); end,nil)

Hello. I can't seem to get the SRS working with ExportScripts. When the ExportScripts is in the Export.lua, SRS doesn't connect the Game plugs. The SRS Client still connects to an SRS server on a DCS server join, but only shows the Ctrl+Shift+ESC message after that. Any idea what might be wrong, please? These are my only lines in Export.lua. dofile(lfs.writedir()..[[Scripts\DCS-ExportScript\ExportScript.lua]]) pcall(function() local dcsSr=require('lfs'); dofile(dcsSr.writedir()..[[Mods\Services\DCS-SRS\Scripts\DCS-SimpleRadioStandalone.lua]]); end,nil);

Sadly no, the DCS-ExportScripts doesn't work unless it's the first and even if the SRS is first, it doesn't connect.

Hello. Any of you using SRS together with DCS-ExportScripts (Stream Deck), please? Enabling DCS-ExportScripts in export.lua makes my SRS to be unable to connect to the Game. Thanks a lot in advance!

So the question is whether it is possible to have three or more icons, not whether you can have three way switches. The solution, as far as I know is to have text instead of icons when you need more than two states.

Hello since the 2.7.10.19473 patch, that was supposed to add the "Ground crew is now heard with a closed canopy" feature, I am unable to do so. That's correct. I used to be able to until that patch, that was supposed to fix what was actually working for me. I've tried countless times (and took off naked countless times because I'm used to not opening the canopy). Any idea how that could happen and where the issue is, please?

Known issue, unless you ask the devs.

Which makes it unflyable since MSFF2 is not nearly as long as the real stick.

No solution yet. It's as intended according to Yo-Yo. I know of the Spitfire, P47 and Mosquito being affected. @Yo-Yo, you guys should decide if you want to force us to buy a real life length stick, so that we don't have to use the curves, or use regular joystics and add a Special Menu setting to turn off the axis offset/emulate a short stick. I'm sure you'd agree that these Special Menu settings are trivial to implement. Just last night my friend wasn't able to fly the Mosquito with us, because he only owns the MSFF2 and he either has to not use curves, which makes it silly to fly with a short stick, or not be able to trim the aircraft. Is it really working as intended? Yo-Yo's solution of 50% saturation (which obviously halves your max elevator deflection) is definitely not a good way of solving the issue. It may be fine if you are fast, since max deflection would give you black out anyway, but when you slow down, it's an unreasonable handicap for what has a trivial solution.

It's a known issue amongst players, but the devs claim it works as intended. It's the same for the Spitfire. It makes me mad, I had to buy a new joystick and my MSFF2 is gathering dust.

It's a known issue amongst players, but the devs claim it works as intended. It's the same for the Spitfire. It makes me mad, I had to buy a new joystick and my MSFF2 is gathering dust.

For some reason, your mission makes my GPU and CPU utilisation act strange. GPU is only on 40% and CPU on 10%, making only 20-30 FPS on the ground. No problems on other missions so far. Any ideas, please? EDIT: Looks like the culprit was the DCS ExportScript in Scripts folder.

What was your RPM? I found out it's the warning goes on on higher boost if your RPM is lowered.

+1 The same issue as on the Spitfire, which is still not corrected.