Jump to content


Crashing Bug


  • Please log in to reply
9 replies to this topic
Pig Catapult Pig Catapult

Watcher

  • Member
    • Member ID: 3,058
  • 190 posts

Posted 08 December 2013 - 10:32 PM #1 Crashing Bug

Specifically, some scenario-start-scene-setting picture montages cause the window to go white and the program to stop responding while eating up to 50% of my CPU. I know this happens with Backwater Calls and Dilecia, but the ones for the four default scenarios work just fine.

Is this at all fixable?

I've been having other bugs, too, like the game sometimes crashing without going white during cutscenes where the characters talk by floating over their heads if another program is playing audio, occasional severe lag in large battles while the computer is doing the enemies' turns (It stops, my cursor does the "waiting" animation for several seconds, then the game resumes at the start of my turn, the enemies' turns all handled), and, a couple times, parts of the UI just not responding at all.

I'm running Windows 7.
Darkness grew in a forgotten wood
Creeping as the darkness should
Then it crept up through the trees
Over fields and over seas
But shade is not a wretched thing
Sit and hear the shadows sing

Ishad Nha Ishad Nha

Hand of Avadon

  • Member
    • Member ID: 4,773
  • 2,366 posts

Posted 09 December 2013 - 02:44 AM #2 Crashing Bug

Bugs that bad should be a problem with your computer not the BoA game itself.
BoA is Windows XP or whatever. You might able to use a Compatibility Mode in Windows 7, this will enable you to run programs from earlier versions of Windows.

Pig Catapult Pig Catapult

Watcher

  • Member
    • Member ID: 3,058
  • 190 posts

Posted 13 December 2013 - 04:57 PM #3 Crashing Bug

When I try to run it in compatibility mode, the program won't even start properly.
Darkness grew in a forgotten wood
Creeping as the darkness should
Then it crept up through the trees
Over fields and over seas
But shade is not a wretched thing
Sit and hear the shadows sing

Ishad Nha Ishad Nha

Hand of Avadon

  • Member
    • Member ID: 4,773
  • 2,366 posts

Posted 17 December 2013 - 08:37 PM #4 Crashing Bug

I don't have Windows 7 myself, we will need to find someone who does.

Smoo Smoo

Shaman

  • Member
    • Member ID: 3,503
  • 294 posts

Posted 20 December 2013 - 11:51 PM #5 Crashing Bug

I'm running Windows 7 (64-bit) and play BoA with Windows XP (Service Pack 2) compatability mode and it works fine.
My Scenarios. Rate them.
In fact, rate Quarhag Pass if you've played it.

Ishad Nha Ishad Nha

Hand of Avadon

  • Member
    • Member ID: 4,773
  • 2,366 posts

Posted 21 December 2013 - 04:12 PM #6 Crashing Bug

"Specifically, some scenario-start-scene-setting picture montages cause the window to go white and the program to stop responding while eating up to 50% of my CPU. I know this happens with Backwater Calls and Dilecia, but the ones for the four default scenarios work just fine."
A quick fix is to replace graphics that cause crashes with those that don't, find replacments from the official four scenarios. You can always look at the proper scenario graphics with a graphics program.

Enraged Slith Enraged Slith

Revenge of the Slith

  • Member
    • Member ID: 27
  • 2,634 posts

Posted 22 January 2014 - 02:01 PM #7 Crashing Bug

Blades isn't working for me anymore. :(

I don't think I've altered anything recently, so it must be something new with Windows 7 or my graphics card.

Ishad Nha Ishad Nha

Hand of Avadon

  • Member
    • Member ID: 4,773
  • 2,366 posts

Posted 22 January 2014 - 04:01 PM #8 Crashing Bug

Did you change your operating system before it stopped working?
You get regular updates on Windows, that may be a cause of it.

Enraged Slith Enraged Slith

Revenge of the Slith

  • Member
    • Member ID: 27
  • 2,634 posts

Posted 23 January 2014 - 12:07 PM #9 Crashing Bug

View PostIshad Nha, on 22 January 2014 - 04:01 PM, said:

Did you change your operating system before it stopped working?
You get regular updates on Windows, that may be a cause of it.
Okay, I figured it out. It was an Avast! update that added some features. Turning off "Deep Clean" or whatever it's called fixed the problem.

Mr.TiC Mr.TiC

Citizen

  • Member
    • Member ID: 11,952
  • 14 posts
  • LocationCroatia

Posted 25 January 2014 - 05:29 AM #10 Crashing Bug

True, avast was getting on my nerves as well although I wasn't sure what I did to kill my problem. :)




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users