Make your own free website on Tripod.com



 

This page is designed for people having problems and/or having found solutions or suggestions relating to add-on files. It is intended to compliment the FS2002_tips page and the forum, both of which contain useful information in this area but this is a more specific area for this subject to be addressed.

If you which to submit either a problem, solution or suggestion to this page, please e-mail flightsimvetclub@hotmail.com with the subject heading "Add-on problems Problem/Solution/Suggestion (whichever is appropriate)" and be sure to include the file name, full description and any other information you consider helpful.

Thanks to Mal for suggesting the idea for this.

Date Submitted

Submitted by

Status

Filename(s)

Desciption

8th November 2001

Mal Lloyd

Solution

helio295.zip
h295_2k2.zip
Helio Super Courier views fix.

If you change from forward view to side or rear views, when you return to forward view the last, previous view remains displayed behind the instrument panel. This fix stops that from happening.

Open panel.cfg and find the heading "[VIEWS]". Immedeatly below this heading insert the line "VIEW_FORWARD_WINDOWS=0". How did I know this? I didn't! By comparing panel.cfg from
another aircraft which didn't have the problem, ABD's Corsair, I got a hint. It appears that the entry after the "=" needs to be the forward window's title. In this particular case, the Helio's title just happens to be "0". I think I had other aircraft with the same problem, so time to start searching. 

// Panel for Helio Super Courier by Fred Choate 

[Window Titles]
Window00=Main
Window01=GPS
Fixed Window30=FORWARD_LEFT
Fixed Window31=LEFT
Fixed Window32=FORWARD_RIGHT
Fixed Window33=RIGHT
Fixed Window34=REAR_LEFT
Fixed Window35=REAR
Fixed Window36=REAR_RIGHT

[VIEWS]
VIEW_FORWARD_WINDOWS=0

VIEW_FORWARD_RIGHT_WINDOWS=32

VIEW_RIGHT_WINDOWS=33

VIEW_REAR_RIGHT_WINDOWS=36

VIEW_REAR_WINDOWS=35

VIEW_REAR_LEFT_WINDOWS=34

VIEW_LEFT_WINDOWS=31

VIEW_FORWARD_LEFT_WINDOWS=30 

6th November 2001

Mal Lloyd

Ongoing dhc3otte.zip DHC3TOtter.zip

DHC3 Otter and DHC3T Turbo Otter by Steven Grant and Fred Choate. These two aircraft are packaged so that wheel version and the float version are in one aircraft folder.  It appears that this is not recognised by FS2K2, so I found it necessary to separate them.  This is how I went about it.

Firstly I have two temporary folders that I call "Downloads" and "Junk" following Andrew Herd's convention. 

1.  Copy DHC3 Otter to "Downloads" and retain as a back-up, "just in case".

2. Make two copies in "Junk", labelling one "Wheels" and the other "Floats"

3. Open the "Wheels" folder and delete model, sound and texture folders relating to float version and the float air file.

4. Open the aircraft.cfg file and delete the entire section headed "[fltsim.1]" contain the float version details.

5. Use the FS2K2 aircraft editor to add this wheeled version to your aircraft folder.

6. Return to "Junk". Open the "Floats" folder and delete the non-float  model, sound and texture folders and the non-float air file.

7. Open the aircraft.cfg file and delete the entire section headed "fltsim.0]".  Renumber the remaining "[fltsim.1]" as a replacement "[fltsim.0]". 

8. Scroll two thirds of the way down the aircraft.cfg file to find "[contact points]":

    -  Amend points 0, 1 and 2 to equal "4.000" instead of "1.000"  (as some kind person posted in "tips")

    -  Amend "static pitch" from the existing 10.something to around 1.000 to 2.000

9.  Use the FS2K2 aircraft editor to add this float version to your aircraft folder.

Use the same procedure for DHC3T Turbo Otter.

If you wish, tidy up the installation by aliasing the wheeled panel to the float panel (or vice versa).  Don't bother to alias the sounds or you will loose the splashes on the floats or gain them on the wheels.

I think the float versions sit a little deep in the water and it may be this that creates the need for high taxiing power.  I guess the contact points need editing to alter this.  Anyone have any ideas?

13th December 2001

Mal Lloyd

Solution

3rd Party Twin Otters

There are several Twin Otters around, I'm not sure if they are different versions or just repaints of a single version so only part of this may apply.
Porpoising: If you are getting the bounce when stationary adjusting the height of the COG usually fixes it. This can be found in the aircraft.cfg file at the end of [contact points]. There is no problem experimenting with this figure as long as you remember the original to come back to if need be. My version is "static_cg_height=5.819755" but yours may need to be different depending on the other geometry.

I had one occurrence of the nose disappearing into the runway during heavy breaking. Once again in [contact points] I identified point0 as being the nosewheel.
point.0=1.000000,19.583333,0.000000,-6.416667,2360.907127,0.000000,0.568311,44.100000,0.166429,2.500000,1.042797,0.000000,0.000000,0.000000,0.000000,0.000000
The ninth group, 0.166429, refers to static compression where 0=rigid. I wonder if this figure is too low and what we are seeing is the nosewheel collapsing? I intend to have a play with this, but haven't done so yet.

If you are interested in the airfiles there are some interesting articles on the Abacus site
http://www.abacuspub.com/ by Tom Goodrick and Rabbijah Guder that may help.

These figures shouldn't imply that the designers were at fault. We've struck a few problems that seem to be introduced by FSedit if using that for the installation. Hope you can get something out of this.