John Dowson

Strange...you should be able to attach files, not sure whats going on there... Ok, no problem. Hmmm...I don't understand how a restart with no other changes can change things... Ok. If your issue re-appears, try attaching the requested files again and I'll take a look.

Ok, glad its now working, and thanks for reporting back on how you configured this. John

Ok. But I didn't need to see your bat file - I know what is in it! I was just suggesting that you could open it and play around with the command that starts MSFS (including removing the FastLaunch option) to see if you can get it to work. The command is at line 7: cmd.exe /C start shell:AppsFolder\Microsoft.FlightSimulator_8wekyb3d8bbwe!App -FastLaunch Its the same for every MS Store user. This command uses your user AppsFolder settings, which may be the issue. I don't think uninstalling and re-installing FSUIPC7 is going to help. John

Was just looking at this but Pete beat me to it... No, that's the type of the value being written:

Right-click on the MSFSwithFSUIPC7.bat file, located in your FSUIPC7 installation folder (i.e. not the link on your desktop) in windows explorer, an select 'Edit' or 'Edit with Notepad++' (or whatever your preferred editor is). Run the uninstaller that is generated in the installation process. You can also find this in your FSUIPC7 installation folder. You can also uninstall using the windows settings apps uninstall page, which will run the uninstaller for you. John

Could you please activate logging for axes events, produce a short-ish (as short as possible!) log file showing your issue, then show me that together with your FSUIPC4.ini file. I presume you know this is no longer supported. You should really update (if possible!). John

These are FSUIPC7 files not MSFS ones. Your FSUIPC7.ini file will be in the same location as the FSUIPC7.log file. If you cannot see the file extensions, you will need to change your Explorer preferences. John PS. Your log file is cut short after the Carenado loaded. Did you try to operate anything? Wa FSUIPC7 still running or did it crash? Maybe you can activate event logging and produce another log file, load the aircraft, operate a few buttons/switches, then exit and attach that log file, together with your ini.

Ok, thanks for the update. I've identified the problem and the Pan View axis will be back in the drop-down in the next release of FSUIPC6. It was an issue with the update from 6.0.10 to 6.0.11. John

Ok. But this seems to contradict your previous statement: Not to worry, as I don't think this relate to your problem. Well, you shouldn't have done this as an Adminstrator, but it shouldn't matter. But the folder you are starting things from (C \WINDOWS\ system32>) might. Maybe try it again from a non-admin account, and from a non protected folder (if you start a command prompt as a non-admin, it should default to your home folder). Yes, it does seem that something is amiss in your MSFS installation. If its the -FastLaunch option that is confusing things, you could try removing that option from the line in the MSFSwithFSUIPC7.bat file to see if that makes a difference. Really, you need to determine what command to use to start MSFS. The next time you install, I suggest that you opt to create the desktop start icon, which you can then use to determine the command used (from the URL field in the properties). I have no idea why the standard command that works for almost everyone else is not working for you. Have you tried running the desktop link as administrator (right-click and select 'Run as administrator')? Maybe also worth trying, but if the start commands don't work in a command window, I doubt they will work from using the link. John

@asessa I've added the A320Neo autobrake setting to offset 0x0260 in the attached version v7.0.3c which holds the following values: 0 - off, 1 - lo, 2 - med, 3 - hi This comes with the proviso that it will only hold the correct state if the state is changed using FSUIPC7 - if the state is changed from the UI, then the events to maintain this offset are not seen. FSUIPC7.exe John

@jaxx I've removed the correction previously added in the attached version v7.0.3c if you can try it: FSUIPC7.exe

@Paulcoy That does sound strange... Did you try the batch file directly and checking the contents of the command window for the error? Alternatively, open a command prompt and enter the following and let me know what error you get (or if MSFS starts): cmd.exe /C start shell:AppsFolder\Microsoft.FlightSimulator_8wekyb3d8bbwe!App -FastLaunch You can also try start shell:AppsFolder\Microsoft.FlightSimulator_8wekyb3d8bbwe!App -FastLaunch John

Then why not start FSUIPC7 from the MSFSAddon Linker and forget the FSUIPC7 batch script? Well, it won't launch on its own with MSFS unless the provided batch file is used. As I said, can't MSFSAddon linker start FSUIPC7? This is what is confusing me. Are you launching MSFS/FSUIPC7 using the desktop icon manually or using MSFSAddon Linker? If the former, what is starting MSFSAddon linker? If the latter, then that seems to solve any issues, no? Seems like you have a choice of either 1. use MSFSAddon linker to start MSFS and also start FSUIPC7 2. use MSFSAddon linker to start both MSFS and FSUIPC7 by getting it to call the MSFS/FSUIPC7 batch script or desktop link 3. change the FSUIPC7 batch script to start MSFSAddon Linker (which would then start MSFS) instead of MSFS directly The choice is probably restricted by what MSFSAddon linker can do. I'll take a look at the MSFSAddon linker at some point, but I won't have time for this for a while. John

I'm sorry, what do you mean by this? FSUIPC does not use Mobiflight, although Mobiflight may use FSUIPC. I am not familiar with Mobiflight. What does the WASM module do? Is this for a particular aircraft, or generally for the G1000? How does mobiflight handle this? Maybe log the events to see if you need to set something else first, such as one of the _SLOT_INDEX_ events. Does mobiflight communicate directly to MSFS or via FSUIPC (or both)?

