Toedde Posted February 13 Report Posted February 13 Hello John, since my update to 7.501 i have an issue with the FBW Remote Tool that comes with a myOffsets.txt file. It says that "The Server reported a problem: Any Uses the legacy LVAR Interface. This command is not supported." Any is the WebSocketsServer, right? Class Instance ID: 0 WebSockets Server: Info: Connected to: Any Connection via Wideclient.exe? : No FSUIPC Version 7.501 ws://localhost:2048/fsuipc/ Due to the 20 KB limitation i am unable to add the FSUIPC7.log Can you give me a hint where else to look to solve this error? Tia Thorsten FSUIPC7.ini myOffsets.txt
John Dowson Posted February 13 Report Posted February 13 2 minutes ago, Toedde said: Due to the 20 KB limitation i am unable to add the FSUIPC7.log Upload limits are restricted for new uses - your limit will increase the more you post. You can compress the file, but if still to large you will have to use one of the (free) file transfer services, such as https://filetransfer.io/. 5 minutes ago, Toedde said: Any is the WebSocketsServer, right? Class Instance ID: 0 WebSockets Server: Info: Connected to: Any Connection via Wideclient.exe? : No FSUIPC Version 7.501 ws://localhost:2048/fsuipc/ Sorry, but I have no idea what that is - are you actually using the WebSocketServer? Does the FBW Remote Tool use the WebSocketServer? 9 minutes ago, Toedde said: i have an issue with the FBW Remote Tool that comes with a myOffsets.txt file. It says that "The Server reported a problem: Any Uses the legacy LVAR Interface. This command is not supported." This is confusing...the myOffsets.txt file is for adding simvars to offsets, not lvars. And I have no idea what the "legacy LVAR Interface" is. As this is from the "FBW Remote Tool ", you should contact them to see what this means and what you need to do to correct this. Please post/update here if/when you have further information. John
Toedde Posted Monday at 09:51 AM Author Report Posted Monday at 09:51 AM Hello John, thank you for your support! I found the solution and what causes the issue. After FSUIPC starts from the EXE.xml the websocketserver connects not complete to the sim. So i stopped manually and restart it after the FBW was loaded and everything works well as it should. Thanks again for your assistance Thorsten
John Dowson Posted Monday at 09:59 AM Report Posted Monday at 09:59 AM 4 minutes ago, Toedde said: After FSUIPC starts from the EXE.xml the websocketserver connects not complete to the sim. So i stopped manually and restart it after the FBW was loaded and everything works well as it should. Ah, ok - that is interesting. Maybe the websocket server is expecting an FS version in offset 0x3308 when started, and that is now not populated until a simconnect connection is established. You could check if this is an issue by adding Init3308=13 to the [General] section of your FSUIPC7.ini file, which will initialise that offset on start-up. I could also delay the auto-start of the WebSocket server until a connection to MSFS is established, or until an aircraft is loaded? Maybe @Paul Henty could advise on this?
Paul Henty Posted Monday at 10:25 AM Report Posted Monday at 10:25 AM Quote Maybe the websocket server is expecting an FS version in offset 0x3308 when started, and that is now not populated until a simconnect connection is established. Yes, that's what's happening. The WebSocketServer uses my DLL and that gets the version information when the connection to FSUIPC is opened. Will 0x3308 be 0 before the SimConnection is made? I could check this in the socket server and retry until I get a proper version number. Paul
Toedde Posted Monday at 10:28 AM Author Report Posted Monday at 10:28 AM Works!!! After adding WebSocketServerAutoStart=Yes Init3308=13 below the Autostart option it connects correctly. Great work, thank you so much!!!!
John Dowson Posted Monday at 11:36 AM Report Posted Monday at 11:36 AM 1 hour ago, Paul Henty said: Will 0x3308 be 0 before the SimConnection is made? Yes 1 hour ago, Paul Henty said: I could check this in the socket server and retry until I get a proper version number. You could do that, but probably better if I delay the auto-start of the WebSocketServer until FSUIPC is connected to MSFS. Your update would also help if/when the WebSocketServer is manually started before MSFS is running, but I could also disable the manual start until MSFS is available. 1 hour ago, Toedde said: Works!!! After adding WebSocketServerAutoStart=Yes Init3308=13 Great - thanks for the confirmation. Note that you should set a value of 14 if/when using MSFS2024! John
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now