Some of the configuration files inside the c172pfg1234 folder will continue to refer to and use many files in the original folder, but this is not a problem right now. Make changes to the 3D file or texture of the aircraftĮdit the -set file to refer to the model within the new aircraft folder Rename the aircraft folder (if you use the same name for the new folder, the aircraft will not be listed in fgrun) To summarize, when making a copy of an existing aircraft and making changes to that aircraft, these steps must be followed: Selecting this name launches the aircraft model named c172pfg1234. What has happened here? Flight gear uses the first part of the -set file to identify the aircraft. Fgrun displays a different -aircraft parameter when launching: fg-scenery=C:\Program Files\FlightGear\data\Scenery C:\Program Files\FlightGear\sceneryįgrun is launching the original c172p, obviously there has to be a way to launch the modified aircraft by changing a parameter somewhere.Ĭhange the name of the -set file in the new airplane folder (. fg-root=C:\Program Files\FlightGear\data Displaying the launch parameters from the fgrun launcher shows the following :Ĭ:\Program Files\FlightGear\bin\Win32\fgfs.exe There is one more step needed to make the airplane load into Flight Gear. The experience has been very interesting and rewarding so far, and I look forward to publishing the model. Listed below is an earlier version of how to change the aircraft, this write up will be replaced soon with an actual run-through. The method used for adding colours to the model at present is Materials only, since this is the easiest to use, and also textures are difficult to apply smoothly to a model, at least in my experience.Ĭhanges planned for the C172 are as follows:Īdd instrument panel with custom instrumentsĬhange the wheels and tires for a better versionīouncing on landing, changing gear damping settingsĬhanging engine power from 160hp to 180 or 200 this is done in real lifeĪdding an experimental glass panel - most probably from an airlinerĮach version will be saved separately after modification to preserve recovery if a model goes wrong after a change. The versions of Wings and Blender have the required import and export features and Wings runs without crashing, so that version is chosen. The 3d tools used are Blender 2.4 and Wings 3D 1.4, Win32 versions running in WINE on Linux Mint 19.3 Tricia on a 2015 HP 45 laptop. Starting with the Mirage 2000, with some success in changing the tires and wheels in that aircraft, I returned to the Cessna 172 and other aircraft that I had started to modify. the HAT axis were messed up.Īll credit still goes to Farmboy.New knowledge on how to modify aircraft and how to use the folder structure has revived interest in modifying aircraft. UPDATE: I have gotten dual throttle working but i had to use a totally different Config file (one that chocboy got in another topic)īut when i move the left throttle it grabs the right throttle as i move the left down(virtual) then i have to move the right one back again(any info on this?) I just downloaded this game yesterday (saturday) because i got the joystick.ĭoes anyone have any info on this issue? or have a full workable version for the Cyborg-X? the camera immediately rotates all the way to the left. What happens when i load up and the Cockpit appears. But when i load up my game its all haywire. I copied and pasted the XML file that Farmboy posted. sim/current-view/goal-heading-offset-deg Note : button #'s listed in code do not correspond to numbers printed on joystick.ĮDIT**** Speed Brakes are now setup as proportional instead of UP or DOWN. For 4 engines you would swap the /controls/engines/engine/throttle and the /controls/engines/engine/throttle locations in the xml code. I also have a configuration for the Saitek Aviator joystick with similar functionality but it is older and slightly more primitive:Ĭurrent setup if for twin engines. Here the three throttle levers control either throttle/propeller/mixture or throttle #1/#2/#3 or propeller #1/#2/#3. my configuration for the Saitek throttle quadrant: I'd suggest a multi-mode approach where you can toggle between different modes for the joystick throttles controls. You could instead bind each throttle to one specific engine, but if you do so you will have problems with aircraft with 3 or more engines. That axis handler controls the selected engines (you can select a single engine with shift+1,2, etc and all with ~ or shift+~). The default binding for throttle is usually the Nasal script "controls.throttleAxis() ". The number 1 throttle controls both engines. But when I use the number 2 one, nothing happens. I was wondering what to put in my joystick xml if I wanted control over both engines
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |