John Dowson

No, that was correct - sorry I misnamed it. Yes, worrying... I will check the changes made, and also I will see if I can reproduce here - I guess I have to register for a VATSIM account to do this, no? John

Hi Glyn, As I said, everything must be running at the same privilege level. If you are running MSFS with Admin rights, that will run FSUIPC7 (and FS2Crew) with Admin rights, so you need to run Pilot2ATC with Admin rights. To do this, go into the Compatibility Properties of the Pilot2ATC.exe and check the box 'run this program as an administrator'. John

Not sure, but I don't think so. The provided ones will be overwritten and so will lose any changes, but new ones added should be preserved (the uninstaller will attempt to delete the folder but this will fail if it still has files inside it). Although maybe better to add such files to the WASM persistent storage location instead. John

By doesn't work, you mean the LvarScanDelay ini parameter has no effect? The log file you attached seems to indicate that it was loaded correctly, and the Debug level logging was set: Are you saying that you don't see any lvars until after you Reload? If that is the case, are you sure you are not just trying to list the lvars before they have actually been loaded (i.e. longer than 45 seconds after the aircraft was loaded)? If you think you are having issues, can you also please activate Debug level logging in the WAPI (and also keep activated in the WASM) and send me both your FSUIPC7.log and FSUIPC_WASM.log files. John

Hi Ross, Yes, that helps enormously, thanks. I will take a look at this next week. Could you also please try the attached dll to see if the same problem exists in this version. This is also version 4.976, but is the original build before the VS toolsets were updated. Thanks, John FSUIPC.dll

Hi Andreas, Are you using the stock A32NX or the FBW mod? And by 'debug mode console', do you mean the MSFS dev mode one (and not the FSUIPC logging console)? I cannot see any such errors in the FSUIPC7.log file. Yes, these are for two new indexed variables that I have added to offsets: FUEL DUMP ACTIVE FUEL DUMP SWITCH requested for indexes 1-16 (as the 747 has 16 individual pumps). Requesting a variable that doesn't exist (or if the index is out of range) should result in a SimConnect error reported in the FSUIPC7.log file, which I don't see. And I don't know why you are continually seeing these messages. The simvars are only requested once, most probably on a 6Hz period (although I would need to check). Later: Ok, I can see those error messages, both in the stock A320 and the FBW A32NX, and also in some other aircraft (e.g. 787), but not all - seems to only affect aircraft that use the new fuel system variables. This only seems to affect the MSFS console window - no error messages are logged (or received) by FSUIPC7. Not sure what to do about this at the moment. It seems only to be an issue with these messages being logged in the console window and not much else. I'll report this to Asobo to see what they say. I am not sure why these variables are being continually logged either, as they are only requested once. I will report back if/when I hear anything from Asobo. I don't like making previous versions available, and only the latest released version is ever supported. I don't mind making the previous release available upon request, if there are issues with the newly released version (and while these issues are being investigated), but I won't be making previous releases permanently available. John

Please download and install the latest release of FSUIPC7, v7.2.13. The dll wasn't updated in this version (I will update), but I have just tried it and it seems to work fine. John

Where is this lever? Is it the one with the tooltip 'ENGINE CONDITION'? There are a few lvars that look they relate to this lever: Condition_Lever_CutOff_1 PC6_IDLECTRL_LOCK PC6_IDLECTRL_LEVER And I can see that a FUEL_SELECTOR_ALL event is also logged with a parameter of 1 when you move to a certain position - then its logged with value 0 straight afterwards (this event seems to be continually logged!). I've tried setting those lvars but that didn't seem to have any affect. It may be possible with a combination of setting lvars and sending events (via calculator code), but first you need to determine the lvar changes and events sent when you move in the UI and then try and replicate. Otherwise, there seem to be quite a few events that don't seem to have any affect when sent via Simconnect (e.g. using FSUIPC) but do when assigned in the sim. If you find a control/event in the MSFS control assignments that works, you can assign this to a key press (in MSFS) and then assign to that keypress in FSUIPC7. I am pretty busy at the moment with various issues with the latest SU7 and FSUIPC7 updates so don't have time to look into this any further at the moment. I can maybe take a further look later in the week, once things have settled down a bit.... John

So the lever just acts as an on/off button, no? Then why do you want to assign it as an axis? You can assign to that control to any button or switch. If you really want to assign to an physical axis, you can initially assign the axis to an unused axis control (left hand side of axis assignments dialog) and then assign to the Set Fuel Valve Eng1 in the right hand side of the assignments panel, with a parameter of 1 when going into a certain range and a parameter of 0 when exiting. Otherwise, please explain exactly what you are trying to achieve, i.e. what are you trying to assign to this? Have you tried assigning something to that control? Having download/update issues with SU7 so can't take a look at the PC-6 yet, will do later if you can provide further info on what you are actually trying to do. Thanks, John

It should be ok under this folder (although I see I have missed the 'Work' folder in the documentation - I will add/update). Do you see your FSUIPC_WASM.log files there? The FSUIPC_WASM.ini needs to be in the same location as these files. Can you try changing the LogLevel to Debug in the ini file in that location, to see if that has any affect? It will work there but that file will get overwritten when you next update, so better to add to the other location really... John

Sorry, looks like I forgot to update the FSUIPC_WAPID.dll. Can you try the attached please - drop it into your FSUIPC utils folder, replacing the version already there. John FSUIPC_WAPID.dll

