Help with Black Colorado and Pennsylvania please?
 

ok, the problem I have is that the Colorado Battleship is showing up black, and all ships that use the Colorado skin (the Pennsylvania Battleship) are showing up black in game. The question I have about this is will getting Dirct X 10, or making the skin lower res or something help? or does anyone have any other ideas? because, as silly as it sounds, this is the kind of thing that will make me not want to play (they are my favorite battleships!)

I tried reinstalling the patch, and I tried reinstalling the game, and I only got it to work twice. Any help would be greatly appreciated!

ok will have a look, came across a similar complaint months ago about a black Iowa.. was dates on skin usage.

EDIT: dates look fine to me.. skins should be implemented correctly. Don't know what your problem is, sorry.

ok something has caught my eye...

The DATA/SEA/NBB_COLORADO is missing some dds files. Instead there are tgas like in SH3. I bet if you convert those TGA's to DDS files it will fix your problem...??


Maybe anyway...

I have the same problem, so it could not be an incidental thing...

I saw that too, I tried opening and resaving them as DDS, but it didn't work.:down:

Is there a solution to the BLACK BATTLESHIPS problem yet? Easy to test if leaving Pearl, just look over your shoulder at the pair floating in the harbor.

In my case, the overall skins of the ship are straight black, but all the gun turrets are showing up OK.

Oddly... it seems that the skins are OK when viewed from underwater? I think the submerged portion of the hull looks OK, but I can't tell by looking up thru the water if the above water is rendering.

When the camera is completely out of water looking down thru transparent water, it looks like the black continues below the water line. But when I submerge the camera, I don't seem to see that.

But I dunno, maybe I'm seeing things :doh: maybe it is just a black hull and the water effects make it look like there's more to it...


Another side note, I happened to run 1.3 for the first time without the CD installed (cuz I was excited bout that). I wouldn't think that would have anything to do with it but...

I was testing PH last night (i merged the 1.3 PH with my campaign_loc) and I didn't see any untextued (black) BBs, and there were a few BBs there. Guess I should make a quick mission with the US BBs.

Is the black BB issue only on specific dates? I looked at the roster, and the texture dates look fine.

tater

In my case the date is Dec 9, 1941 out of Pearl.

Has anyone tried the TGA to DDS conversion yet I suggested !!????? Using the Nvidia tool obviously...

see post #5

If the roster cfg pointed at dds instead of tga you could just change the text and try as well.

There are a few cases in game where the text file calls a TGA and the real file is dds and it doesn't seem to care, oddly. (the mission loading screens are called in the career start as "1943.tga" but the real file is a dds)

I found post #5 a bit vague, did the saving not work, did he use the NVidia tool, did he successfully create the "correct" type of dds file the game can recognise and install it then test it....???

Sounds to me like it probably isnt that anyway...

It doesn't work. Also conversion of tga's to dds... It is very strange. I think it's the same situation as some of us have previously when we wanted to implement ships from SH3 to SH4. situation is the same. I think there is somewhere a clue to solve this...

regards
Ad

I just made a mission with Colorado and she looks fine to me. Perhaps it's a graphics card issue for those that have the problem?

tater

I saw a post on the Ubi forum from a guy who had the exact same graphics card as me (Nvidia 6800 Ultra) and his graphics looked fine based on the screenshots he posted. So drivers are maybe a suspect...

I also saw someone else mention something about if you haven't completely rebooted the PC and have been running the game and installed the patch between PC sessions where you didn't fully shutdown (standby mode) that it somehow screwed things up and rebooting/reinstalling fixed their problem. Seemed unlikely to me...

So tonight I'm gonna first try just a full reboot (or as I like to call it, the tech support approach to fixing anything.) Next I'll try a driver upgrade, and if all else fails, I'll revert to the clean install and repatch.