John Dowson

Why is this different from your previous topic posted:?

No point running it if the entries are not there, but it won't do any harm either. Can you set a Log->Custom value of x200200 and show me a log with that logging added.

How are these knobs assigned? Do they work as expected when using Linda? If you can share how they are assigned, I can take a look. Also try activating logging for Events to see if that reveals anything. If using the FBW A320, many of the standard FS controls don't work as expected - check to see if there are any presets for the functions you want to implement on the HubHop preset site https://hubhop.mobiflight.com/presets/

Yes, your xbox one controller is recognised ok: Its the phantom one that is causing issue, same as in the previous post I refeenced: You could try running the attached regedit script to remove this, but I suspect windows will just add it back. I may look into getting FSUIPC to ignore such entries if this is going to be an issue, John removexboxcontroller.reg

What 'following controls'? They are not reset. Please see the section on profiles in the User guide. If your aircraft is already assigned to a profile, then the profile-specific checkbox will always be checked and inactive in the axis assignment panel. In the buttons and keys assignment panels, you can always check/uncheck the profile specific checkbox to see the profile-specific or general assignments, as all general button and key assignments apply to the profile, unless overridden. When first creating a profile, you are asked if you want to import the general axes assignments - they won't be available unless you do this. If you have any further questions, please attach your FSUIPC7.ini and FSUIPC7.log files, and tell me what assignment you think is being 'reset'. John

Why would there be conflicts with USB connections? Any program can request a connection to a usb device. FSUIPC supports HID joystick type devices directly, and other HID type devices using lua. But, if it is available to your program, you can do anything you want with it there, including writing to FSUIPC offsets. Maybe download FSUIPC and take a look at the SDK folder to see the tools provided for programmers. As your post relates to MSFS, I will move this to the FSUIPC7 support sub-forum. John

You still have the same issue - the throttle's GUID is being associated to two devices, one with the name 'CH THROTTLE QUADRANT' and one with an empyt name: This looks to be an issue with a phantom xbox one controller entry, the same as reported in this thread: The final solution in that thread was to leave the controller with an empty name, so you are now doing. I don't think there is much else to be done, but I will look into this issue further when time permits. John

As you are using MSFS/FSUIPC7, I have moved your post to the specific FSUIPC7 sub-forum. I have not heard of this issue before... There is a maximum number is SimConnect clients, which is defined by the maxClients parameter for each connection in your SimConnect.xml. However, this usually defaults to 64, which should be high enough, but there is a long standing issue where unused connections are not returned to the pool, so frequently re-connecting clients can exhaust the connection pool. For such issues, you should increase this to 128 or higher. You can check and increase this, but I don't think this will be your issue... You could activate SimConnect logging and check what errors you get there when this occurs. You can also attach an FSUIPC7.log file generated when FSUIPC7 cannot connect and I can take a look - I don't think it will tell me much but there maybe further logging I can add/enable to get more information. John

As far as I am aware, there is no access to z vars provided by the the SDK. But you say they are A:vars aka simvars....so what is the difference between a Z and and and A var? If they are treated the same via the SDK, then you can just use the facilities provided by FSUIPC to add any available simvar to an offset. Otherwise, if they are more like L:vars, then I would need to check if they were readable by the WASM and provide a mechanism to pass the values back to FSUIPC as I do with lvars. But I can't really say much more until I know more about what z:vars are and how they can be accessed. I don't see anything about these in the MSFS SDK documentation - do you have any references? John

This really should be possible....maybe take a look at these posts for other VRInsight devices John

First, you posted in the User Contributions sub-forum where it explicitly states Not for support requests. You also don't say what aircraft you are using. Many add-on aircraft can use custom controls and/or lvars, rather than the standard controls provided by the FS. If you want help with specific assignments, please attach your FSUIPC ini and log files, the latter generated showing your issue and with relevant logging enabled (e.g. usually axis controls for axes assignment issues and events (non-axis controls) for buttons a & key assignments). I provide extensive documentation. FSUIPC is a product that work with an huge range of controllers and all aircraft, and the configuration of each controller can be different for each aircraft and for each persons' preference. It is just not possible for me to provide specific guides for each controller or aircraft. There are plenty of guides for specific issues in the User Contributions and FAQ section, and I think there are also several user-posted videos on youtube on various issues.

