OldUnreal (Engine)

I got a new computer recently. Quad 3.3, window 7 64 bit, GeForce 560 Ti, you know, can run pretty much anything at absolute maximum.

But who cares when it doesn't run Unreal properly?

Now, I know that a lot of old games have that good old "I don't run well on more than one core" problem. I know how to tell a program to only use one core.

Problem is, it makes no difference with this computer. It still runs too fast, its not LIGHTNING fast mind you like it probably should. But I don't quite understand what is going on.

I cannot call this a good computer if it doesn't run Unreal 1 well. Anybody has a clue on how to fix this?

are you running the 227H patch? I ask as I am running u1 on a Windows 7 Pro Quad Core Q9650 3ghz and Radeon HD 3450 which seems to run fine, not choppy or too fast.

Activate vsync to stop the game from having these seizures. 227h should fix this issue, but a few options may be necessary.

Or set FramerateLimit in the advanced options/ini files of your renderer to your screen refresh rate. But that should already be the case with the 227 patch.

I'm not using unnofficial patches. And I don't want to rely on that either. There are lots of other games in that generation and heck, other on that engine that don't have that luxury.

I need to find a way to fix it other than just patching it, and I prefer the latest official version anyway. Closest I could do is try to force VSync through NVIDIA but it does nothing, doesn't work at all in Software mode actually (it doesn't lock the FPS).

well, it's as official as possible, because without Epic's permission it wouldn't exist and the patches were made to fix especially such problems. Without the new features which are optional, it behaves exactly the same as before. Anyways, your decision...

Try to force CPU affinity in TaskManager to one CPU only.

Yeah, anywhere I ask for help people really have no more idea what is going on than I do, it seems.

Yes, I'm fully aware of what the patches are, and they are great, but they just get in my way, but I'll probably just have to deal with it.

Like I said in my first post I already know the affinity trick/using 1 core. Even with only 1 core running at 1% its still running too fast.

Weird. You didn't mention if its an Intel or AMD? AMD offers some multicore fix tool...don't remember its name atm, but can look it up...

Edit: DualCore Optimizer

yes any information you can add might help.
What specific version of unreal?
What video card model?
Video card driver revision?
Have u tried Opengl?   Directx?  or just software mode?
Is this on a desktop pc or laptop (if laptop does it have speedstep disabled)?

Also just a thought, can you right click on the unreal.exe and run it in compatibility mode?  Maybe try it in XP SP3?  I dont suspect it would fix the issue, but worth a try.

I'll downgrade my 227H on my quad core to 225F (or whatever patch you have), and try to see if I can duplicate.  Only thing is I have an ATI card on that pc, and its at the office, but can do Mon morning if no resolution by then.

Other games on UE1 actually have the same problem, just take a look at UT99 or Deus Ex.

In my experience, the setaffinity thing was always useless or very temporary. The best way to fix that issue (excluding 227) is to enable vSync in you game settings, not you GPU's control panel. In Unreal.ini, in your renderer's chapter, there should be something like SwapInterval. Set it to 1. If you're using opengl (which is recommended, especially with ulgr), the line is not present by default in unreal.ini, but you can simply add it at the end of the chapter.

SwapInterval seems to do nothing for software mode.

I have a GeForce 560 Ti and an intel i5-2500k (sandy bridge). This is a desktop PC.

The only mode besides Software that works in the older version (Unreal Gold here, thats 226) is Direct 3D, which has huge and ugly brightness issues, and the mouse gets all smoothen up and feels absolutely horrible.

Compatibility mode doesn't seem to change anything.

The closest I came to a fix is FRAPS... since it locks the FPS, the game runs perfectly while recording, but I don't have the HDD space. There is a new 30-second cache recording option, but it lags.

Its funny that there isn't just a simple versatile FPS limiter that does this ANYWHERE. There is one, but it works only on select games, and not in Unreal software mode.

Swapintervall is only working on D3D8/9 or OpenGL with the multimedia patch update (OMP). But that's again some kind of patch then...

D3D7 is having VSync and original OpenGL doesn't work anyways on most cards since at least 224.
SoftDrv never had such an option, but even D3D7 looks better than SoftDrv in my opinion

I will just say that if patches get in your way, then you're doing something wrong. I fail to see the logic in trying to solve a problem that has been already fixed in a patch.

I will just say that if patches get in your way, then you're doing something wrong.

No, I'm not. Different =/= wrong.

I fail to see the logic in trying to solve a problem that has been already fixed in a patch.

You don't have to get it. But like I said, this is for more than just this game anyway. Not all old games have the luxury of unofficial patches.

Does the vSync in D3D7 work ? I fail to see why anyone would play in software mode and this workaround should work in D3D.

If vsync, setaffinity or max fps doesn't work and 227 is not an option, the list of possible solutions has ended and you're pretty much screwed.

You might also give turning CNQ off if you have an AMD processor, though I personally do not recommend it.

I've explained why Direct 3D is worse than Software, and I have pointed out I have an Intel processor.

the OMP's are based on UTGLR, which are working too for UT/DeusEx. This offers a solution for at least some of the UEngine1 games. Other than that I'm running out of ideas pretty much now. For me 224/225/226 are working on my Win7-64 (not perfectly, but they do), with Quad 3.2Ghz and NVidia GTX260, buts its an AMD and maybe this makes a difference here. Maybe there are INTEL specific tools which can help, and a look into this direction could be an idea.

I'll keep looking. Thanks for trying to help.

I'll try to find out more too. But if you find a solution, let us know, would be helpful for other players too.

I've explained why Direct 3D is worse than Software

Hum, if all else fails, maybe try ulgr's D3D modified Renderer ? They should be better and have less bugs, but in my experience, they are much slower than the original D3D7. After this, I'm out of ideas too.

Can anyone help me with this then:

In an updated version (I'm still keeping the old one around but this isn't the point), using OpenGL or Direct3D looks horrible thanks to anti-aliasing or some such. I despise this with all my heart.

But easy enough, there are settings for this. But if you disable them, the lighting gets all screwed up and I get squares of light all over.

...how do I just disable AA without any funky side effects...? I want sharp looking textures. Not something that makes me feel like I don't have my glasses. (which is what AA does).

EDIT: I think its more than just AA, just removing AA doesn't do that, but having NoFiltering to True causes the above problem.

Also, FrameRateLimit doesn't work in Software.

unfortunately you are not very specific about the effect which is disturbing you that much.
AA indeed doesn't do much difference in optics, except its specific purpose of course.

So I can only guess - if people dislike something, then its most of the time the coloring, which looks more washed out in glide f.e., this for OneXBlending must be set to true.

If talking about not so sharp, maybe try to set LodBias to -1.

For anything else I need more input

As for software, it wasn't changed that way, it's still the way it was in older versions, but do you have the speed problem in the updated version as well there?

any chance you could post a screenshot of the issue?

Sounds like you have Anisotropic Filtering off or set to a low value. LODBias should indeed help there. Also make sure that your video card drivers are not forcing a low AF value.

Also, there is no dedicated AF option in Unreal, is there?