Jump to content
The simFlight Network Forums

John Dowson

Members
  • Posts

    13,216
  • Joined

  • Last visited

  • Days Won

    270

Everything posted by John Dowson

  1. I'm pretty sure the latest installer is ok. However, there was an earlier version of the beta installer that did not correctly insert a registry entry with the documents location. Could you try the following please: - uninstall FSUIPC7 by double-clicking the uninstallFSUIPC7.exe (located in your installation folder). Also manually remove any documents or document folders for FSUIPC7 if any are left behind - re-install using the latest installer Then check everything is installed in the correct place. If not, post me your InstallFSUIPC7.log John
  2. Yes of course, sorry. I don't understand why the installer is finding this file under C:\Users\David\AppData\Roaming\Microsoft Flight Simulator\UserCfg..opt - this check is returning true for you for some reason: IfFileExists "$APPDATA\Microsoft Flight Simulator\UserCfg.opt" steamInstall So its installing a steam-install bat. Very strange....
  3. You could try Everything - its a very useful little utility for finding files. I'd like to know what's happening so I could maybe improve the installer. For the time being, if you re-install you will have to edit the .bat file each time as it will be removed and re-written.
  4. Ok. But what is the location of your UserOpt.cfg file? Do you have them in both locations?
  5. All versions should do that! Are you saying that the latest installer puts them directly in your C drive, rather than in the documents folder? It shouldn't....if thats the case, can you show me you InstallFSUIPC7.log file please? John
  6. Hi Martin, No, sorry - you need to contact SimMarket. They handle all sales. John
  7. As Pete identified, the installer thinks you are running a steam version. However, FSUIPC7 itself knows you are using an MS Store version (that's why I needed your FSUIPC7.log file!). The installer determine the installation type by the location of your MSFS UserOpt.cfg file. It first checks in the steam location, which is (for you) C:\Users\David\AppData\Roaming\Microsoft Flight Simulator\UserOpt.cfg Do you have such a file? For MSFS installs, it should be (for you): C:\Users\David\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\UserCfg.opt The latter is the one FSUIPC7 uses, so I don't understand why the installer finds the first (or what it is doing there). Did you maybe buy the steam version, return it, then buy the MS Store version instead?
  8. No problem if you want to manually move the documentation. However, they won't be removed when you run the uninstaller so you'll have to remove them manually. And when you install an update it will re-install the documents in the Documents folder again (in a folder labeled FSUIPC7) unless you uncheck that option.
  9. Did you read the section on 'Limitations' in the provided README.txt. If not, please do so. Key press commands do work when MSFS has the focus, but the keys received by FSUIPC7 are limited due to issues with the MSFS SDK. Hopefully things will improve in subsequent releases - current release is still 0.7.0.0. Not sure I understand what you are saying here (I'm not familiar with USBKEYS opencockpit) - how is FSUIPC involved? What is the issue with FSUIPC. If the "commands generated by USBKEYS opencockpit are not recognized" (by MSFS I presume), then isn't that an issue with USBKEYS opencockpit? Note also that there are known issues with many controls/events currently not working, again due to issues with the SDK.
  10. Sorry, what does this mean? What do you actually see when you click the Register button?
  11. Maybe also try right clicking the link and running as administrator?
  12. What does this mean? The hot key has nothing to do with the web socket server. You should not start that unless you intend to use it. The bat file looks fine. Could you right-click on the link you use to start MSFS (if you use one), and let me know what the URL is (in Web Document tab). It should match the one in the bat file: start "" steam://rungameid/1250410 If it matches, I've no idea why it isn't working. If it doesn't, edit the bit in bold (in your bat file) and replace with the URL. And btw, I asked for your FSUIPC7.log file, not your InstallFSUIPC7.log file.
  13. Hi Marc, could you try one thing please. Delete all the parameters in the [General] section of your ini and let that get rebuilt the next time FSUIPC7 runs. You have a lot in there not applicable anymore. The empty line is strange. I'll do some further tests when I get a chance. For now, if cleaning your ini doesn't help, just turn on the Exit with FS option and restart with MSFS (or use the provided link/bat file).
  14. Sorry, what is Alt+7 supposed to do? What do you mean by "nothing appends"? As I previously said, the hot key to display FSUIPC7 is Alt+F. You can also access via the icon in the system tray. Please read the provided README.txt file and User manual. So it looks like its not starting MSFS, but starting FSUIPC7. Your last image shows FSUIPC7 but expanded to fit the entire screen. The black box is nothing to worry about - that's just the command window that the bat is running (which is hidden when you use the link) Not sure why its not starting MSFS for you. Could you attach your MSFSwithFSUIPC.bat file please, together with your FSUIPC7.log file and I'll take a look.
  15. It will be a false positive. You can ignore (or report it). Someone also reported that Malwarebytes also reports a trojan in the zip.
  16. @IanAbel Thanks. Topic closed.
  17. Its Alt + F (not 7). If its running, you should see an icon in the system tray (maybe hidden). Did you see the FSUIPC splash screen at all? Steam main screen? Does it start MSFS? You should see an MSFS splash screen for 30 seconds or so, then the MSFS window should appear. The FSUIPC splash screen should appear after two minutes, then sit in your system tray. Can you tell me what you see please? If the created link doesn't start it, can you try: - running the MSFSwithFSUIPC7.bat file directly (from you FSUIPC7 installation folder) - starting MSFS manually, then running the FSUIPC7.exe
  18. Maybe ask them?
  19. I don't know - you need to ask PMDG. In FSUIPC we just provide access to the data they provide. John
  20. As I said, you should try the LINDA support and forums. The A320 is a popular add-on and I'm sure many people use this with FSUIPC/LINDA without issues. I just can't help you with issues involving LINDA as I don't use this. John Later: also check that your controllers are off in P3D. You have this in your attached log: But that may be due to the old version where this was incorrectly reported.
  21. Hi Jean-Luc, first, your FSUIPC6 is quite out of date - I can only support the latest version is which is 6.0.10. You can download from www.fsuipc.com or the Downloads -< Updated Modules section of this forum. I think you also need to update your LINDA installation as I believe you need 3.2.6 for P3Dv5. If you still get errors after you update, you should initially try the LINDA forums & support as I can really help with LINDA. John P.S. 24KB is a very small file and doesn't really need zipping!
  22. In about 40 minutes....hopefully!
  23. You need to download the latest key file. Already many posts about this unfortunately. I do publish the information - it is (was now!) a beta, and as such you should try to follow the announcements on each release as to what to do. Once released, (and out of beta) this won't be an issue..... The key file you need is on the FSUIPC7-beta announcements page: John
  24. There is no key file valid until 3rd November. 3rd November is the build date of the FSUIPC7 version, not the expiry of the license.
  25. You shouldn't do that. It will create problems and a mismatch between your installation location and your registry settings, and the uninstaller won't work. If you want to change the directory name, simply re-install to a new folder, then move any required files across ()e.g. .ini, key), and then remove the old folder. Ah, so you did re-install? Ok, I'll add quotes around the start command, although should be: start "" "F:\MSFS2020\Community\0AA - FSUIPC7\FSUIPC7.exe" Can you try that please. Remove the splash screen, or just the animated dots? I've added this as when you start MSFS you see nothing for around 30 seconds before the MSFS screen is displayed. You can edit to remove the splash or the animated dots, to suite your needs. 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.