swaaye wrote:
Yes, I used "u2_retail-031403.exe"
swaaye wrote:
I've never had the game crash on me before. The annoying problems with it are 1) it's not that fun 2) the load times don't get faster on new computers even when they are insanely faster than what I originally played the game on.
The load times are annoying and it also has an annoying tendancy to freeze during either the Standby or Initializing screens. Either that, or it goes off into limbo for so long that I can't tell the difference and end up hitting the reset button.
As for it not being fun; I was actually enjoying it. Other that the fact that the Acheron mission crashed every couple of minutes on the surface, I really liked it. Exploring the inside of the creature was great.
DosFreak wrote:Mabye it's a memory/resource issue? Can't remember what memory monitors work on 9x but you may want to load one of them up while playing the game.
It might be, but I have double what the system reuirements call for. The minimums are 256MB RAM and a GeForce2 MX card with 32MB. The recommended specs are 384MB RAM and a GeForce3 with 64MB or better, which is what mine has (64MB).
I've noticed that it tends to crash more in the outdoor areas, than when I'm inside. However, some of the indoor areas in the Hell mission were huge with a lot of detail and I think it only crashed once.
On the other hand, I did notice a severe framrate drop in some areas for no apparent reason. I would be exploring an area and the framerate would be fine, then I'd grab a pickup or switch weapons and suddenly the framerate would drop to the single digits. Usually if I quit the game, reboot my system and then reload that same area it will be fine again. I mean, I get slowdown (a LOT of slowdown) if there's too much action on the screen, which I can mostly understand, but there doesn't seem to be any direct cause of these slowdowns. In one fairly small room in the Hell mission, there was a rectangular walkway around a large piece of machinery with a large, circular door on one side leading to a huge central area. I could walk all the way around the room, look up, etc, all at normal speed, but the second I faced the door, the game became a slideshow. The door wasn't even open. I rebooted and loaded that area again and the game was somewhat sluggish when the door opened, but didn't slow down to the ridiculous degree that it had before.
I know my system isn't exactly top of the line, but Halo came out the same year as Unreal II, and other than having to turn off particle effects, I can't recall Halo ever slowing down like that. It also never crashed on me.
When I got to a certain point in the first Unreal, it started to crash with a message (I think) about "actors" or maybe something about the world size. Whatever it was, I found the listed word in the INI file with a number after it, which I increased. I think I had to increase it a couple times, but that fixed the crashing issue.
I was hoping there might be something similar for Unreal II. Maybe some allocation that needs to be increased. I took a quick look, but didn't see anything that stood out.