WebMaximus

I hear you, seems there is never enough of time is it 🙂 Speaking of it, time to enjoy some flying using your brilliant software where I now have a perfectly working flaps lever rather than messing around with boring xml files 😅 Thanks again for all your help John, really appreciated!

Ah, I clearly need to open my eyes. Didn't spot that last line with no line feeds but everything on a single line. Is there a particular reason why you put it in there like that? Rather than using the "normal" format used by other add-ons. Good to know the encoding is OK 👍

That's interesting indeed why the encoding was set to UTF-8 BOM. Since I certainly never went into the Encoding menu in Notepad++ for this file before, it must be one of the other programs who modified the file. Either way, I've now changed the encoding as you suggested and even when I already had it working fine as you know, I of course wanted to try it out 🙂 So, I started removing the manually added FSUIPC entry to make sure my EXE.xml was clean from FSUIPC related entries. I then ran the setup file which told me the existing version needed to be uninstalled. As expected. This time, the uninstallation went fine without ending up in that loop I had before. A good sign! I then ran through the installation with all default options which went fine. However...when checking EXE.xml after the installation where I of course thought I would now find an entry to FSUIPC, I didn't. Checking the log file (attached), it this time tells me EXE.xml indeed was updated. Which I can also see looking at the time stamp of the file. Which makes it very confusing why I didn't see an entry for FSUIPC in there or what am I missing here 🤔 Opening EXE.xml in Notepad++ again and checking under the Encoding menu, I now see how it's no longer set to UTF-8 which I earlier converted it to and saved the file. Instead, it's showing me this: InstallFSUIPC7.log

Certainly no rush over here having it fixed since it's easy enough to do it manually 👍

Just let me know if I can be of any help 👍 Might also mention the uninstall ended up in a never ending loop I had to kill via Task Manager. Maybe related if it tries removing the entry from EXE.xlm it thinks is in there.

Ah, got it. I've attached the file here but again, no big deal since I already have it working after adding FSUIPC myself. Brilliant with the discount, will get a new license right now 👍 Enjoy the rest of your weekend John and great to see you're still around in the FS community after all these years 🙂 EXE.xml

Working like a charm 👏 Thanks you so much @John Dowson for your help and your excellent piece of software 👍 So, time to buy my registration code 🙂 I've bought older versions of FSUIPC in the past (version 4 and 5 as I recall it). Is there some form of discount before I go ahead and buy a license for this latest version of FSUIPC?

You were right as seen here from the log file. I'm still surprised since it's working just fine after I added it manually to EXE.xml and I have other things in EXE.xml as well where I had no issues having those added in there automatically during the installation of those addons. Such as Couatl for GSX, some Aerosoft stuff etc. So not sure why FSUIPC doesn't like my EXE.xml file 🤔 Or...it does like it, it just doesn't like to be added automatically 😉 Adding FSUIPC7 auto-start for MSFS2024 via the MSFS EXE.xml. Updating EXE.XML for MSFS2024 MS Store install Error loading EXE.xml file: C:\Users\richa\AppData\Local\Packages\Microsoft.Limitless_8wekyb3d8bbwe\LocalCache\EXE.xml **** Auto-start of FSUIPC7 with MSFS2024 will not be enabled **** **** To resolve, remove or rename this file and re-install: C:\Users\richa\AppData\Local\Packages\Microsoft.Limitless_8wekyb3d8bbwe\LocalCache\EXE.xml****

Thanks John, that was quick and now it looks much better 🙂 One thing though I wanted to mention is how my EXE.xml (for MSFS2024) wasn't updated even when I had that checked during the installation. Which as you know is also the recommended and default value for that setting. To have FSUIPC start automatically with MSFS2024. Not sure if it could be related to me having both MSFS and MSFS2020 installed? During the installation, I picked only MSFS2024 since that is the one where I need some help from FSUIPC it appears. No big deal though, I can add it to EXE.xml myself but still wanted to point this out to you.

Hey @John Dowson Thought I would try and play around with this over the weekend but looks like the trial license downloaded from the post you're referring to already expired? I don't get the assignments menu option and when clicking Help-About it confirms the registration expired.

Brilliant, many thanks John for your reply. Will try what you suggest. I have been using FSUIPC in the past (like you, I've been in this FS playground for many, many years now) so I'm not new to FSUIPC but I suppose I will have to invest some time remembering how all is done 🙂

I just moved to MSFS2024 and do all my flying in the iFly 737 MAX8 using a Honeycomb Bravo TQ where I've added a 737 throttle set from Flight Sim Factory to make it a bit more realistic. In MSFS2020, I was able to calibrate the flaps axis to match the flaps in the aircraft but now in MSFS2024 where the calibration options changed a bit, I'm struggling to match the hardware flaps lever with the software one (the one seen in virtual cockpit). Now I'm wondering if maybe FSUIPC could help me achieve what I'm looking for, to calibrate the flaps axis to match the hardware flaps positions with the flaps positions in the aircraft. Anyone had any success doing this with FSUIPC or maybe you have some other tips how to accomplish this? Another option might be using SPAD.next which I've played around with in the past but I always found it to be rather complicated and would prefer finding an easier way doing this if possible. This is what my HC Bravo looks like with the 737 throttle set installed with the predefined flaps positions.

OK, thanks for the quick reply. Haven't had the chance to install the NGX in P3Dv4 yet but hope I will the next coming days being able to do some testing. I read someone said it was a bit better in P3Dv4 vs in P3Dv3 so no reason to start messing around with hex editors unless absolutely necessary. About LM and posting in their support forum I'm not really sure what to say in such a post to make them understand what I'm talking about since I barely understand this myself :D

Being late to this party I just wanted to ask what the current status is? I just got P3Dv4 and realized I'll need to buy FSUIPC5 but will I then be able to use the DynamicFriction.lua I've been using in P3Dv3 for the PMDG NGX? I also found this thread where people seem to fix this themselves by editing a dll file. It's starting with this post.

Ah, got it. Many thanks for the clarification Pete!