SlyCoopersButt said:
Now would I be correct on guessing that what is meant by the Welsh callouts is that there is going to be both English and Welsh versions of the XR2?
Steve is thinking about getting some English callouts with a Welsh accent done as an optional voice pack for the XR2. Nothing is decided yet, though. Stay tuned for updates.
SlyCoopersButt said:
And what would the rough weight of the XR2 be in dry and wet mass? I haven't see such a figure around. I know that the weight is subject to change during development.
I'm still working out the exact figures (plus I haven't run anything by Steve yet, and he will have some say, too), but I am thinking it will be roughly 40-50% more massive than the XR1, wet and dry. It will, however, have a higher thrust-to-weight ratio than the XR1 and it will also have Altea Aerospace Generation II SCRAM engines, which should be good to mach 20 or so. It's still early, though, so this is subject to change. Steve and I see the Ravenstar as a high-performance "Luxury Learjet" type of spacecraft.
Do you think you could add 1440-wide panels? I don't like how the 1280-wide panels get cut off on my 1440x900 monitor.
In technical terms that is possible -- the issue is the amount of work involved to support each panel resolution. I might do a 1440 panel if there is sufficient demand for it (I'll put up a poll). Have you tried running with 1600 panels? That would require you to scroll a little bit to see the edges, but that would probably be better than seeing gaps on the sides.
It'd be wonderful if you could change the skin either by the scenario file or in the scenario editor... and perhaps make your own skins?
There will definitely be a skin pack for the XR2, both for the ship and for payload modules, so users will be able to create their own skins. As for switching on the fly in the screnario editor, I will try to get that into a late Beta if I can. Ah, so many tasks...
Besides this favor, could it be done (I imagine not...) in a way to have the panels as external files and specify them in the config with filename and dimensions?
In-post-edit: Even if it is technicaly possible you would either need a very complex config for button positions, or read from a (bit-)map the positions via color code, or apply a rather complicated mathematical matrix (don't slay me for the wrong term here) based on width for the positions, or some plug-in-ish way to kinda 'drag 'n drop' your panel together.
In any of the cases it would mean a massive amount of work dougs part.
Did I miss something?
You are quite correct: it would be a massive amount of work to make the panels be driven by config files.

Every single button, light, and displayable area on each of the different panel resolutions has its own coordinates, and so the code must manage each. While it would be possible to make the panels be driven via config files, each panel would still require custom graphics to go with it (i.e., a new panel background that is the right width), so it still would be much more than just config file editing.