Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[milvipes]

Much dissatisfaction has been expressed about King George V BB as the visual model for IJN and USN generic BB, and archie1971 has done a wonderful job in correcting it for generic IJN BB. By leveraging off his work, I've repainted her in USN colors (measure 22).
Yes, it's nice to have historical ships like Arizona or Iowa represented in this game, but the fun part of this game is that we're creating our own version of history! This ship allows you to spam your dream campaign with battleships wherever you want, whenever you want, and how many you want.

Download here
Note however, that since archie's original mod is quite old, newer versions of USSBBGeneric ships.ini entry are not compatible with it. You must replace the stock entry with the content of the attached txt file.

[cbradbury]

Note that this cannot be used in BAT, as there is no USSBBGeneric in WAW - adding it would lead to a ctd.

[urmel]

Thanks milvipes,works in my 413.4.

[Griffon_301]

Funny thing is, in TGA the USSBBGeneric works, so it's just one or two classfiles that are missing in WAW I guess... Time to look through the classfiles in objects.ships to activate it again...

[SAS~vampire_pilot]

Would be interesting, I could not track down the error.
TGA was basically stock ships only when Monty left off. WAW ships was already heavily modded.

It would be only of historical interest but for compatibility's sake with very old missions, maybe a nice thing to have.

[Griffon_301]

I really guess it's a single classfile that's missing in WAW...as a plan b, would it be possible to just clone an existing classfile of a BB and rename internal references to USSBBGeneric?

[asheshouse]

Is there really a need to have a ship named *BBGeneric in the FMB menu. I would say not.
The only argument is, supposedly, to maintain compatibility with old missions.
How many are affected?
Is it not simpler to consign the Generic ships to the dustbin and, maybe, simply update the very few old stock missions which would require it.

[Griffon_301]

I fully agree with you but considering backward compatibility for older PTO campaigns it would be nice to reintroduce the USSBBGeneric to WAW again...
I have an idea and might investigate after returning from our vacation...

[asheshouse]

You can add extra ship names to the chief.ini, to maintain compatibility, without adding new classes.

Example - Clone USS Colorado as USSBBGeneric2  (Generic2 cause my SASModAct already has Generic)

Add the following text lines to chief.ini

Code: [Select]

USSBBGeneric2         ships.ShipAsheUSS$Colorado         1 icons/shipDestroyer.matand

Code: [Select]

[Ships.USSBBGeneric2]
 com.maddox.il2.objects.ships.ShipAsheUSS$Colorado
In FMB you will find a new ship option in the menu for USSBBGeneric2   --   which uses the Colorado model.

In the *.mis file when saved you have

Code: [Select]

[Chiefs]
  0_Chief Ships.USSBBGeneric2 1 0 2 1.0
[0_Chief_Road]
  37180.45 41005.00 120.00 0 64 7.330833911895752
Using this method any existing model in the game can be given optional names.

[SAS~vampire_pilot]

Huh.
I never thought about it that way. Thanks for that tip.

[cbradbury]

How clever is that?

A quick question, ashe - does the cloned ship have its' own characteristics e.g. guns, speed, or does it retain the generics' features as by this method nothing has changed in ships.ini?

P.S. I think I answered my own question - I changed the IJNBBGeneric default speed in ships.ini, then cloned the Fuso to that slot - the latters' speed was retained.

Don't quite understand why, I would have assumed that the game read the ship info from its ships.ini entry. Cool, anyway.

[asheshouse]

It will be an exact copy of the original. Any variations would require a new “slot”.