Page 1 of 1

Unreal/ UT Core 2 Duo Performance

Posted: Fri Dec 14, 2007 8:14 pm
by ToMegaTherion
Hi everbody,
I am playing Unreal/ UT99 on a Laptop with the following specs: Core 2 Duo T 7300, Geforce 8700 m gt, 2 gb of ram and Windows Vista home premium 32bit. I have problems with the performance of Unr/UT (with the Oldunreal patches and s3tc textures), i.e. extremely unstable framerate. Does anyone have similar problems? Any suggestions on how to get decent framerates?

Re: Unreal/ UT Core 2 Duo Performance

Posted: Fri Dec 14, 2007 10:51 pm
by GreatEmerald
Yes, it's always the same issue. When starting UT/Unreal (use the Troubleshooting launcher, BUT there select to play UT normally), open your Task Manager and right-click on Unreal.exe, set affinity and select only one processor. There is a patch to solve this permanently, but you can use this advice for now.

Re: Unreal/ UT Core 2 Duo Performance

Posted: Sat Dec 15, 2007 9:35 am
by ToMegaTherion
Thanks for the suggestion, but you can't set the affinity in Vista. Guess I'll have to wait for a patch which solves this issue.

Re: Unreal/ UT Core 2 Duo Performance

Posted: Sat Dec 15, 2007 11:24 am
by Hyper
Apply the dual core fix from my site. Also you may want to read the 'choppy performance' section at my help page. Here you also can find the download.

http://www.hypercoop.tk/indexh.htm

Re: Unreal/ UT Core 2 Duo Performance

Posted: Sat Dec 15, 2007 12:04 pm
by ToMegaTherion
Problem solved now, thanks a lot. I applied the Dual Core Fix, deactivated Threaded Optimization in the Nvidia driver and enabled Vsnyc in the UnrealTournament.ini. Now I have prefect framerates. This fix also solves similar problems I have with other older games, so THANKS A LOT again!

Re: Unreal/ UT Core 2 Duo Performance

Posted: Sun Dec 16, 2007 11:10 am
by ToMegaTherion
...well, in fact framerates are insane, even with one core (200-300 average). I noticed this while playing Operation NaPali. The cutscenes run so fast that you can't understand the speech. But this is still better than constant stuttering.

Re: Unreal/ UT Core 2 Duo Performance

Posted: Sun Dec 16, 2007 3:17 pm
by Smirftsch
with VSYNC enabled, it shouldn't be possible to get such high framerates, unless your screen supports a refresh rate of 300Hz...

Re: Unreal/ UT Core 2 Duo Performance

Posted: Sun Dec 16, 2007 4:53 pm
by ToMegaTherion
with VSYNC enabled, it shouldn't be possible to get such high framerates, unless your screen supports a refresh rate of 300Hz...
Certainly not, but that's what fraps tells me. At any rate, it is so fast, that the cutscenes don't work anymore.

Re: Unreal/ UT Core 2 Duo Performance

Posted: Sun Dec 16, 2007 7:58 pm
by Smirftsch
so its almost sure to assume that vsync doesn't work as expected. Did you try it with the OMP installed, using OpenGL?

Re: Unreal/ UT Core 2 Duo Performance

Posted: Tue Dec 18, 2007 2:55 pm
by ToMegaTherion
so its almost sure to assume that vsync doesn't work as expected. Did you try it with the OMP installed, using OpenGL?
Yes, I have the OMP patch and I have activated vsync in the ini.

Re: Unreal/ UT Core 2 Duo Performance

Posted: Tue Dec 18, 2007 5:31 pm
by Smirftsch
It's possible to override the vsync game settings with the grafix card driver settings. Did you make any changes there?

Re: Unreal/ UT Core 2 Duo Performance

Posted: Thu Dec 20, 2007 8:00 am
by ToMegaTherion
It's possible to override the vsync game settings with the grafix card driver settings. Did you make any changes there?
Yes, I tried to force Vsync in the driver, but the framerate didn't change at all.

Re: Unreal/ UT Core 2 Duo Performance

Posted: Fri Dec 21, 2007 3:28 pm
by ToMegaTherion
Okay, I ended up playing the game on my single core desktop PC now :(

Re: Unreal/ UT Core 2 Duo Performance

Posted: Sun Jan 06, 2008 4:32 pm
by Masterman
I realize this is an old thread, but I just stumbled across it. If you haven't already fixed it heres a tip, as I was having the same problem on my AMD dual core notebook. Right click desktop and go into your power settings. Make sure that under AC power in you have it turned to always on. This fixed my problem. Stupid as hell, but it works... :)