XR2 Config Program

[DarkEnergy]

I was wondering if anybody has thus far made a configuration program for the XR2, sort of like the DGIV config program.

If no one has, I know a couple programming languages and could make a config program for it, which I'm sure would help a lot of people. I could have a program for modifying the basic variables up within a couple days if one is needed.

 

[Countdown84]

I'm pretty sure this hasn't been done, but it would be a GREAT addition to an amazing spacecraft. Would be nice to extend to the XR1 and XR5 as well (they have similar config files)

 

[pattersoncr]

It comes with a config file you can edit.

 

[zerofay32]

I think having a more visual interface would make changing the config even easier.

Zerofay32

 

[DarkEnergy]

It comes with a config file you can edit.

It does come with a config file, but the point of the program is to make it easier for users to change common values like oxygen and fuel without having to go through the entire file looking for what you need.

Some people who aren't as computer savvy as others may not be able to find the config file and when they do, they may not know what values do what. A config program would make these values easily accessible to all users, not just the experienced ones.

 

[Kaito]

It does come with a config file, but the point of the program is to make it easier for users to change common values like oxygen and fuel without having to go through the entire file looking for what you need.

Some people who aren't as computer savvy as others may not be able to find the config file and when they do, they may not know what values do what. A config program would make these values easily accessible to all users, not just the experienced ones.

XR2Prefs.cfg I believe
And he has comments about all the stuff. I'm pretty sure a trained monkey could do it

 

[DarkEnergy]

Well, it's totally up to you guys. I really don't mind making one, but if it isn't needed, then I suppose that's okay too.

 

[TSPenguin]

It is not needed. But it won't hurt having it.
Diversity is always good. And if someone rather use a GUI than editing the file directly or holding copies with favorised settings as presets, then that is perfectly fine.

Diversity enriches us all!

 

[Countdown84]

I don't have any problem editing the config file, but I've always thought that a nice GUI was sort of a "missing piece" for the XR craft, compared with the DGIV.

In particular, it would be nice to have easy ways to modify UMMU crew and skin settings.

I agree that it's not needed, but I definitely think it would be nice to have.

 

[TSPenguin]

Keep in mind that the crew names for each scenario are stored in the scenario.
So the names would only appear on new XR Craft. Maybe you could write a scenario parser for that as well.

 

[Countdown84]

That's a really interesting idea, TSPenguin - maybe instead / in addition to a configuration program you'd have a utility that opens a scenario file and allows you to set all the failure states, propellant levels, animation status, crew status, skin, etc. etc.

A little schematic of the XR2 showing what was parts are in failure state would be very slick.

 

[DarkEnergy]

Okay, I think I will start on a config program then. I think I'll be able to make an editor of scenarios for the crew/failures as well. I'll probably combine the ideas into one program.

I really like the idea of having a schematic for failures in the program. I'm pretty sure I could pull that off.

I should have a simple oxygen and propellant config program out within the next couple days. For now it will be limited to the XR2 but I will extend it to the XR5 in the futurre as well. I'll be on vacation for a week, starting in two days, so I don't think I'll make any more progress on it until next week. Thanks for the great ideas guys!

 

[zerofay32]

Good Luck.

Zerofay32

 

[dbeachy1]

This sounds like a great idea -- keep us informed! :speakcool:

 

[DarkEnergy]

Okay, I have a basic program up and running! So far you can adjust 5 values: Main Fuel ISP, Scram Fuel ISP, Oxygen Loadout, Oxygen Consumption, and APU Fuel Rate. Of course I will probably add more, but in my opinion these are the values that will be changed most so I added them first.

So far there are a couple neat features in the program. You can load the current values from the preference file and modify them from there. A pretty cool feature I added allows you to save certain configurations to ".xr2" files and then load them into the program. This lets users save their favorite configurations so they don't have to put in the data every time.

What are other important values that the program should cover? Which values in the XR2 preference file do users change the most? Once I get feedback on the new values, I will add them and continue to a failure schematic and possibly crew editor.

By the way, I'm happy to hear that the creator of the XR2 likes the idea! If only there were a bow emoticon...

---------- Post added at 06:39 PM ---------- Previous post was at 05:51 PM ----------

