Ok, I started one last attempt to make RF work using the autoexec.cfg "fix".
Outfront: It didn't work! Still, I feel I got a lot closer to actually making it work.
Here is what I did / A total newbies "Guide" to getting closer to oldschool RF:1. Get a proper editor for .cfg files (I used:
http://www.chip.de/downloads/Notepad_12996935.html)
2. Create a file called autoexec.cfg in your INSTALL-base-directory (.../ufo_ai/
base/
2b. Put in the line: exec autoexec.cfg
3. Create a file called autoexec.cfg in your PROFILE-base-directory (.../yourname/applicationdata/ufo_ai/
base/)
3b. Put in the famed line: set g_reaction_fair 0
3c. Experiment using things like set cvar g_reaction_fair 0, set g_reaction_fair "0", set g_reaction_fire 0 and hence 8! possible combinations.
4. Wonder why it isn't working
----
Notes:- Now this may seem a little too much but I actually found, while reviewing the ufoconsole.log, that the autoexec.cfg isn't even executed unless you take step 2.-3. . If you just create an autoexec.cfg in either your install- or profile-directory the file is NOT executed for whatever reason.
- lines like set g_reaction_fair 0 and set g_reaction_fire "0" produce no further entry in the .log-file
- lines involving "cvar" produce the .log-entry: "invalid flags 0 given"
(whatever that means now, but something was trying to be happening
)
----
Request to the developers:- PLEASEEE clarify any time soon if that autoexec.cfg fix actually does hold ANY promise of changing RF in the 2.3-build.
- If yes, pleaseee explain how to do it properly.
- I mean, what is "
* introduced cvar g_reaction_fair to activate/deactivate reaction fire timeout" in the update-notes for march 2010 supposed to MEAN?
- Please do not view this as a rant or something. Yes, I am impatient for I have waited looong for this and RF spoils it bad.
However, I would like to see my impatience viewed as a major compliment to your otherwise awesome game.