Jump to content
The simFlight Network Forums

wogapat

new Members
  • Posts

    3
  • Joined

  • Last visited

Profile Information

  • Gender
    Not Telling
  • Location
    UK

wogapat's Achievements

Newbie

Newbie (1/14)

  • First Post Rare
  • Conversation Starter Rare

Recent Badges

0

Reputation

  1. Thanks. No problems so far. Just re-installed (again) to a clean location and the problem seems to be corrected. The program is no longer in an admin protected directory and happily creating the .ini and .log file from the MSFS .xml start-up. Thanks for your help. I really appreciate you taking the time.
  2. Thanks. I'm not sure how that path ended up protected. One for me to try and figure out. Worked out last night that running the FSUIPC MSFS shortcut as admin seemed to pull it all together. At least now the .ini file exists and can be read. I'll stick to doing that, for now, until I can figure out what windows is doing. I have a standalone m.2 drive for MSFS. FSUIPC is installed in top-level directory there which shouldn't be protected like that. Now the .ini exists, and is being read even when I start up normally, I could just leave it and not get logs. I've had a few add-on crashes, though, which I think the .log file may help me narrow down. Thanks for your reply.
  3. FSUIPC v7.2.10v Windows 11 Version 21H2 I first noticed this issue when my key & button assignments wouldn't save. I have a registered version of FSUIPC. I looked through the forums and found references to the .ini and .log files, created when FSUIPC runs. I checked the installation directory and those files don't exist. I ran a search of my system. They definitely don't exist. After a little testing, I've managed to narrow it down to FSUIPC needing to be run as an administrator. When I run the .exe as an adminstrator the .ini and .log files are created. When I run MSFS, and start-up FSUIPC from the .xml, FSUIPC does not create the .ini and .log files. Hence why my assignments are not saving. Here is what I've tried: 1 - Setting the 'run as administrator' in the compatibility settings of the .exe properties. - FSUIPC fails to start with MSFS 2 - Creating a .manifest file to try and force it. - FSUIPC starts with MSFS but the manifest is ignored. 3 - Changing the security properties of the FSUIPC directory to give 'write' rights - I get all sorts of security permissions errors and the .log and .ini file are still not created. I appreciate this is more a system issue than an actual problem with FSUIPC but I can't seem to get around it. Any suggestions, please?
×
×
  • 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.