OldUnreal (Engine)

On BuF, a very interesting thing came out of discussion for a possible UT patch. It's related to the timing problem, where you get crazy time shifts when you have unlimited framerate in UE1. There is some interesting insight in the article written by AnthraX there, and even some solution proposals. I wonder if something like that could be done for U1 as well? Also, any general thoughts about it from the dev team here?

The article is here (it's a TXT file): http://utgl.unrealadmin.org/ACE/Timing.txt

since already quite some time in good company with anthrax in IRC some fix is done already, not this version but its already covered.
Also some some basic fix for that was already in 227f (not entirely sufficient though).

I'm curious, which type of fix is it?

I guess the most important part was to set the affinity by default to one CPU / Core and that for all OS, Win, Lin and Mac.
Also using some different timing method as described in the doc. I didn't implement the last version from Anth yet but current tests show no problems of any kind, so maybe I'll leave as is.

Well, there are 4 methods listed in the doc.
You can auto set affinity? That's neat. I never knew that was possible.

I guess the most important part was to set the affinity by default to one CPU / Core and that for all OS, Win, Lin and Mac.

That for UT would make my day.

http://www.robpol86.com/index.php/ImageCFG

no idea if UT anticheats will catch once you use this, but it's a MS tool originally but the download is really missing

Some of the earlier versions of ACE caught modified UT.exes but with the public versions you're safe. I'm not sure if it's a good idea to use such a tool though. Some threads (eg: networking, input related threads) DO still benefit from being able to run on multiple cores. It's just the rendering that has to be restricted due to RDTSC problems. I guess I could make a custom UT.exe for use on non-ACE servers though

and FYI, the code I sent to smirftsch for use in Unreal is based on one of my older experiments. It's using RDTSC with automatic calibration (aka TimingMode=3). It works well but it's not the optimal solution resource wise.