John Dowson

License sent via PM. John

Any other assignment shouldn't affect this, unless the assignment is being triggered. Maybe check your assistance settings as these can affect things like flaps. I will take another look at some point to see if I can see any spoiler controls, or/and if the spoiler events have any effect.

Please see the section Gauge local variable access (L:vars), by macro on page 39 of the Advanced User guide. If using MobiFlight, you can also assign to just write the value to a spare/free FSUIPC offset, and gave a lua script that monitors the offset (using event.offset), and then when the offset changes you can update the lvar using ipc.writeLvar. You can also have an offset for reading the value of the lvar, by having another lua script that monitors the lvar value (event.lvar) and writes the value to an offset when it is changed. Better to have the read/write offsets as distinct offsets, although you could use the same one if you prefer.

Also, you should change this: to just so that the profile is loaded if you use a different variant.

I have this aircraft now and the throttle worked with my default throttle assignments - assigned with Send Direct to FSUIPC calibration using Throttle1 and Throttle2 controls. But this means that your throttle assignments should also work, so something else must be going on... The flaps lever has 3 discrete positions, and my default flaps switch assigned to Flaps Incr and Flaps Decr also works ok. Assigning an axis to Flaps Set also works, but exhibits strange behavior - using Axis Flaps Set works better. I don't see any spoiler controls....does this aircraft have spoilers?

So, the assignments are not working, nothing to do with profiles. For the throttle, try the Axis Throttlen Set controls, or the Throttlen Axis Set Ex1 controls to see if they work, Also, you can try setting logging for Axes Controls and see what is logged when you move the throttle in the VC, and then use that. I am more surprised about the flaps and spoilers. Does the aircraft actually have axis controls for these, or are they in discreet positions, so that you can only set them to a specific value and inc/dec them? If it does have axis controls, again try logging axis controls and see what is logged when you move the axis in the VC. Also, more and more aircraft are starting to use lvars for axis controls - for some strange reason...! Try listing the lvars to see if any look applicable. Your key assignments are also very strange: Each assignment is the same, and just runs a lua script. The lua it runs is waiting for an event: Each time you press one of those assigned keys, the lua script will be killed and re-started. If the script is handling the 12 key assignments, you don't need those keys assigned in FSUIPC7, and you want the lua script auto-started when the aircraft is loaded. I suspect this may be because your other lua script is maybe preventing the key press from being processed. Try activating logging for Buttons & Keys, make sure the Lua 12-Keys+AP script isn't running (you can temporarily assign a key or button to kill the script), and then try activating it. However, you don't need that script to log lvars in FSUIPC7. The easiest way yo do this is just use the Add-ons->WASM->List Lvars menu item. If you want to list them on a key/button assignment, use the List Local Panel Vars control. I don't have the Cockspur C510 so it is difficult to help with this further. If you continue to have difficulties, I can maybe request a press-copy license and take a look. John

That is logging from Buttons & Keys (which I didn't ask you to set). Did you actually set logging for Events? If so, and none were reported, just try the standard events I mentioned to see if they have any affect. No. I don't have a license for this aircraft - it is payware. John

You cannot assign an axis (left-hand side of the axis assignment window) to a non-axis control, such as Rotor Brake, as this doesn't make any sense, as you would be sending the axis value to the Rotor Brake control. If you want to assign an axis to a non-axis control, you would usually do this on the right-hand side of the axis assignment window, and assign to send one control when it enters a specific range, and another when it exists a specific range. So you can assign to send your Rotor Brake control (or preset) for lever up when the axis moves up into the range and then assign to lever down when it moves down into the range. If your axis range is the standard -16384 - +16384, and as I presume you will be using these axes like a lever, then you can use any range really, but I would suggest something like -12500 - +12500 for both your up/down ranges. John

By default, it matches in the aircraft title, which is defined in the aircrafts aircraft.cfg file, and logged by FSUIPC7 (in the FSUIPC7.log file) with entries such as the following: These are the names that are added to the profile when you create a profile or add an aircraft to an existing profile. Because you don't really need to, a FSUIPC will add the names (aircraft or folder name) for you - you can just edit these to get better matches on different variants of the same aircraft. The actual location will be either under your MSFS Official or Community folder, depending on whether the aircraft is a default/included one or an add-on, and will be under: <aircraft-folder-name>\SimObjects\Airplanes\<aircraft-name> All profiles are matched using the [Profile.xxx] sections in the main FSUIPC7.ini file. What do you mean by 'Doesn't seem to work'? Do you mean that the profile is not loaded? Any issues with profiles, please attach your FSUIPC7.log and FSUIPC7.ini files, together with the relevant aircraft-specific profile file if using profiles-in-separate-files. John

You may also need to send an event, with or without the lvar update. Set logging for Events in FSUIPC7 (Log->Events), open the console window (Log->Open Console) and see if any events are logged when you use the Avionics Master Switch in the VC with the mouse. If so you can use that. First try it on its own, as that may also trigger the lvar change (and animation). If not, you may need to send the control(s)/Event(s) as well as setting the lvar. You can do this by either overloading your assignment or creating your own preset. But first you need to determine which, if any, of the standard MS controls/events it is using. It would normally be one of the AVIONICS_MASTER_* events, but for some aircraft this can be a combination of various electrical events. I don't have the JF KingAir so cannot look into this for you, but if you try the above and report back any events you see, I can maybe help you set up a preset to use those events. Alternatively, you could ask about this on the MobiFlight Discord channel (under the HubHop support channel). Cheers, John

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.