Looks like you need to remove a registry entry...I'm finishing now (got to take the dogs for a walk!) - I'll post you a regedit file tomorrow. John

The data is as explained in the PMDG offset document - please see that to find out how to interpret the data.

The lua example I showed you should do the first part - you need to add the ability to write out the CDU_data array variable to a text file.

Not sure what you mean or what FSUIPC has to do with this....

I think changing the aircraft/livery name is not a good idea as any changes will get overwritten when you update. Just use multiple substrings, so that you catch each livery, e.g If you load an aircraft with a livery that is not matched, just add it to the profile using the FSUIPC UI. Afterwards, you can look at the ini and change the full aircraft name. FSUIPC will only add full aircraft names to profiles, even when using UseAirLocForHvars - I will change this at some point to add the folder name instead... This really isn't that complicated.... John

Why are you posting me ASP3D logs? It means nothing to me - show them to AS. You can post your FSUIPC log file here, not logs from other client programs. And the title of your post is very misleading. It is not working as you do not have it configure correctly, not due to FSUIPC. Is FSUIPC even running?

That picture means nothing to me. I support FSUIPC, not whatever that is. But, as that screenshot shows, do you have FSUIPC installed and running? If not, install it and run it and try again. If your issue is that FSUIPC7 is not auto-starting with MSFS, see Otherwise, tell me what your issue is with FSUIPC7, otherwise I suggest you try the support for the program you are using. John

If it works with LINDA, it should also work without, as that is built upon FSUIPC's lua facilities. See the appendix on VRInsight devices in the Advanced User guide, together with the additional document Lua Plugins for VRInsight Devices.pdf. John

Btw, if you have a keyboard where it is difficult to tell the state of the Num, Caps and Scroll lock, you can use this free utility: https://keyboard-leds.com/ That is what I use. It sits in your tray and shows the state of the locks and allows you to change the state easily, and is pretty customizable. John

Fixing the script how? Is this your issue? I don't see this at all and would need to see your logs to see why this is happening. The script works as expected here, although I find it very difficult to control using keys rather than a yoke or joystick... I think I also now understand why the Num5 key isn't working for you - you do not have NumLock on! I just tried with NumLock off, and the other keys still work but not the 5 key. So, either switch numlock on, or change the centreAllKeycode from 101 (Numpad5 with NumLock On) to 12 (Numpad5 with NumLock Off). Looks like the other numpad keys send the same keycode regardless of the NumLock state. Or, you can just add the following line to the bottom of the script to support when numlock is on or off: event.key(12, 0, 1, "flightControl") -- request on initial press only, NumPad5 with NumLock Off John

Can you try this one first - just start MSFS/FSUIPC, once it has started exit and show me your updated FSUIPC7.ini and FSUIPC7.log files and I'll see if a registry edit is needed. John FSUIPC7.ini

How do you want to read this data, and what do you want to do with it? If you want to read all of the CDU data, you can do this using a multi-dimensional array. Something like: -- Define the size of the array - we will start are indeces at 0 to make offset calculation easier CDU_Colums = 24 - 1 CDU_Rows = 14 - 1 -- Initializing the array CDU_data = {} for i=0,CDU_Colums do CDU_data[i] = {} for j=0,CDU_Rows do CDU_data[i][j] = 0 end end -- Read the data: 0x5400 == 21504 in decimal for i=0,CDU_Colums do for j=0,CDU_Rows do CDU_data[i][j] = ipc.readUB(21504 + i + (j*(CDU_Colums+1))) end end I haven't tried this! John

No - the only FSUIPC version compatible with FSX/FSX-SE is FSUIPC4. To determine what control is used for a specific button (FPS panel or otherwise), you can activate logging for Events (non-axis controls), open the logging console and press the button in the virtual cockpit. See if any event is logged, and if so, you can assign to that. If no event is logged, you could try using a mouse macro. However, not all aircraft support mouse macros - from the User guide: This indicates that mouse macros will not be available. If there are no standard controls/events and mouse macros are not available for the aircraft, you could look into using lvars. If you let me know which default aircraft you are using, I could take a look to see what is available for the GPS of that aircraft, John

Btw, if you did this in the FSUIPC_WASM.ini file located under your Community folder, this will get overwritten the next time you update FSUIPC7. Make sure that you have copied this file to your WASM persistent storage area so that this is preserved - see the Advanced User guide for details. John