John Dowson

What do you mean exactly? What "screen remains black" - your entire screen, or your P3D window? If you are in full screen mode, have you tried in windowed mode (Alt-Enter)? Have you tried hovering the mouse over the P3D task bar icon - this will show you if there are other windows - maybe there is a pop-up asking for something which is blocking the loading? Either way, please provide more information. You can always uninstall FSUIPC6 and get P3D working first, then install FSUIPC6 once you have P3D running correctly.

Ok, so something is working... I have an idea of what the issue might be. I'll look into this, but tomorrow now. I didn't know that but makes sense now I think about it! I can do that. I can provide both methods as they are trivial to implement. For the struct-array methods, would you prefer to pass in pre-allocated (with a size), or should the function allocate and the caller free the memory?

I don't understand that! All that I changed in your macro file was this line: 5=AP Disc=RX4000018d,3 to 5=AP Disc 5.1=RX4000018d,3 5.2=RX4000018d,13 i.e. I added a left button mouse release to your AP Disc mouse macro. This cannot/should not affect your other macros.... Please check that nothing else has changed, then activate logging for events (non axis controls) and buttons & switches, and generate a log file when you try to activate your your mouse macros. Then show me that log file together with your ini file.

Those are standard events that you need to request via Simconnect, ot you could use the FSUIPC SDK and use the offset area instead. Nothing to do with hvars. I have no idea what they are....! To log simconnect events, you could install FSUIPC and use its logging facilities, which are available in the unregistered version.

As I said, I haven't tested yet. I'll take a look over the next days... Thats fine, you can also just use 0 for the start event number and the default will be used, and if you can also give a 0/nullPtr for the logging function, and its own logging file will be created. Not sure why that is - I will take a look. John

I did this this morning, but haven't gotten around to test it yet...you could try with the following (you will still need the static lib): FSUIPC_WAPI.dllFSUIPC_WAPI.h As I said, its untested - I am planning to write a simple C client to test, but may take me a few days.... John

What do you mean - to get some sort of callback when a H var is activated? If so, then no, I don't think that is possible. Can hvars have values? I thought/assumed they were something you activated/set. You can do this using the WASM + API, but I have only included an hvar file or the A320Neo. For other aircraft, you will have to discover and provide your own hvar file to use hvars.

The scripts are available here: There is a beta release available with native support for up to 128 buttons. Please see John

This is certainly not possible with FSUIPC7. It is something you could possibly do using the developer console, and maybe by tweaking a config file somewhere, but I wouldn't know how to do this. You may be better of asking on the Asobo forums.

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: