Game freezes frequently campaign when loading battle


#1

Hello All,

It seems to be totally at random, but the game will freeze at the “press any key to start battle” screen after deployment during campaign mode. I can usually kill the GSB.exe task and start from the previous turn and continue for a random number of turns and then it will crash again. It only crashes on battles, they can be various sizes and configurations, and I have had it happen on 2 completely different PCs.

PC I play on the most -
Windows 7
16gb ram
GTX 560 ti
I7 920
EVGA X58 LE mobo
running via Steam

Secondary
Windows 7
2GB
GTX 260
Core 2 duo 2.13ghz
Asus 680i mobo


#2

After reading your report, I am sorry to say that i only have more questions than answers:

  • are you using any mods / DLCs during the campaign.
  • does the debug directory hold any clues
  • is the internet connection stable ?
  • have you tried getting steam to “reverify” the content

#3

I have the nomad, order,swarm and tribe dlc as well as the campagin. I had all the DLC before starting the campaign mode.

I just attempted to validate and steam did say there were two failed files. I think it redownloaded them. reverified data and it was successful. My internet connection is pretty stable.
I checked the debug folder and I had two possibly relevant files, but there were dated on the 21st and not the 24th. I’m going to test the game now to see how it works, I will keep this post updated.

Thank you for your questions,

drawdebug.txt

Initialising 3D Engine
Driver : nvd3dum.dll
Description : NVIDIA GeForce 8800 GTS
DeviceName : \.\DISPLAY1
About to Create 3D Device with width: 1920 and height : 1200
Checking For Shader Support
NumSimultaneousRTs:4
hal_caps.PixelShaderVersion >= D3DPS_VERSION(2, 0)
Finished initialising 3D Engine
Initialising Render target of 512 X 512 rt_ship
rt_ship
Initialising Render target of 2048 X 2048 rt_offscreen1
rt_offscreen1
Initialising Render target of 2048 X 2048 rt_offscreen2
rt_offscreen2
Initialising Render target of 2048 X 2048 rt_transition
rt_transition
titlescreen2048.bmp
cwfont20.dds
zekton16.dds
box_background.jpg
textbutton.dds
textbutton_h.dds
dialog_titlebar.dds
button_close.dds
button_close_h.dds
border_depth.dds
debris.dds
contrails.dds
escapepod.dds
escapepodengines.dds
shield_impact.dds
client_interlace.dds
dialog_client.dds
19px_highlight.dds
19px_highlight_black.dds
smokeclouds.dds
runninglight.dds
shield_collapse.dds
Releasing texture: border_depth.dds
Releasing texture: rt_ship
Releasing texture: rt_offscreen1
Releasing texture: rt_offscreen2
Releasing texture: rt_transition
Releasing texture: titlescreen2048.bmp
Releasing texture: cwfont20.dds
Releasing texture: zekton16.dds
Releasing texture: box_background.jpg
Releasing texture: textbutton.dds
Releasing texture: textbutton_h.dds
Releasing texture: dialog_titlebar.dds
Releasing texture: button_close.dds
Releasing texture: button_close_h.dds
Releasing texture: debris.dds
Releasing texture: contrails.dds
Releasing texture: escapepod.dds
Releasing texture: escapepodengines.dds
Releasing texture: shield_impact.dds
Releasing texture: client_interlace.dds
Releasing texture: dialog_client.dds
Releasing texture: 19px_highlight.dds
Releasing texture: 19px_highlight_black.dds
Releasing texture: smokeclouds.dds
Releasing texture: runninglight.dds
Releasing texture: shield_collapse.dds

debug.txt

----DEBUG FILE----
Windows Vista detected
GSB Debug File. App version Full 1.32
Desktop resolution is 1920 x 1200
Initialising Direct3D
Initialising global vertex buffer
creating render targets
success in initialising 3D
Initialising Direct Input
Finished Initialising Direct Input
Initialising Sound Engine
Initialised Sound System with 512 channels

Finished Initialising Sound Engine
releasing D3D engine
D3D released
END DEBUG—


#4

Its still crashing after fixing the files.


#5

Sorry, i still have no idea at to what the problem is.
More questions:

  • when you start the game, what version number appears in the top left corner ?

#6

Version Full 1.59 it was in the top right for me.

It doesn’t seem to be related to the size of battle either. Other games run fine. I can play Battlefield 3 for hours without crashing…

Are there any video card options that may affect the game? FXAA? Other fancy options?


#7

Has anyone had the game freeze just before a battle?


#8

Not in my case . . At the moment i am drawing a blank on what the solution is.
Apart from ensuring you have the most up to date drivers, you could try turning all the additional graphical features off and see if that helps . .


#9

Hello all again,

Soo this is happening to me on 3 different computers… the two previous and a core i3 sony vaio with Intel HD 3000 graphics… not sure whats going on here, but it seems like more people should be experiencing this issue… This is also on 3 different ISPs , and routers…

I’m going to try playing without the internet going to see what happens…

Maybe someone can do some testing? I am playing as the swarm is the only thing consistent factor between the 3 computers… (I like the swarm a lot so I’ve been 100% as them).


#10

Ookay, so why does the campaign mode require an internet connection?

If the internet connection is a major factor for the problem and I can’t play it without the internet, I guess I’m up a creek then :confused:

Maybe its the swarm, I’ll a campaign with a different race…


#11

Used Rebels, and after about an hour or so of playing it did the same crash.


#12

Because that is how GSB’s campaign mode obtains the opposing-force fleet setups from Positech’s server. Galactic Conquest routinely draws its OPFOR setups from fleets which other human campaign players have created for themselves in the past. These get turned around and randomly served out to other players’ campaign client installs as enemy fleets, ad infinitum.

That might be the case. As per above, Galactic Conquest is not meant to be played without an active internet connection. I am unaware what number (if any) “default” fleet setups actually ship with the campaign add-on.

For example, once upon a time Steam did a terribly bad job by failing to advise potential buyers that you needed persistent internet for Galactic Conquest. I have no idea if they still fail to mention that on their website. That requirement was (and still is) mentioned on the GSB campaign’s own webpage, as seen here, directly above the purchase links:

" You will also NEED an internet connection as you play the campaign, because of the games tight integration with the online server that selects enemies for you to fight. "

However, if you determine that the presence or lack of a persistent internet connection is not the cause of your GSB campaign trouble, and you continue to experience no success in troubleshooting this issue, I suggest that you send a forum private message to cliffski (the game’s developer) and explain the problem to him.


#13

Thank you for the reply. I had no idea that’s how campaign worked. That’s cool. I was thinking since it does not seem persistent for a lot of people, would it be my account/product key failing? Would the game mention any conflict?

Maybe I should try a non-Steam install? Because I have tried different networks with the same problem, all through Steam.


#14

You could always reinstall everything and see how that goes. I concede it’s an extreme suggestion, and a bit of a time-sink, but lesser measures don’t seem to have benefited you so far.

I caution you that I’m emphatically not a Steam gamer, so I can’t aid you much in putting that particular Humpty Dumpty back together again. But there are various searchable posts on the GSB subforums which can point you in the right direction. You may wish to discover these before you embark on such a venture.

Non-Steam? That sounds like a major common denominator which hasn’t been isolated yet in your testing. Consider giving it a try once you can commit a nice uninterrupted block of time to it.

It’s been rather a long while since I’ve installed the campaign for any reason, so at this juncture I’ll simply wish you good luck and remind you that if your next round(s) of troubleshooting happen to fail, you can always send a PM to cliffski about your problem.


#15

I’m getting the same freezes during campaign play when I’m prompted to press any key to continue and sometimes after battles as well. In both cases all I can do is CTRL ALT DEL and end the game through the Task Manager because it will stay locked up indefinitely. I just verified my Steam files and there were no problems there, my GSB version is 1.59. Typically I can play 45 minutes to an hour before the game locks up, sometimes less. I’m not using any DLC because at this point I’m pretty frustrated with the constant lock ups.

My system:

CPU - AMD Phenom II X6 1090T 3.2GHz
Motherboard - Gigabyte GA-890GPA-UD3H
RAM - G.SKILL Ripjaws Series 16GB (4 x 4GB) DDR3 1600 (PC3 12800)
GPU - NVIDIA GeForce GTX 470
1.5TB of hard drive space - 1TB drive and 500gb drive
OS - Windows 7 Professional 64 bit

My debug files:

----DEBUG FILE----
Windows Vista detected
GSB Debug File. App version Full 1.32
Desktop resolution is 1920 x 1200
Initialising Direct3D
Initialising global vertex buffer
creating render targets
success in initialising 3D
Initialising Direct Input
Finished Initialising Direct Input
Initialising Sound Engine
Initialised Sound System with 512 channels

Finished Initialising Sound Engine
releasing D3D engine
D3D released
END DEBUG—

Initialising 3D Engine
Driver : nvd3dum.dll
Description : NVIDIA GeForce 8800 GTS
DeviceName : \.\DISPLAY1
About to Create 3D Device with width: 1920 and height : 1200
Checking For Shader Support
NumSimultaneousRTs:4
hal_caps.PixelShaderVersion >= D3DPS_VERSION(2, 0)
Finished initialising 3D Engine
Initialising Render target of 512 X 512 rt_ship
rt_ship
Initialising Render target of 2048 X 2048 rt_offscreen1
rt_offscreen1
Initialising Render target of 2048 X 2048 rt_offscreen2
rt_offscreen2
Initialising Render target of 2048 X 2048 rt_transition
rt_transition
titlescreen2048.bmp
cwfont20.dds
zekton16.dds
box_background.jpg
textbutton.dds
textbutton_h.dds
dialog_titlebar.dds
button_close.dds
button_close_h.dds
border_depth.dds
debris.dds
contrails.dds
escapepod.dds
escapepodengines.dds
shield_impact.dds
client_interlace.dds
dialog_client.dds
19px_highlight.dds
19px_highlight_black.dds
smokeclouds.dds
runninglight.dds
shield_collapse.dds
Releasing texture: border_depth.dds
Releasing texture: rt_ship
Releasing texture: rt_offscreen1
Releasing texture: rt_offscreen2
Releasing texture: rt_transition
Releasing texture: titlescreen2048.bmp
Releasing texture: cwfont20.dds
Releasing texture: zekton16.dds
Releasing texture: box_background.jpg
Releasing texture: textbutton.dds
Releasing texture: textbutton_h.dds
Releasing texture: dialog_titlebar.dds
Releasing texture: button_close.dds
Releasing texture: button_close_h.dds
Releasing texture: debris.dds
Releasing texture: contrails.dds
Releasing texture: escapepod.dds
Releasing texture: escapepodengines.dds
Releasing texture: shield_impact.dds
Releasing texture: client_interlace.dds
Releasing texture: dialog_client.dds
Releasing texture: 19px_highlight.dds
Releasing texture: 19px_highlight_black.dds
Releasing texture: smokeclouds.dds
Releasing texture: runninglight.dds
Releasing texture: shield_collapse.dds