[Nuke]

i kinda also want to improve input within scripting too. right now we pretty much have low level access to key presses, mouse axes and buttons, trackir and control axes. the problem is they were kinda implemented as they were needed and arent very intuitive or uniform, both for scripters and players, the way they are implemented. on the script side they all work in different ways and arent really consolidated into a simple structure. scripts that i am currently working on use a lua based parser to load a table file containing keybinds, and the only way for the player to configure them is by editing a text file. i consider this a dirty hack. making custom functions available in the control options would make script development a lot easyer (and better for players too, since they dont need to do anything new to use a new feature).

[Reprobator]

I agree with the 1st point : multiple input
New joytick and hotas use multiple input id for each part of it (stick/throttle/rudder) and with the last logitech g940 system you'll loose the force feed back feature with using pp joy.
X52 series is taking ages too and i guess it'll be quite soon before they renew theirs hotas product and i guess they'll use the same thing than logitech.

My x52 is getting more and more crazy and the only thing that retain me from buying the g940 is the fso support, as i ll spend  90% of its lifetime on fs2 ^^
The mod flexibility would be great too !

[Wanderer]

I don't know much about DirectInpit and even less about SDL so I'm not sure how to even approach the multiple stick issue.



As for the different response curves... Could you please answer the following

• What would be the preferred response curve types?
• On what range should these exists?

1: support for more than one joystick
2: separate mouse and joystick bindings (no mixing joystick x and y with mouse x and y)
3: more axis commands (lateral thrusters, vertical thrusters, reverse thrusters, view commands (retail snap, pan snap, relative pan, absolute pan, slew, ect))
4: make it trivial to add more key or axis commands as theyre needed in the future (from c or possibly scripting)
5: ability for scripting to post custom commands to the binding options screen, and reading of these options from scripting
6: config import/export from text file
7: advanced mouse options (privateer style, freelancer style, or standard modes)
8: advanced keyboard axes with custom ramping rate settings

All of these would have to be post 3.6.12 ops.

[Nuke]

sdl isnt that hard to work with and i think freespace already uses it. heres some code from the nukesim engine.

Code: [Select]

SDL_Joystick *stick;
int numaxes;

if(SDL_NumJoysticks())
{
stick = SDL_JoystickOpen(0);
numaxes = SDL_JoystickNumAxes(stick);
}

its kinda preliminary so far, this pretty much looks for a joystick, if it finds it it opens the first one, producing a handle, and puts the number of axes into numaxes. for a system which uses multiple joysticks, you get the number of joysticks, iterate through them, count the axes on each, generate some mapping data. to get at the raw joystick data you do something like this:

Code: [Select]

int joyaxes[6] = {0,0,0,0,0,0};

if(stick && numaxes > 0) //get joystick state
{
SDL_JoystickUpdate();

for (unsigned i=0; i < numaxes; i++)
{
joyaxes[i] = SDL_JoystickGetAxis(stick, i);
}
}



[chief1983]

FSO doesn't use SDL on Windows, just Linux and OS X.

[Nuke]

FSO doesn't use SDL on Windows, just Linux and OS X.

why not? sdl works just as well in windows from what i can tell from using it.

[portej05]

We've been looking at it, and taylor had this to say (actually, I wish I could find it )

Basically, the issue is that SDL support was put in there so that other platforms would work, and so that we didn't break anything, it doesn't change the original behaviour of OSApi.
It'd be a bit of an effort to work around that issue.

[Tomo]

DirectInput appears (as far as I can tell from MSDN) to work pretty much the same way.

- I've only got one joystick so I can't be sure!