Do not download the second Beta 1.1!!!

I am going back to version 1.0X.010. I liked the first Beta 1.1 (wish I could still run that) but the second one is loaded with very severe problems. First of all, I am averaging more than one crash-to-desktop per hour. Secondly, it is riddled with errors --- Social Production indicates it is being moved over to Military Production, but it is really being wasted (so worse than original). If you do ^N in campaign mission, it restarts you, but with random settings. At some point after you load a saved game, it will tell you that all your units are outside their range. At that point, any other game you load will have the same problem. Fortunately, ending the program and restarting fixes that problem.

At any rate, until Stardock gets there act together on this one, stick with the first beta if you haven't already upgraded!

45,105 views 41 replies
Reply #1 Top
woops Just updated to beta 2. About to start a game :/
Reply #2 Top
I concur. I am at a point where the game crashes every time at this particular turn and I do not know why. Looking at the debug file, there are a ton of errors. I would like for there to be some way to forward this info so Stardock could use it, but I don't want to post it here for all the world to see!
Reply #3 Top
Well i think your wrong on this one i updated to the 2nd beta yesterday and i have had the perfect game no more BSOD no more path to long error so i don't think i will go back
Reply #4 Top
im pretty lucky with it so far, a few bugs but nothing game breaking as of yet.
Reply #5 Top
if you have the HD space make a copy of your game folder before you get the beta. I got 3 versions of Oblivion on my comp now while I test several mods.
Reply #6 Top
sorry to hear that i havnt had a single problem with the new beta...less crashes than the previous one.
Reply #7 Top
Until Stardock gets their act together


It's a Beta FFS. At this rate they'll stop providing them.
Reply #8 Top

Yeah. You _do_ realize that a beta test is intended to _find_ bugs, glitches, problems, balance issues, etc - if you want a stable release, you don't use Beta test versions.
Reply #9 Top

I am going back to version 1.0X.010. I liked the first Beta 1.1 (wish I could still run that) but the second one is loaded with very severe problems. First of all, I am averaging more than one crash-to-desktop per hour. Secondly, it is riddled with errors --- Social Production indicates it is being moved over to Military Production, but it is really being wasted (so worse than original). If you do ^N in campaign mission, it restarts you, but with random settings. At some point after you load a saved game, it will tell you that all your units are outside their range. At that point, any other game you load will have the same problem. Fortunately, ending the program and restarting fixes that problem.

At any rate, until Stardock gets there act together on this one, stick with the first beta if you haven't already upgraded

#1 It's a beta. Please do not tell other people not to use a build. The point of a beta is to find bugs. Without public beta testing, instead of 1.1 coming out in a week or so it would come out in a month or two like you see with most games that don't have public betas of their updates. So yes, there are bugs.

#2 Social production is not wasted. Certainly not here. I've gone over it over and over. I coded that aspect of the new build myself. So if you have a reproduceable scenario, I'd like to know about it.

#3 If you are experiencing crashes, again, we would like to know about that. Your debug.err info would be very handy for that. What you were doing when it crashed.  The only way these things will get found is either A) Users help us find them or B) Stardock's QA finds them. If it's purely up to B, then 1.1 will take much longer to come out.

#4 I am not sure what you mean about random settings in campaign missions.

Reply #10 Top
It's a Beta FFS. At this rate they'll stop providing them.


Exactly! IT IS A BETA!! It will be buggy. The WHOLE purpose of it is to find your crash bugs, ships out of range bugs, Ctrl N bugs and every other bug that us peons can find before they release it as final. You are testing this patch, so instead of complaining about bugs in a Beta version, either report them to Stardock so they can be fixed, or do not download the beta. Its very, very simple.
Reply #11 Top
Jeezes, will the irrational bitching never cease?

Complaining about a *BETA* build being buggy? Are you insane?

Ass hat.
Reply #12 Top
This is an April fools joke thread right?

