John Dowson

The updated version has just been released - let me know how many lvars you now see and if ASCRJ_FO_ARMREST_UP is one of them. Either way, I think its better, for the time being at least, if I load all available lvars. I'll take a look at this over Easter.

Ah - I forgot to add an extra receiving event for the additional CDA - I'll correct that shortly and upload a new version. Sorry about that.

Try with the attached - I've added a left mouse release to that macro thus: CS B757.MCRO

Are you using the new WASM with the new client (both have been updated)? If so, can you set both the WASM + the client to debug logging (using the ini files), load the CRJ and then list the lvars and then show me your log files (WASM + Client). Ok, but there is no output returned from that function. There's no way to see the lvars & values unless its picked-up by the WASM. Your log files should give me a clue.

I'm not sure I understand you.... You can set lvars using one of the setLvar functions. To get the value of an lvar, use the getLvar functions. The execute calculator functions only executes the provided code, it does not return any values.

You most likely need to add a mouse button release code. Can you show me your macro file please.

You can assign to the Throttle Inc and Throttle Dec controls on the right hand-side of the axis assignment panel, assigning to the Throttle Inc from 100 to 16383 and Up, and to the Throttle Dec from -100 to -16384 and Down (leaving -100 to +100 as your 'null'/dead zone - you can increase this if you wish).

Yes, I still need to look into providing hvar access via the SDK. And, as I guess you are using Paul Henty's .net client library that will also need updating. However, before I look at the SDK I will add the lvar/hvar access functionality to FSUIPC7, so it will be a while before I can get around to looking at the SDK. I also intend to provide a dll of the WASM API (WAPI) which can be used to talk to the WASM module directly (rather than via FSUIPC), so you could look into using that as a solution for the time being (when available!).

It is probably being display outside of your screen coordinates. Delete the Window ini parameter from your FSUIPC7.ini file, in the [General] section. Otherwise, if you hover over the FSUIPC7 icon in the task bar, you should see a pop-up of the main window which you can select, right-click and then move. Clicking the system tray icon should just show you the icon context menu. You need to double-click to open, or single-click and then select 'Show...'.

Did your installation complete successfully? Is your EXE.xml in the correct format? Are you using a steam or MS store version? What version are you using - is it the latest (v7.0.8, v7.0.8a or v7.1.0b)? There are so many posts on this now. Please review what I have already said on this topic before posting again (search the forum). And if you do post again, please include your InstallFSUIPC7.log file and your EXE.xml.

I have updated and release both FSUIPC6 and FSUIPC7 with this correction - please see the Announcements page. John

I have just released version 0.4.3. This supports of to 1022 lvars. There is also a minor change to the CDAType enum that may require code changes to anyone implemeting their own client.

All your settings are saved in your FSUIPC.ini file (so FSUIPC5.ini for FSUIPC5, FSUIPC6.ini for FSUIPC6, etc). You can also save your .key file (which contains your registration details) and any .lua or .mcro or .dll files that you use. Also, before you do this, make sure that you are using the JoyLetters facility. Your device GUIDs may change if you re-install windows, and it will be a lot easier to remap your settings if you are using JoyLetters.

I don't think that would work due to the way the WASM will automatically reload lvars on an aircraft change. Its a lot easier to handle if the WASM module already had the lvar lists available, rather than filtering on a call post-load....

You can use as many event files as you need. I was just thinking that you could split the events into different files, so AS1000 events in one file, AS3000 in another, etc. Then, if using something like SimStarter, you could just load the files for the events needed for the loaded aircraft. However, there is no issue having all events available for every aircraft.

I can increase to allow however many are needed, although updating to handle more than 1024 lvars is a bit more work. I can do this (in a later release), but before doing this I would also consider other possibilities to maybe reduce the number of lvars requested to those that are actually being used. Something like I proposed in the Announcement:

The joy ids used are assigned by windows and taken from the registry. They do not need to be consecutive. Do you actually have an issue?

How many lvars does the CRJ have? The WASM currently supports up to 876 lvars, I can increase this to 1024. I am planning to make a new release in the next few days anyway - with a few extra functions in the API (mainly a creatLvar function needed by FSUIPC), I will update to handle 1024 lvars in this release. John

Did you try just clicking Yes to allow FSUIPC to run? If it continues to mistrust the FSUIPC4.dll, see this FAQ entry: John Later: I see Pete replied at the same time!

As @jaxx says, please check you are using the correct version. If you still have the lua scripts active, the buttons will still be recognised but you will get two buttone presses - one for the "real" button and one for the virtual one (with device number 64 or 65). Of course, the UI will only show one of these, but if you 'ignore' the initial onw shown and press the button again, you will see the other. To prevent this, you should remove the lua scripts when using the 7.1.0a beta version and just use the "real" button for assignment.

P is the action (Pulse). B is the joystick - you are using "JoyLetters" so the assigned letter is used. The mapping from joyletters to ids is stored in the [JoyNames] section of your FSUIPC7.ini file. 35 & 32 are the button numbers K123/K122 are the keys (F12/F11) 8 is the shift parameter (normal) PB is <Action><Joy#> , or maybe better as <Action><JoyLetter>

The license applies to all versions. If you need the new functionality to directly assign more than 32 buttons, then yes, thats the version you need. However, the license is the same for all versions. Attached is a trial license valid until 10/04/2021. Just download and save into your FSUIPC7 installation folder. Note that this license will NOT validate in the installer. John FSUIPC7.key

I haven't really thought about this, but its open source, no restrictions, use an adapt as needed. Thats fine - I have no issues with using/changing or redistributing. A comment on the original source would be nice, but I'm also not bothered about that either really - use, change and re-distribute ad you like. I also have more of an idea how this can be used in managed c or, more generally, by any other language. I am aiming to upload a new dll library project in the next few days, that will use the currently provided API but expose them in a dll so that they can be accessed in other languages.

As Pete says, please see the documentation. If you are having issues, please show me your FSUIPC7.log and FSUIPC7.ini files.

Thanks - I added the links.