Very impatient dates bug
danicast:
Quote
One thing about this bug that's kind of odd is that there's a post over at the S2C forum with the exact same bug apparently happening at the exact same time.
Ops, now thatīs interesting. Sounds like some borked sim trying to enter the lot. Maybe you have a corrupted char or object.
Repeat the experience with debug mode on and post the error log here, please.
McNum:
Quote from: danicast on 2008 March 09, 00:42:06
Quote
One thing about this bug that's kind of odd is that there's a post over at the S2C forum with the exact same bug apparently happening at the exact same time.
Ops, now thatīs interesting. Sounds like some borked sim trying to enter the lot. Maybe you have a corrupted char or object.
Repeat the experience with debug mode on and post the error log here, please.
I've done it with debug mode on a few times myself to get an error log. However, there is no error log. The game reports no error.
I've tried in a clean neighborhood (made from clean templates found here) to eliminate any Maxis-borked Sims. No dice.
However... I discovered a pattern. I might be able to beat this bug now.
My usual routine when making a Sim ask another out on a date is as follows:
Click Phone -> Call -> Ask Out on Date
Set speed to 3
Community Lot
Car
Then my Sim would run over in fast forward, call up the target and be out of there in 10 seconds flat.
On one of my tests to flush out an error, it worked flawlessly. But how? I forgot to set the game in Fast Forward. That's right, at Speed 1 there is no bug. Well, not that I've seen yet. But if I hit speed 3 at any point from the phone call and until the load screen... "Hurry Up!" "You stood me up! I hate you!"
What exactly does Speed 3 do? Does it just let the game run at whatever speed it can do? Because if that's the case, I know what's wrong. Two weeks ago I installed a Windows Vista update that should improve game speeds, and it did a little. What if Sims 2 is using some silly way to count time before standing up a date and that get counted as fast as a Core2Duo can do when put in Fast Forward?
Preliminary results? I may have found a workaround... more testing required.
If my theory is right, it means I have an inverse performance issue. The game can't keep up with my PC. ;D
danicast:
Borked graphics, game freezes. It happens that the graphic card need some time to proper render stuff. When you put at speed 3, you basically is telling the computer to render everything faster. Maybe thatīs why your game is freezing.
Need moar ram cause vista is a memo hog.
McNum:
The game isn't freezing, the date timing is just screwed up. It's not a graphics card issue, the game renders absolutely perfectly here. It looks and runs as smooth as all the Lies and Propaganda movies EA sent out for all the EPs.
Further testing reveals that Speed 2 is also working out. It's a CPU issue, I bet.
If Speed 3 is really the "Go nuts!" speed, then using a computer 4 to 8 times faster than the very high end PCs at the time of Nightlife's release "Go nuts!" speed could cause some issues. Dual core CPUs weren't readily available when the Nightlife code was written, and 2GB of RAM would have been overkill at that time, too. It wouldn't be the first game I've seen get confused by more CPU power than it was designed for.
Also moar ram? It's a 32 bit Vista. If I add moar RAM, I'm getting too near the cutoff point. At 4,294,967,296 bytes of memory, physical or swapfile, any 32-bit system will ignore the rest. 4GB memory isn't a suggestion, it's the law. Unless you go 64-bit, which has its own can of worms attached.
Moar ram isn't worth the money. Sure I could get one more GB with no problem, but the 4th would be wasted since combined with Windows' swap file, I'd be over 4GB total. So, yeah. I'll get moar ram when I go 64-bit. Not before.
danicast:
Quote
The game isn't freezing, the date timing is just screwed up.
Babe, sounds like objects conflicts. I would check that.
Navigation
[0] Message Index
[#] Next page
[*] Previous page