kjg71
09-12-2007, 11:19 AM
Hi all,
I actually have never asked this question before, but after being invited to the Open Source Motion Forum it kind of got me thinking about the software side of things and the question as to which method is the best and why for motion control.
(BTW thanks for the invite -- I plan to share any of my hardware designs for sure)
so....let me draw attention to the software side which has provoked the big question.
When it comes to game control, there are generally two methods for interaction.
1. Game Data Method
2. Game Controller Method
I have chosen the later for now as it works with all PC games as well as provides all the information needed for representing most of a vehicle's motion.
Game data is a future method that I would be looking into because when all the hardware is working and runs to satisfaction, I would welcome the extra motions that only game data can provide.
Game data extraction method seems to be a proverbial favorite amoung many (if not all) motion cockpit builders, yet it does requires so many more things to be in place....... maybe I am wrong?
From my humble opinion, Game data appears to require that the target game have a method of built-in (or at least capable of) communication through third-party data extraction. This method requires an active involvement with the actual game developers or with individuals who are skilled in programming this functionality. Optionally, some of the popular sim titles seem to have public game extraction software created for them already which can make things much easier for those specific titles and many of you are using these currently.
The Game controller method on the other hand allows you to control your motion with literally thousands of more titles which opens some real posibility for great legacy games including space sims or even newer games in which the developers are reluctant to provide such game telemathy.
Now, this is just a personal opinion, but it seems that it would be easier or at least advantages to develop game controller apps for motion cockpits because at the very least you can test things out while playing a game before having to focus on the game data hooks and everything associated with those.
Game controller control also does not need encoders which can save on time and extra hardware if your just starting out. Now, with no encoders it is basically a "follow the stick or pedel" method with limiters for your range end, but I have not seen that the accuracy of encoders is needed unless you want to go half way through a move like a half roll and then hold. Certainly this would add more fine tuning, but it's seems to be a good enhancement more then a requirement. For game data, encoders and the code/electronics for them are certainly a requirement.
Again, I am not condeming game data as it is certainly beneficial because it can yield some very unique effects and if its offered, by all means tap into it.....but is it the only one that makes sense?
Below is an overview that compares the two (again my observation) Please offer some comments because I am just wondering why motion simmers have "game data" as a preference
Maybe it is that all the games that most motion simmers would want to play does have game data apps available?
maybe I am just thinking along a different line?
here is the list:
Game Controller Actions
Accelerating
Braking
Rolls
Climbs
Dives
Turns
Lifts
Drops
Landing Gear/Boost
Game Data Only
Turbulance
Ground Textures
Taking Fire
Physical Bumps
Crashes
For any of you that have worked with both, Does game data pervide a better experience for the Game Control Actions listed above?
So there's my question/s I certainly have game data control on the radar, but for know I am focusing on game controller control cause it seems to be a good fit. But maybe it is all personal preference or maybe there is some other a reason why many have stayed away from this method?
I also just went to X-sim site and looked at how they handle the game controller method and it seems they do but are saying:
"d) if your a game does not support ForceFeedback you can use either a game specific plug-in or your joystick movements (not recommended)"
Hmmm .......again not reccomended.
Has anybody played around with game controller control in X-sim or even your own home grown app?
Regards Kyle
I actually have never asked this question before, but after being invited to the Open Source Motion Forum it kind of got me thinking about the software side of things and the question as to which method is the best and why for motion control.
(BTW thanks for the invite -- I plan to share any of my hardware designs for sure)
so....let me draw attention to the software side which has provoked the big question.
When it comes to game control, there are generally two methods for interaction.
1. Game Data Method
2. Game Controller Method
I have chosen the later for now as it works with all PC games as well as provides all the information needed for representing most of a vehicle's motion.
Game data is a future method that I would be looking into because when all the hardware is working and runs to satisfaction, I would welcome the extra motions that only game data can provide.
Game data extraction method seems to be a proverbial favorite amoung many (if not all) motion cockpit builders, yet it does requires so many more things to be in place....... maybe I am wrong?
From my humble opinion, Game data appears to require that the target game have a method of built-in (or at least capable of) communication through third-party data extraction. This method requires an active involvement with the actual game developers or with individuals who are skilled in programming this functionality. Optionally, some of the popular sim titles seem to have public game extraction software created for them already which can make things much easier for those specific titles and many of you are using these currently.
The Game controller method on the other hand allows you to control your motion with literally thousands of more titles which opens some real posibility for great legacy games including space sims or even newer games in which the developers are reluctant to provide such game telemathy.
Now, this is just a personal opinion, but it seems that it would be easier or at least advantages to develop game controller apps for motion cockpits because at the very least you can test things out while playing a game before having to focus on the game data hooks and everything associated with those.
Game controller control also does not need encoders which can save on time and extra hardware if your just starting out. Now, with no encoders it is basically a "follow the stick or pedel" method with limiters for your range end, but I have not seen that the accuracy of encoders is needed unless you want to go half way through a move like a half roll and then hold. Certainly this would add more fine tuning, but it's seems to be a good enhancement more then a requirement. For game data, encoders and the code/electronics for them are certainly a requirement.
Again, I am not condeming game data as it is certainly beneficial because it can yield some very unique effects and if its offered, by all means tap into it.....but is it the only one that makes sense?
Below is an overview that compares the two (again my observation) Please offer some comments because I am just wondering why motion simmers have "game data" as a preference
Maybe it is that all the games that most motion simmers would want to play does have game data apps available?
maybe I am just thinking along a different line?
here is the list:
Game Controller Actions
Accelerating
Braking
Rolls
Climbs
Dives
Turns
Lifts
Drops
Landing Gear/Boost
Game Data Only
Turbulance
Ground Textures
Taking Fire
Physical Bumps
Crashes
For any of you that have worked with both, Does game data pervide a better experience for the Game Control Actions listed above?
So there's my question/s I certainly have game data control on the radar, but for know I am focusing on game controller control cause it seems to be a good fit. But maybe it is all personal preference or maybe there is some other a reason why many have stayed away from this method?
I also just went to X-sim site and looked at how they handle the game controller method and it seems they do but are saying:
"d) if your a game does not support ForceFeedback you can use either a game specific plug-in or your joystick movements (not recommended)"
Hmmm .......again not reccomended.
Has anybody played around with game controller control in X-sim or even your own home grown app?
Regards Kyle