FSIC Messageboard
  SDOE General
  Keyboard inp file conflicts

Post New Topic  Post A Reply
profile | register | preferences | faq | search

UBBFriend: Email This Page to Someone! next newest topic | next oldest topic
Author Topic:   Keyboard inp file conflicts
Da Jug head
Pilot
posted 08-18- 09:59 PM     Click Here to See the Profile for Da Jug head   Click Here to Email Da Jug head     Edit/Delete Message   Reply w/Quote
Somebody asked "why bother".

Here's one reason.

The following commands conflicted and were settled

lights- shift L and V, Shift L was used as V is for tilting an engine and something that new will more than likely have nav lights.

cmdBrakesLocked was asigned Shift B, but this command is already used for wheel brakes on.

the command is now cmdBrakesLocked =Ctrl B

Last, are these two the same command with different wording?

cmdDBrakeToggle = X
cmdDiveBrakesToggle = X
If so, from now on please use the spelled out version (cmdDiveBrakesToggle)

Ronin, I'm sending you the keyboard file, can you update the reference card? Don't worry about including the file, as it's going in a download with the startup.ppf, and servers.dat file

[This message has been edited by Da Jug head (edited 08-18-2001).]

IP: Logged

Ronin
Pilot
posted 08-19- 12:03 AM     Click Here to See the Profile for Ronin   Click Here to Email Ronin     Edit/Delete Message   Reply w/Quote
Jug-

You bet! Send it on over!

Ronin

IP: Logged

ArgonV
JAG
posted 08-19- 12:08 AM     Click Here to See the Profile for ArgonV   Click Here to Email ArgonV     Edit/Delete Message   Reply w/Quote
Simple fact is there are too many commands for each one to have its own letter. They are going to conflict! But as long as the one aircraft doesnt use them both then you are ok.

IP: Logged

71hemicuda
Pilot
posted 08-19- 12:46 AM     Click Here to See the Profile for 71hemicuda   Click Here to Email 71hemicuda     Edit/Delete Message   Reply w/Quote
Hey Jug could you send me one too at lahndt@ptialaska.net I would be very thankful for it. Thanks.

IP: Logged

Raider
Pilot
posted 08-19- 09:55 AM     Click Here to See the Profile for Raider   Click Here to Email Raider     Edit/Delete Message   Reply w/Quote
If we had a standard keyboard.inp then plane builders could just build off that. The plane builder can name the command for a dof anything they want. Each builder does not have to create a new key command everytime they add something new.

If I want to use the key "W" to start the windshield wiper I don't have to add a new line to the keyboard.inp like

cmdwindshieldwiper = W

I just name the dof "cmdWingFoldToggle" which is already in the keyboard.inp Then I put in the readme.txt "If you want to use the windshield wipers press 'W'."

If this craft has folding wings, then pick another letter to use for the wipers.

IP: Logged

Da Jug head
Pilot
posted 08-19- 10:39 AM     Click Here to See the Profile for Da Jug head   Click Here to Email Da Jug head     Edit/Delete Message   Reply w/Quote
Other than Ronin, who has the template for the reference sheet, don't worry about asking for it.

I need to make one more pass through the startup.ppf, and keyboard.inp file, then these 2 plus the servers.dat and updated missionseditor.ppf file will be posted as a single downloadable file. (Self extracting zip of course)

[This message has been edited by Da Jug head (edited 08-19-2001).]

IP: Logged

All times are CT (US)

next newest topic | next oldest topic

Administrative Options: Close Topic | Archive/Move | Delete Topic
Post New Topic  Post A Reply
Hop to:

Contact Us | Fighter Squadron Information Center

(This site Copyright (c) 1999 Inertia LLC)

Powered by Infopop www.infopop.com © 2000
Ultimate Bulletin Board 5.45c