Leaderboard

Yes - its just a name (string) attached to the calculator code - you can use whatever is appropriate. You can also give a fixed value rather than using a parameter ($Param) if you prefer, and have several presets each setting a different fixed value. John

Thanks John I have reverted back to an earlier version which accepts fsuipc to assign cyclic controls via aileron elevator and also axis cyclic longitudinal and lateral I posted a bug report regarding the cyclic issue. Cheers Rhys

Hi Ray, That offset is just for the 'Fuel Tank Selector', and it is not a custom control. To set this, you would use the Offset Word Set control. To empty the tanks, try writing 0 to the tank level offsets (using Offset Dword Set😞 John

Well, its added now - but I may make this dependent on an ini parameter, as I said. John

You can limit the range of the axis by manually editing the FSUIPC calibration entry. If you assign and calibrate the spoilers, then open and find the calibration entry: It will look something like this: You can decrease the minimum value and increase the maximum value to fool FSUIPC into thinking the axis range is larger than it is, and then the calibrated down to the standard -16384 - +16384 range. So, for example, if you doubled the top range: Spoilers=-16383,32768/16 the axis would only move half way through its positive range as your axis input value of 16384 would be calibrated to 8192.Try different numbers to get the range you require (change this when the FSUIPC axis assignments or calibration window is open, and click to reload your settings once the changes have been saved). John

Useful for me to see why it failed. Looks ok/valid on a first look, so not sure why its failing. May help me to improve the install process if its failing on a valid xml file. I will look into it further when time permits. Cheers, John

Ah, got it. I've attached the file here but again, no big deal since I already have it working after adding FSUIPC myself. Brilliant with the discount, will get a new license right now 👍 Enjoy the rest of your weekend John and great to see you're still around in the FS community after all these years 🙂 EXE.xml

Do you mean Hvars? And if so why is the title of this topic 'Lvars'? K-type variables are events, B-type Input Events, etc. You can use both H (HTML) and L (local) type vars in FSUIPC7, either directly or using presets / calculator code. The easiest way to use hvars is via calculator code really. There is no actual way to discover the available hvars for the loaded aircraft, as there is with lvars, so the way this works in FSUIPC7 is that you have to let FSUIPC7 know which hvars you want to use by providing a *.hvar file (some are included as an example). This is documented in the Advanced User guide, under the WASM section. Once a hvar is known to FSUIPC7, you can use it either in a macro or a lua script. But these days almost everybody uses hvars via presets (calculator code). You can define your own preset to trigger a hvar: in the myevents.txt file, e.g. Trigger_My_Hvar#(>H:hvarName) Then assigning to the preset 'Trigger My Hvar' would trigger/set the hvar ' H:hvarName'. See the documentation for further information. Also take a look at the available presets in the events.txt file as many of these will use hvars. You can find available presets by pressing the Find Preset button in the assignments windows once Select for Preset is selected/checked. John