Fly through dangerous parts of the world, and risk the safety of your plane, crew, or passengers!. Keep detailed logs and statistics for every flight you make (great for virtual airlines). Maintain your aircraft in good condition, otherwise you may experience unique and suprising failures. Manage an airline (make money, manage aircraft fleets, etc). Make money for successful flights be fined if you do something wrong. Provide in-flight passenger services such as movies, music, and drinks. Hear them scream if you make drastic mistakes, and get their opinion of your flight in real time. Passengers react to how you fly your plane. Add passengers to your flights! Finally, you're not alone in the sky. I'm a bit baffled in that I read comments elsewhere that seem to imply that having the different versions of SimConnect.msi on a user's system and installing them somehow makes this problem go away. It may not work with an FSX-A or earlier simulator. I am okay with this, since a binary compiled with 9 will work in FSXA and FSX-SE, but be careful if you start to use the 7 library and dll. No error is returned, the values simply don't change. 
In particular, SetDataOnSimObject will not change the value in a fuel tank or a payload station. But some of the vital functions do not actually work. One would hope that a simconnect 62607 would be backwards compatible with a 61259 server.įield research indicates that it does connect without an error message, and no error returns are received in response to any SimConnect calls. A program compiled with a 61259 (FSXA) will connect to a 62607 (SE) server. This is how it's working on my system and so far, so good.
Fspassengers x sp2 not installed install#
7.0.Ī normal user machine that has FSX-A installed and running will normally have 61259 of the dll installed then installing FSX-SE will also install 62607, and so clients can connect to either one depending on which simconnect.lib they have compiled into their binary. My understanding is that each separate version of SimConnect uses a separate simconnect.lib, and that is revision-locked to the SimConnect.dll that's installed on the user machine which actually makes the connection and passes requests and data back and forth between the client and server inside FSX. I may be making some error in not knowing the ins and outs of it and that may be causing me undue trouble. Please correct me if I state something wrong here in my understanding of how SimConnect works.
I've adapted FSCaptain to handle the Steam Edition, but in order to do that I had to compile versions of the binary with a 9 version of simconnect.lib and simconnect.h.
I posted on the 'Steam Compatibility' thread in General Chat but figured I'd bring further discussion here since this is very technical and only concerns SimConnect.
Questions about SimConnect can be posted in the SimConnect forum.Īny other question that is not specific to an aspect of development or tool can be posted in the General chat forum.īy following these guidelines we make sure that the forums remain easy to read for everybody and also that the right people can find your post to answer it. Questions about terrain design can be posted in the FS2020 terrain design forum. Once airport development tools have been updated for FS2020 you can post tool speciifc questions in the subforums of those tools as well of course. Questions about airport design can be posted in the FS2020 airport design forum. Questions about aircraft design can be posted in the Aircraft design forum. Either post them in the subforum of the modelling tool you use or in the general forum if they are general. Questions about making 3D assets can be posted in the 3D asset design forum. Tag FS2020 specific questions with the MSFS2020 tag. So therefore we would like to ask you all to use the following guidelines when posting your questions: But having all questions about FS2020 in one forum becomes a bit messy. Which the release of FS2020 we see an explosition of activity on the forun and of course we are very happy to see this.
0 kommentar(er)
