John Dowson

What do you mean by "nothing"? Do the lvars/hvar work when using them directly, but not via assignments? Or do they just not work? What have you tried?

The logitech yoke and pedals are probably the most common yoke/pedals out there. Thats also what I used until recently, and it shouldn't be a problem setting them up on FSUIPC5. The assignments in FSUIPC6 are the same as in FSUIPC5. You should consult the User Guide, section The Easy Step-by-Step Way to Calibrate Your Controls. You should be able to calibrate to use the full range of your yoke. Calibration "slopes" are lso provided, so that you can make it more or less sensitive at different stages of travel. This is also available in FSUIPC5. Yes, brake calibration facilities are also provided. However, we don't allow you to sync left/right brakes - they are differential brakes after all. But you should be able to calibrate so that they useable. Really, its is best to just try. You could try setting your yoke/brakes up with P3Dv5/FSUIPC5 first. Otherwise, I could supply you with a trial/time-limit license to try FSUIPC6 if you prefer.

Yes, that is correct. Many aircraft continually emit certain events, with the events being different depending on the aircraft. You can such events using the DontLogThese ini parameter. Best to use in a profile. See the Advanced User Guide for details. No. But you have only assigned to the ALTITUDE_SLOT_INDEX_SET control. That should just switch to 'Managed' mode (as parameter=2). Doesn't it do that? Have you tried changing the altitude using the AUTOPILOT ALTITUDE LOCK VAR (offset 0x07D4)? And what does AUTOPILOT ALTITUDE LOCK VAR:3 hold (offset 0x0818)? Maybe try logging those offsets (using Log->Offsets... facility) and also try setting the lock VAR (LOCK VAR:3 is read-only). You can maybe also try using hvars to pull/push the VS knob - best to initially try using the WASM->Execute Calculator Code functionality. You can try with the following: to pull: (>H:A320_Neo_FCU_VS_PULL) to push: (>A320_Neo_FCU_VS_PUSH) They are the hvars in the current A320.hvar file. However, not sure if thats up to date - if they don't work, you can try the following: (>H:A320_Neo_FCU_VS_HOLD) (>H:A320_Neo_FCU_VS_PUSH)

And what happens if you try to increment with a different value using the Set Lvar... menu option? If you can set there, it should be the same via assignments and you are doing something wrong. Again, logging would help. And are you using the FBW mod or the stock A320? If the stick one, you should try the FBW mod instead. What does this mean? If you want to change the value based on the existing value, you would need to read the value first, apply whatever multiplier (ot function) you require, and then write the value back. If you want to do this, you would have to use a lua script.

Ok, but strange, Maybe you just needed to restart FSUIPC, or reload yout assignments if manually changing your files while FSUIPC is running.

You could try reading the WASM section in the Advanced User Guide... You need to set the LogLevel ini parameter to Debug in both your FSUIPC7.ini file (in [WAPI] section) and in your FSUIPC_WASM.ini file ([General] section).

If it works through the lvar menu, it should work using macros. Please activate debug logging for the WAPI and WASM, change the value using the lvar menu, then try changing using your assigned button or key. Then show me your FSUIPC7.log and FSUIPC_WASM.log files, together with your FSUIPC7.ini and macro file. Alternatively, if not using the latest FSUIPC7 beta (see Announcements section), you could try that and add the lvar to a free user offset, and assign your button to an Offset * Set control .

If changing the lvar doesn't change the switch, then no, you can't do it this way. You should try setting lvars manually (using the Add-ons->WASM->Set Lvar... menu entry) to see if they work before attempting to use them. You should try using the standard controls. Please see my previous comments and the link provided.

Please read the provided manual/instructions. The format of yout macro is wrong. It should be: [Macros] 1=L:XMLVAR_Autopilot_Altitude_Increment=Set,1000 Or, better, just: [Macros] 1=L:XMLVAR_Autopilot_Altitude_Increment=Set And then provide the parameter (1000) as the parameter to your assignment. In this way, you can assign it to one button with a parameter of 1000, and another with a parameter of 100.

