Possible solution to some random crashes - requires testing

**Gigantus** · March 19, 2013, 08:13 PM

We have had a good number of crashes reported where the log ends with the call for the loading bar or logo. A seemingly related problem as pointed out by k/t leads us to the assumption that the large number of loading screens may be responsible.
To test this will require participation of members due to the randomness of it happening.

Please proceed as follows:

Make a copy of the data\loading_screens folder
Delete the loading_screen_20 to 69 files in the data\loading_screens folder

Kindly report back if the instances of random crashes have reduced in cases where you would expect to get a loading screen.

**Katagelan** · March 19, 2013, 10:06 PM

I did that and the Ctd's are less frequent.
What may complicate the test is that it seems that the mysterious Ctd's related to artillery are there too.
Maybe you remember that issue that plagued me in Call of Warhammer.
These Ctd's also occured during the loading screen before a battle.

**Gigantus** · March 19, 2013, 10:10 PM

The artillery problem in COW was related to the projectile, that will not be an issue here. It will most likely be related here to the loading screens themselves.
Could you reduce your loading screens by another 10 (delete 11-19)? and continue testing?

**Katagelan** · March 20, 2013, 04:54 PM

Done.

**the man, the myth, the legend** · March 20, 2013, 06:10 PM

After deleting the loading screens, it seems as if my campaign map freeze issue is fixed. Thanks.

**Hanti** · March 20, 2013, 07:30 PM

I've removed ALL your loading screens and replaced them with only two new ones made by myself. My IrfanView could not read your pictures anyway (although game showed them well).
Not a single CTD after removal.

**Gigantus** · March 20, 2013, 08:57 PM

Originally Posted by Hanti

I've removed ALL your loading screens and replaced them with only two new ones made by myself. My IrfanView could not read your pictures anyway (although game showed them well).
Not a single CTD after removal.

You may have just hit the jackpot. The screens show 'Targa 2' as format but the usual one is 'Targa 10'. I have redone one loading screen, please have a look if Irfanview can read it and use it for testing.

**Hanti** · March 20, 2013, 09:51 PM

**Gigantus** · March 21, 2013, 02:30 AM

Yes, I am aware of the rather curios way those screens are done (the middle area is totally translucent in GIMP preview). It is the same way the character portraits are done: in portrait mode they show a background but in the unit list at the bottom they don't. Unfortunately there is no way to reverse that.

Could you just use that loading screen and see if you still get crashes? I saved it in the targa 10 format.

**Hanti** · March 21, 2013, 04:56 AM

Originally Posted by Gigantus

Could you just use that loading screen and see if you still get crashes? I saved it in the targa 10 format.

It seems working normal. No CTD until now. The test will continue anyway.

**Gigantus** · March 21, 2013, 05:19 AM

I have been able to convert the format into a 'previewable' version (Targa 10, 24 bit) - attached are the first seven loading screens if you would like to test. It appears the screens were created with Photoshop and then saved in the wrong format.

The remaining screens are converted as well now. Once the test goes well I am going to upload them as a patch as they total a respectable 78MB.

**k/t** · March 21, 2013, 05:13 PM

I replaced all the loading screens with those 7 and for a while all was well, but then I still got a crash (when trying to reload a game). There's something about a character record and also the loading bar. Is that in the proper format?

Spoiler Alert, click show to read:

**WhiffOfGrapeshot** · March 21, 2013, 05:49 PM

Yeah, asking for "loading_bar.tga.dds" is strange. There is no such file in the directory.

And I wonder if the character_record problem has anything to due with some of the faction heirs not being in the family trees, so when a king dies, things go bonkers.

**k/t** · March 21, 2013, 08:13 PM

Yes there is. There's "loading_bar" and "loading_logo". They're before the loading_screen files, in the same folder.

I don't think the multiple family trees would cause such a problem. TLK and SS use them.

**Gigantus** · March 21, 2013, 08:42 PM

Originally Posted by Maximicus

Yeah, asking for "loading_bar.tga.dds" is strange. There is no such file in the directory.

And I wonder if the character_record problem has anything to due with some of the faction heirs not being in the family trees, so when a king dies, things go bonkers.

The game looks for the TGA.DDS version by default, if not present it will use the regular TGA version.

**k/t** · March 21, 2013, 11:03 PM

Crap, got another one while starting the game. When the red text started appearing I pressed Esc and boom.

Spoiler Alert, click show to read:

Could there be something wrong with the loading_logo and loading_bar?

Whoa! Again! This time I got as far as the campaign menu, and I clicked Continue Campaign. The loading screen came up, and then boom.

Spoiler Alert, click show to read:

And again! Same place as the second time.

**Gigantus** · March 22, 2013, 12:46 AM

I have done a little more formatting, this time inclusive the logo and bar. Simple delete the existing loading screens and then extract in the data\loading_screen folder.

**k/t** · March 22, 2013, 01:21 AM

Which ones are the exiting loading screens? I didn't know they are classified by entry or exiting.

Or do you mean the existing screens? The 7 new ones?

Nooooo! It didn't work.

I clicked Continue Campaign. First it showed a loading screen with the loading bar, but only for a very short time, then it switched to another loading screen without a bar, and then it crashed. Why would it switch screens like that?

Spoiler Alert, click show to read:

**Gigantus** · March 22, 2013, 01:42 AM

Typo gremlin strikes again.

First time I hear of the double loading screen.
I am of two minds to recommend to everyone to simply rename their loading_screen folder so that the vanilla TGAs are being used. If the errors continue (loading_bar in last line of log) then we have been barking up the wrong tree.

**k/t** · March 22, 2013, 02:00 AM

I'll wait until other people report.

Thread: Possible solution to some random crashes - requires testing

Thread Tools

Search Thread

Display

Possible solution to some random crashes - requires testing

Re: Possible solution to some random crashes - requires testing

Re: Possible solution to some random crashes - requires testing

Re: Possible solution to some random crashes - requires testing

Re: Possible solution to some random crashes - requires testing

Re: Possible solution to some random crashes - requires testing

Re: Possible solution to some random crashes - requires testing

Re: Possible solution to some random crashes - requires testing

Re: Possible solution to some random crashes - requires testing

Re: Possible solution to some random crashes - requires testing

Re: Possible solution to some random crashes - requires testing

Re: Possible solution to some random crashes - requires testing

Re: Possible solution to some random crashes - requires testing

Re: Possible solution to some random crashes - requires testing

Re: Possible solution to some random crashes - requires testing

Re: Possible solution to some random crashes - requires testing

Re: Possible solution to some random crashes - requires testing

Re: Possible solution to some random crashes - requires testing

Re: Possible solution to some random crashes - requires testing

Posting Permissions