Surely the original poster KNOWS exactly what a BETA is.....
Reply #14 Top
I have found it to be more stable actually... Besides, you use the beta to help debug the build so that the released version comes quicker, and so you have some input on the released version. If you are worried about crashes, I think you should stay with the previous released patch.
Reply #16 Top
Unfortunately lots of kids out there don't understand what the term Alpha or Beta means in software releases. NeverWinter Nights releases beta builds all the time of their patches, but of course tons of kids download it anyways then bitch about how it doesn't work and how horrible Bioware is. Pure comedy really. Other forums are moderated and delete posts like this but oh well.

Now if the beta reformated your system then maybe he would have a point in warning people not to casually use it.
Reply #17 Top
"#2 Social production is not wasted. Certainly not here. I've gone over it over and over. I coded that aspect of the new build myself. So if you have a reproducible scenario, I'd like to know about it."

I haven't had it crash on me yet, but I have seen wasted social production. Wasted bad word maybe? Didn't actually help make a ship but I didn't really check to see if I was paying the BCs for it.

Exact situation -
No social projects left on planet.
Planet with shipyard producing some ship (Forgot what).
Military spending at 0%
Social spending at 100%
Research 0%

The social spending was moved over to military but appeared in parenthesis. It seems that unless there is some military spending left over social spending didn't actually make a shipyard produce. When I bumped military spending to 5% the problem righted itself. I do not know if this is a bug or on purpose or even if this is what he was talking about.
Reply #18 Top
I never had problems with 1.0X or 1.1b1. With 1.1b2, I have a game that, when I hit "Turn" goes off into never never land and never comes back. The Debug log doesn't look like it has anything meaningful in it. If the devs want., I'll be happy to forward my save game, but that's probably what's required to diagnose this further.

Reply #19 Top
Some of the complaints are starting to make this look like a WoW forum. Please provide constructive criticism.
Reply #20 Top
have a game that, when I hit "Turn" goes off into never never land and never comes back


I've been having this problem with first beta. i find it is a ship with movement points left and the game is waiting for you to move it first. it doesn't target it for ya though. i move some specific ship and then the game goes on.
Reply #21 Top


I've been having this problem with first beta. i find it is a ship with movement points left and the game is waiting for you to move it first. it doesn't target it for ya though. i move some specific ship and then the game goes on.


Not the same. My game is insensitive to input. There is nothing I can do.


Reply #22 Top
#3 If you are experiencing crashes, again, we would like to know about that. Your debug.err info would be very handy for that. What you were doing when it crashed. The only way these things will get found is either A) Users help us find them or B) Stardock's QA finds them. If it's purely up to B, then 1.1 will take much longer to come out.


I posted earlier that I was having problems with the 2nd beta as well. I have already read about posting the debug error file on the boards. I just don't want to post all of my info on forums for the world to see. I have saved 2 debug files for you to use the information to make the game better than it already is.

Why don't I want to post my info? Ok, ok. I'm playing as a beginner (completed 1 previous game, never played the first GalCiv), and I don't want to be made fun of. Ok, not really, but if there is alternative way to get the info to you, I'd love to help out.

Basically nothing on my computer has changed since the official release. Beta 1-A seems to work fine as well. The game freezes (not crashes) at the same turn in a game every single time. The "Turn" button disappears and there is nothing that I can do. There are a ton of errors in the debug file.

With that said, I love the game!
Reply #23 Top
I never had problems with 1.0X or 1.1b1. With 1.1b2, I have a game that, when I hit "Turn" goes off into never never land and never comes back. The Debug log doesn't look like it has anything meaningful in it. If the devs want., I'll be happy to forward my save game, but that's probably what's required to diagnose this further.


Same scenario here, and I extend the same offer to the devs.
Reply #24 Top
I think we have the range of replies here, from Frogboy's diplomatic and setting the facts straight to the outright flaming and crucifixion of the original poster

Those who do download and play the beta, please give reports and files to Stardock, it goes along the lines of what can I do to help make it better.

Reply #25 Top
but if there is alternative way to get the info to you, I'd love to help out.


There is an email somewhere for you to send the debug.err to. Maybe someone can post what it is and how to use it (if it's not stickied or something). I don't crash hardly ever, except when I mod the wrong thing to the wrong value