|
Post by Dan K. Hansen on Jun 17, 2008 16:19:36 GMT
OK folks. MAKE SURE FILES ARE SHOWN INCLUSIVE THE EXTENSIONSSee how hereInspired by the fact that so many apparently has serious problems with following my instructions on how to install aircraft into FSX (especially HJG-aircraft). I'll describe another way of doing it that may seem more evident and/or easy to follow. Stay tuned this very evening (UTC) as I will be using some of the neat features in FSX and hopefully more of you will have a bit less trouble installing and a bit more fun flying our great HJG-aircraft in FSX. See you all later.
|
|
|
Post by Dan K. Hansen on Jun 17, 2008 19:14:38 GMT
OK here goes first section: 1. EDIT YOUR FSX.CFG file- Make a backup of your FSX.CFG file
FSX.CFG can be found here (in a standard install)
C:\Documents and Settings\<logon-id>\Application Data\Microsoft\FSX
And here in Windows 7:
C:\Users\<logon-id>\AppData\Roaming\Microsoft\FSX
- Open your FSX.CFG with Notepad
- Find the section:
[Main] User Objects=Airplane, Helicopter SimObjectPaths.0=SimObjects\Airplanes SimObjectPaths.1=SimObjects\Rotorcraft SimObjectPaths.2=SimObjects\GroundVehicles SimObjectPaths.3=SimObjects\Boats SimObjectPaths.4=SimObjects\Animals SimObjectPaths.5=SimObjects\Misc
- Add the following line:
SimObjectPaths.x=SimObjects\HJG
(where x should be replaced with the next successive number)
It should then look like this:
[Main] User Objects=Airplane, Helicopter SimObjectPaths.0=SimObjects\Airplanes SimObjectPaths.1=SimObjects\Rotorcraft SimObjectPaths.2=SimObjects\GroundVehicles SimObjectPaths.3=SimObjects\Boats SimObjectPaths.4=SimObjects\Animals SimObjectPaths.5=SimObjects\Misc SimObjectPaths.6=SimObjects\HJG
- Save and close your FSX.CFG
2. CREATE DIRECTORIES/FOLDERS- Create a HJG-folder here:
C:\Program Files\Microsoft Games\Microsoft Flight Simulator X\SimObjects\HJG
- Create the following sub-folders (HJG_Panels and HJG_sounds) as well (like this):
C:\Program Files\Microsoft Games\Microsoft Flight Simulator X\SimObjects\HJG\HJG_panels C:\Program Files\Microsoft Games\Microsoft Flight Simulator X\SimObjects\HJG\HJG_sounds
Stay tuned!
|
|
|
Post by Dan K. Hansen on Jun 17, 2008 19:21:34 GMT
Now take a good look at a screenshot of my folder setup used as an example, and you may be able to get the idea:
|
|
|
Post by Dan K. Hansen on Jun 17, 2008 19:34:12 GMT
The rest should be pretty evident: Inside your panel.cfg and sound.cfg you just have to edit the alias to: Panel.cfg:[fltsim] alias=HJG_Panels\<whatever your panel foder name is>example: [fltsim] alias=HJG_panels\panel.b707-320badvc.1970 Sound.cfg:[fltsim] alias=HJG_sounds\<whatever your sound foder name is>example: [fltsim] alias=HJG_sounds\B707_PW JT3D7_fanjet To give you an idea of what to place in the panel/sounds folders see here for two examples of first the panel folders and then the sounds folders: (please note that I use my own naming convention, you are of course free to use your own too, as long as there is consistency!) panel ex.:sound ex.:
|
|
|
Post by Dan K. Hansen on Jun 17, 2008 19:37:16 GMT
The Core files (separate download) should be placed in the default gauge / sound folders:
C:\Program Files\Microsoft Games\Microsoft Flight Simulator X\Gauges
C:\Program Files\Microsoft Games\Microsoft Flight Simulator X\Sound
The Effect (separate download) files in the default effect folder:
C:\Program Files\Microsoft Games\Microsoft Flight Simulator X\Effects
Now the only thing remaining is to add textures
|
|
|
Post by Dan K. Hansen on Jun 17, 2008 19:49:59 GMT
Please use the correct texture for the right aircraft!
That aside.
in each of the texture zip-files you will find a "add to aircraft.cfg.txt" file which tells what to place in your aircraft.cfg file of the relevant aircraft.
PLEASE TAKE NOTE OF THE FIRST TWO LINES IN THE aircraft.cfg FILES!!!
// Add your [fltsim.xx] sections here. // Remember to start with 0 (zero).
These two lines are actual placed there for you to read, and a very good indication of what you are expected to do in order to have your favorite texture to show!
Each texture has its own fltsim-section
They are each numbered with a unique number starting with 0:
[fltsim.0] [fltsim.1] [fltsim.2] [fltsim.3] ... ...
If this rule is not obeyed this particular aircraft will show up black!
and finally if you want to isolate your HJG-aircraft from the others in the selection menu, add the following two lines in each fltsim-section:
ui_typerole="Classical Airliner" ui_createdby="Historic Jetliners Group"
here is an example from my B707-320C aircraft.cfg file:
[fltsim.0] title=HJG B707-320C Cathay Pacific Airways 1977 sim=B707-320C model= panel= sound= texture=cathay_pacific_1977_351c_vr-hgu kb_checklists=boeing707-320c_check kb_reference=boeing707-320c_ref visual_damage=1 atc_id=VR-HGU atc_airline=CATHAY atc_flight_number=320 atc_heavy=0 atc_parking_codes=CPA atc_parking_types=GATE,RAMP ui_manufacturer="Boeing" ui_type="707-320C" ui_variation="Cathay Pacific Airways (1977)" ui_typerole="Commercial Airliner" ui_createdby="Historic Jetliners Group" description=HJG Boeing 707-320C repaint by Michael VERLIN
[fltsim.1] title=HJG B707-320C Pan American 1964 sim=B707-320C model= panel= sound= texture=pan-american_1964_321c_n799pa kb_checklists=boeing707-320c_check kb_reference=boeing707-320c_ref visual_damage=1 atc_id=N799PA atc_airline=CLIPPER atc_flight_number=320 atc_heavy=0 atc_parking_codes=PAA atc_parking_types=GATE,RAMP ui_manufacturer="Boeing" ui_type="707-320C" ui_variation="Pan American (1964)" ui_typerole="Commercial Airliner" ui_createdby="Historic Jetliners Group" description=HJG Boeing 707-320C repaint by Camilo LUENGAS
|
|
|
Post by Dan K. Hansen on Jun 17, 2008 20:04:31 GMT
OK, "I've done everything you've said and my aircraft still wont show"
My reply to this will be:
"No you haven't" otherwise your aircraft would show!
The main reason for a NO-SHOW is a wrongly aliased panel: NO-PANEL => NO-SHOW (FSX thinks its an AI-aircraft)
Wrong SIM reference: (check that the sim-part of the fltsim-section is actually in sync with the *.air file in the folder:
sim=B707-320C should reflect that there is a B707-320C.air file present (note you shall NOT include the extension in the aircraft.cfg file)
wrong MODEL reference
model= indicates that the model folder is used
in the B707-320C you will notice there are several modeltypes all using the same air-file, but isolated by each own model folder:
model model.323C model.323C_S2HK model.HK3 model.S2HK
hence you could use the same aircraft.cfg file but using different models by indication which model folder you should use. In case you have a 323C_S2HK model, your fltsim-section should have this model statement: model=323C_S2HK
If not the sim and the model sections are correct you will get a no-show. If you have wrongly aliased your panel you will get a no-show. If you haven't installed the core files you will get a panel without gauges If you haven't installed the textures correct you will get a no-show. If you haven't installed the sounds correct, you will have a very silent aircraft. If you have wrong bitmaps in the texture folder, you will get a black aircraft.
Have fun and PLEASE don't forget that there is really no magic involved, just pure logic and file references.....
and finally:
ALL of our current aircraft have been installed on at LEAST 3 computers without errors, so if you have a problem with a no-show it is very likely your own fault ;-)
Our aircraft do all show in both FS9 and FSX id installed correctly.
Please go through your install procedure thoroughly a few times before asking at the forum.
Who knows, the penny might actually drop? ;-)
Yours sincerely
the HJG-team
|
|
|
Post by Dan K. Hansen on Jun 17, 2008 20:08:46 GMT
And by the way, you can actually use these same procedure with any 3. party aircraft not just HJG. and you will then be able to isolate the default aircraft from all the goodies ;-)
In FS9 they were all mingled together in one big mess.
As a matter of fact you could easily add a WOAI folder under SimObjects and place all your AI-aircraft in here well stuffed away from the other aircraft in your hangar.
Lets spend more time flying than installing!
|
|