Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[Soulwynd]

While playing windowed, the new version locks up winXP (even need to reset the comp) at map generation, near the end when it scrolls through the map. The screen flashes as if changing resolution and even locks the keyboard.

I tried importing a map from the older version and the game locks (with error screen) up whenever I exit the game from adventure mode.

I haven't tested it more than that, since it was starting to annoy me.

That's pretty much it. Let me know what kind of information you need.

[FFLaguna]

quote:Originally posted by Soulwynd:
<STRONG>While playing windowed, the new version locks up winXP (even need to reset the comp) at map generation, near the end when it scrolls through the map. The screen flashes as if changing resolution and even locks the keyboard.</STRONG>

I do not have these problems, and I always play windowed. I have generated a new world with the new version, and have played adventurer many times. I have only had one CTD, and it was unrelated to these issues. You make it sound like eeeeverybody is having this problem, but I don't think that's the case.

[Soulwynd]

Not at all, I was just describing what was going on. From the begining I thought "I bet this is only me, so it will never get fixed."

And, I didn't try full screen yet... Don't feel like having it locking my system again. The older version works just fine for me.

[ December 12, 2006: Message edited by: Soulwynd ]

[Toady One]

So it has troubles as it is scrolling?  This is when it is creating inventory items for the historical figures, mostly.  It'll be hard to catch without a crashing save.  Were there any mods or did you use any old files when you updated?  The syntax has changed somewhat.

[Soulwynd]

It locks up my system when it gets around hist figs 6000+ or so. The only custom thing I'm using is my window resolution set at 1024x384 with sounds off and intro off. I managed to get version 0.22.120.23a to do the same lock up. The only similarity I can tell is that it rejected well over 40 maps, around 70 actually. I've never had DF 0.22.120.23a reject that many maps before, so maybe that's why I didn't have this lock up with it before. My guess is that it could be a memory leak of some kind or my computer is going nuts.

[ December 13, 2006: Message edited by: Soulwynd ]

[Soulwynd]

So, I downloaded it again and uncompressed to a new folder and tried again without even modifying the init file. It only had 2 rejected maps and locked up at hist figs 7300.

So I just reseted the comp and here I am =p

[Toady One]

What are the specs on your system?  Could it be a memory problem?  There's a tad more info on the items now, relating to temperature, and finalize hist figs is just creating a lot of items.  It's possible it's reaching some kind of cap from your system.

[Soulwynd]

AMD 1600+ with 1gb of ram, running winXP sp2. It shouldn't be a problem but I also noticed even the older version is doing the same bug, just not as consistent. I've had it lock up my system 3 times at map gen while the newest does it every single time for me.

I use plenty of memory & cpu intensive programs here, renderers, games, cads, etc and I've never had anything crash on me like that before. I have another machine here with a similar build, I will try using the newest version there tomorrow.

[Toady One]

If that's not the problem, have you updated your graphics drivers?  These bugs that cause system meltdown in common portions of the game that everybody else is cruising through have often been fixed/caused by driver updates.

[Soulwynd]

Yeah, I try to keep my drivers updated. I really have no clues to what's causing it. The rest of the game runs just fine. It's only map gen that does this to me.

I'm gonna try the newest version on my other machine, if it works, at least I will have some maps to play with the newest version  

[Soulwynd]

Figures it creates maps just fine on my other comp. So I made a couple for now...   ... I have no idea what's causing this bug.