Set by the GDPR Cookie Consent plugin, this cookie is used to record the user consent for the cookies in the "Analytics" category. Set by the GDPR Cookie Consent plugin, this cookie is used to record the user consent for the cookies in the "Advertisement" category. This cookie is used for authentication and for secure log-in. These cookies ensure basic functionalities and security features of the website, anonymously. i.Necessary cookies are absolutely essential for the website to function properly. The only direct "hacks" into FSX or P3D are those listed in the Log file from FSUIPC, near the beginning. That was and remains the main purpose of SimConnect. FSUIPC uses standard controls supported by SimConnect, 100% The same goes for 99% of the rest of what it does. No, not for any controls, axis or otherwise. If my understanding is correct (I have asm/C++ background) FSUIPC simply reads locations in memory of FSX/P3D. Now regarding offsets - Pete will be able to explain more, but offsets can easily get broken by new versions of P3D. Steve, can you give details of exactly which version of FSUIPC you are testing P3Dv3 with (For Pete's sake! ) Clearly the basic offsets still work (those which give out pitch/roll/alt), for otherwise, prosim instruments would indicate that there's a problem. Another example where it will all fall apart is if P3D becomes 64bit, etc.Īnyway, long story short - Offsets can indeed be broken by new p3d version. It's really a hack software is allowed to do when it's reading process memory. If that's the case - they are not documented and wouldn't be supported by the developer. Those locations contain variables which which store certain information (pitch/roll/ligts etc). Then try the other way (No FSUIPC, P3D only). Try to disable controllers altogether in P3D controls section and set rudder via FSUIPC and see what happens. I doubt that rudder problem has anything todo with FSUIPC. Now, Steve - try to isolate your problem. In my particular setup - only trouble I had was with Axis, not offsets - so easier to overcome. Regardless, I found it perfectly viable at the moment as long as user is prepared to resolve some technicalities. V3 is yet far from being the "holy grail"
0 kommentar(er)
