@Graf Paper
Hi! Thanks ^^
It's the same; you can call her also "LUS=ship X"; her will be desplayed with the name you prefer.

@GOZO
Thank you; This is strange; they've been used by some users, never cause CTD; please continue tests, and refer me ^_^ If there is a problem we are here for solve!

I had some CTD's when I had the community units also. I was suspecting either the HOS or LUS from Vondos. But then after I removed community units and reinstalled VonDos's ships, no more CTDs.
Also;
I remember someone pointing out some of the old ZIPs had the wrong folder structure so when you JSGME enable them you had a CTD. For example my Old Hospital Ship was like that. I THINK VonDos FIXED THESE already. So if you downloaded before this, check the folders for these two ship inside MODS..

Thank you for clarifying that entry for Aquitania, VD. :)

I've been working on combining the ships from the AOTD-AA-Ship-Schleuse-Bugfix, Community Units, and all of your ships into a single mod for my install of GWX, just to keep it simple and not clutter JSGME with too many mods.

Part of that effort includes alphabetically organizing all the entries in EnglishNames.cfg.

Here's my observations:

There are a few duplicate entries between the AOTD-AA-Ship-Schleuse-Bugfix and Community Units. To my knowledge, listing a ship twice can cause CTDs. Please correct me if I'm wrong about this.

There are also instances where a duplicate listing is ambiguous, such as:
...where I believe it must be one or the other but I cannot find the corresponding folder in '..data\Sea' to determine the correct entry in EnglishNames.cfg.

Lastly, there are entries that seem correct but there appears to be no matching folder for the ship in '..data\Sea'.

The way I understand it, any ship that is called in one of the campaign layers must match its data exactly as listed in '..data\Sea', '..data\Roster', and EnglishNames.cfg. This is especially problematic with the random layer, Campaign_RND.mis, where the ships called range across the entire list and one single error will cause a CTD. Compounding the aggravation is that the randomness used means you may go 5 minutes or 5 months before a broken ship is called by Campaign_RND.mis. The scripted layers are not usually the trouble, since only specific ships are called.

Any ideas you can share with me, VonDos, would be deeply appreciated.

A small idea can be this: open your "shipname".cfg in your ship folder; for example nlus_.cfg in data\sea\nlus_ folder and you'll be able to know roster real name (that is also first ship identifier in campaign layers ^_^

I've tried that. Comparing the .cfg file in the ship's folder to the entries in EnglishNames.cfg leads me to two conclusions...

1. There are ships which have folders in '..data\Sea' that are not listed in EnglishNames.cfg.
2. There are ships listed in EnglishNames.cfg that do not have folders in '..data\Sea'.

Suffice it to say things are a real mess and I'm not sure if I'll ever get it all sorted out. I'm hoping I can because that should bring an end to the CTDs from using Community Units with the AOTD-AA-Ship-Schleuse-Bugfix.

Some of this might have been avoided if EnglishNames.cfg wasn't such a mess. That's why I'm making it alphabetical, to keep better track of the entries.

Thanks for the tip about the name in the ship's .cfg file, VD! :up:

P.S. Shouldn't I keep the GWX entry 'LUS=HMT Aquitania' instead so your new Aquitania will show up in the campaign missions or is the 'LUS' tag what is used by the campaign so that 'LUS=Cunard Aquitania ocean liner' will still show Aquitania in all her glory without the need to edit the campaign files?

Ok..time for bed despite my overactive mind causing me to be restless. My eyeballs are bleeding from staring at text editors and files all night and half of the previous day.

Be sure; name chosed isn't related with campaign layer :up:

Goodnight ^^

Hey VonDos, all the ships you gave me have been linked up here: http://www.bts-mods.com/?page=sh3-unitmods-page1

That's 14 ships if I'm not mistaken, if you've got more you're welcome to upload them and I'll get everything linked up ASAP :cool:

Nice news ^^ Thanks! :up:
Yes, they're 14; some days and they will be 15, when Duilio will be ready :D

Great ships:up: Can i use them with GWX 2.1?

Yes, you can ^_^ i also use them with GWX 2,1; they work fine. :up:

Just out of interest, was there a reason only these ships were included in GWX 3.0:
Warspite by Von Dos
S.S. Rex by Von Dos
Laconia by Von Dos
St Georgio cruiser by Von Dos

Are the Queen Mary, Aquila, Hospital ship, Aquitania, Normandie not included because of historical accuracy, ie they didnt serve in WW2?
Do they work in GWX 3.0?

Want to make my new GXX 3.0 as historically acurate as possible b4 i start a new career. Can anyone enlighten me pls.
Thanks....

The only ship By Von Dos in GWX 3.0 is the Averof.
It was an updated version of Von Helsings Averof.
I added the visually correct Guns and the Plate on the rear.
(Even Von Dos didn't know about that plate!)

The others are added by BBW's add ons.

Ah yep sorry i meant to say why was only these particular 4 ships added into BBW add ons for GWX 3.0? Do you know if there is an historical aspect?
Its just if the ships tht wern't included and they were in WW2, I'd like to add them provided they are compatible with GWX 3.0 of course.

As far as damage zones, and such?
Most of Von Dos's ships are OK, if not all.

BBW adjusted scripts from the 2.1 files if I'm not mistaken.

Some of Von Dos's units were not around then.

Give us all some time to adjust things.
I know BBW is working on things, Von Dos is working on things,
And so on and so forth.

And it's Christmas!
What are you doing here?
:rotfl:

I'm waiting to DL, install and open my Christmas present from The Team! :lol:
Besides, I worked a 12 hour day shift today so...Bah, humbug! Got paid rather well, tho...the wonders and downfalls of rotating shifts!

Seriously, you will get lots of questions...but I doubt any impatient demands for answers. We are just getting them "on record" and will wait patiently while things get sorted out for the next months. I know I'm counting my blessings...GWX3.0 and a new ASUS 26" widescreen on the 29th...:rock: . Too bad there isn't a widescreen "fix" for SH3 but with a program this old, you just live with the small inconvenience of running a 4:3 resolution.

Hey, were all extremely happy here...this is the expected result of the release of GWX3.0!

Vic