Jump to content
The simFlight Network Forums

John Dowson

Members
  • Posts

    13,437
  • Joined

  • Last visited

  • Days Won

    278

Everything posted by John Dowson

  1. This issue has been addressed, and hopefully fixed, in the latest release. The locations are different depending upon steam vs ms store install. For details, see Note that I will be posting there when I update the FSUIPC7-beta release.
  2. 0x0262 is for setting - its 0x0264 for reading. Please note that there are 3 different styles of 'pause' in MSFS: 1. Active pause (default key: PAUSE): this is more like a lat/long/alt freeze - it freezes the plane, but the world moves on. Be careful when using this! 2. Sim pause (default key: ESC): takes you to the MSFS menus. Not really a pause, more of a temporary stop! 3. The real pause (no default key): this is the proper pause and is activated by the Pause On and Pause Off controls (no toggle) The third one is the one to use. This pause mode also updates offset 0x0264 correctly. I've checked offset 0x0262, and that works for pausing/unpausing (with the real pause). For the time being, I'll mark offset 0264 as partially working, until we can get the pause state correctly from the other pause modes. John
  3. There are currently issues with the SimConnect functions to load/save files. Asobo are aware of this issue. There is also a problem in FSUIPC7 related to the location of such files, and currently they won't be removed correctly. I reported this here: John
  4. This problem didn't exist in the Alpha and Beta releases - it was introduced in the official release.... John
  5. Thanks for reporting, I'll update.
  6. Ok, glad its now working. This was mentioned in the release note, under 'Issues'. John
  7. Thanks for reporting this. Looks like the reading is ok via a simvar, but the setting via an event isn't working. I'll check it to see if its an issue with the event or an FSUIPC7 issue and get back to you. This may take a while though. John
  8. Well, that folder itself seems to be the 'default' location - this is where FSUIPC's auto-save files are saved. The ones from MSFS seem to go into different places under this folder, depending upon where you save from. Check under MISSIONS\Custom or MISSIONS\Custom\CustomFlight maybe.
  9. For Steam installations, the default flight plan folder seems to be under <USER>\AppData\Roaming\Microsoft Flight Simulator\
  10. There seem to be registry entries when MSFS is installed from the MS Store, but not when installed via Steam. And the different installations have different default paths for various files. Its all a bit confusing at the moment, and different to how things were located in the alpha/beta releases. Yes, sorry, that's correct. Offset 0x3308 is set by FSUIPC7 on start-up. Offset 0x3124 is set once connected to the sim.
  11. These are problems related to the MSFS SDK, not FSUIPC7. What works in the final version will also depend upon what is working in the SDK! Its due to the current state of the SDK that I have released FSUIPC7 as a beta, to hopefully track down such issues, report them to Asobo/Microsoft, and get them fixed. Cheers, John
  12. As mentioned in the 'Limitations' section of the release note, "actions" (usually called events or controls) related to view control (including the PAN * events) are currently not working in MSFS. For view control, you currently need to assign in MSFS. Are there any non-view control "actions" that don't work for you? John
  13. FSUIPC7 can handle up to 16 "joystick" (USB HID compliant) type devices. You can also have 16 devices per WideClient instance (for buttons & switches, not axes), running on separate PCs. John
  14. It looks like the arrow keys are not recognised by MSFS - they don't even appear in the MSFS list of 'Status of Input Events'. I will report this. Could you try to see if your key assignments work when FSUIPC7 has the focus? I just tried with elevator down/up and that seems to work. If all your assignments work when FSUIPC7 has the focus, then this means the events are working but the corresponding input events are not yet working. All you can do at the moment is to assign to different keys. You can also try activating logging for 'Buttons & keys' and 'Events', which should also show you when FSUIPC7 is receiving the key press and what it is doing with it. John
  15. I have a few GF devices (GFP8's, GFT8's & GFR48's) and they work just fine with the GFDev64.dll and FSUIPC7. John
  16. Hi Laurie, please download the latest version of FSUIPC7, released yesterday. It does not require the SimConnect.dll. John
  17. Did you read this thread? Or search for similar issues? As posted just before your post, please see
  18. There were registry entries in the beta version, which is what FSUIPC7 is currently using. However, it looks like these are no longer present in the released version, which is why FSUIPC7 now cannot determine the default location for flight files and plans. Many offsets won't be populated until MSFS is running and FSUIPC7 is connected. For example, you could check offset 0x3124 (FS version being used) or 0x3308 (FS version as determined by FSUIPC) which will be the first offsets written to when MSFS is detected. However, these offsets aren't currently cleared if MSFS closes. This is because usually you would have FSUIPC7 to auto-close with the FS, but I could clear these in the case that FSUIPC7 remains open if this helps. John
  19. You can try putting the dll in the Windows system folder (and reboot), but this really should be done by the SDK installer (and would then also require users of your software to also install the SDK!). The way to embed the dll is to use a static library. Seems like Asobo only provided a static library for unmanaged C/C++, maybe a static library for managed code will come later. I think for now, you should just include the SimConnect.dll along with your application. John
  20. Its on my list, I'll let you know once implemented. John
  21. Ok, glad that's now cleared-up. Thanks for reporting back. John
  22. It seems that the location for flights and flight plans has changed since the beta. This is causing issues with autosave, as well as flight loading/saving. There also seem to be issues in SimConnect in this area (the required functions are not documented as not or partially working). Also the FS installation location is no longer reported correctly, due to a change in the registry entries/values used, and also the different installation method used by Steam compared to the MS Store. I will investigate these issue. John
  23. I mean your "required" location, i.e. wherever you want to install it. It can go anywhere. If you have FSUIPC6, it will be in your installation folder. If you can't see the extensions, they are hidden from you and you will have to change the Explorer options to see the extensions. You can use the 'Open Folder' option in the FSUIPC6 logging tab, which will open an explorer window on your FSUIPC6 installation folder. Your FSUIPC6.ini file will be there. John
  24. I think it means v11.0: 8484 MSFS version = 11.0.282174.999 John
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use. Guidelines Privacy Policy We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.