[Goober5000]

Whoever has asked for features only to be told "we can't do that, it will break the pilot file" needs to speak up now.  Taylor is committing some new pilot file code this weekend, which leaves a small window of opportunity to add some features before things get hairy again.  We posted about this over a month ago, but nobody spoke up.  If you care about your feature, now is the time to say so.

Please note that this is limited to features like autopilot, glide controls, and additional key mappings; not bumping the ship limit.  The ship limit bump requires a major overhaul.  This is a call for the features that are less major but still significant enough to corrupt pilot files.

[Axem]

Cool, how about...

A way to easily edit default keybindings?

A Push/Toggle option for Glide? (which looks like it fits into your autopilot/glide/etc thing )

A way to use every key in the key-press sexp?

That's all the comes to mind from the projects I'm in.

[karajorma]

Is any of this stuff going into the 3.6.9 Branch? Cause I was led to believe that this was all HEAD only.

[jr2]

I'll have to search my post history... IDK.

(@#$@ wish there was a way to dump it all to a file... searching would be easier.)

EDIT: posting some linkies from other instances: (searched forums main for "pilot code", posted results I thought might be relevant).
Code to map joystick axis to buttons
id like a couple new functions in scripting
The 'Post the stuff you asked for during the code freeze' thread
Re: A few things to make the mouse support better - ? (not sure)
Really trivial (I hope) request
Re: The poor man's substitute for Newtonian Physics
Re: The number of primary banks
My first tbm  - ?
Suggestion for a new feature (HUD distance info in Multitargets)
Mouse Button Support
Additional Axes
USB flight stick & USB rudder combo
EDIT2: done now.. will post results from my own posts later.

[Nuke]

support for more joystick axes for lateral, vertical, and reverse thrust
seprate mouse bindings
multiple joysticks
most of what jr2 posted

[ARSPR]

Well, I would like that at least HUD distance info and aiming points were available for multitargets (or even better enhacements like "Multitarget my Target's wing" command and so on).

See this thread: Suggestion for a new feature (HUD distance info in Multitargets).

There were even some old good test builds from Backslash but in some recent PM, he told me that some of that code is ready to go but it can break pilot files.

Edited:        --------------------------------

Suggestion for a new feature (HUD distance info in Multitargets)

EDIT2: done now.. will post results from my own posts later.

This link doesn't point to the thread title. Use mine instead

[taylor]

Is any of this stuff going into the 3.6.9 Branch? Cause I was led to believe that this was all HEAD only.

Nope, HEAD only.  3.6.9 isn't broken, so no point in fixing it.

support for more joystick axes for lateral, vertical, and reverse thrust
seprate mouse bindings
multiple joysticks

Not going to happen any time soon.  These things require reworking the input code, which isn't going to happen at this time.  You'll have to wait for the all new pilot file code before that happens.

Remember that this isn't a replacement for the new pilot file code, but only a standard upgrade since it's already broken and we might as well add a few minor things at the same time as fixing it.  Adding support for new mouse buttons, changing the joystick support, and anything else in that basic category, will NOT happen with the upcoming code fix.  Valid things that we are looking to add now would be things like the push-to-glide control, or that Freelancer-style mouse patch that was posted a while ago.

[jr2]

Hmm, FreeLancery mouse patch is listed AFAIK in the link list I posted

[taylor]

Hmm, FreeLancery mouse patch is listed AFAIK in the link list I posted

Yeah, I noticed it.

But you could cut out anything that involves adding support for more mouse/joystick buttons, making mouse/joystick bindings completely separate, adding support for multiple joysticks or rudder pedals.  Those are things that aren't going to happen.  We are only making a set of small upgrades for now.  The big stuff isn't going to happen until the new pilot file code, when there is new control/input/limits code going with it.

[Nuke]

ah well, and i was about to order some rudder pedals too 

[Colonol Dekker]

Ummm, just off-hand how about being able to order larger capships to do more than just "fire on my target" or "depart"

[Wanderer]

Dekker...

http://www.hard-light.net/wiki/index.php/Objecttypes.tbl

[MP-Ryan]

If it hasn't gone into this branch, fix the red alert bug? =)

[taylor]

If it hasn't gone into this branch, fix the red alert bug? =)

Which one?  There are a few that I know about, and most of them are going to require the new pilot file code to get fixed, not the little upgrade we're doing now.

[MP-Ryan]

If it hasn't gone into this branch, fix the red alert bug? =)

Which one?  There are a few that I know about, and most of them are going to require the new pilot file code to get fixed, not the little upgrade we're doing now.

This one?  I don't know how major it is, you never said =)

[taylor]

This one?  I don't know how major it is, you never said =)

Oh, yeah that one is already fixed and is in both branches of CVS.  That fix didn't require any changes to the pilot files though, just code fixage.  It's only a pilot file issue to the extent that your loadout data would have already been screwed up, and the code change couldn't fix that, merely prevent it from happening next time.

[RazorsKiss]

I have several that aren't pilot-file specific

[Nuke]

what about support for more primary and secondary banks and turret loadout? iirc that had something to do with pilot files

[RazorsKiss]

Yeah - I have several related to that, actually - primary/secondary bank setup, especially.

[taylor]

what about support for more primary and secondary banks and turret loadout? iirc that had something to do with pilot files

That requires much more than pilot file changes though, so it would take someone to do all of that extra work.  I'm not working on HEAD code anymore, since I'm sticking to the stable code tree for the rest of the year and working only towards the next two official versions, so we're at least one dev short already on new things like that.  It probably isn't going to happen until the new pilot file rewrite shows up anyway, just because of how much other work there is to do and how little time everyone really has right now.