Thanks, and sorry I can't help further. This is a very strange problem - please report back if/when you have found the cause and/or a solution. John

Looking at this again, the log extract shows that the Sim has stopped, so you weren't in a flight, which is why it wouldn't connect. Was that not the case? Please use the v7.2.13 released version (download if not done already). Please try one last time with this version. There really should be no difference between when auto-started and manually started (except maybe with permissions). John

I'm sorry but I am getting confused as you said it is now showing in the system tray...it helps me a lot if you could be a bit clearer... Is this correct: You start FSUIPC7.exe by double clicking it, you see a splash screen which disappears after a few seconds, you then see the FSUIPC7 icon in the system tray for a brief period, but it then disappears, and when you go back to the installation folder the FSUIPC7.exe has been removed. ? If that is not the case, please explain. If that is what is happening, then sorry but I have no idea what can be doing that, but it must be something like an anti-virus program. FSUIPC is not crashing - if it was there should be something logged somewhere (i.e. in the Windows event viewer), and it certainly isn't 'deleting itself' - that must be done by another program or service.

Is this actually an axis control then? i.e. the parameters to that control are over a range and not 1/0 (on/off)? Please confirm, and if that is the case then yes I can flag them as axes controls. I will post a version here for you to test once confirmed. John

What happens when you click the 'Set' button? It should change to 'Reset' and show the buttons to enable calibration. If that is not the case, can you tell me what happens and/or attach a screenshot of the calibration window. Also attach your FSUIPC7.ini file so I can take a look. Can you start MSFS/FSUIPC7, activate axes logging, load an aircraft, apply and release your toe brakes, then exit FSUIPC7 and show me your FSUIPC7.log file as well. Thanks, John

It won't, as its a WASM ini parameter, not a WAPI one. You need to add it to your FSUIPC_WASM.ini file, either under your Community/fsuipc-lvar-module folder or under your AppData folder, which is better as it then will not be overwritten when you update - please see the Advanced User guide for details. John

If this happens also when assigning directly via P3D, how do the aircraft makers tell you how to configure the throttle? Have you checked or asked about this on the Aerosoft or Milviz forums? I see Pete has also just replied... Sounds lie you are assigning in P3D and then calibrating (not assigning) in FSUIPC. I am surprised this works, as this can cause issues due to priority levels, as Pete has said. I currently don't have any of those add-ons to check - but I'll see if I can get one to take a look... John

Ok, so you can open the FSUIPC main window from the system tray icon, or by pressing Alt + F? What do you actually mean by this? That he FSUIPC7.exe file is actually deleted from the folder where it was installed? If so, then this can only possibly be done by some sort of anti-virus program, and you should have a notification somewhere that this was done. You could try searching for the FSUIPC7.exe using Everything (available from https://www.voidtools.com/downloads/) - this may show you where it is if it has been quarantined by an anti-virus program. Or please explain what you mean by 'keeps deleting'. If FSUIPC7 is running, which it must be doing if its in your system tray, I cannot see how it can be deleted. John

You do not have to list the lvars before using them. Lvars are automatically loaded 5 seconds (by default, changeable using the LvarScanDelay WASM ini parameter) after the aircraft is 'ready-to-fly'. And listing lvars doesn't reload them - it just lists those available (in memory), that have already been received. This sounds strange as lua scripts are not started unless the lvars have been loaded...Maybe they were loaded (do you see any lvars?), but the ones you are using aren't available? Note that with more complex aircraft, not all lvars are available with the default LvarScanDelay of 5seconds and this may need to be increased. I have mine set to 45 seconds, which is tuned for the airliners as they seem to take a long time before they are available, especially in the FBW A320. I also have the Just Flight Arroe III/IV and have no issues with lvars, so maybe try increasing that parameter. You could add Debug level logging to to the WAPI, which will log further messages so that you can see when the lvars are available. If you are still having issues, activate that debug logging and show me your FSUIPC7.log file. Also, make sure you are using the latest version of FSUIPC7, v7.2.13, released a few hours ago (and recompiled against the latest SDK released with SU7). John

Are you using the Working Title mod? There is a report in the Asobo forums that this is no longer working correctly since SU7 with the lesson scripts - may be related? https://forums.flightsimulator.com/t/su7-new-lessons-ifr-vor-issues-with-workingtitle-g1000nxi/472878 John

Your installation log looks fine, except that you are installing quite an old version. Please download the latest version, v7.2.13, and try again. Why do you think this? Your log shows the FSUIPC7.exe was installed ok: John

FSUIPC just uses the AP Alt Var Set English control/event. No idea why this has changed. Are you using the stick G1000NXi or a mod? Btw, just release FSUIPC7 v7.2.13, which has been recompiled against the latest MSFS SDK for SU7 (0.16.0.0), as well as containing a few bug-fixes + additional offsets/features. John

You need to install the x64 ones, and make sure its the combined package (2015, 2017, 2019 and also now 2022 I think...). And its the IctallFSUIPC7.log file I need to see about the install problems, if you still have them after installing the VC++ restribs. John

One thing you can do to try and track this down is to activate logging for IPC Reads and IPC Writes, using the FSUIPC7 Log menu. Also Open the logging console (from the same menu). When you get that error, take a note of the timestamp of the last message logged, then acknowledge the message and then exit FSUIPC7, and show me your FSUIPC7.log file. John