pilotjohn Posted December 11, 2022 Report Posted December 11, 2022 Is it 16 (64-79)? I'm trying to space my panels out. Thanks!
John Dowson Posted December 12, 2022 Report Posted December 12, 2022 I think you can have up to 300 devices in total, virtual or otherwise, with 256-299 being reserved for VRI, and 0-15 for standard joystick type hid devices. John
pilotjohn Posted December 12, 2022 Author Report Posted December 12, 2022 I'm specifically asking about the FSUPIC specific range that starts at joystick #64 (via offset 0x3340)? Based on the 36 bytes, it seems to be 9. Is there a way to use more somehow?
John Dowson Posted December 13, 2022 Report Posted December 13, 2022 Offset 0x3340 only supports up to 9 devices, as you say. You can use offset 0x7F00 which supports up to 16 devices with 128 buttons. John 1
pilotjohn Posted December 16, 2022 Author Report Posted December 16, 2022 @John Dowson Thanks... I tried to use 7F00 with the client libraries, but FSUIPC doesn't seem to be reacting to them. Any thoughts on whether this is a client library or FSUIPC issue? Or me? I posted a thread here:
John Dowson Posted December 16, 2022 Report Posted December 16, 2022 I don't know...those offsets have been around for quite a while now, so I don't think it is an FSUIPC issue but I can check. However, I am away from this afternoon, back next week, so it will take me a while before I can take a look at this in detail. Keep me updated if you find anything, otherwise I will report back once I have checked that offset area (mid to end of next week), John
pilotjohn Posted December 16, 2022 Author Report Posted December 16, 2022 So I used the client library's FSUIPCExampleCode_CS project to test this out by modifying the BC004_WritingOffsets example. 0x3340 triggers and logs, 0x7f00 does not. This removes StreamDeck and my original setup/code from the equation at least.
John Dowson Posted December 22, 2022 Report Posted December 22, 2022 Sorry but I still haven't had time to look into this.... I am on holiday now, until the 3rd January, but will try and look further into this issue next week, when time permits. I will report back again once I have investigated. John
pilotjohn Posted December 22, 2022 Author Report Posted December 22, 2022 49 minutes ago, John Dowson said: Sorry but I still haven't had time to look into this.... I am on holiday now, until the 3rd January, but will try and look further into this issue next week, when time permits. I will report back again once I have investigated. John Thanks... please let me know if you need me to test anything.
John Dowson Posted January 4, 2023 Report Posted January 4, 2023 Ok, I have now looked into this. Offset area 0x7F00 is badly documented, and is for real joysticks not virtual ones. Basically it is a copy of the facilities provided at offset 0x03C0, but for joysticks with up to 128 buttons, not the facilities for virtual joystick buttons provided at 0x3340. I will correct the documentation. So, for your original question: On 12/11/2022 at 11:20 PM, pilotjohn said: Is it 16 (64-79)? I'm trying to space my panels out. For virtual device access via offsets, it is only 9 (64-72) and via offsets 0x3340 and 0x29F0. This provides access to 288 virtual buttons. Sorry for the confusion, and the time taken for me to look into this. Regards, John
John Dowson Posted January 4, 2023 Report Posted January 4, 2023 ...and I won't be increasing this. Too many changes would be needed to support more, especially considering WideClient....I am afraid you will be limited to 9 virtual devices for external triggering. John
pilotjohn Posted January 4, 2023 Author Report Posted January 4, 2023 Ugh, ok thanks for looking into it.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now