Extract some planes from Ultrapack 1.7, UI1.2 to merge them? - BangBoomBang2 - 26.10.2009
Hello,
i would like to extract some planes from Ultrapack 1.7 and UI 1.2 to get them working together with HSFX4.0 mod pack.
Last of those has already the most planes of all packs included, but not all. I would like to have it all together (from those packs) AND it uses SFS (which seem to load faster) and is compatible with Patch 4.09m
I have heard you can add planes to HSFX by putting their folder structure into the MOD folder.(and using JSGME to "activate"
them)
I have already compared the air.ini files and made a list of which planes from UI 1.2 and UP 1.7 are missing in HSFX4
(plus MIG15 and F86 from PeterD)
But the air.ini entries do not correspond to the plane directory names. For Example there is a CANT 1007 and CANT1007t
entry in the UP1.7 air.ini but only one CANT-1007 directory. How does the air.ini or whoever "reads" the air.ini know
WHERE to find the plane directory ? Another example: there is a HurricaneMKIBOB entry in the UP1.7 air.ini
but no corresponding directory ?
I add the "difference" list now what is missing in HSFX 4.0 compared to UP1.7 and UI1.2
in UP1.7 but not in HSFX 4.0:
CANT1007
CANT1007t
CameraShip
CR32
HurricaneMkIBOB
IAR80
IAR80B
IAR80C
IAR80M
IAR81Cnew
Il-4late
Me262V3
MsMorko410
N1K3
P24b, e, f, g
MohawkIIIBOB
SeafireMKIIL
SeafireMkIILCW
SeaHurricane
Su-26
Typhoon
TyphoonMkIB
in UI1.2 but not in HSFX4.0
B17GMod
B25D5NC
B25D20NC
B25J15
B25J22NA
B29 Silver Plate (the one in HSFX is different, has a He111 cockpit!!!, so the UI1.2 is better)
C47A
C47B
Hawk75A3
Hawk75A4
P38F1LO
P38G5LO
P38G10LO
P38G15LO
P38H5LO
P51D25NA
P51D30NA
F51D30NA
SpitfireMkVcFB4xH
SpitfireMkVcCF4xH
SpitfireMkVIIIHF
SpitfireMkVIII25lbs
Ta152C0
Ta152C1
Ta152C3
I also want to make such a list for the maps... but first the planes should come together.
BangBoomBang2
- Guest - 26.10.2009
Wait for the next release of HSFX, they will most likely have many of those aircraft added.
- MoistBandage - 26.10.2009
I'm sorry to say.
You cannot simply state that 1.2 is better than 4.0 just because of one thing. because then I could simply say that 4.0 has more accuarte FM's. making 4.0 better by 10 fold. You should really think before you write
Anto is right by the way.
- BangBoomBang2 - 26.10.2009
Hello
@MoistBandage
:oops: Sorry, my sentence about the B29 Silverplate
Quote:B29 Silver Plate (the one in HSFX is different, has a He111 cockpit!!!, so the UI1.2 is better)
was incomplete.
I meant ONLY the B29 Silverplate version FROM U1.2 is better, because its cockpit looks more accurate (seems to be a newer version ?) AND the nuclear mushroom cloud looked better too. (it missed somehow in HSFX 4.0, looked like the conventional
Mistel explosion.)
I did not mean to compare the whole packages, ONLY the two B29 versions.
BangBoomBang2
Re: Extract some planes from Ultrapack 1.7, UI1.2 to merge t - HH_Cipher - 26.10.2009
BangBoomBang2 Wrote:CameraShip
SeafireMKIIL
SeafireMkIILCW
SeaHurricane
Typhoon
TyphoonMkIB
We already have those. And the Sea Hurri, and the Seafire's are included in Ui1.2
Re: Extract some planes from Ultrapack 1.7, UI1.2 to merge t - 8FS_Bulau - 26.10.2009
BangBoomBang2 Wrote:... the air.ini entries do not correspond to the plane directory names. ... How does the air.ini or whoever "reads" the air.ini know WHERE to find the plane directory ?
As far as I understand it, when the game loads the air.ini, it looks for all the planes in that list, first in the MODS folder, then in the .SFS files. The name of the directories in the MODS folder can be anything. What matters is what is IN the directories.
- vtrelut - 26.10.2009
From someone who has a lot of experience in this kind of undertaking (check the C6 mods pack available at check-six.fr), and who knows partly what happened during the HSFX 4.0 building process:
1) making the whole thing 4.09m compatible does make sense.
2) wanting to add all the planes from several packs working together may not make sense: there are incompatibilities between some new slots (java code conflicts), and there are many overlaps, so a lot of confusion would result from this. For instance, why having 2 Curtiss H-75A-2, 2 Curtiss H-75A-3, A-4? The first thing to do is... to choose what is sensible to combine and include, and also what is believable from a historical perspective. The Cant Z.1007 torpedo is a fictitious frankenplane, which was available prior to the release of 4.09m and her Sparviero. Now that we have a proper Italian torpedo bomber, it makes little sense to keep the CANT Z.1007 torpedo slot.
3) if no choice is made, the result could be a bloated, heavy and unplayable game with a lot of fat and poor performance.
4) SFS are only a partial answer to this, and we should not expect too much. HSFX was built in SFS format by a very small team, basically only one person having done all the SFS encryption and compression work... Let him breathe, thank him for his awesome work and enjoy it, it should be more than enough... Charlie Chap is the hero of this, he made a sensible choice of what to include and what not, let us respect this. We now have such a bunch of Spitfires, Bf-109s, Seafires, Hurricanes to the point where we easily lose track of which one should be used for what purpose, don`t we?
As a campaign builder I can tell you it is a real challenge to find a use for all of these new slots...