![]() |
|
#1
|
|||
|
|||
|
DirectOutput Designer Application
Hello,
I am programmer from Germany working on a DirectOutput Designer Application. The Application makes it possible to define Pages and uses events from games (currently lock-on only) to trigger actions like switching certain LEDs or displaying texts. It allows to connect Saitek Profiles to a configuration and certain pages and to save or load a configuration as "DirectOutput-Profile". Currently the application is developed under java using JNA to access the directoutput.dll. I can map most of the functions and the features of my programm work well with the X52Pro. The only problem I encounter is the identification of the device connected. As I understood the Device only holds a GUID from which I have to determine the device type and its abilities by myself. To get the GUID from a device I use Code:
Code:
Code:
I attached some pictures of the Application. But the Frontend isnt completely finished yet. Greetings rampage |
|
#2
|
|||
|
|||
|
First of all the GUID-Structure looks correct and secondly it also looks like all the information is in there.
29DAD506-F93B-4f20-85FA-1E02C04FAC17 29dad506-fffff93b-4f20-ffffff85fffffffa1e2ffffffc04fffffffac17 So I think it's the way you are turning the data in to a string that is causing the problem. Quote:
I hope this helps Dar ![]() |
|
#3
|
|||
|
|||
|
Thanks for the feedback. I believe the problem is that java has no unsigned numbers. Guess i got to convert the numbers to unsigned before converting them to a hex string. That would explain why field 3 is actually converted correctly while field 2 is not.
Last edited by rampagemt : 18th May 2010 at 13:07. |
|
#4
|
|||
|
|||
|
Looks promising,
Any change that there would be a way to let TS3 recognize one of the MFD buttons so you can use that button to scroll trough the channels on the server your on? Anyway, i am definitely going to keep an eye on this thread. |
![]() |
| Thread Tools | |
| Display Modes | |
|
|