The proving ground example is a little confusing, only because ProvingGround.opt and ProvingGroundHangar.opt do not exist
In your example you have
Example:
ProvingGroundHangarModel = FlightModels\ProvingGround.opt
This will load "FlightModels\ProvingGroundHangar.opt" and "FlightModels\ProvingGround.ini" (or txt files).
the example requires 2 opts the ProvingGround.opt and ProvingGroundHangar.opt
But by default the Proving Ground just uses the Hangar.opt, which is a single opt
Sorry but I'm just trying to get my head around why it has to use 2 opt's
Ok for another example if I wanted to use the Imperial Hangar as the ProvingGroundHangarModel
Would I have to use
ProvingGroundHangarModel = FlightModels\ImperialStarDestroyer.opt
So that would load ImperialStarDestroyerHangar.opt and the ImperialStarDestroyer.ini.
But if this is the case why do I have to use ImperialStarDestroyer.opt, which it a model of a Starship, not a Hangar, only the ImperialStarDestroyerHangar.opt is a Hangar opt????
or could I just use
ProvingGroundHangarModel = FlightModels\ImperialStarDestroyerHangar.opt
Would that still load ImperialStarDestroyer.ini or not?
Or by you example do I have to rename the Opts I wish to use ProvingGround.opt and ProvingGroundHangar.opt
I'm sorry to go on about it, but a bit of clarification would help please
_________________________________________________________________
On another note, and I probably should have mentioned this before, as you might know I converted all the [CraftName***].txt files to *.ini files, but if you try to use Hangar.ini, it doesn't work, if you do not use HangarCamera.txt, HangarMap.txt and HangarObjects.txt the game loads it's default settings
You can try it yourself,
Move the Hangar***.txt files mentioned above
create a Hangar.ini file
The copy and paste this into it
Code: Select all
[HangarCamera]
;Camera X,Y,Z
Key1_X = 1130
Key1_Y = -2320
Key1_Z = -300
Key2_X = 2240
Key2_Y = 300
Key2_Z = -400
Key3_X = -1120
Key3_Y = 1390
Key3_Z = -790
Key6_X = -1200
Key6_Y = -1530
Key6_Z = -850
Key9_X = 1070
Key9_Y = 4640
Key9_Z = -130
[HangarMap]
; Must contain at least 4 object line.
; Format is : model index, position X, position Y, position Z, heading XY, heading Z
; or : model index, markings, position X, position Y, position Z, heading XY, heading Z
; Numbers can be in decimal or hexadecimal (0x) notation.
; When position Z is set to 0x7FFFFFFF, this means that the object stands at the ground.
;ModelIndex_314_HangarMonitor
314, -1059, 1313, 0x7FFFFFFF, 38600, 0
;ModelIndex_309_HangarCrane
309, 725, -416, 0x7FFFFFFF, 23500, 0
;ModelIndex_313_HangarGenerator
313, -1352, 1440, 0x7FFFFFFF, 536, 0
;ModelIndex_310_HangarCrate
310, 794, -810, -848, 6800, 12500
;ModelIndex_310_HangarCrate
310, -803, -1464, 0x7FFFFFFF, 49200, 0
;ModelIndex_310_HangarCrate
310, -1563, 944, 0x7FFFFFFF, 51436, 0
;ModelIndex_083_ContainerBox
83, -506, -2136, -722, 32836, 16480
;ModelIndex_083_ContainerBox
83, -841, -1628, 0x7FFFFFFF, 53100, 0
;ModelIndex_083_ContainerBox
83, 1240, -2098, -722, 272, 16480
;ModelIndex_084_ContainerSphere
84, -834, -2034, 0x7FFFFFFF, 32336, 0
;ModelIndex_080_CargoCanister
80, -3474, -275, 0x7FFFFFFF, 29436, 0
;ModelIndex_002_Ywing
2, -1038, -798, 0x7FFFFFFF, 7700, 0
;ModelIndex_050_Shuttle
50, 0, 1146, -1288, -741, 50536, 0
;ModelIndex_310_HangarCrate
310, -873, -1456, -849, 60472, 20400
;ModelIndex_310_HangarCrate
310, -3095, -592, 0x7FFFFFFF, 51436, 0
;ModelIndex_083_ContainerBox
83, -1751, -1996, 0x7FFFFFFF, 31172, 0
;ModelIndex_083_ContainerBox
83, 979, -2103, 0x7FFFFFFF, 37036, 0
;ModelIndex_084_ContainerSphere
84, -1374, -2068, 0x7FFFFFFF, 40536, 0
;ModelIndex_080_CargoCanister
80, 3474, 357, 0x7FFFFFFF, 20536, 0
;ModelIndex_080_CargoCanister
80, -195, -1910, 0x7FFFFFFF, 54372, 0
;ModelIndex_004_Bwing
4, 1378, 40, 0x7FFFFFFF, 40036, 0
;ModelIndex_315_HangarWorkStand
315, 1179, 273, 0x7FFFFFFF, 40036, 0
;ModelIndex_002_Ywing
2, 1100, -523, 0x7FFFFFFF, 49036, 0
;ModelIndex_315_HangarWorkStand
315, 820, -705, 0x7FFFFFFF, 49036, 0
;ModelIndex_315_HangarWorkStand
315, -1065, 200, 0x7FFFFFFF, 16600, 0
;ModelIndex_001_Xwing
1, -1003, -100, 0x7FFFFFFF, 16600, 0
;ModelIndex_003_Awing
3, -950, 560, 0x7FFFFFFF, 16600, 0
;ModelIndex_315_HangarWorkStand
315, -1065, 800, 0x7FFFFFFF, 16600, 0
;ModelIndex_058_CorellianTransport2
58, 965, -3600, 0x7FFFFFFF, -9500, 0
[HangarObjects]
LoadShuttle = 1
ShuttleModelIndex = 50
ShuttleMarkings = 0
LoadDroids = 1
IsHangarFloorInverted = 0
FlightModels\HangarCrane.opt = FlightModels\RebHangarCrane.opt
FlightModels\HangarDroid.opt = FlightModels\RebHangarDroid.opt
FlightModels\HangarDroid2.opt = FlightModels\RebHangarDroid2.opt
FlightModels\HangarGenerator.opt = FlightModels\RebHangarGenerator.opt
FlightModels\HangarMonitor.opt = FlightModels\RebHangarMonitor.opt
FlightModels\HangarRoofCrane.opt = FlightModels\RebHangarRoofCrane.opt
FlightModels\HangarWorkStand.opt = FlightModels\RebHangarWorkStand.opt
Open the game and go to the Pilot Proving Ground to view the hangar, if the Hangar.ini worked you should see a YT1300, a B-Wing, a A-wing next to the X-wing, but no the game hasn't loaded them, now replace the HangarCamera.txt, HangarMap.txt and HangarObjects.txt, you should now see the custom Hangar, I'm not sure why this happens
If you play a mission and your mothership starship uses a custom hangar opt say the CalamariCruiserNew.opt which has a custom hangar opt and CalamariCruiserNew.ini, the Ini file loads the custom settings overriding the default settings and the Hangar****.txt files.
.
.
.