I would like to begin on failures, but unfortunately I'm not exactly sure how they are set in the scenario file... I'm assuming the variable "Internal_Systems_Failure" is where the failures are set, but I'm not sure what the value after it actually does... Any help here would be much obliged.

I just thought of another idea while typing this. I could put a slider in the config that governs the chance of a failure during the flight. Then, according to the chance, I could set a random failure in the scenario.

 

[Countdown84]

DarkEnergy,
That was fast! I'm really excited about where this might go; should be a great addition to the XR2. The ability to save multiple configurations is a GREAT idea.

As far as suggestions, let me offer a bunch of ideas. If I were doing this (which would imply that I know how to program, which I don't -- yet), I would say that if you're going to bother to write a configuration program, it should (ultimately) be comprehensive - i.e. completely replace the need to manually edit the config file. That said, I know that may take a lot of work, and even doing a subset of the things listed here would be really nice.

To that end, you might create a bunch of check-box style options that correspond to the on/off parameters in the config file - like whether the APU autostarts, whether damage is simulated, whether a "commander" rank is required to pilot the ship, etc. Ideally, hovering the mouse over a box would pop up a tooltip that contains Doug's explanation of the parameter (From the config file)

There are also a number of important parameters that take number or drop-down box input: things like main thrust, hover thrust, LOX consumption rate, etc. etc. These are all pretty important to tweaking the flight experience.

Probably least important are the audio callout enable/disable options. Those are easy enough to edit manually.

Personally, I find one of the last accessible/ most confusing areas of the config file is the custom Secondary / Tertiary HUD configuration stuff. Some kind of GUI for modifying those values would be AMAZING, but probably a lot of work.

Finally, you have Cheat Codes. I don't use these, but they would lend themselves easily to a check-box input.

Maybe you could arrange all of this in a program with multiple tabs - e.g. one tab for fuel and consumables, one for general ship behavior, one for cheat codes, etc.

As for how to handle failures in the scenarios, besides the Internal_Systems_Failure parameter, there are the following which set whether or not a specific piece of the XR2 is damaged:

DMG_0 1.000000 Left Wing
DMG_1 1.000000 Right Wing
DMG_2 1.000000 Left Aileron
DMG_3 1.000000 Right Aileron
DMG_4 1.000000 Landing Gear
DMG_5 1.000000 Nosecone
DMG_6 1.000000 Retro Doors
DMG_7 1.000000 Top Hatch
DMG_8 1.000000 Radiator
DMG_9 1.000000 Airbrake
DMG_10 1.000000 Left Main Engine
DMG_11 1.000000 Right Main Engine
DMG_12 1.000000 Left SCRAM Engine
DMG_13 1.000000 Right SCRAM Engine
DMG_14 1.000000 Fore Hover Engine
DMG_15 1.000000 Aft Hover Engine
DMG_16 1.000000 Left Retro Engine
DMG_17 1.000000 Right Retro Engine
DMG_18 1.000000 Forward Lower RCS
DMG_19 1.000000 Aft Upper RCS
DMG_20 1.000000 Forward Upper RCS
DMG_21 1.000000 Aft Lower RCS
DMG_22 1.000000 Forward Star. RCS
DMG_23 1.000000 Aft Port RCS
DMG_24 1.000000 Forward Port RCS
DMG_25 1.000000 Aft Star. RCS
DMG_26 1.000000 Outboard Upper Port RCS
DMG_27 1.000000 Outboard Lower Star. RCS
DMG_28 1.000000 Outboard Upper Star. RCS
DMG_29 1.000000 Outboard Lower Port RCS
DMG_30 1.000000 Aft RCS
DMG_31 1.000000 Forward RCS
DMG_32 1.000000 Bay Doors
IS_CRASHED 0

I think they're pretty self-explanatory. I'm not sure what IS_CRASHED means exactly (maybe that the craft is no longer pilotable).

Good luck!

 

[Travis Reed]

DarkEnergy,
That was fast! I'm really excited about where this might go; should be a great addition to the XR2. The ability to save multiple configurations is a GREAT idea.

As far as suggestions, let me offer a bunch of ideas. If I were doing this (which would imply that I know how to program, which I don't -- yet), I would say that if you're going to bother to write a configuration program, it should (ultimately) be comprehensive - i.e. completely replace the need to manually edit the config file. That said, I know that may take a lot of work, and even doing a subset of the things listed here would be really nice.

To that end, you might create a bunch of check-box style options that correspond to the on/off parameters in the config file - like whether the APU autostarts, whether damage is simulated, whether a "commander" rank is required to pilot the ship, etc. Ideally, hovering the mouse over a box would pop up a tooltip that contains Doug's explanation of the parameter (From the config file)

There are also a number of important parameters that take number or drop-down box input: things like main thrust, hover thrust, LOX consumption rate, etc. etc. These are all pretty important to tweaking the flight experience.

Probably least important are the audio callout enable/disable options. Those are easy enough to edit manually.

Personally, I find one of the last accessible/ most confusing areas of the config file is the custom Secondary / Tertiary HUD configuration stuff. Some kind of GUI for modifying those values would be AMAZING, but probably a lot of work.

Finally, you have Cheat Codes. I don't use these, but they would lend themselves easily to a check-box input.

Maybe you could arrange all of this in a program with multiple tabs - e.g. one tab for fuel and consumables, one for general ship behavior, one for cheat codes, etc.

As for how to handle failures in the scenarios, besides the Internal_Systems_Failure parameter, there are the following which set whether or not a specific piece of the XR2 is damaged:

DMG_0 1.000000 Left Wing
DMG_1 1.000000 Right Wing
DMG_2 1.000000 Left Aileron
DMG_3 1.000000 Right Aileron
DMG_4 1.000000 Landing Gear
DMG_5 1.000000 Nosecone
DMG_6 1.000000 Retro Doors
DMG_7 1.000000 Top Hatch
DMG_8 1.000000 Radiator
DMG_9 1.000000 Airbrake
DMG_10 1.000000 Left Main Engine
DMG_11 1.000000 Right Main Engine
DMG_12 1.000000 Left SCRAM Engine
DMG_13 1.000000 Right SCRAM Engine
DMG_14 1.000000 Fore Hover Engine
DMG_15 1.000000 Aft Hover Engine
DMG_16 1.000000 Left Retro Engine
DMG_17 1.000000 Right Retro Engine
DMG_18 1.000000 Forward Lower RCS
DMG_19 1.000000 Aft Upper RCS
DMG_20 1.000000 Forward Upper RCS
DMG_21 1.000000 Aft Lower RCS
DMG_22 1.000000 Forward Star. RCS
DMG_23 1.000000 Aft Port RCS
DMG_24 1.000000 Forward Port RCS
DMG_25 1.000000 Aft Star. RCS
DMG_26 1.000000 Outboard Upper Port RCS
DMG_27 1.000000 Outboard Lower Star. RCS
DMG_28 1.000000 Outboard Upper Star. RCS
DMG_29 1.000000 Outboard Lower Port RCS
DMG_30 1.000000 Aft RCS
DMG_31 1.000000 Forward RCS
DMG_32 1.000000 Bay Doors
IS_CRASHED 0

I think they're pretty self-explanatory. I'm not sure what IS_CRASHED means exactly (maybe that the craft is no longer pilotable).

Good luck!

The values that are 1.000000 are percentages, 1.0 being 100% of course. To reduce a system's effectiveness, reduce the percentage. IS_CRASHED is there to decide whether the craft is pilotable, regardless of crew health.

Personally, I'd like to see every parameter configurable at some point. However, the top for me are the ISP settings, O2 Loadout, O2 Consumption Rate, O2 Consumption Multiplier, APU fuel consumption, Coolant heating rates, engine thrust, and crew (both in the config and in scenarios).

 

[DarkEnergy]

Okay, thanks for all of the support and tips! I think I understand the failures, so I'll probably get started with that. I'll look into tabs and tooltips as Countdown suggested. Unfortunately I probably won't progress much further until next Thursday due to a vacation.

Once again, thanks for the tips and I'll get adding the new features.

 

[Travis Reed]

I should have added that I have no idea what specifically the Internal Systems Failure parameter does or how it works...you may want to get Doug to clarify...

 

[wehaveaproblem]

Just wanted to throw in another 'great idea' reply. Good luck with this, it will make setting up the XR2 for racing much easier.

Do you plan to have a transferable save file? so people can share and exchange configs easily?