John Dowson

There is a lua script available for this in the User Contributions sub-forum: The script should work in MSFS for the audio callouts, but the display facilities currently won't work unless they are using the Wnd library, which I doubt. You should also be able to disable the display facilities, or create your own lua from this.

I am not sure I fully understand your issue - it would help if you could attach the lua file that is causing this problem, as that would be where the solution. if any, would need to be applied....

Ok, that is the FSUIPC7 splash-screen. That is always displayed when FSUIPC7 is started, so that you know its running, as it starts and sits in your system tray. You cannot turn this off at the moment, but I guess I could add an option to do this. But I don't see why this is an issue, and if disabled, there would be no indication that FSUIPC7 had been started. If this really is an issue for you, I can add an ini file option (in a future release) for this to be disabled.

No, they shouldn't conflict as only one (the first match found) will ever be used. Just makes things a lot easier, and by using aircraft substrings, the same aircraft with different liveries will also match, and so saves you having to add an aircraft to a profile when you are using a different livery. Looks a lot better/cleaner, with one profile for the PMDG 737/777 and 757, and another for the PMDG 747. Note that you were previously also assigning the steering tiller to the same axis as the rudder (which is common) but only in some of your old profiles, You may want to consider addung this back to both of your current profiles.

But why would you want to do this? Why do you have several profiles for the 747? You only need separate profiles if the controls/assignments are different - they should be the same in all 747 variants, so you should only need one profile. Usually you would add an aircraft to an aircraft profile rather than creating a new profile. And rather than adding each livery, you should change the names used in the profile section, so if you change: to then that would match all 747-8 aircraft, or you could change to to match all 747s, and you can even add the 757 as that looks to be the same: There are slight differences in rudder/steeringtiller assignments, but I would have thought this should be the same for all 747 variants... Similarly, you probably only need one profile for the 777.

As I said in my previous post, if you don't want to see the splash screen, don't use or even install the desktop icon, by deselecting the checkbox on the end of the installation process. All the desktop icon does is start MSFS and display the splash screen for 30 seconds or so while MSFS is starting. FSUIPC7 does nothing with start menu's, so if that is bringing up a splash screen then something else is doing that. You can easily create a desktop shortcut to just start MSFS if that is what you want to do.

You have one Community folder, under R:\FS11\Community\. The C:\Users\alhar\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalState\packages\ folder is for the Community apps read/write storage area. These different locations are explained in the WASM section of the Advanced User guide. I don't have any experience with the Volocopter - I loaded it the first time (or maybe second) to look at your throttle question. I don't know much, if anything, about this aircraft. Getting warm here - outside temperature in the shade is 25C, and feels a lot hotter in the sun.... Have some gardening to do later, but I will wait until 7pm or so when its cooler...! Glad its now working. Cheers, John

Check any anti-virus software you are using (including WindowsDefender). I cannot see any reason that it won't run unless it is being prevented somehow, especially as you were able to re-run it previously. Also reboot first, just in case that helps.

