.99 crash reports

Simply put- I'm crashing too much for the game to be ready.  I'd say I average around 1 crash per hour of play- the crashes seem fixable, might all be the same crash, I"m not entirely sure, but it has to be crash-free for the game to be ready.

 

I'm enjoying the changes otherwise, it's the stability that's an issue.  Fix that and the game is ready.  I'm not sure what constitutes acceptable, but I'd say in 2.5 hrs of otherwise enjoyable gameplay I had 2 crashes, that's a bit much.

 

 

11,422 views 22 replies
Reply #1 Top

The game is rock stable for me on both XP and Win7.

From reading the boards, it seems to me that people who have crashes are the people who reload games or regenerate worlds.  Which to me screams MEMORY LEAK!

Reply #2 Top

If we are putting a number on acceptable crashes per gameplay hour, I think 0 is a good, acceptable number. Good games shouldn't crash, and certainly not frequently or consistently. I just finished over 40 hours of X-com and crashed only once, and it still made me mad.

That said, I'm not crashing when I play FE. But I fully support anyone who does that should demand a crash-free game.

Reply #3 Top

They are aware of the memory leak problem and I think they are fixing it, probably not before release though.

Reply #4 Top

Yea, memory leaks are the only real issue I have.  The game is very ready for release.  I own hundreds of PC games, literally hundreds.  This game as it is right now would be among the best in terms of stability at release.  

Reply #5 Top

Quoting Tuidjy, reply 1
The game is rock stable for me on both XP and Win7.

For reading the boards, it seems to me that people who have crashes are the people to reload games or regenerate worlds.  Which to me screams MEMORY LEAK!

 

ALL my crashes are on reloads.  In about 60-100 hours (sooo much) of playing since I got the beta a couple of weeks ago, it's never crashed once in the middle of play.  While I think any crashes are bad, if they only occur when reloading - well that's the best kind, I think.  Nothing lost.

Reply #6 Top

Yep, no crashing here either.

Reply #7 Top

No crushing here, but mess nevertheless after re-loads.

Reply #8 Top


Remember MoM?? Of course you do... XD

It crashed...especially with that Whirlwind spell...really touch and go.

I guess what I getting at is: these crashes impact the game less that trying to cast or do something in the game. Most, if not all, are mitigatable.

Ultimately, it would be nice if Stardock was able to flush out these last few...but if they do, it will be at the cost of balancing concerns...cause it's being released on Oct 23. The frog has spoken.

 

Reply #9 Top

As a proud Skyrim player, I can handle the odd crash here and there (still, some are more touchy on the matter, and let's remember FE has something to prove here after WoM).

I'd be more concerned about save consistency, myself.   

Reply #10 Top

We had some installer issues with 0.99 unfortunately.  We're going to be releasing an update tonight with an improved installer. But not everyone's data files got updated the same.

Also, for those of you who modify your data in some way, be aware that this can, at this stage of big patches (which won't exist post 1.0 because you won't see 900+ megabyte "patches) it's best to reinstall from scratch if you're modding.

Reply #11 Top

I looked at the .991 changelog.  It's possible that could fix my problem- as they appeared to be lockup-style crashes.  The patch problems I had were on the newer laptop and not the older one.

 

Will try again over the next few days.   I play on two different laptops (one high end, one now mid end) and one uses NVIDIA, one AMD, so I get a variety of looks.  

 

I did notice the game chugged a bit more than previous builds, but I attribute that to the monster phase movement, which is a compromise I can easily accept.

Reply #12 Top

Hopefully the updated installer will fix it.  So when you say crash, you're saying you got a lockup or it actually crashed?

The updated installer should fix the data crash (won't affect Steam users as Steam's installer doesn't have the issue).  But updated EXE should address the lockup reports we got.

Reply #13 Top

It was a lockup- which seems to be fixed in .991.

 

Only technical issue I'm having now is some sluggishness which I am not sure if it's due to the monster phase issue or a memory leak, or both.

I'm guessing memory leak as it seems to get worse over time, whereas I assume fewer monsters are in a world as the game goes on.

 

 

Reply #14 Top

Crashing with the .991 update.  The opening menu loads, I click New, loading proceeds for roughly 15 seconds, and then CTD.  I'm uninstalling and downloading the full beta now. 

Reply #15 Top

Any crash talk needs to be backed up with series of zip files. I don't see any here. Did you e-mail them in?

Reply #16 Top

The programdata subdirectory indicated in the Reporting thread is for Win7.  If anyone can tell me where to look for the appropriate archive on WinXP, I'll be more than happy to upload it.  I asked about this once before, and suggested amending the thread accordingly.  No response was received.  I am reminded of Kraxis' canny observation when the Kingdom forces left him stranded: "What am I, chopped liver?"

Reply #17 Top

You could try searching for a the folder called screens. It should give you the FE game directory for one and the FE program data directory for the other.

Reply #18 Top

Quoting seanw3, reply 18
You could try searching for a the folder called screens. It should give you the FE game directory for one and the FE program data directory for the other.

 

I'm afraid I uninstalled about 90 minutes ago, after finding no link to the archive for WinXP players, and no archive after doing a brief directory search.  I figured that as nobody had put up that information since the request was made four months ago, chances were it wouldn't show up anytime soon, and just getting the basic info out was important.

 

If CTDs happen again after a full reinstall, I'll be more than willing to upload the files.  Assuming someone can tell me where they are.

 

Reply #19 Top

Quoting seanw3, reply 16
Any crash talk needs to be backed up with series of zip files. I don't see any here. Did you e-mail them in?

 

You don't need to anymore, Stardock gets it automatically.

 

Reply #20 Top

Quoting Alstein, reply 20

Quoting seanw3, reply 16Any crash talk needs to be backed up with series of zip files. I don't see any here. Did you e-mail them in?

You don't need to anymore, Stardock gets it automatically.

 

I hope that's the case, because after the lengthy download and reinstallation, the same CTD occurs repeatedly from the main menu.

Reply #21 Top

I really hope people are not doing that. Just because they get a crash zip automatically doesn't mean they have the context of the crash to be able to solve the issue. Many crashes may even be ruled out by their smart exception program. If you are repeating a crash, you need to make a ticket and get it solved. That is the whole point of beta testing. 

Reply #22 Top

Problem was solved, in any case--with thanks to Derek for his timely response.  It appears I had to regenerate the My Games/Fallen Enchantress directory completely.  Simply removing existing mod content and leaving "Use Mods" unchecked under Options wasn't sufficient.