John Dowson

No, sorry - the calc code executed by a preset is not currently logged in the FSUIPC7.log, only in the WASM log file. I will correct this at some point. Glad its all now working. Cheers, John

That is because you have Select for FS control checked - you need to check Select for Preset. See your last image. Note also that the preset drop-down takes a second or two to load, so once you click the drop-down ypi need to wait for it to be loaded. The preset menu is also very large - containing 10888 presets: I am looking into some UI improvements to make presets easier to find in such a large list. John

Ok, thanks for the update. Could you possibly let me know what the preset names for the DCDU are as this may help others who have the same problem finding these.

This seems to happen for some users with an Microsoft Store installed version of MSFS, and I do not understand why. The installer looks at that folder, using the %localappdata% environment variable, and if it cannot find the UserCfg.opt file then it reports that error. I think this is related to permissions and the (complicated) series of links that the MS Store version uses, but I cannot do anything about this, as far as I am aware. This error does not prevent you using FSUIPC7, but prevents two components being installed. If you cannot resolve this issue (sorry, but I am out of ideas as to what causes this) then you can install these two components manually. these are: 1. The FSUIPC7 WASM module. To install manually, first download the WASM module from www.fsuipc.com, or use this link. Extract/unzip the archive, and then move the fsuipc-lvar-module folder to your MSFS Community folder. That's it. 2. The Auto-Start component, which starts FSUIPC7 automatically with MSFS. This is done by a file called EXE.xml located under the same folder as your UserCfg.opt file. You can either create this manually or add an entry for FSUIPC7 to this file if it already exists. Complete details on the format of this file can be found in this FAQ entry. I always recommend trying a trial license with FSUIPC7 before purchasing. I can PM you one if interested - let me know. Cheers, John

Ok, I have taken a look an can see the issue. The ext.setfocus() lua call does change the focus to the main FS window, but the mouse-look controls are still applied to the sub-window and not the main window with the focus, and the only way to switch the mouse-look focus is to click in the window. This is very strange and I don't understand why. I will ask about this on the P3D forums. They should and I have checked this here (via button assignments though, not lua) and they seem to work as expected. Why do you think they are not working?

I have tried both the presets A320 Neo FCU ALT PULL, & A320 Neo FCU ALT PUSH in the FBW A320 stable and they seem to do the same as pulling/pushing the knob in the VC, although I cannot confirm this 100% as I do not fly the A320. Can you try assigning to another preset to see if any presets are working for you in the FBW A320 stable. I suggest you try assigning a button or key to the following presets as it is easy to see the result: A32NX_FCU_ALT_INC & A32NX_FCU_ALT_DEC. However, note that there are two presets each of these, with the same name. Make sure you assign to the second one in the list as the first one is for the dev version, not the stable. John

@zap737 Did you resolve this issue? What was the problem?

I have just installed the DA62X improvement mod and tested this, and it is working as expected - well, nearly. The only problem is that the aileron axis is reversed, so the presets need changing to the following to account for this: Otherwise it works as expected. This is my aileron assignment to the preset: John

You keep on saying the same thing, which is not correct. I have explained and shown you how to do this in my previous post, and you must also have done this with your previous throttle. What is not clear about my previous explanation on how to do this?. Can you explain in more detail why you cannot assign as I have advised?

Why not? You can assign an axis to up to 4 distinct controls. Check the checkbox next to the first first checkbox and select Throttle1, then check the checkbox for the second dropdown and select Throttle2. This is the same as you would have assigned to your previous throttle. I do not understand why you are having such difficulties... John

So you replaced the FSUIPC WASM? If so, you probably just re-installed it then. Shouldn't be necessary but foes no harm. I will check to see if the presets for the stable version of the FBWA320 are working later today and let you know. John

Does the lvar actually change value? Uoi can use the Add->ons->WASM->List Lvars menu option to see the lvar values. You can remove such messages that are continually sent by adding DontLogThese=67227 to the [Genera;] or (better, as such messages are aircraft dependant) to your [Profile.xxx] section. The log file is always created - you just need to change the logging level by setting LogLevel=Debug in your FSUIPC_WASM.ini file. Are any presets working for you? This really should not be that complicated.... I will install the mod later and check that this is working.... John

What was your problem?

That is not needed. Your problem is with presets, not PMDG offsets. MF presets are provided by the events.txt file, and your log shows that this is not installed: This is usually installed by default, unless you uncheck this option. So either you manually opted not to install this, or there was an error during installation. In the case of the former, re-install FSUIPC7 and make sure that you select to install this file (or accept the defaults), and in the case of the latter please show me/attach your InstallFSUIPC7.log file. John

