(0.80) BUG - Tactical Combat unable to move or attack

from Elemental Forums

During tactical combat I'm unable to move my units or attack enemy units.  But spells and abilities work and I can pass my units turn and then things return to normal.  I can't see any real pattern to this, it  just happens at random.

DirectX Version: DirectX 11
Machine Name: DESKTOP
Operating System: Windows 7 Professional 64-bit (6.1, Build 7601) Service Pack 1 (7601.win7sp1_gdr.120830-0333)
Languages: English (Regional Setting: English)
System Manufacturer: Gigabyte Technology Co., Ltd.
System Model: X48-DQ6
BIOS: Award Modular BIOS v6.00PG
Processor: Intel(R) Core(TM)2 Duo CPU     E8400  @ 3.00GHz (2 CPUs), ~3.0GHz
Physical Memory: 4096MB RAM
Page File: 2739MB used, 5447MB available
Windows Dir: C:\Windows

 

 
 

PS

Love the changes and have enjoyed watching the game progress.  Keep up the good work.

8,083 views 5 replies
Reply #1 from Elemental Forums Top

I've had that happen but not recently.  I think it happened in a wildland

Reply #2 from Stardock Forums Top

One time, I looked at an enemy unit's detail sheet on it's turn, which seemed to "lock up" the game (I couldn't do anything, not even pass), but turning auto-play on for a moment cleared that up and it hasn't happened again since, so I didn't bother reporting it.

Offworld Trading Company
Reply #4 from Elemental Forums Top

hmmm, yea more info would be useful... checking enemy info seems like it could be a culprit, lemme know if you find out more (I'll try it too)

Reply #5 from Stardock Forums Top

I've never had it happen again, but then, I haven't *tried* to make it happen again. Will try some now = P

Edit: Got it to freeze mid-animation, but didn't actually lock up. May need to try it with a new game, where I'm not facerolling the NPCs so hard yet = P

Got a lock up.

As with my first time at this bug, activating auto-play briefly got things moving again (though it cost me the battle as I'd been planning a Sweep, which auto-play didn't do >.<). Unfortunately, my last autosave is NOWHERE near this point in time. Would this have dumped to the error log? I'll copy it out to desktop just in case...