312_JS

Hello @Bailey, parts of the F1EE lua stopped working since the recent large F1 patch. For example the functions in the DCS ID 80xx range - exporting speed, waypoint distance and bearing, RPM, etc. They don't even show up in the DCS Comms list in the Stream Deck app. Any idea what might have gone wrong? The basic DCS IDs with which these functions work with seem to export as expected.

I have the same issue in 2D. I can have almost everything maxed out and have around 100 FPS unless I am on deck. Then I get 27 FPS. Found out it's the Terrain Texture set to HIGH that's causing it for me. When I set it to LOW, with otherwise the same settings, I'm at 90 FPS on deck.

Mine? I've been flying MP with it for ages. Last time I tried it was a couple of years ago though.

Yes. I don't know what to teach you. Just do it the same way I did. I don't believe I did anything special to make it MP friendly. :)

I'm so glad you decided to give us the option to keep the louder sound. I instantly liked it when it arrived the last patch. Cheers!

Still a thing. ruddershake.trk

I never had an issue with any of the Spitfire reticles I made. https://www.digitalcombatsimulator.com/en/files/2448553/ https://www.digitalcombatsimulator.com/en/files/3309745/

Added the link, I hope. :)

Will do! Cheers.

First public version of my Mirage F1EE profile. https://www.digitalcombatsimulator.com/en/files/3330054/ Thanks to @Bailey & @jonny415, I stole some of your work.

Same here. Trains also stutter by the way.

No matter how much I try, I am unable to set the nose wheel steering to high sensitivity after I've turned the nose wheel steering to OFF (and then back to ON). It just stays on low sensitivity regardless on the switch position.

Yes, that would agree with my experience. But there has to be another factor. I had several very fast flights on deck yesterday and haven't felt any rudder shake.

I'll try to record a track, but they get corrupted for me almost every time. Here's a short video though. Never mind my friend's cursing.

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)