The screenshot says its version 4.934, so you need to update. If FSUIPC is crashing on start-up, then this is normally due to a corrupt weather file. Try disabling weather by setting NoWeatherAtAll=Yes to the [General] section of your FSUIPC4.INI file. If this solves it then either your wxstationlist.bin file is corrupt, or one of the .wx files saved with scenarios is bad. To resolve this, delete all of the .WX files from your FS Documents folder (where your flights are stored), and the file "wxstationlist.bin" in your <user>\AppData\Roaming folder for FSX. If that doesn't solve your issue, please show me/attach your FSUIPC4.log file, and also your InstallFSUIP4.log file if this issue only appeared after updating. Why won't it run? What error do you get? If it ran previously, I can't see why it won't run again, You can try re-downloading the zip file, unzip it (don't run it from the zip file) and try again, And there is no need to delete any files.

This happens every now and again, but I am not sure why it happens to this version and not the previous version... If you can report this to McAfee, they should be able to check the file and once confirmed it is virus free they can add an exception so that it passes. Thanks for reporting. John

You assign to an axis in the left-hand side of the axes assignment tab (This side to send an axis value) : The right-hand side is to send specific controls/presets when entering/leaving axis ranges, and the axis value is not used (This side to send button controls). The Select for preset checkbox applies to both sides. It is positioned there as I initially only intended this to be used on that side, but as a side effect it can also be used for axis values, such as in this case. There is only one Community folder used by MSFS...I think you mean you are using the addonlinker program to control what is there.... John

What do you mean by this? Please give details. How are you doing this? What do you mean by "another 747"? Can you please attach your FSUIPC6.ini file so that I can see your settings. Also a log file showing your issue would be useful, with logging for Events and Axis controls enabled. The log file will probably be quite large so will need compressing/zipping. John

Before anything else, please make sure that you are using the latest (and only supported) version of FSUIPC, which is 7.3.20. If not, please update first and try again, and then attach the log files if the Volocopter throttle isn't working.

Can you please attach the full log files...and its the FSUIPC_WASM.log file I need to see, with Debug level logging, not the FSUIPC_WASMIF.log. I don't even know why you have that file - under normal conditions, the WASMIF/WAPI should log to the FSUIPC7.log file. Where did you find that file? And only set logging for Events in FSUIPC7 (and no other logging), and also set Debug level logging in the WAPI as well.

Just checked that throttle preset in the latest update and that is working fine here - please show me your FSUIPC_WASM.log file. As for the AP/Garmin in the Volocopter, I am not sure what that is (is it even a Garmin?)...I am not sure if it is possible to control this from external applications at the moment... John

If the problem is with FSUIPC7 not running, please see the README.txt or the Installation and Registration guide - you will need to update your VC++ redistributables to the latest combined package. Otherwise explain your issue with FSUIPC7 if that is the problem, or contact the support for your smartcars program. I can only support FSUIPC, not the programs that use it. And please take care to post in the correct forum for the product you are using. I have moved your post to the FSUIPC7 support forum. John

The SU13 update has just dropped, so I will get back to you after I have updated and checked things (tomorrow sometime). In the mean-time, can you activate Debug level logging in the WASM and show me/attach your FSUIPC_WASM.log file, as this will show what is being received and applied in the sim. See the WASM section in the Advanced User guide if you don't know how to do this. So do I - this is normal in the Volocopter. Different events are continually send for many MSFS aircraft. You can stop these being logged by using the DontLogThese ini parameter, preferably in your Volocopter profile. Again, see the Advanced user guide for details. Or you can safely ignore these. John

I can't really help if using PM - you should try PM support. Having said that, your issue seems to be similar to this (very old, but still valid) post: You can also try logging: set logging for Events (non-axis control) and also offset monitoring for the PM APU offsets (560F, 5624 and 5625). If you keep the logging console open (check Send to console window), you can then see what events (if any) are being used and how those offsets change when you operate the switch on the PMSystems screen. You can then try and duplicate that behavior. This is quite common for spring loaded switches - they only have one (single direction) or two (dual direction) buttons. If you need to send another value to an offset (or a control, or whatever assignment) when it springs back to the central position, then this should be assigned to the button release of the 2 buttons for the non-central position. Pete retired several years ago now. Cheers, John

For the Garmins (if they are functional/working in the Volocopter), both Asobo and WT, you can use the MF presets that are also included in FSUIPC7. You can use the MF HubHob site to search for the relevant preset:

@Oodi MenakerSorry for the delay. Could you please test the attached dll: FSUIPC6.dll Thanks and regards, John

Ok, so its the Pro Desk Sim add-on package that is providing the detents - that is what I was missing! Try the settings I gave and adjust as needed. As it is difficult to get an axis range value when using such a detent add-on, its probably easier to adjust the detent ranges in ini file directly (and reload afterwards - as per my previous instructions). Your problem is because you are using a specific axis value (FlapsStart = FlapsEnd) for each detent. an axis with 32768 values is never going to hit that value exactly every time on each detent, which is why you need a range around the (central) detent value for each detent. Ok, thanks. Pete didn't mind attached or pasted - the problem with pasted is that many people just post extracts, and pasting makes the topic a lot longer and IMHO more difficult to read. With an attachment, you know its the whole unadulterated content. Ok, no problem. John

Ok. Make sure that you understand what those lines are doing before you duplicate, as you will need to use the correct flags for each button, and get the parameter for the clear flag control (1004) correct to clear the flag for the button you are testing. John

The velocity uses the Lvar XMLVAR_VOLOCITY_COMMANDED_VERTICAL_SPEED for the throttle. To use this, add the following line to a file called myevents.txt in your FSUIPC7 installation folder (you must create this file if not already present): Velocity Throttle# $Param 16384.0 / (>L:XMLVAR_VOLOCITY_COMMANDED_VERTICAL_SPEED,·Number) The lvar holds values between -1 (full down) to 1 (full up), so as my throttle axis goes from -16384 to +16384, this code is dividing the axis input value ($Param) by 16384.0 to get the desired range. Adjust this if needed, depending upon your axis values range. Once you have created the myevents.txt file and have added that line, restart FSUIPC7 (no need to restart MSFS). Then assign your throttle axis to that preset - check the Select for Preset box and assign with Send to FS as normal axis and you should see the preset Velocity Throttle listed. John

It is easier for me if you attach files (rather than pasting contents), and also provide me with the log file I asked for... Presuming 5 is the Auto button, you need to duplicate and add a condition to entry 47. First try with the button flags, so use: You may also need to clear the button flags manually when you go back to the Auto position. If you need to do this (try without first), instead use: Not sure which way around it should be either - if its the opposite way, switch the 72471 and 72472 parameters around on lines 47.48 (first case) or on lines 47,49 (2nd case). John

Not sure what you mean...so each position gives a unique button press? How about the button release? How you program a 3-position switch depends on the releases as well as the presses. For example, if there are 3 buttons, 0 ( centre), 1(left/up), 2 (right/down): 1 <--> 0 <-->2 Moving from 0-> triggers button 1, so you would assign the appropriate mouse-click (left mouse) to button 1 press. If moving from 1->0 gives a button 1 release, then you can profram the right-mouse click for the release of button 1. Similarly you can assign to button 2 press/release, but with the mouse-click/codes reversed. If moving from 0->1 gives a button 1 press and release, you cannot do it this way, and the problem you then have is how to assign the centre 0 button/position, as this would need to trigger either a left or right change, depending upon where it came from. To do it this way, toy would need to overload your assignments (i.e. have to assignments for the 0 button), and a conditional test in each to determine which is used. If this is the case, you can initially try adding conditions to the button latch flags for buttons 1 and 2. That may work, but this again depends on how the buttons work. If it doesn't work with latch flags, you need to either find an offset or lvar that holds the button position and use that as an offset condition (you can add the lvar to an offset). Otherwise, and maybe easier, you can use your own offset and overload the assignments to button 1 and 2 to also update/set your own offset, and then you can use this with an offset condition on your overloaded assignments (you will have two, one for each direction) to button 1. Please see the Advanced User manual in using conditional assignments (actually called COMPOUND BUTTON CONDITIONS in the manual), as well as on using button flags and offset conditions. You can use logging for Buttons & Keys to determine when button presses and releases are triggered. Give the documentation a read and give it a try. I recommend you do this with the logging console window open so that you can see the logging in real-time. If you get into difficulties, show me what you have so far (i.e. attach your FSUIPC6.ini file) and also attach a log generated with logging for Buttons & Keys and Events (non-axis controls) activated where you just load the aircraft and then move the switch through its positions: 0 -> 1 -> 0 >- 2 -> 0 John