How to continue the Fellowship campaign when the Ents cause a CTD while attacking Isengard

[Marquis de Faux]

Greetings,

I have a crash to desktop in every battle involving ents. I'm playing the Fellowship campaign but I cannot attack Isengard because it always crashes. I'm on Windows 10, Steam version.

Thanks.

[Veteraan]

Greetings,

I have a crash to desktop in every battle involving ents. I'm playing the Fellowship campaign but I cannot attack Isengard because it always crashes. I'm on Windows 10, Steam version.

Thanks.

I'm afraid this cannot be fixed at the moment, although some effort has been put in solving this annoying problem.

For more info go HERE.

[Marquis de Faux]

I'm afraid this cannot be fixed at the moment, although some effort has been put in solving this annoying problem.

For more info go HERE.

Alright, thanks. Is there anyway I can skip past this in the Fellowship campaign? There is no autoresolve.

[Marquis de Faux]

I'm in the Fellowship campaign and I can't attack Isengard with the ents because it keeps crashing. Is there any way I can skip this, or autoresolve it somehow (even though there is no autoresolve button)?

[Ngugi]

Use the cheat code for auto-win (goodle for cheat codes)

[Marquis de Faux]

I can't autowin because that needs autoresolve, the Fellowship campaign has no autoresolve.

[Ngugi]

Ah darn, then I'm afraid I don't know any solution I'm afraid

[Withwnar]

You can try this...

http://www.twcenter.net/forums/showt...5#post10869085

Change the red line to be:

restrict_autoresolve false

I assume it works in the Fellowship Campaign. At the start of every turn autoresolve is turned off again.

The simpler solution is to comment out this red line (as shown: with a ";" in front) in {Third_Age}\data\world\maps\campaign\custom\Fellowship_Campaign\custom_script.txt ...

;##################### Restrict autoresolve ##################
monitor_event PreFactionTurnStart FactionIsLocal
;restrict_autoresolve true
end_monitor

monitor_event FactionTurnEnd FactionIsLocal
restrict_autoresolve false
end_monitor

... but you'll need to restart the campaign.