Help understanding what might be the issue

JG7XMAN
Posts: 4
Joined: Fri Apr 12, 2019 1:48 am

Help understanding what might be the issue

Postby JG7XMAN » Mon May 04, 2020 8:20 pm

I posted this on HiFi's forum:
___________________________________
Hey guys! Question:
  • The Simconnect.xml that is in the HiFi\AS_P3Dv4\SimConnectFiles has this encoding in its header: <?xml version="1.0" encoding="Windows-1252"?>
  • The Simconnect.xml that is in the Prepar3D v4 SDK\config\SimConnect has this encoding in its header: <?xml version="1.0" encoding="UTF-8"?>
The issue here that I use OpusFSI for head-tracking (it's weather function is turned off) and it requires the <?xml version="1.0" encoding="UTF-8"?> version to work.

I run ASN P3DV4 in NETWORK mode and it doesn't connect with the sim unless I use the .xml file that is in the SimConnectFiles folder with the "Windows-1252" encoding. However, I loose functionality of OpusFSI's TrackIR limits (which keeps my eye-point inside the defined space - i.e. the cockpit). Note: I regain OpusFSI's TrackIR limits functionality when I revert back to the "UTF-8" simconnect version P3D endorsed.

Can you please make use of the standard one P3D issued please?
__________________________________________

Can someone explain why this would cause issues? Please assume you are talking to a 5 yr old :)

JG7XMAN
Posts: 4
Joined: Fri Apr 12, 2019 1:48 am

Re: Help understanding what might be the issue

Postby JG7XMAN » Tue May 05, 2020 6:24 pm

A fix suggested by on th the techs at HiFi solved my issue.
Apparently, the simconnect.xml and dll.xml files must have the same encoding - in my case UTF-8. Some applications apparently require the dll.xml to be one or the other to function correctly.

Does anyone know why?


Return to “SimConnect Interface Questions”

Who is online

Users browsing this forum: No registered users and 25 guests