John Dowson

Yes, you are free to do that - I will add a license file to the WASM package to say that it is free to use and redistribute. I was planning on also making the WASM open-source but I would like to give the code a good clean first as it has been through quite a lot of changes and there is quite a bit of redundant code, but I just haven't had time to do this so far. However, if any developers using the WAPI require any changes, I can either look into it or give them access to the github repo so that they can tale a look themselves. John

You posted in the FAQ sub-forum again, as you did with your first post (which I also responded to asking for further info but then you never replied back). I have moved your post again, but the next time you do this I will just delete your post. What version of FSUIPC are you using? Last time in was P3Dv4.5 with FSUIPC6.... Please see the section 'Multiple Joysticks for Multiple Pilots' in the FSUIPC Advanced User guide. Ah - I see Pete has replied... John

There are various zoom controls you can try: ZOOM_IN ZOOM_OUT ZOOM_MINUS ZOOM_PLUS ZOOM_IN_FINE ZOOM_OUT_FINE VIEW_ZOOM_SET VIEW2_ZOOM_SET

Do you mean mouse macros or a lua script? Or possibly an lvar macro? Sounds more like a mouse macro. if you can move in both directions, then why not have two mouse macro scripts, one for eaxh direction, and then assign to those? Alternatively, if you want to set each position explicitly, then you can use an lvar macro, e.g. a macro file containing 1=L:ovhd_ign_switch1=Set and then assign to that macro with the parameter (0,1,2,3,4) for each position.

Ok, thanks for the update. You log file does show that the ActiveSky library was loaded ok: John

Thanks - that is interesting, and different to what I see, but maybe because the file isn't blocked in my system. I do have a pending windows update, so I will take another look once I have updated. One last question - what version of windows are you running? I have windows 11 on my dev machine, I can check in windows 10 on my flight machines tomorrow as well. Thanks, John

Can you elaborate on this please. Which tab of the properties and which option are you referring to? Me neither - several thousand users have installed this without issue, so I am surprised about this, it must be something peculiar to your system. Anyway, glad it is now installed, but any further information that you can provide may be useful for others who come across this issue. Thanks, John

There looks to be an issue in your P3D installation: Can you uninstall the P3D client, install that again and try again.

Can you show me/attach your FSUIPC6.log file please.

Can you please show me a screenshot of this error as this is new to me. I need to see your FSUIPC6.log file, not the installation log. If no such file is created, then FSUIPC6 hasn't been started, This is very strange as well. The FSUIPC6 installer will detect if FSUIPC5 is installed and uninstall this the first time that it is ran, and it seems that you have ran this several times already. if you remove manually, you also need to check your DLL.xml file and remove the FSUIPC entry from there if present. What version of P3Dv4 are you using?

Ok. I have added code to load that dll if present, so you need to copy that dll to your FSUIPC6 installation folder and try the attached version. Let me know how it goes. John FSUIPC6.dll

Not sure how this works...how can they sync if moving two throttle levers independently? I will take a look at this in P3D/FSUIPC6, and compare this to MSFS/FSUIPC7, but this will be next week sometime. I will report back once I have taken a look. John

Yes, they are also available in v7 - why can't you see them?

Have you tried assigning a key press (or button) to the throttlesync controls? There are three such controls: Throttlesync On, Throttlesync Off and Throttlesync Toggle.

Check your task bar - it sounds like this is happening because windows is asking for your permission to run the installer, but the question isn't being displayed. When this occurs, you should see an icon for this in the task bar.

Sure, I can look into this. However, I don't currently have AS for P3Dv6. Do you happen to know what the AS dll file is called for v6? FSUIPC6 currently looks for one of the following AS dlls: as_connect_v5.dll, as_connect_64.dll or as_connect_v6.dll. John

You have installed FSUIPC6 under your P3Dv4 folder, which is under your Windows Program Files folder. You should not install there - please re-install into a non-windows protected folder and try again. FSUIPC5 is still supported but no longer available for sale. Do you have an FSUIPC6.log file - if so, and you get the same problem when re-installing into a different folder, then please show me that file. That is very strange, but I don't know how FSUIPC6 could cause this, especially if you get no such error with FSUIPC5.

Did you install the latest combined VC++ redistibutables? If not, please do that. Also make sure that you extract the installer from the zip file and that you are not trying to run the installer from within the zip file itself. Yes, this is correct. There is nothing wrong with the installer. Try downloading, unzipping and installing again. If you get the same issue, check any ant-virus software, including windows defender. Maybe that is preventing installation.

Yes, but this shouldn't happen.... next time, post and attach your ini as well as your .log file and I will take a look. You have one profile for the Cessna 208B, but this has an empty axes assignment assignment profile, so you will have no axes assigned when using this: You should either delete that (as well as the [Axes.Cessna 208B] section. And when you create profile-specific assignments, you should edit the aircraft names by shortening them to catch more variants. So, for the above profile section, you should change to: That is just an example. For now, I would delete that profile an exes profile section as it is empty. Yes - you are using quire a few presets for this (mainly for the G1000). When using presets, always better to use profiles, as many are aircraft specific. Ok to use G1000 presets in a general profile though, especially if multiple/most aircraft you fly use the G1000. Cheers, John

Your assignments are stored in your FSUIPC7.ini file (and maybe other *.ini files under your Profiles folder, if using profiles-in-separate-files functionality). Your settings will not be lost - MSFS updates will not affect FSUIPC settings. The usual cause of this issue is due to using exact aircraft names in profiles (rather than substring matching), which means that the same aircraft with a different livery (ir name) foes not match the profile. Or when an aircraft title/name has changed, possibly in an MSFS update, but this happens rarely. If you could attach your FSUIPC7.ini and FSYUPC7.log file, generated when you load an aircraft where you think the settings are lost, then I can take a look and advise. Please attach these files, when FSUIPC7 is no longer running and do NOT use the New Log function, as I need to see the complete log file. John

How did you do this? Why doesn't this work in MSFS/FSUIPC7? The problem with syncing throttles in this manner (i.e. setting a throttle value that is different from the one set by the assigned throttle axis position) is that is that any movement on the throttle controller can cause a movement in the throttle axis which would then send another value that would override the synced position. To prevent this, you would also need to disconnect the throttle axis (via offset 0x310A). Can you show me how you did this in P3D, and explain why this doesn't work in MSFS. Thanks, John

Ok, thanks. I can see them now on the HubHob site, all pretty new (9th July).

No, this is not clear at all. You are mistaken - there have NEVER been such options in the drop down. To assign to throttles 1 & 2, you assign as I have shown you, assigning the one axis to the two distinct controls. You do not say which version of FSUIPC6 you update from, but I can guarantee that no assignment options in the drop-downs have been removed. You do not seem to be responding to anything I am saying, and just keep repeating the same thing which I keep telling you is not true. I see no point in continuing with this conversation. John

Yes - you have to have Mouse Look enabled for those controls to work, as they toggle mouse look on/off only when it is enabled. As I said, for the focus issue I will ask P3D - but first I need to check in P3Dv4 and P3Dv6 to see if they have the same issue. Cheers, John

👍