Wartortle

Hi Gary, There's an update to FSX:SE coming out on Monday along with a new version of FSUIPC (38c, I think). However, in the meantime, you can try the following: 1. Go to Control Panel, Programs & Features. 2. Uninstall any version of SimConnect with a version number of 10.0.62601 or greater. 3. In your steamapps folder, find the SimConnect.msi installer and run it manually. If you have UAC enabled, you will need to confirm the elevation prompts, etc. 4. Run FSX:SE as normal from Steam. Roc

Hi Pete, Firstly, hope you had a good Christmas! Secondly, thanks for the feedback - providing you the functions you need would make the most sense so I'll email you separately. Thanks, Roc

Hey Pete, Any thoughts on my point from earlier, please? Roc

Okay, thnx Pete. Are you able to build in some sort of detection at DLL load up time so that, for example, if FSUIPC is installed for 62607 it's okay. However, we supply a Steam patch which updates it to 62608 so that the next time FSX:SE is run, FSUIPC can check and detect the new version and then fallback to an inoperable/disabled state so that it doesn't crash the game? It'll be a nightmare from a support perspective if every time a new version of FSX:SE is released, it causes crashes for existing users. Open to options here, especially if there are things we can do to make your integration life easier! Roc

Hi Pete, I'm one of the Devs that's working on FSX:SE and I'd like to ask you a question about the detection method you've used for FSUIPC. Firstly, great job on getting it converted so quickly - it's really going to make a massive difference to the community to have this crucial piece of software working for them. My question is how you're detecting the version for FSX:SE. Specifically, the currently released version is 62607 - if this is incremented to 62608, will anything stop working with FSUIPC? Unlike previously (largely static) versions of FSX, the FSX:SE version is going to be updated on a regular basis with improvements, bug-fixes and so on. As you can imagine, keeping the version number the same for future releases will cause us various support problems but, equally, we don't want to break tools like FSUIPC when we release a new build. Would it be possible for you to detect versions >= 62607 as valid versions of FSX:SE? Roc