John Dowson

👍 No bother!

The sixe/position coordinates are only used the first time a window is created. After that, its size/position is stored in your FSUIPC ini file, under the [ExtWindow] section. To use the new coordinates, delete the entry from that ini section. You can also move/resize the window using the arrow keys and the ctrl key to toggle between move and resize. You need to give the window the focus first. John

I have no idea. There is only one version of FSUIPC, and it can either be used with or without a license. You can also download from https://fsuipc.com/. If your key is not validating, it is most likely because you do not have the required VC++ redistributables installed. Please download and install the combined (ie. for 2015, 2017, 2019 and 2022) VC++ redistibutables, both x86 and x64, from https://learn.microsoft.com/en-us/cpp/windows/latest-supported-vc-redist?view=msvc-170 John

You need to install the GoFlight driver, most probably the 64-bit version (although you don't say what version of FSUIPC or simulator you are using). The GoFlight drivers are available from https://fsuipc.com/, together with a list of supported Go Flight devices. John

FSUIPC7 is not crashing - it is MSFS that is crashing, and FSUIPC7 was then exiting as MSFS was no longer available. You will also see an exception for FSUIPC7 when the MSFS SimConnect drops, but this is nothing to worry about. So your issue is that MSFS is crashing. I cannot help with this - please see the Asobo support forums for MSFS crashes. By the way, you seem to be running FSUIPC7 from your Desktop. This is generally not a good idea - you should at least create a folder and run FSUIPC7 from a sub-folder (and preferably not on Desktop or under Documents, i.e. not in a OneDrive folder). John

As I said, once you have assigned your axes to a profile, the only way of changing this is by editing the ini, either removing the aircraft from the profile, or deleting the profile-specific axis section.

Did you read the documentation? Please see the Installation and Registration guide, section Invalid Key Issues (or the provided READme.txt). In ALL cases, this issue is ue to one of three reasons, which are: 1. You do not have the required VC++ redistributables installed 2. You aare NOT entering the details exactly as given/provided (all 3 parts must match: name, address/email and key) 3. You are using an overly-aggressive anti-virus that is blocking the validation There is absolutely nothing wrong with the validation method. You need to read the documentation. Or see one of the many many support requests, e.g. I am continually asking people what the problem was once they have validated correctly but don't get any response, and i can only assume it is due to the fact that they have either not read or nor understood the documentation. Note I have also updated the topic of this support request. Please always give an appropriate topic for your issue - 'FSUIPC7' means nothing as it applies to every single post in this forum. And please look for similar topics before posting - this one has now been reported hundreds (if not thousands) of times. John

As I have said, I would like people to upgrade when a new version is available. You should download when you see the pop-up message, and then install once you have finished the flight session, or before you start the next session. Installation of a new version takes less than a minute and should not give any issues. If you do not update to the latest version, your version of FSUIPC is no longer supported. I also release beta versions for any important changes that could cause issues, so if there are any issues, most are fixed before release. However, i cannot check everything here - for example, I have no PFC devices, there are many add-ons that use FSUIPC that I don't have, etc. So if there are any issues with a release, I would like to pick these up (and fix them) asap, not when someone has found an issue after upgrading from a version that is 5 or 6 versions old. I may consider adding an option to completely disable new version notification. However, if i do this, it will be under the condition that you no longer require support if using this option. I am closing this thread now as I have nothing further to say on this issue. John

It should still close when using the Last option - and also when using Kill - it is for this that these options are provided! So are you saying that it works when using Run/Close but not when using RunReady/CloseReady? If so, that is very strange asthere is no realdifference, apart from the time when the program is started. Also, if WideClient can't close a started program, it will not shut down automatically itself. I will look into this further in September anyway and try to work out what is happening. I don't think there is much I can do about this though, except maybe clarify things in the documentation. I will report back sometime in September. Regards, John

It may be an issue if its starting other programs, but if its working in FSUIPC it should really work in WideClient. Is it the same program, starting the same programs as on FSUIPC? If not, you could try that as a test, to make sure. I;m pretty sure that would work - WideClient hasn't changed for many years and this would have been reported earlier (many time!) if this wasn't working. But I will double check this, but, as I said, I cannot do anything now until I am back from mu holidays, in September. Ok - let me know how that goes. However, if you use kill, I don't see how your program could run the the 2nd batch job on closing.... Why don't you use FSUIPC / WideClient to start the ProSim modules? Or are you doing it this way to run the 2nd batch script on close? John

Can you check what the actual process name of the prosim process on your client PC is called (using TaskManager) - runprosim.exe may start an exe with a different name. If that is the case, you need to put the actual process name in the CloseReady1 entry, e.g. CloseReady1=Yes,"<processName>.exe" From the technical guide: Also, please try using the Last and Kill keywords (instead off Yes). John N.B. Note I am an holiday now and away from my flight PCs so cannot look into this in more detail at the moment (and I don't use or have prosim!).

Yes - I saw that when I made the second script and corrected it! As reading the value of an lvar by name is quite time consuming (as it has to go through the list of available lvars) , the script cant also be more efficient: id = ipc.getLvarId("L:Lear_LDG_Weight") if id == nil then ipc.createLvar("L:Lear_LDG_Weight",10361) while (id == nil) do ipc.sleep(50) id = ipc.getLvarId("L:Lear_LDG_Weight") end end ipc.execCalcCode(" (A:TOTAL WEIGHT, pounds) (>L:Lear_LDG_Weight) ") -- get current total weight ipc.sleep(200) ldg_wt = ipc.readLvarById(id) ldg_wt = math.floor(ldg_wt + 0.5) Basically if you are accessing an lvar by name more than once, it is better to get the id of the lvar and use the id functions. John

Even better: if ipc.getLvarId("L:Lear_LDG_Weight") == nil then ipc.createLvar("L:Lear_LDG_Weight",10361) while (ipc.getLvarId("L:Lear_LDG_Weight") == nil) do ipc.sleep(50) end end ipc.execCalcCode(" (A:TOTAL WEIGHT, pounds) (>L:Lear_LDG_Weight) ") -- get current total weight ipc.sleep(200) ldg_wt = ipc.readLvar("L:Lear_LDG_Weight") ldg_wt = math.floor(ldg_wt + 0.5)

I don't have the fenix, but if you engage vnav by pressing the altitude button, you could try the preset FNX320_FCU_ALTITUDE_KNOB_PUSH. See https://hubhop.mobiflight.com/presets/?vendor=FenixSim&aircraft=A320 for a list of the available presets for the Fenix - all MobiFlight presets are available for assignment in FSUIPC. You can also see these by using the Find Preset button in the assignments panel, after checking Select for Preset:

What part? And what part don't you understand? In which panel? as I said, you cannot change this in the axis panel. In button & key assignments, you can assign a button to either a profile or not, and should be able to check/uncheck the profile-specific checkbox accordingly. If this is not clear, please provide more information - what arte you trying to do? Which panels are you using - axis, button or key assignments?

For PMDG aircraft, you can use the provided custom controls. See For the NG3, the custom controls are: #define EVT_MCP_VNAV_SWITCH (THIRD_PARTY_EVENT_ID_MIN + 386) #define EVT_MCP_LNAV_SWITCH (THIRD_PARTY_EVENT_ID_MIN + 397) You can also use FSUIPC's logging facilities to determine what is being used: set logging for Events, open the logging console and see what is logged when you press the switch in the virtual cockpit. This will be a custom control using the Rotor Brake control, which is an alternative method of using PMDG custom controls, also described here: (N.B. when logging events in many add-on aircraft you will see many events being continually logged - you should ignore such events using the DontLogThese ini parameter) For the Fenix, you can also use logging to determine what is being used. If no events are logged, try listing the available lvars (Add-ons ->WASM->List Lvars) to see if any look applicable.

There are a few things that could be improved in the script: 1. You only need to create the lvar once, do you should handle this if the script is being called multiple times. 2. If you create an lvar using ipc.creatLvar, you don't need to reload the WASM afterwards - this is done automatically. As for the timing issue, lvar values are, by default, updated and send out from the WASM at a frequency of 6Hz, so roughly every 166ms.Therefore a delay of 100ms is not going to be enough most of the time, although this depends on the timings. Taking into account the time needed to send and process the request, you would need a delay of 200ms to make sure the new value had been received. if you want faster updates, you can set the WASM ini parameter LvarUpdateFrequency to VisualFrame. if ipc.getLvarId("L:Lear_LDG_Weight") == nil then ipc.createLvar("L:Lear_LDG_Weight",10361) ipc.sleep(600) end ipc.execCalcCode(" (A:TOTAL WEIGHT, pounds) (>L:Lear_LDG_Weight) ") -- get current total weight ipc.sleep(200) ldg_wt = ipc.readLvar("L:Lear_LDG_Weight") ldg_wt = math.floor(ldg_wt + 0.5)

Thanks for this - I will move it to the User Contributions section. Also note that another way to use the mode switch to have different assignments to the same button/switch depending on the mode switch positiin is to use compound assignments. You need to manually edit the FSUIPC7.ini file to do this, and the method is documented in the Advanced User guide. However, this is only applicable to button (and key) assignments, not for axis assignments. John

Your license information is available in your SimMarket account. John

Yes, you need a radar.bmp file for any of this to work. This was provided by ActiveSky, but that functionality isnt available for MSFS. Once you have the radar.bmp file then sharing/displaying shouldnt be a problem. But I do not know how you can generate such a file with MSFS. Note I am on holiday now until September. John

👍

You just add it to your ini and it akways applies. But dont switch it off (i.e.set to yes), try setting it to Enum first. This will still monitor, but using a different method.

Just caught me in time... Currently lua is the only possible way to do this. I will look into allowing 2 parameters for events at some point, but I have a few more urgent things that I need to do before I can look into this. Note I am now on holiday until September, although I will be checking for support issues occasionally. John

Please also note that I am now on holiday until September, although I will check for support issues occasionally. I am now out-of-contact until Monday though. John

As with all other users who report this, your key validates just fine. I will pm you a key file and try this. Save the key file to your FSUIPC installation folder, then re-run the installer and validate the key by clicking the Register button at the end of the installation process, If it validates, then the only possible reason that you are unable to register is that you did not enter the details correctly. If it does not validate, and you have installed the required VC++ redistibutables, then it can only be your anti-virus software blocking the validation - please check that.. Can you PLEASE respond once you have done this. I would like to understand why so many people are having this issue so that I can update the documentation accordingly, but nobody is responding. John