TATW crashes when attacking Isengard

[tprb]

Moved from Vanillla 3.2 essential bugfixes


Hello,

I have a problem with my campaign.
I am Rohan and I'm attacking Isenguard.
When I attack the actual city my game crashes.
All other battles are running fine.
I got the feeling it has something to do with the unique settlements.
(In custom my game also crashed when I would attack Minas Tirith)
I am using TATW 3.2.

Thanks in advance!

[TomSrx]

On what platform are you playing? As far as I know if you are not playing on a PC, half of the custom settlements will not work due to incompatibility issues in the files.

[tprb]

On what platform are you playing? As far as I know if you are not playing on a PC, half of the custom settlements will not work due to incompatibility issues in the files.

I'm playing on OS X El Captain.
I run the game with wineskin.
It works perfectly fine except when I attack Isengard (or I want to play with an unique settlement in custom).

[TomSrx]

I'm playing on OS X El Captain.
I run the game with wineskin.
It works perfectly fine except when I attack Isengard (or I want to play with an unique settlement in custom).

Hmm, half of the custom settlements do not work when playing on a mac, it just crashes. However you are using wineskin so I don't really know then what is the trouble. Is there a crash log? It could give you a clue about what is wrong.

[tprb]

Hmm, half of the custom settlements do not work when playing on a mac, it just crashes. However you are using wineskin so I don't really know then what is the trouble. Is there a crash log? It could give you a clue about what is wrong.

I don't really know anything about what might be wrong that's why I am here.
I looked through the crash report and this is what might cause the problem?

Thread 12 Crashed:: WinMain
0 libgranny2_intel.dylib 0x03e0b00f MarkAddressAsTouched(rebasing_context&, void*, int) + 57

Thread 12 crashed with X86 Thread State (32-bit):
eax: 0x00000004 ebx: 0x628a0900 ecx: 0x00000004 edx: 0x8421c620
edi: 0x00000010 esi: 0x102c35b0 ebp: 0x102c35c0 esp: 0xb112e690
ss: 0x00000023 efl: 0x00010282 eip: 0x03e0b00f cs: 0x0000001b
ds: 0x00000023 es: 0x00000023 fs: 0x00000023 gs: 0x0000000f
cr2: 0xf4ef0004

This is the report I got when I attacked Isenguard.

[tprb]

I just checked and attacked hornburg (another unique settlement) and my game crasht!

So it has something to do with unique settlements...

[Joseignacio]

It happens many times that the game crashes when you are using some units (Ents, Balrogs, spiders and others ...) if you solve it in a battle instead of autoresolve.

This happens mainly in new hardware/software.

You could try to autoresolve, just to check if this is the bug (Save earlier so no matter if you are defeated), in this case there is a lot of information on the bug but unfortunately no solution by now except not including these units in the battle.

http://www.twcenter.net/forums/showt...wolves-crashes

[tprb]

It happens many times that the game crashes when you are using some units (Ents, Balrogs, spiders and others ...) if you solve it in a battle instead of autoresolve.

This happens mainly in new hardware/software.

You could try to autoresolve, just to check if this is the bug (Save earlier so no matter if you are defeated), in this case there is a lot of information on the bug but unfortunately no solution by now except not including these units in the battle.

http://www.twcenter.net/forums/showt...wolves-crashes

I'm not attacking with Ents, Balrog or anything special.

I tried to autoresolve and my game does not crash then, but I lose while I outnumber them 1100 to 900 .

[♔atthias♔]

I'm not attacking with Ents, Balrog or anything special.

I tried to autoresolve and my game does not crash then, but I lose while I outnumber them 1100 to 900 .

use the ~ key then type auto_win attacker and hit the auto resolve button
it is a cheaty way to bypass your problem