FORUM › Forums › Software › CLS2SIM Software › CLS2SIM Conflicting with another program that pulls telemetry?
- This topic has 1 reply, 1 voice, and was last updated 3 years, 10 months ago by moespeeds.
-
AuthorPosts
-
12/01/2021 at 00:59 #2248moespeedsParticipant
Hiya guys,
I have a CLS-E Stick and Rudder Pedals. I’ve been playing DCS with it, and everything has been working fine.
I recently added a Simxperience GS5 seat and Belt Tensioner. The software that drives these is called Sim Commander, and to pull the telemetry from DCS, I use a program called Space Monkey.
It seems the Space Monkey and CLS will block one or the other out, depending on how I order them in the export.lua. For whatever reason, whichever line I put before the other, that is the program that is blocked out. So with the CLS line first, it cannot connect to DCS, but pulls telemetry for spacemonkey just fine. If I put the spacemonkey line first, CLS connects to DCS, but spacemonkey cannot pull telemetry. No matter what I try, I cannot get both to work.
They are using different ports.
I also have the following error in the DCS log whether CLS is working or not:
2021-01-11 23:41:10.261 ERROR Lua::Config: Call error LuaExportStop:[string "C:\Users\moesp\Saved Games\DCS.openbeta\Scripts\Export_BEH_Motion_Cls.lua"]:133: attempt to index global 'c' (a nil value) stack traceback: [C]: ? [string "C:\Users\moesp\Saved Games\DCS.openbeta\Scripts\Export_BEH_Motion_Cls.lua"]:133: in function 'LuaExportStop' [string "C:\Users\moesp\Saved Games\DCS.openbeta\Scripts\ExportSM.lua"]:110: in function 'SimLuaExportStop' [string "C:\Users\moesp\Saved Games\DCS.openbeta\Scripts/SimShaker.lua"]:528: in function 'LuaExportStop' [string "C:\Users\moesp\Saved Games\DCS.openbeta\Scripts\SimShaker-export-core\ExportCore.lua"]:40: in function <[string "C:\Users\moesp\Saved Games\DCS.openbeta\Scripts\SimShaker-export-core\ExportCore.lua"]:34>.
I have hotplugging in DCS disabled, I have yet to try changing that.
Below is a photo of settings for both programs. Spacemonkey listens on UDP port 6666.
Any help in troubleshooting this is greatly appreciated.
TIA
Moe
NJ, USAAttachments:
You must be logged in to view attached files.12/01/2021 at 14:52 #2250moespeedsParticipantIs it possible to force CLS2SIM to use another port to communicate?
-
AuthorPosts
- You must be logged in to reply to this topic.