John Dowson

What does this mean? If you want my assistance in this matter, it would help if you could answer my questions and follow my instructions... Did you try starting FSUIPC7 directly (by double-clicking the FSUIPC7.exe)? What do you see? Have you re-installed the combined VC++ redistributables, as indicated in the README.txt (i.e. uninstall the ones currently installed and install the combined package available from Microsoft)?

As Luke says, auto-save has always been an issue with PMDG aircraft, but it normally only causes a freeze for a few seconds (while the data is being saved). If it takes longer, it can be due to anti-virus/anti-malware software. Make sure the save-flight folder is excluded from such software (or just disable auto-save). The SDK save-flight function (which is what FSUIPC7 uses to save a flight) is also still not functioning correctly anyway, so its probably not worth using at the moment, although it does work sometimes, it is not yet 100% reliable. John

I don't have this aircraft so cannot investigate, but maybe these other topics on the same issue can help: John

Did you try starting FSUIPC7 directly (by double-clicking the FSUIPC7.exe)? Did you try re-installing the VC++ redistributables, as recommended? Did you trad the README.txt?

It is always helpful for others if you can give your solution. Also, you should always specify what aircraft you are using as problems/solutions can be very different depending upon the aircraft in question. John

This is by design. General button and key assignments are inherited by all profiles, unless overwritten by that profile, so you can always assign a button or key press to the current profile or to the general profile. General axis assignments are not inherited by a profile, so only axis assignments in that profile apply. When you initially create a new profile, you are asked if you want to import the general axis assignments into that profile. Once the profile is created, and an aircraft is assigned to that profile, new axis assignments can only created in the aircraft profile. John

No problem, I understand. When I get time, I'll take a look at the xml file to see of that reveals anything.... Note that in MSFS, every aircraft is different - this is the Longitude pulse preset (but not TOGGLE_LOGO_LIGHTS as you said): LONGITUDE_PULSE_LIGHTS_TOGGLE#(>K:PULSE_LIGHTS_TOGGLE) and the xcub: XCUB_PULSE_ON#100 s0 7 (>K:2:LIGHT_POTENTIOMETER_SET) l0 (>L:LIGHTING_POTENTIOMETER_7) XCUB_PULSE_STANDBY#0 s0 7 (>K:2:LIGHT_POTENTIOMETER_SET) l0 (>L:LIGHTING_POTENTIOMETER_7) Kodiak 100: Landing_Lights_Pulse#1 (>L:SWS_LIGHTING_Switch_Light_Landing, Enum) MSFS is a different beast from FSX/P3D - most aircraft are specific in their controls without much in common. It is a bit of a nightmare for support! Regards, John

You assign an axis on the left-hand side of the axis assignment dialog box. The right-hand side is for specific controls when entering/leaving axis ranges. Remove that, and assign as follows: You don't seem to be familiar with how FSUIPC works. Please consult the manuals - at least the User Guide and maybe also a quick look at the Advanced User guide, so you at least know where things are. Try consulting the manuals before posting please. John

That is a rather annoying response from mobiflight... Some of mf team seem to think that only mf should be used, when there are many other options available, with and without using MF. And they didn't mention anything about the pulse switch.. If it can be controlled in MobiFlight, it can be controlled via FSUIPC. And as MobiFlight use the MF presets (only - I think), if there is no preset, I don't know how they can say that. What is the option in the MF dropdown to control the pulse then? John

The event logged seems to depend on the position of the Off-Taxi-LDG switch - I see TOGGLE_LOGO_LIGHTS when pressing Pulse when that switch is in the Off position, and TOGGLE_LOGO_LIGHTS followed by TOGGLE_TAXI_LIGHTS when in the TAXI position, and no events when in the LDG position. There is also an lvar called XMLVAR_FORCE_PULSE_ON, which initially I saw this change between 1 and 0, but setting/changing this lvar had no affect on the switch position. Later, this lvar didn't change value regardless of switch position. Strange... So, in summary, I have no idea...did you ask and get any response from the MobiFlight community? John

Yes, of course... Again, of course...Try assigning to FSUIPC's (i.e. direct to FSUIPC calibration) throttle axis and then calibrate. That should be the default assignment. For som aircraft, you may need to use a different throttle control, which you can assign in a profile-specific assignment for that aircraft (or class of aircraft). You assigned in the buttons tab - PAN View is an axis - delete/remove your current assignments, go into the acis assignment tab and move your hat switch (any direction), and then select 'Send to FS as normal axis' and select the Pan View control. You can! However, as I said, if you do this, FSX will occasionally automatically assign a controller that isn't assigned in FSX, so you get dual assignments, both in FSX and FSUIPC. If/when this occurs, you can go into FSX and remove the assignments on controllers/buttons/axis that you have in FSUIPC. Alternatively, and to stop this issue completely, we recommend disabling controllers in FSX and just assigning in FSUIPC. But you don't have to do this if you don't want to. But you need to check for dual assignments each time you get an issue like the one that started this topic... John

