Crash to desktop after adding Export.lua settings for SimAppPro Dynamic Vibration Sync

[SomeCallMeTim]

I've just received my new F15EX throttle handles and want to get the vibration working in DCS but every time I add the lines 

local wwtlfs=require('lfs')
dofile(wwtlfs.writedir()..'Scripts/wwt/wwtExport.lua')

to the export.lua file DCS crashes when loading into a mission. I've had the Orion 2 throttle base and F18 stick for a while and I had the same issue trying to enable the button lighting sync when I first got it. I even raised a support ticket with WinWing over a year got for this but I never got an answer so I just stopped using the sync feature but now I'd really like to get the throttle vibration working. 

Repairing the export.lua file via SimAppPro correctly adds the lines and the wwt directory along with it's lua files but DCS crashes every time even when the SimAppPro lines are the only ones in the export.lua file. And if I clear out the export.lua file DCS works fine again. It also makes no difference whether SimAppPro is open or not.

I'm running the latest DCS beta standalone version BTW.

I'll raise another ticket with WinWing but in the mean time does anyone have any ideas?

[speed-of-heat]

does the file ..Scripts/wwt/wwtExport.lua exist?

[prestonflying]

Hey, try attaching your log files from your Saved Games/Logs/dcs.log when you notice the crash. Might be some clues in there

[SomeCallMeTim]

The wwt directory gets created fine along with both lua files. The log file bellow shows an access violation but I've come up short searching for that particular code.

# -------------- 20230919-134752 --------------
DCS/2.8.8.43704 (x86_64; MT; Windows NT 10.0.22000)
G:\Games\DCS World\bin-mt\edCore.dll
# C0000005 ACCESS_VIOLATION at 00007ffff5f55db3 00:00000000
SymInit: Symbol-SearchPath: 'G:\Games\DCS World\bin-mt;', symOptions: 532, UserName: 'Arty'
OS-Version: 10.0.22000 () 0x100-0x1
0x0000000000005db3 (edCore): setClipboardText + 0x3C3
0x000000000006fc15 (edCore): Lua::CheckedLoader::loadFile + 0x4E5
0x00000000000702d9 (edCore): Lua::CheckedLoader::tryLoadFile + 0x9
0x000000000098b31a (DCS): SW + 0x4F4F6A
0x0000000000899d38 (DCS): SW + 0x403988
0x000000000089ba17 (DCS): SW + 0x405667
0x000000000087746b (DCS): SW + 0x3E10BB
0x000000000009a0aa (edCore): Common::FSM::sendOutputSymbol_ + 0x2A
0x0000000000099a12 (edCore): Common::FSM::enterToState_ + 0xC2
0x0000000000099f4b (edCore): Common::FSM::onSymbol_ + 0x1FB
0x00000000008993b6 (DCS): SW + 0x403006
0x0000000000857f24 (DCS): SW + 0x3C1B74
0x0000000000858e02 (DCS): SW + 0x3C2A52
0x000000000270adb0 (DCS): AmdPowerXpressRequestHighPerformance + 0x135CDAC
0x0000000000c5a782 (DCS): SW + 0x7C43D2
0x00000000000153e0 (KERNEL32): BaseThreadInitThunk + 0x10
 

I've tried AV and FW off, adding AV and FW exclusions but no difference and it's the same with both 32 and 64bit DCS. I've got a ticket raised with WinWing and they are going to give me some remote help so we'll see what they come up with. 

[prestonflying]

This looks unrelated to the wwtExport.lua file SimApp Pro uses to power the F15EX shaking

I would try the following:

1. Remove all Export.lua entries, either comment out like -- dofile, or rename the file for testing so it is not loading the export lua functions.
2. Load into a standard instant action mission

This will most likely work, then re-enable the wwtExport lua line entry in Export.lua, I suspect this will also work. This would indicate an issue with something else, most likely a mod or another lua file.

And the whole log file would be great also, there is more information like which Export lua files are being loaded and might give a hint. The call stack shown appears to be related to setting clipboard text, perhaps from another mod or a custom mission.

Best of luck, and report back with any findings

[SomeCallMeTim]

1. Remove all Export.lua entries, either comment out like -- dofile, or rename the file for testing so it is not loading the export lua functions.
2. Load into a standard instant action mission

Already tried that. It only crashes if I have the SimAppPro entries in the export.lua file, even when on their own. I normally have other entries in export.lua and they have always worked fine. I also did a DCS update cleanup  and that made no difference either. What I haven't done yet trying it with a clean Saved Games\DCS.openbeta directory, i.e. no mods etc at all. WinWing haven't found an answer yet either but they are gibing me some remote assistance tomorrow to try to get to the bottom of it. 

 

In the mean time here is an error log:- 

dcs.log-20230919-134752.zip

[SomeCallMeTim]

I've just tried it after cleaning both the DCS directory and the Saved Games\DCS.openbeta directory and still get the same crash  so it's got to be something very weird.

[SomeCallMeTim]

I finally managed to solve the problem and yes it was a bit weird. 

I turned off all unneeded app and services and found DCS no longer crashes with the SimAPppPro settings in export.lua.

Turns out it the culprit was NordVPN and If I simply pause the VPN connection it works fine. Interestingly even if I add DCS.exe and SimAppPro.exe to the NordVPN split tunnelling list to bypass the VPN it still crashes. Pretty odd as no other program I have has an issue with the VPN and I just bypass with split tunnelling it if required

At least now I can get on with mapping the many many buttons on the F15EX throttle handles