As I said, you need to determine what is showing that pop-up. You should be able to do that from the task bar - did you try? It would help if you also showed me your FSUIPC6.ini file.... However, your log shows that there was an error starting ProSim: So, if FSUIPC didn't start prosim, something else did. If FSUIPC didn't start prosim, it won't be able to stop/kill it when terminating. Could that message therefore be from ProSim that has lost its FSUIPC connection as FSUIPC has terminated? The error reported (Error=2) indicates 'file not found', which is the error FSUIPC is receiving from windows when trying to execute your ProSim run command.

Was FSUIPC already running when you did this? If so, try either restarting it or 'Reload' your assignments. If its still not there, check the extension is. .mcro - if its not, it won't be recognised. You can take a look at your FSUIPC7.ini file, in the [MacroFiles] section, to see if your file is listed - if not, it is not named correctly or is in the wrong location.

First, your log file is in the same location of your FSUIPC7.ini file. in the FSUIPC7 installation folder. This is the location you selected or accepted during the installation process. If you don't know where this is, you can use the File -> Open Installation Folder... menu option. If you can't see the FSUIPC7.log file there, you probably have windows explorer et to hide known file types. If this is the case, see the Addendum in the Installation and Registration guide (Identifying Files in Windows Explorer). And you should not need to edit the FSUIPC7.ini file except for some more advanced uses. You can assign most things via the UI. Which aircraft are you using? Try activating logging for Events (Log -> Events), then open the console (Log -> Open Console). Then operate the functions you want to assign in the UI, and you will see what event the loaded aircraft is using (it can be different for different aircraft). Then, knowing what events are logged, you can then assign to those to controls via your devices. For further help, please let me know what aircraft you are using and what you want to control/assign. Also, please see the provided documentation, and for further help please attach your FSUIPC7.log and .ini files and let me know what you have tried and what your issues are.

The same location as in all versions of FSUIPC - in the FSUIPC installation folder. If you don't know where that is, use the File -> Open Installation Folder... menu option. If using lvars, you may want to look into using the latest FSUIPC7 beta (if not already) that allows you to add lvars to free user offsets for reading and writing. See the Announcements section for details and to download. John

Please show me your FSUIPC7.ini file. Also, please activate logging for Buttons & Keys as well as Events and generate a short log file showing your issue, i.e. turn each of your encoders to show your issue, and attach the FSUIPC7.log file generated.

64. Thanks for the update.

But don't the controls do what you want - i.e. either increment by 100 or 1000, as you want? If you want different sized increments, you could use one of the Offset <size> Increment/Decrement controls (where <size> is the size of the offset, probably a dword). Maybe try with offset 0x07D4 (Autopilot Altitude Lock Var). In the A320, you may have to switch between managed and selected modes (using the ALTITUDE_SLOT_INDEX_SET control). There may be more info on this on the Asobo forums, e.g. https://forums.flightsimulator.com/t/a320-fcu-variable-autopilot-altitude-lock-var-vs-displayed-altitude/307093/7 John

It pointed to that folder as that was the previous installation location (as you had it installed there for both v4 and v5) and the installer will always default to the previous installation location. But it IS possible for you to change this - the installation page after the component selection page (in the installer) is the 'Choose Install Location' page, where you can select the destination folder by using the Browse... button. What you cannot change is the location of the add-on.xml file, as this is defined by P3D. The problems you encountered were due to the fact that you installed for both v4 and v5, so used a single installation folder. When you ran the installer again, to install v4 into a different folder, this would have ran the uninstaller first and uninstalled, and then the default folder for the v4 install would be the v5 folder. You could have changed this, but didn't. And it would have also replaced the uninstaller (*for both v4 and v5) in that location with the v4 uninstaller just created. If you then ran the installer again, to install for v5, this would detect the v4 uninstaller and run that, so v4 would be uninstalled when installing v5. So, the problem in the installation/uninstallation is that if you want to switch back from using a shared installation for both v4 and v5 to separate installations, you should first manually run the uninstaller to remove and then run the installer twice, once for v4 and once for v5. Well, you may have problems in future (when updating) doing this as the FSUIPC registry entries will not be correct. You should delete and use the installer. Uninstall everything first (using the uninstaller first and then manually removing everything), and then install again using the installer, running it twice if separate installations required. And it is highly recommended to choose an installation folder outside of your P3D add-ons folder, and outside of a windows protected folder, e.g. C:\P3D Add-ons#FSUIPC6 (for shared location) or C:\P3Dv4 Add-ons\FSUIPC6 (for v4 only location).