👍 As I said, I am surprised that the setfocus call doesn't move the focus to the main FS window. I will check this later in the week. May also be worth trying two consecutive setfocus calls... Cheers, John

You can remove those. You just need for entries for each device - two (name and GUID) with the letter and two with the id. You can remove everything else, but take a backup first in case you remove the wrong entries... Do you use any additional software for the Razer Tarturus? If so, that may have updated the name in the registry when it was installed, so you could try r-installing that, if applicable. If you do this, it may also require a manual update of your ini, aa both the name and GUIDs must match between the id and letter entries. The new name will be picked up for the if entry, but you may need to then manully change the name in the letter entry so that they again match. Cheers, John

So you didn't have the WASM installed when you tried the presets? If not, this is why the presets didn't work. It is the WASM module that applies the preset calculator code to the aircraft. And presets will also not be loaded if the FSUIPC7 WASM module is not installed. So I am getting more confused.... And why are you installing the WASM manually? The WASM module is installed (by default) by the FSUIPC7 installer. That depends on what you want to do. The WASM menu entries are used for testing lvar/hvar/caculator code. Presets are far easier to use than lvars/hvars on there own, And (almost all) presets are aircraft specific - you need to use the presets defined for the aircraft that you are using. I suggest you try using presets again. And please familiarise yourself with the WASM section in the Advanced User guide, which will tell you how to use presets as well as lvars and hvars. If they are not working, then you are either using the wrong preset or have an issue with your assignments. I suggest that you double-check everything and try again. If it still doesn't work, activate logging for Events and WAPI->Debug and generate a short FSUIPC7.log file where you just load an aircraft and then press a button or key assigned to a preset (that isn't working) and then show me that file together with your FSUIPC7.ini file. Note also that I only supply the mechanism to implement presets, and do not control what the preset actually does. This is a community effort led by MobiFlight, and questions on specific presets should be directed to the MobiFlight discord channel. But you need to make sure that the preset mechanism is working for you first. John

If you have changed this you may need to delete some files manually. The files managed by FSUIPC will be listed under the [AutoSave] section in your FSUIPC4.ini file. You can use a free program called Everything that is very useful for finding files - available from https://www.voidtools.com/ They should be in the following folder, relative to your main Steam folder: steamapps\common\FSX\Modules John

I think you mean Mouse Look, not move. I thought this would set focus to the main FS window - it surprises me that the focus stays with a sub-window. I will check this at some point. Yes, sorry - looking further at this it seems that this restores the focus to the previous window that held the focus, after it has been moved to another window. Why don't you move it to a corner rather than the centre, i.e. use mouse.move(0, 0, 2). There should not be any switch in that position. I will do some tests on the focus movement in P3Dv5 later this week, when I have time, and will report back. John

Are you using the Advanced Mouse Controls option in P3D? So ext.focus(0) and ext.focus() do not set the focus back to the FS main window? If not, where does the focus go - does it change at all? You could also try using the key focus restore control (1125), i.e. ipc.control(1125). But you can still do/try this when controllers are enabled in P3D,,,I can't see what having controllers enabled in P3D has anything to do with this....

As I said, please tell me the name of these presets. If you open your events.txt file in an editor, do you see the presets in the file? All presets in this file will be loaded.

No, don't delete anything if you do not know what you are doing. The Missing joystick message is because you have an assignment to that letter. You need to change the letters if the GUIDs to match your assignments. If you show me your files, I can do this for you. You shouldn't disconnect and re-connect when FSUIPC is running. Moving devices to a different USB socket/hub can sometimes cause ids to change, but you should be ok with this as you are using joyletters for your assignments, not the ids. Best to show me your files for FSYUPC6 as well and I can update for you. You shouldn't need to redo your assignments.

They will be in your FSUIPC4 installation folder, which is the Modules folder under your FSX installation folder.

They are preset names, available in the assignmert drop-downs once you have checked the Select for Preset checkbox. Please see the WASM section in the Advanced User guide on how to use presets, as well as lvars and hvars. Again, please see the provided documentation. However, if you are unfamiliar with hvars (and lvars), it is easier to stick to using presets (as these can use both lvars and hvars, as well as other variable types).

Please first tun regedit and take a back-up of your registry. Then, disconnect all of your devices. Run the attached regedit script - just save it and then double-click it in windows Explorer to run it: removeDevices.reg Then reboot and re-connect your devices and try again. Any issues, please show me all 3 files - log, ini and JoyScan,csv.