posted 08-21- 12:48 AM               

Here are fixes for the current problems
Right aileron trim not working

Find the following line:
inpAileronTrimDownDigital = RightArrow : 0.01

Ther are 2 space between the : and 0.01, delete one of the spaces. (Yes this is the only problem). Here's the correct line:
inpAileronTrimDownDigital = RightArrow : 0.01
You will also find the same problem with this line:
inpElevatorTrimDownDigital = UpArrow : 0.02

here's the correct line, minus the extra space
inpElevatorTrimDownDigital = UpArrow : 0.02
RATO problem. find cmdBomb = A, change to:
cmdBomb = Shift A

The old belief that you can ALWAYS map 2 commands to the same key may not be true under certain circumstances. This will require some testing to be sure. Also, extra spaces DO make a difference if they are BETWEE the equals sign and a value (great, now I have to check EVERY stinking entry to make sure this isn't a problem somewhere else)

This has lead me to 3 conclusions:
1) There needs to be a standard file that developers use.
2) Certain commands need to be inviolate (cannot have another command mapped to the same key)
3) Someone needs to control this file

Once I get # 1 and 2 worked out, I'm going to turn this file and the startup ppf file over to either the DIME group or The Crew. Things have got out of hand and this is causing too many problems for the users. I want to give control of these files to one of these groups so some kind of quality control can be maintained over these darn things. The last thing we need is for people to get frustrated because things don't work right.

posted 08-21- 01:27 AM               

But this looks like it could be a nightmare; I am trying to fix a names.ppf file so I can install Somme without losing Pacific. Using copy/paste, it took what seemed like forever, and I am still not sure it is correct in syntax ( spaces and delineators in the right places ). So, there's another that may have to be kept updated...arrrggghhh!!!!

posted 08-21- 01:33 AM               

I agree though it needs to be controlled.

posted 08-21- 11:08 AM               

Builders who use a self-extracting .exe file need to be VERY careful what they put in there. IMO the startup.ppf and keyboard.inp files are "out of bounds." You can include a new file with a new name, i.e. "newstartup.ppf" and directions on how to activate that file, but overwriting someone's existing startup.ppf or keyboard.inp is a no-no I reckon. If you're adding a "new" function that requires a new key command, then it should be a line in a readme that explains what to add, so that the player can look at his own keyboard.inp and make sure he (or someone else's plane) hasn't already taken that key combo. If the player isn't up to the task of checking/modifying his keyboard.inp, then he either doesn't get the feature or he takes it to the forum/email to get help.

Personally I prefer to look at the .zip file so I can see what's in there so that I can protect any "experimental" or "custom" files I may be tinkering with.