I'll leave this for other PMDG users to answer (hopefully). You don't say which version of FSUIPC or P3D you are using (or PMDG),. There was an update for the PMDG 747 SDK back in April, and a corresponding update to FSUIPC5 and FSUIPC6, so check you are on the latest versions. If you are, it may also be worth asking on the PMDG forums. John

Your ini's show that both your FSUIPC5 and FSUIPC6 are out of date. Could you update both please - only the latest versions are supported. They also show that your devices are recognised multiple times with different GUIDs. I think it would be worth cleaning these as its hard to tell what assignments are being used, especially without seeing you log and joyscan files. Could you attach both your FSUIPC5.Joyscan.csv and FSUIPC6.joyscan.csv files, as well as an FSUIPC5.log and an FSUIPC6.log and I'll let you know what needs to be removed. AFTER you have updated both version please!. Also re-attach both your ini's. John

But maybe it also affects one of these buttons? I am only suggesting disabling your assignments in MSFS to test to rule this issue out. You can also try activating logging for buttons and events, and produce a short log file where you activate your strobes and the other actions occur. This will show what events are seen. Maybe also another log file when you start on the runway and it works as expected.

The Pan View axis is still available. However, something strange is happening with that axis as if I remove my assignment to it, it no longer appears in the drop-down. Very strange - I will look into it. For the time being, if you select <custom Control>, then enter 66416 in the custom control pop-up, this should assign to Pan View. John

Ah, then that could be why you had assignments to your new device when it was connected. You should certainly activate this. Maybe be a good idea to manually remove the previous assignments first. If you need any help, activate the joyletters facility (change ini parameter AutoAssignLetters in [JoyNames] section to Yes), start P3D/FSUIPC briefly, then attach your .log, .ini and .Joyscan.csv files.

This could be related to a know bug/issue in MSFS with certain controllers/devices that have a constant pressed down state, such as the Honeycomb Alpha yoke and also I believe the TH HOTAS Warthog. Its known to effect heading bug increments but can also can effect other areas. See https://forums.flightsimulator.com/t/heading-increment-bug-10-degree-instead-of-1-explained/290173 for details. To check if this is the issue, try temporarily removing your MSFS assignments to that device, or disconnect the device.

But in the 747-400F, the switch is activating the same macro. Therefore it is the macro that is behaving differently in the different aircraft, no? And, if its a mouse macro, its most probably due to the fact that the rectangle Ids have changed. So you will need to make a new macro for that series of aircraft. Thats because the 400F is already assigned to a profile, as I have tried to explain many times. If you want to create a new profile for that file, you will have to remove it from the existing profile first. To do this, you need to change this line: 1=PMDG 747 so that it sub-matches ONLY those aircraft you wish to use for that profile. As you are extending this, you will probably want to add multiple entries to cover different liveries. You can always just give the full tile of each aircraft if you are finding the substring match difficult, or look into changing the ini parameter ShortAircraftNameOk=Substring to something that works for you. But the profile system is working as expected. You just need to understand how profiles are assigned, re-organise your profile assignments to remove the ones that don't currently work in the profiles they are in, then create a new profile based on the existing profile that mostly works, and then re-do the assignments/macros that need changing. John

@jaxx Please see the following: They were the wrong way around and I added a correction to this and raised with Asobo, and it now looks like this has been fixed. I'll check this and remove the correction I added for the next release. John

I know nothing about MSAddon Linker. if you use that to launch MSFS, then can it also launch FSUIPC7? Alternatively, if its ok to start this after MSFS, then you could use FSUIPC's run Programs facilities to start this. Or you could manually change the provided batch script to start MSFSAddon Linker instead of starting MSFS. It wouldn't if you are not starting it. This I don't understand. So it is running? What launched it? Your installation looks fine, and I don't think using MSFSAddons linker should affect the batch start-up script (and it is working for Katoema!). Can you try starting by double-clicking the file MSFSwithFSUIPC7.bat (located in your installation folder). Using this there will be a command window created (maybe iconized) - please check that for errors. Also, if you can right-click your standard MSFS start-up icon, select Properties and tell me what it says in the URL field please.

Can you please attach your installation log, and also an FSUIPC7.log file please and I'll take a look.

You can create a new profile based upon an existing profile, and then just modify any assignments that need changing for that aircraft. Then as you did not get a menu asking for the profile selection (new, new based, on, etc) then that means that the loaded aircraft has already been assigned a profile, that profile name will appear in the FSUIPC options title bar. As the substring match assigned to your PMDG 747 profile is/was 'PMDG 747-400', then this will be loaded for both the 747-400 and the 747-400f. But again, this contradicts what you have previously said. I think you are failing to understand how profiles work, and the distinction between axis profiles and buttons/key assignments. When you have an aircraft assigned to a profile, in the axis assignments you will automatically see the profile as only the profile axis assignments are used. However, with button and key assignments, general assignments are used and then update (and replaced if necessary) by the profile specific assignments. This is why when you go into the button or key assignments panel, no profile is selected, and so if you add/modify or review any assignments, this will apply to the general profile (i.e. all aircraft). However, if you check the profile specific checkbox, the buttons/keys for that profile are loaded and then any updates made will apply to the profile specific assignments. This allows you to make both general and profile specific key and button assignments when an aircraft is already in a profile. John