[StratComm]

It is off by default, if you mean -pcx32.  Or if you're refering to 16bit display color depth as opposed to 32, you can always change that manually and most of us would rather use 32-bit.

[Overlord]

As i have mentioned several months ago, there should be a "Value" tab on the features page.
Example:

[karajorma]

Originally posted by Overlord
As i have mentioned several months ago, there should be a "Value" tab on the features page.

Good point. Hard to implement RT?

[StratComm]

On a similar note, to at least have a listing of all supported flags somewhere, even if they don't have a check-box associated with them.  Remembering everything that can be set by the command line is hard for me, a veteran, and I know a lot of the newcomers don't even know that you can change your FOV, for example.

[RandomTiger]

Originally posted by karajorma


Good point. Hard to implement RT?

Kind of, need to change the structures inside the fs2_open build as well as the launcher interface. I've always intended to do this but its going to have to wait until the whole system changes over (with WMCoolmon code and other additions).

Im not taking general requests, I dont want to spend all the time I have on the launcher. The thought of that is enough to drive me away for another 6 months.

If you do make request consider using 'could you please' rather than 'this 'should' do this'. Either that or start paying me for this.

I'm looking at what Kazan wanted because he made the effort to find me and ask me about it outside the forums.

And Im implementing (hopefully) what karajorma wants because its easy and hes willing to work with me to implement and test it.

-----

sfried, last time I looked (that was a while ago), 32 bit textures were off by default and the mode depth (16 or 32) is selected in the same way as fs2 retail.

You might want to try pcx compression (-pcx2dds), 32 bit colour depth but takes up a lot less space, the compresion means the image quality suffers though.

[StratComm]

Please excuse us RT, we tend to get caught up in the feature requests.  You know all we ask from any of you is that you do what you feel up to doing, everything else is secondary.  Besides campaign-specific requests, the only reason these feature request threads exist at all is to give coders itching to take on a new project some ideas as to what to do.  At least, that's the take I've always had on it.  

[karajorma]

Originally posted by RandomTiger
Kind of, need to change the structures inside the fs2_open build as well as the launcher interface. I've always intended to do this but its going to have to wait until the whole system changes over (with WMCoolmon code and other additions).

I figured that might be the case (which is why I asked if it would be hard to do). If it was simple you'd have probably done it right from the start

Originally posted by RandomTiger
And Im implementing (hopefully) what karajorma wants because its easy and hes willing to work with me to implement and test it.

Always have been RT.

[RandomTiger]

Originally posted by StratComm
Please excuse us RT, we tend to get caught up in the feature requests.  You know all we ask from any of you is that you do what you feel up to doing, everything else is secondary.  Besides campaign-specific requests, the only reason these feature request threads exist at all is to give coders itching to take on a new project some ideas as to what to do.  At least, that's the take I've always had on it.  

Thanks for that

Its just sometimes I it seems like so many people are going 'I want, I want' then when you need someone to test your feature then only a small number of regulars (like karajorma and lightspeed) can spare any of their precious time to test it.

As a result bugs slip through and go un-noticed and then you get people (and I have had this) shouting at you. And its like, 'who the hell are you to be shouting at me? Your not paying me for this!'

Campaign-specific requests are good, keeps us tided to the MODs which is the future of our project and community. Bring them on but consider a few things (for all requests):

1. Its more fun for coders to work on a verity things. The more fun it is the more we will do and want to do.

2. Try and think out requests in detail.

I hope karajorma doesnt mind me taking his request as an example. All I know is how my launcher passes flags and settings around and some of the ins and outs of the D3D engine.

I didnt know multi MOD's were possible, I didnt know if they were officially supported, if many people used them, why anyone would want / need to use them.

When I have worked on freespace in the past I've only had enough time to code, I've not had the time to look at MOD's and how they work or keep up to date with the improvements of the filing system. I dont have the background knowledge someone like Bob will have from coming from that background.

I could go and learn all this stuff or people could do the research and fill in the blanks for me.

With input from someone who knows the system better and who in the end will use it, the implementation is likely to be better as well.

3. Be patient

We cant get onto most requests straight away, if its a good request theres a good chance we have already thought about it in a form but havent had time to get onto it. Overlords request is an example of this.

4. Think about problems

Try to figure out problems we might run into, exceptions or other bugs or limitations that might cause issues. If we know this stuff before we start it could make it easier and quicker to implement.

5. Never assume something is easy

Things are often more complicated than you might think, usually because of the nature of the code thats already there. Theres nothing more annoying than 'can you do this quickly because its really simple'.

Sometimes, not often, something complex is easy!

6. The most important, be willing to test the result.

Otherwise, two choices

1. The coder tests it. That means hes not implementing someone elses feature request. Also since its been developed on his system, bugs are less likely to show up.

2. It doesnt get enough testing and bugs get in there and arent found until the coder is half way through implementing someone elses feature.

[RandomTiger]

On a lighter note heres a picture of my face mapped onto Gollum holding my graphics card!

[BlackDove]

Productive

[karajorma]

That is one of the weirdest yet funniest things I've seen in ages

[WMCoolmon]

RT: Something else I've noticed, when switching in between OpenGL and D3D and vice versa, nonstandard resolutions aren't carried over. It's a slight bother for me, not anything too serious.