FOW bug is #1 on our priority list...it's been a tough nut to crack, so any saved games you guys can send over would be great!

Several of those other bugs actually have fixes, but we've decided they're too risky to put in for 1.0    that's the most frustrating part of getting close to the release version...only showstoppers get past the 'could cause more bugs than it solves' filter.

I'd like to see the mouse cursor thing addressed as I've repeatedly fixed it and then something makes it go back to showing the wait cursor at inopportune times.

As for edge case bugs causing negative reviews, in 20 years I've never seen that happen.  Even the FOW thing, which is being fixed, isn't that big of a deal.  

Professional reviewers are professionals, not Star Trek convention attendees.

I agree with Frog that "edge cases" shouldn't affect game reviews (and in my case, they won't), but the FOW bug isn't that much of an edge case. I've seen it over a half-dozen times and for someone like me, the bug is a current-play-through killer. The exploration phase is so important -and so fun - that the elimination of it 1, 2, 3 and sometimes 4 or 5 hours in to a game makes me very tempted to give up that play through. 

It has occurred in half my games and I have sent those saves in (and will send the latest one in, too). For a game that gets SO MUCH right, leaving some of these potential bugs in seems a disservice to the hard work of everyone and frankly, disappoints me.

Still love you guys, though. 

the problem when the game has so many bugs is that you don't know whether you are misinformed about how something works or whether it's just broken

the game is hard enough to learn even without all the flaws

At this point, we'll go with random kill animations playing early (an annoying blip to a reviewer) than risk breaking a core part of the animation system that could result in a lower score   

The FOW fix, on the other hand, would have to be VERY risky to not put in. Once we figure out whats going on there we'll let you guys know. 

Scott and Brad,

I've reported this a number of times on this forum but because you guys seem to be reading this, I thought I'd ask here.

I have had repeatable CTDs (and an occasional shut-my-machine down event) that just makes the game unplayable for me (reported to tech support [#EUX-824-48658]).

My question is - I have a fairly new video card.  Does anyone there have an Nvidia GTX-970?  It's a popular card but I'm thinking to myself "maybe they just don't have one there to test ???".  It seems to be a bad graphics call (I get a "DX error" when it CTDs - and it happens when combat/spell effects are happening - or when a tool tip try to pop up).  There is nothing special about my system and I play a ton of games (with no problems like this).

Just curious (and concerned).

Mozo

Not 100% sure but i think in my last game it happened when i saved/reloaded to get a different hero (recruit hero sovereign skill)

Here some saves and debug.err from a game where i got the fow bug on turn 12 already. Includes a save from the start.

Edit: nm, i am glad you found and fixed that bug !