John Dowson

Sorry, but I do not understand the question. I download and add the events.txt file (from MobiFlight - the file that contains the presets) either on the day of release of FSUIPC7 or sometimes the previous day. So the preset file included in FSUIPC7 version 7.4.16 will be from the 24th or 25th July. The date individual presets are added is only available in the MobiFlight HubHop site (https://hubhop.mobiflight.com/presets/), where you can also download the latest events.txt file if there are new presets you want to use not included in the one installed by the FSUIPC7 installer. John

That is a message from your acars program, not FSUIPC. Is FSUIPC7 running? You need to verify that first. If programs that use FSUIPC cannot connect, it is usually because they are running at a different privilege level. Everything must be ran at the same privilege level to connect. John

You did, and I cut and pasted your key here and it validated just fine. I would like to know now if the key validates ok for you now. And if so, why did it not validate when you cut and pasted previoulsy. It is trivial and I am not arguing - I would just like to understand why so many people seem to have issues with registration, I get several support requests every week on failed registration issues, but whenever I check/validate them here they are all fine. I send the key to the OP (i.e. you in this case) and then i get told its all fine now but I never get to the bottom of the issue as to why the customer/client could not validate correctly themselves in the first place. If I could find out what the issue is for such users, I could update the documentation (or even the registration process) so that I do not get so many support requests in something that should be so straight-forward. So any feedback on what the issue was is important so that I can improve things going forward.

There are already presets defined for this: Check Select for Preset, click the Find Preset... button, and they are under MobiFlight->FenixSim->A320->Radio. John

What did the trick? I only entered your registration details and validated them to generate a key file for you...if the key now validates, you must have entered it incorrectly previously,

Still not got hold of the B727, but another user has posted the following presets for the cut-off levers - add them to your myevents.txt file (create this file if you don't have it): You can then assign to these by checking Select For Preset, click the Find Preset... button and they will be available under Personal-> FlightSim Studios -> B727 -> Fuel.

Great! - thanks for the update. John

I really can't answer such a general question - all the information you need should be in the User manual, so start there. If you have any specific questions om assignments then I can respond. Read the section THE EASY STEP-by-STEP WAY TO CALIBRATE YOUR CONTROLS in the User manual. Calibrate the rudder and look into adding a 'Slope'. which is a response curve - see the User manual. FSUIPC does not interact with TrackIR - you calibrate TrackIR within the TrackIR application. John

Hi Ray, I can't see anything assigned to device U - if you remove that entry, does it get added back? You should also consider: - updating to the latest version if FSUIPC6, 6.2.1 - using substrings for your aircraft profile names to catch all variants, rather than adding each variant/livery e.g. change to and update all your [Profile.xxx] sections similarly, using substrings that will catch all variants of the aircraft

Ok - thanks doe the update.

You are adding some simvars to FSUIPC offsets using the myOffsets.txt file, and it is two of these that are causing those messages: Remove those from your myOffsets.txt file, Note also that the other FUELSYSTEM variables may also give issues when using an aircraft that doesn't use the new fuel system: John

Does this occur with all aircraft or just one or more? The only cause of such micro-stutters that I can think off is excessive logging by MSFS. Can you open the MSFS logging console (from the development menu - you need to switch-on devmode to see this, in the MSFS options). If you see lots of messages logged, please tell me what they say. Usually this is caused by requesting sim variables from the new Fuel or Electrical systems when using an aircraft that does not use these systems. Also please attach your FSUIPC7.log and FSUIPC7.ini files (from your FSUIPC7 installation folder) - no additional logging needed for the time being. Make sure you exit FSUIPC7 before attaching files, and you can zip/compress them if too large to attach.

This is how the forum is set-up and is nothing to do with me - I do not control/manage the forums, It is also quite common for such forums to have restrictions/limits for new users which increase over time. The initial low upload limit causes me a lot of issues as well, as I nearly always need to see either an ini or log file, and the initial limit doesn't allow for either (unless compressed). Ok.

It is no bother to me and I am not frustrated. However, I am always trying to reduce the time I am spending on support so that I can spend more time on other things, such as improving the functionality and documentation. If I continually have to answer or explain things further then the documentation is obviously not good enough and needs to be updated, otherwise I repeatedly get asked the same questions which is not only wastes my time but also that of my customers. I therefore like to clarify/update documentation (including FAQ entries) so that I can reduce such queries. I am therefore asking why it was not clear to you that you needed to set that ini parameter from the FAQ entry so that I can update it...

Your WASM log file shows this: If you have read the FAQ entry, it says to set LvarScanFrequency=0 Have you tried this? And can you tell me why the FAQ entry isn't c;lear on what to do about this...the FAQ entries are there so I don't have to explain this to every support request. If you can let me know why the FAQ entry for this isn't sufficient I can update it.... John

Did you not read my previous comment? Your WASM is crashing - please read the FAQ entry for this and follow those instructions.

@xkoote Did you manage to get this working yet using FSUIPC7? Also, do you know how to assign for the fuel cut-off levers in the B727?

@David123 Did you try the above or did you manage to sort out your issue, and if so, what was the problem?

Your upload limit will increase the more you post. If files are too large to attach, even when compressed, you can use a (free) file exchange service such as https://filetransfer.io/.

Can you please ALWAYS attach your full log rather than posting extracts. There is other information I need to see from this, such as which aircraft you are using. Depends... so you have anything assigned to those controls? Try activating logging for Buttons & Keys as this will tell you if those are coming from an FSUIPC7 assignment or not. Do you also have assignments in MSFS, or have you created empty profiles in MSFS for your controllers (recommended)? Many aircraft continually send certain events/controls, and these vary by aircraft. You can ignore such events by using the DontLogThese ini parameter. However, such events logged should not cause any issues - they are just noise in the log. Can you please check to see if you are experiencing a WASM CTD - see the following post If the WASM is crashing, follow the instructions there. If it is not crashing, follow the logging instructions in that post and attach your FSUIPC7.log and FSUIPC_WASM.log files here and I will take a look. John

An issue has been identified that can cause the FSUIPC7 WASM module to crash. When this occurs: - presets will no longer work - lvars will not be updated - FSUIPC can hang when restarted It has been reported that this occurs only when using complex aircraft AND complex scenery, and is more likely to happen after an aircraft change. If you experience any of these systems, please confirm that the WASM has indeed crashed. To do this, firs exit MSFS. Then open your FSUIPC_WASM.log file, located in your WASM persistence area which is: The last line in this file should be an 'END OF PROGRAM' line like the following: If you do not see that, then the WASM has crashed. The crash seems to be an MSFS issue that has been reported. If you find that the WASM is crashing then you can try tuning the WASM via ini parameters to prevent this. You need to disable continual lvar scans by setting LvarScanFrequency=0 and if setting this it is also a good idea to tune the delay of the initial scan, by increasing the value of the LvarScanDelay ini parameter (the default is 5 seconds). Suggest, for complex aircraft, you use: LvarScanDelay=10 Please see the Advanced User guide on setting WASM ini parameters. You should set these in the FSUIPC_WASM.ini file in your WASM persistence area, not the one in your Community folder. If this doesn't yet exist, copy the one from your Community folder to the WASM persistence are location (details in the Advanced User guide) and then edit/modify. If the WASM isn't crashing, then something else is causing your issue. Please enable WAPI Debug level logging (Log->WAPI->Debug) and Event logging, as well as WASM Debug level logging (via the FSUIPC_WASM.ini file) and the next time this occurs please exit MSFSm create a support topic and show me/attach both the FSUIPC7.log and FSUIPC_WASM.log files. John

When you run FSUIPC7 (or when it is auto-started), a splash-screen is displayed for a few seconds, and then FSUIPC7 will sit iconised in your system tray. To open the main window, either use the system trat icon or the default hot-key Alt+F. As you are NOT familiar with FSUIPC7, please read the user manual.... You do not need Steam installed. FSUIPC7 works with MSFS, and this can be a Steam version, and MS Store version or boxed. You can check your InstallFSUIPC7.log file to see what version was detected. No - you don't need WideFS (WideServer + WideClient) installed or refistered. WideClient is for use on a client/slave PC.

No - it will still scan for lvars on an aircraft change. Setting this parameter to 0 will mean that only one scan for lvars will be performed, and after LvarScanDelay seconds after the aircraft is loaded. So, any lvars created after this scan is performed will not be visible to FSUIPC7 for the lvar functionality, although you can still update such lvars via presets/calculator code. It takes place LvarScanDelay seconds after the aircraft is loaded, i.e. after you press the Ready To Fly button and the camera changes to cockpit. The LvarScanDelay parameter takes effect after the camera changes to cockpit, do this is probably after the aircraft has fully loaded. You can check all lvars are loaded by performing a manual scan for lvars, using the Add-ons->WASM->Reload menu option. If this discovers more lvars, you may want to consider increasing the LvarScanDelay ini parameter. Note that some aircraft and utilities seem to continually create lvars. However, it is debatable if such lvars are needed to be known anyway, so they can probably be ignored. And you can always use them via presets/calculator code. John

It wasn't, but this is not needed if FSUIPC7 is installed correctly. I have sent you a FSUIPC7.key file - please save this to your FSUIPC7 installation folder and then run FSUIPC7 to check that it is running as a registered version. Then re-run the FSUIPC7 installer. Your registration details will be pre-populated from the key file - try validating them. Do they validate? If so, what was your previous issue? If not, then it must be due to your VC++ redistibutables - are you sure that you updated them correctly?

You should not delete this one as that is the original that is copied to the paths given in the post. Then that would indicate it is an issue with P3D and not FSUIPC. Try re-installing the P3D client. And try starting with a default aircraft before switching to the PMDG 737.