What would be fantastic would be for the devs to offer an API to direct input/output/variables, so that, even if fans aren't skilled enough to build a unit like this one, they could at least various different video outputs to different monitors. (...like the main screen going out to a collimated display. Forum.)
For video, I would have the user create an .XML file that listed each video destination (Whether single monitor or an array), and the video sources' locations, rotations, orientations, and sizes that should be mapped to it. Input, output, and variable traffic should use a client/server setup, so that multiple computers/devices can be used for control/display. Actual creation of clients could be left up to users.
The goal should be a system flexible enough to allow the use or emulation of a Battletech Tesla Pod.
Providing variables externally shouldn't be difficult at all. Heck, I remember reading about variable extraction/injection used for custom cockpits all the way back in the MW2 days. What do y'all think?
2
I/O API
Started by DeadlyDad, Feb 07 2012 10:50 PM
2 replies to this topic
#2
-
-
- 2,905 posts
Member
- LocationLost
Posted 08 February 2012 - 06:45 AM
This request has been made several times since the forum opened, with no reply as yet from the dev's. There are quite a number of people who want this facility, but it may well have to wait until after launch, as they no doubt have a lot of work to do.
#3
-
-
- 609 posts
Member
- LocationSomewhere north of St. Petersburg
Posted 08 February 2012 - 08:27 AM
A number of us have posted in other threads seeking flexibility in the displays and controls. I never suggested an API, per se, as my understanding is that would be a notable amount of work for the developers.
Of course, anything that they can give us to work from is welcome (with the caveat that it doesn't allow for exploits/cheating). That's where the real challenge comes in, I suspect... making wise choices on what is exposed as exportable data, and what is kept (hopefully) out of reach. You don't want folks getting data on where everyone else is, etc. beyond what their character/mech is actually entitled to.
I don't know what CryEngine 3 can support, as far as making data available to external UI's, etc. I'll be happy if they can make the various displays available as movable/resizeable windows. If we have that, head tracking, and well thought out commands that can have hot-keys assigned as needed, then we should be a long ways towards what most anyone would want. About the only things beyond that would be eventually providing access to data needed for motion platforms and/or tactile feedback systems (which will be an even smaller sub-set of players).
Of course, anything that they can give us to work from is welcome (with the caveat that it doesn't allow for exploits/cheating). That's where the real challenge comes in, I suspect... making wise choices on what is exposed as exportable data, and what is kept (hopefully) out of reach. You don't want folks getting data on where everyone else is, etc. beyond what their character/mech is actually entitled to.
I don't know what CryEngine 3 can support, as far as making data available to external UI's, etc. I'll be happy if they can make the various displays available as movable/resizeable windows. If we have that, head tracking, and well thought out commands that can have hot-keys assigned as needed, then we should be a long ways towards what most anyone would want. About the only things beyond that would be eventually providing access to data needed for motion platforms and/or tactile feedback systems (which will be an even smaller sub-set of players).
1 user(s) are reading this topic
0 members, 1 guests, 0 anonymous users