Why - what is the problem? What do you want to assign it to? What was it previously assigned to in FSX?

Did you check the event viewer to see if there is a crash report? And as I said: If FSUIPC7 is not starting correctly (or crashing on start-up) this is usually due to your system not having the required VC++ redistributables installed - check the provided README.txt for details. You also have windows explorer set to hide know file extensions, so you wouldn't see the log file anyway. I recommend that you update yout windows explorer settings - see the Addendum in the Installing and Registering FSUIPC7 document. John

So your problem was with dual assignments, in both FSX and FSUIPC. You can have assignments in both places, but sometimes FSX will recognise an unsigned controller and automatically re-assign (it does not know that this is assigned in FSUIPC). This is why we recommend disabling controllers in FSX and assigning in FSUIPC. It should be straight forward to switch your assignments from FSX to FSUIPC - the assignments will be more or less the same. For the hat switch (to control views), assign to Pan View (you just need to assign one of the hat switches to this, and the others will be assigned automatically). John

I can't help with actual presets (especially if/when I don't have the aircraft in question), I can only help with getting the preset calculator code being sent to the FS correctly. If you have a problem with a particular preset, check the description if the preset in the HubHob server (https://hubhop.mobiflight.com/presets/) and use the MobiFlight discord server for any questions on specific presets. John

Nothing in the log. You could activate logging (again) for IPC Reads, to see if that logs anything. Also, go to Log->Custom and enter 0x1000000 - that will log any IPC calls. But if the client isn't connecting, I wouldn't expect FSUIPC to see anything... You can show me the log again with that logging activated. John

MSFS CTD'ed and FSUIPC7 quit as MSFS was no longer running. I cannot help with MSFS CTD's - report to Asobo. The log shows FSUIPC was running normally, although you had a few simconnect data stalls (not really an issue, and usually due to an overloaded system). I do not know why your FSUIPC client cannot connect - you need to contact support for the client or SVATT-NG server. John

No, re-installing just updates the files that have changed, it won't affect your settings/assignments. Also you can skip the registration stage as you have already registered and have a valid FSUIPC4.key file. John

It will be under your FSUIPC7 installation folder, i.e. C:\FSUIPC7\FSUIPC7.log If it is crashing, do you see any errors? Is there a crash event in the windows logs (accessible using Event Viewer)? If FSUIPC7 is not starting correctly (or crashing on start-up) this is usually due to your system not having the required VC++ redistributables installed - check the provided README.txt for details. John

You could try with a lua script, which would send the TOGGLE_LOGO_LIGHTS event and then set a timer to set/toggle XMLVAR_LandingGearLightBlink between 1 and 0 every second or so. I'm a but busy to try this at the moment, but should be relatively straight forward - if familiar with lua! Otherwise, maybe try asking about this in the MobiFlight discord channel - they maintain and help with presets. Otherwise, I can take a more detailed look towards the end of the week. John

You have a button assigned to send a keypress (Del), and a key assignment on Del for WideFS KeySend. So, how are you sending the key to wideFS? If you press Del, does that work? The key Del key sent when pressing the button will be ignored when received again by FSUIPC (it does not act in key presses/release it sends). So, if you want the key sent on the button press, assign the button press (and maybe release) directly to the WideFS KeySend control. Any further issues, also be show me your FSUIPC7.log and WideServer.log files, with logging activated for Buttons & keys as well as Events. John

Why do you think this? When FSUIPC7 starts, it shows a splash screen and is iconised to your system tray, from where you can open it, or use the default hot-key Alt+F to open the FSUIPC7 main window. Please read the provided documentation, and if you have any issues show me your FSUIPC7.log file, not your installation log - that looks fine. John

What is changing? Something must be changing if it sometimes connects and other times not. Make sure you have an aircraft loaded and ready-to-flu before trying to connect. And uf you have issues, I always need to see your FSUIPC7.log file, and maybe also your FSUIPC7.ini. John

👍😎

Note you could also just create one preset: My_TBM930_Ignition# $Param (>L:MF_TBM930_ENGINE_Ignition_1_Set) and then provide the parameter value in your assignment, Up to you how you want to do this. John