Model image bug or WAD?

[ADukes]

When there's no country specific model image assigned the game should load the default one. But that's not the case when you have a gap between two models, instead the game loads the country specific image of the previous model.

E.g.: ENG inf model 0 has the image ill_div_eng_0_0 and ENG inf model 1 has no image. You would expect that ENG inf model 1 should get the image ill_div_0_1 but it does not and ends up with the same image as model 0 instead.

 

[Epaminondas]

I think that might be very difficult to do. Wouldn't you have to create a duplicate ill_div_0_1 image and then tag it as ill_div_eng_0_1, and then repeat this duplication and re-tagging for every missing image for every labelled nation. And when images did become available for the missing slots, wouldn't you then have to manually remove all the duplicates you put in before you could tag the new ones? I think it's probably wad.

 

[ADukes]

Either you missunderstood my post or it wasn't clear enough.

If ther is no ill_div_eng_0_1 the game should display ill_div_0_1 instead. The problem is, that if ill_div_eng_0_0 exists and ill_div_eng_0_1 doesn't, the game shows ill_div_eng_0_0 instead of ill_div_0_1.

 

[Epaminondas]

Yes, I did misunderstand and no, you were clear enough. I just didn't pay enough attention. Sorry.

Can you give an actual example of the situation you're describing - I just checked the models file and there are images there for both ill_div_eng_0_0 and ill_div_eng_0_1 so I'm guessing you just picked those as hypotheticals.

 

[ADukes]

I'm guessing you just picked those as hypotheticals.

Correct.

Ill_div_bel_25_2 should be an actual example. There's no Ill_div_bel_25_3 imgage file and so the belgian model 4 destroyer should display the Ill_div_25_3 division picture but does Ill_div_bel_25_2 instead.

 

[Epaminondas]

Sorry to be so long in responding, AD. I've been occupied elsewhere lately. You're dead right with the Belgian example, and I have no real insight as to why it works the way it does. The only thing I can think of is that the system is 'siloed', so that once the _bel tag is added to any model it sets up an internal 'partition' that prevents switching backward and forward between tags - i.e. it will only look in the _bel set. You could try checking that out by duplicating the ill_div_25_3 pick and inserting the _bel addition.

If that it is the case, though, it puts us back where we were in having to manually detect every gap and rename a generic pick to close it.