As the lvar name is the macro entry name, you should not have the same lvar more than once on a macro, especially if using the same action. No, the set values have never appeared in the drop down list. Its usually just the name which should be sufficient for you to identify the action, but in the case of single lvar macros the action is also appended to the lvar name. "Macro invocation" just means when the macro is ran, so when you run the macro, the parameter is copied to the lvar (or, in other words, used to set the lvar). It refers to the parameter however it is supplied, in the macro file or in the assignment. You can do things either way, but better to leave the parameter off in the macro file and just set the parameter in your assignment, i.e. just use: [Macros] 1=L:PITOT_L=SET 2=L:PITOT_R=SET - and you must do it this way if using the same lvar and action with different parameters, otherwise there is no way to distinguish the different entries.

Hi Ralf, Ok, thats good! No idea. Sounds very strange, but that can't be anything to do with FSUIPC. Did anything else change? Try uninstalling FSUIPC (just run the uninstaller from your FSUIPC7 installation folder, or from the windows app management panel) to see if the problem is still there - I suspect so. You can re-install FSUIPC7 again in the same folder - it only rakes a minute or so. Greetings from Galicia! John

First, you posted in the wrong forum. I have moved your post for you. Second, you posted your key in a public forum. This invalidates your license conditions and your key can be banned for doing this. Please, NEVER post your registration details, especially your key, in a public forum. I have removed it from your post. As for your issue, did you enter all 3 fields exactly as written in your purchase email (with the key being 12characters, so no hyphens)? If not, please try again. If you still have issues, post again and Pete can check your details from your order number (I have no access to your details as FSUIPC4 is still with Pete).

What about the instructions isn't clear: ? So, uninstall any of the 2015, 2017 or 2019 ones that you have installed, and then download and install BOTH combined (i.e. 2015+2017+2019) versions (x86 and x64) from the provided link.

First, you posted in the Announcements section, where it explicitly states Not for support requests. I have moved your post for you, but please take care to post in the correct forum in future. K variables are for "key" events, i.e. either standard MSFS events/controls (as listed in the Controls List for MSFS Build 999 text document ) or add-on custom controls, which contain a period. That one looks like one of the latter (as it has a period). Is that an event from the FBW mod? It looks to be, as MF events, handled by the MF WASM, are usually preceded by 'MobiFlight.'. You could try to use add-on custom events in FSUIPC by using "event files", and is explained in the Advanced User Guide, section Add-on Custom Events, P36. Basically create a *.evt file (e.g. A32NX.evt) in your FSUIPC7 installation folder, and add the following content: [Events] 0=A32NX.FCU_HDG_INC The event should then appear in the assignments drop-down menu for you to assign and try.

Which offset is it using to drive the sound? If you know what that is, and if it can be changed, you could maybe do something.... I think the animation is driven differently - I doubt very much the animation is driven by the simvars on the gear position... I don't know if this is a "problem" - more probably just the way the model/animation works. If the sound is driven by an offset and you can change the offset, you could have a lua plug-in which copied the values from the original offset to a new offset but added a delay before doing this. You can then use this new offset, to drive the sound, if that is possible. Or ask them to make the offsets configurable. Then you can control what is written to the offset and when, either by using a timer or possibly a different event or simvar, if there is something that can be used to detect when the retraction has started and completed that matches the animation.

If it was previously working, what has changed on your system? This error is usually caused by missing or corrupt VC++ redistributables, and you need to uninstall and re-install. This is explained in the README.txt file that is included in the zip you downloaded: John

FSUIPC knows nothing about the visual information. FSUIPC will be receiving events and/or simulator variables (simvars) from the FS and updating the relevant offsets. What is the Bas Shaker using to drive the sound - is it using FSUIPC? There isn't anything we can do in FSUIPC - we just show the data as received from the sim, or send the event to control the start of the open/retract. Just checked the BFF Bass Shaker V2 page and it seems it comes with its own configuration software, and it talks to the FS directly, not using FSUIPC. I think you should maybe contact their support for this.