Beta 5 .80+.81 Combat viewer fails to appear, have to cancel using task manager

First time I've ever seen this.  I sent one of my ships to attack a Thalan ship.  I got the confirm battle window, and clicked to see the battle.  But the combat viewer didn't appear - I was left looking at the main map while listening to sounds of combat from the battle I should have been watching.  I could move the cursor and click on things, but without result except for an occasional sound effect (like the sounds that say "you can't do that").  The keyboard was unresponsive, I could not advance anything using the tab key and the escape key didn't bring up the main menu.

I finally had to bring up task manager and kill the game.

The debug.err file is filled with these messages:

Debug Message:  ERROR: (CD3D11Renderer) Failed to create a vertex buffer ((887a0005) The GPU device instance has been suspended. Use GetDeviceRemovedReason to determine the appropriate action.

I've opened ticket #NSZ-259-61315 for this problem.

9,786 views 16 replies
Reply #1 Top

I was just about to make this post for the same issue.

 

About 30%-40% of the time when going to battle viewer game goes black, i hear the sounds and see the cursor but the rest is just black. I have to ctl alt delete and close the game.

 

Also i have had this issue also happen when you get an idealogy event(3 option choice screen). It is super rare but also has happened.

 

Im glad someone else has this issue because i thought it was just unlucky me. I have updated my drivers ran a bunch of different graphics settings but still get it.

 

I have over 65 hours of beta 4 logged with no issues but from day one beta 5 has had this same issue which renders the game unplayable.

 

 

 

Reply #2 Top

It just happened to me again, but a little different.  This time, I had just fought a battle against a couple of ships defending a planet, and the battle viewer worked ok.  But then, when I moved a transport to invade, selected an invasion type and clicked to go ahead, instead of seeing the invasion screen the game showed me the beginning of the last battle viewer and then locked up.  The debug.err file shows the same type of error messages - I have it saved in case the developers want to see it.

Reply #3 Top

By the way, this isn't repeatable by loading a saved game and retrying.  It seems to only happen after I've been playing a while.

Reply #4 Top

In that case you guys are lucky, for me, whenever I try to fight a battle with the combat viewer, the game just pseudo-freezes. I can still move the screen or open planet-views etc, but I can't play any further since the game just says "waiting" for all eternity. Then I have to close the game, since if I try to load, the game also freezes. Unfortunetly Beta 5 broke quite a few things for me, I hope they can get a patch out quickly.

Edit 1: Oh yeah, and even auto-combat has a high chance to "freeze" the game, so basically I can't play the game right now, slightly anoying.

Reply #5 Top

Hey Publius of NV,

Thanks for reporting this issue and creating a ticket with all of the required information! 

For anyone else experiencing this issue, we'd like to grab some data from your system that will help with finding a root cause.

Please take a look at the section below and provide the requested data in your ticket:

https://esupport.stardock.com/index.php?/default_import/Knowledgebase/Article/View/496/161/general-galactic-civilizations-iii-troubleshooting#support

 

Thanks!

Reply #6 Top

I think this issue was supposed to have been fixed in .81, but I just got a similar hang.  The debug.err messages that appeared in the .80 instances of the hang do not appear in the .81 hang, so it could well be a new problem.  I've opened ticket #SVL-510-40517 for this new occurrence.

Reply #7 Top

It just happened to me again, attacking a planet, the battle view does not appear, I'm left looking at the main galaxy screen with no way to interact except to use task manager to kill it.

Once again there's no dump file.  The debug.err has:

Debug Message:  CBattleSystem::AddBattle IncrementMovementHoldCount ticket 0 attackerID 18652 defenderID 5017 count 1
Debug Message:  Battle: Consuming random value 333284699 and seeding the m_battleStream
Debug Message:  Player 0 faction power changed from 386366460 to 405390210 on tick 426381
Debug Message:  totalProduction 1553762 totalBattleRating 403023650 treasury 17399808 influence 625000 numUnlockedTechs 111 numUnlockedCultureTraits 17
Debug Message:  Popup Manager Update: Unhiding BattleInitiationWnd
Debug Message:  Battle Initiated. Attacking fleet 18652
Debug Message:  CBattleSystem::Update attacked 18652 defender 5017, Cancel DecrementMovementHoldCount count 0
Debug Message:  Battle [Seed 333284699] [Attacking Fleet 18652] [Defending Fleet 5017] tick 426498
DebugMessage:  WM_CLOSE message received.
Debug Message:  MWin Strip Engine: Max used verts was 1000 verts
Debug Message:  MWin Strip Engine: Max used verts was 1000 verts
Debug Message:  CModifier::OnDestroyed modifierObjectID 7609
Debug Message:  CModifier::OnDestroyed modifierObjectID 8064
Debug Message:  CModifier::OnDestroyed modifierObjectID 8231
Debug Message:  CModifier::OnDestroyed modifierObjectID 8768
Debug Message:  CModifier::OnDestroyed modifierObjectID 10901
Debug Message:  CModifier::OnDestroyed modifierObjectID 12378
Debug Message:  CModifier::OnDestroyed modifierObjectID 14107
Debug Message:  Fleet Destroyed. [ID 5556]
Debug Message:  Fleet Destroyed. [ID 5558]
Debug Message:  CModifier::OnDestroyed modifierObjectID 13303
Debug Message:  CModifier::OnDestroyed modifierObjectID 17153
Debug Message:  Fleet Destroyed. [ID 5563]
Debug Message:  Fleet Destroyed. [ID 5565]

Followed by hundreds of lines of "Fleet Destroyed", "Improvement Destroyed", "Planet Destroyed" etc.

Reply #8 Top

Couldn't tell with the .81 or even the patch 2 notes if this has been addressed.

 

I noticed in .81 this happened less for me but still happens. Just seeing if this is on the radar or has been resolved yet. Since it pretty much makes the game not playable for anyone who is experiencing it, though it seems like only a few are.

 

I have not done a ticket yet but i probably should if this has not been reliably reproduced.

Reply #9 Top

Have the same thing repeatable in a load my fleet with an escort carrier and a Survey ship attack the pirates and it sits there forever whether I select auto resolve or start.

Reply #10 Top

I thought this was fixed as I played over 100 turns on a new game without incident.   But as the game got to around 250 turns (gigantic) I started getting this frequently.  It doesn't seem to depend on the size of the battle involved at all, whether it's one vs one or a big fight.   I have sent further stuff on my ticket.

I have not had any problem, however, if I auto resolve any battle, but that's not so much fun.

I should add that I can reproduce the problem if I do so immediately from a previous save; however, if I reboot first, I don't reproduce the issue.

 

 

Reply #11 Top

This has also happened to me with the new .82 update, having started a new game. Exact same issue reported by Publius, combat viewer failed but could still hear audio, I also had to kill game. Means the bug is still there

Reply #12 Top

Please submit a ticket so we can look further into this. Thanks. :)

Reply #13 Top

Quoting Island, reply 12

Please submit a ticket so we can look further into this. Thanks. :)
End of Island's quote

I submitted a ticket. The number is given back in reply #6 in this thread.

Reply #14 Top

Must say this has happened to me to with an alarming regularity.

 

A lot less on smaller (Med) maps and less still if I do a computer restart every 15 turns after the 100th or so.

I'll try and do a bug submit report if it happens again.

 

Oh and for the record I have a rock steady rig with 16G of RAM and a GTX 760 gfx card so that should not be the problem.

Reply #15 Top

Until this game breaking bug gets fixed you cannot release the game because you'll totally tank any kind of review score you would get for it. I cannot play because every single game ends because I get the locked up combat viewer error. 

Reply #16 Top

Anyone else who is experiencing this please start a support ticket as well. :)