Simviation Forums

Hey guys. I followed this tutorial (http://forums.overclockers.co.uk/showth ... t=17996209) to give some POSKY planes a VC. I'm having trouble with Part 2 step 2 though:

Part 2: The Panel Merge with default VC
1. Copy-paste the panel folder from the default 737-800 into the Posky 737-600 folder.
2. Copy-paste the folder named texture from the default 737-800 folder into the Posky 737-600 folder**
3. Open the model folder of the default 737-800.
4. Select B737_800_interior.mdl and paste it into the model folder of the Posky 737-600

**You might already have a folder called "texture" if you do you will have to rename it. This will affect the paint its calling so don't forget to update the aircraft.cfg!

What do you need to do to the CFG to make the texture work?

I assume it has to do with this part:

[color=#000000][fltsim.0]
title=Project Opensky Continental Boeing 737-900
sim=OSBoeing737-900
model=
panel=
sound=
texture=
kb_checklists=Boeing737-800_check
kb_reference=Boeing737-800_ref

atc_id=N11411
atc_airline=Continental
atc_flight_number=725
atc_heavy=0
atc_parking_types=GATE, RAMP, CARGO
atc_parking_code=COA

ui_manufacturer=Project Opensky
ui_type=737-900
ui_variation=Continental
visual_damage=1
description=Project Opensky - Boeing 737-900\nVersion - Version 2004.9.3\n\nModel Designer\n

I don't think that will work with the Posky aircraft as they were created with the FS9 SDK. Most Posky aircraft have a version with a VC that should work in FSX.

I don't think that will work with the Posky aircraft as they were created with the FS9 SDK. Most Posky aircraft have a version with a VC that should work in FSX.

There's an FSX model update. It does need to be an FSX model, your right.

8-)

However, to answer your question; Multiple texture folders follow the FS folder naming protocol. The folder name (Texture) plus a suffix separated by a period like this: Texture.1, Texture.blue, Texture.BA etc. The folder is identified in the [fltsim.x] texture= line by the suffix like this

texture=1
texture=blue
texture=BA

Use any default Aircraft.cfg as a reference to see how it works.

However, to answer your question; Multiple texture folders follow the FS folder naming protocol. The folder name (Texture) plus a sufffix separated by a period like this: Texture.1, Texture.blue, Texture.BA etc. The folder is identified in the [fltsim.x] texture= line by the suffix like this

texture=1
texture=blue
texture=BA

Use any default Aircraft.cfg as a reference to see how it works.

Thanks, I'll try it right now.

8-)

However, to answer your question; Multiple texture folders follow the FS folder naming protocol. The folder name (Texture) plus a suffix separated by a period like this: Texture.1, Texture.blue, Texture.BA etc. The folder is identified in the [fltsim.x] texture= line by the suffix like this

texture=1
texture=blue
texture=BA

Use any default Aircraft.cfg as a reference to see how it works.

the reason to Change the Posky texture folder to a new name ie.
'Texture.posky' is because the texture folder copied over from the default 737 folder has a texture config file required for interior model.mdl file

However, to answer your question; Multiple texture folders follow the FS folder naming protocol. The folder name (Texture) plus a suffix separated by a period like this: Texture.1, Texture.blue, Texture.BA etc. The folder is identified in the [fltsim.x] texture= line by the suffix like this

texture=1
texture=blue
texture=BA

Use any default Aircraft.cfg as a reference to see how it works.

the reason to Change the Posky texture folder to a new name ie.
'Texture.posky' is because the texture folder copied over from the default 737 folder has a texture config file required for interior model.mdl file

As I pointed out earlier, this VC tweak will not work with Posky aircraft as they were all created with the FS9 SDK.

Naming texture folders works on the same principle as adding a repaint.

Okay, I have a VC, but hw do I move the viewpoints back? Right now I have this (I'm looking backwards):



Sorry if it's obvious, I'm new at this.

8-)

The easy way is to set up in your settings.  There are some things like "eye point ..." look for the ones that say move forward back etc...

It microsoft's active camera

You can move the eyepoint in Aircraft.cfg. Look under the [Views] section.

Got it working now. Thanks guys.

8-)