Duplicate skin report: ta152h

[Krusty]

I noticed when doing the ta152 skin cataloging that there is a duplicate skin. It's 100% identical.

Slots 2 and 4 are the same. They share the same NAME listing as another skin also, but this one has a unique bitmap to go with it.

The skins:

ta152h_2



ta152h_4




I seem to recall something like this has been around for a while, but as new ones were added the duplicate still remains. I'm not sure if is a duplicate identical submission, or if there should be a different skin entirely under one of those slots.


Submitted for correction.

[Soulyss]

They had to add it a second time, the first one is missing a propeller blade.

[lyric1]

Same issue with the 109-g14 of Dutch guy 9./JG300

[Krusty]

Same issue with the 109-g14 of Dutch guy 9./JG300

Actually with that example, you have a slight difference in the materials properties, meaning it's the same skin but different submissions of it. The Ta152s are 100% identical that I can see.

[Krusty]

They had to add it a second time, the first one is missing a propeller blade.

Interesting enough, HTC started adding 3D prop blades on the newest rides. I noticed this on the P-40 screenshots, I think. This is one of the older ones, heheh

[Chilli]

Krusty,

Wonderful job with the catalog    Can you help me with B239_6?  I loaded it into the AH folder and was able to see the proper identifier in the hangar, however when I select it, it goes back to the default skin identified and never shows the _6 skin.  I know that with the new bump map updates the skins will have to be updated, but I thought that they would still be valid skins, just wouldn't have the cool bump map effects.

Is this still a valid skin, or is there something that I am missing?  Keep up the nice catalog work.  This is exactly what is needed to keep my AH skins folder lean 

[Krusty]

They all still work as of last night. The bump maps only affect the skins that have it applied.

Just a quick mental checklist:

did you:
1) Save the skin *.res to the "skins" folder?
2) make sure you have no local skin files over-writing it (i.e. b239_6 with some working files?)
3) Are you able to log on for a minute or two, then log off?

I read in a thread a long time back that there is an index file of sorts that tells AH what skins are enabled and what are not. This gets updated automatically when you log on. I'm not sure if that's the reason this isn't working, as those B239 skins aren't overly "new" or "recent" and should already be in your skin index file thingamajig.

[Fencer51]

Hmmm.. let me see what my records show.

[Chilli]

No subscription, so that might be the problem thanks.  Hope to be on by the weekend