dgVoodoo 2 if it's below DirectX9 maybe.

MrEWhite wrote:

dgVoodoo 2 if it's below DirectX9 maybe.

It's D3D8 but, as I said, it's not a simple compatibility problem. Already tested :p
It's something about the engine and the system timers.

Did you try the Timer Resolution tool?

http://www.lucashale.com/timer-resolution/

My 2 desktop systems -> 15.6 ms
My laptop (the one with NO problems dealing with Enclave) -> 0.5 ms

WTF.....I'll test right now!

No it doesn't matter 🙁

I used this: https://vvvv.org/contribution/windows-system-timer-tool (the tool linked above is for XP only) to set the minimum time (0.5 ms) but there's no change in the game (dis)behaviour.
Enclave reads always "105 MHz" on new systems (Enclave console -> cpu_updatefreq command). On my 2009 laptop it can read the right CPU frequency.....so this misreading is definitely the culprit, but does anybody get an idea to solve the issue?

I would have thought that if the problem was so completely straightfoward to diagnose that someone would have found a solution already.

I tried a Google search for <compatibility shim for cpu frequency>, which turns up https://msdn.microsoft.com/en-us/library/wind … v=vs.85%29.aspx , but that only suggests setting the affinity of the process so that it only uses a single processor.

That page does link to https://support.microsoft.com/en-us/kb/909944 , which suggests disabling power management. https://support.microsoft.com/en-us/kb/895980 suggests the"usepmtimer" switch in boot.ini.

My laptop processor is a dual core one, so I can say: affinity isn't the problem.
Nor the OS, Win10 64 Nov update!
Maybe the hyperthreading? Don't think so, hyperthreading was around in 2003 when Enclave was released.

It's something about the CPU frequency reading in "new" CPUs.

Jorpho wrote:

That page does link to https://support.microsoft.com/en-us/kb/909944 , which suggests disabling power management. https://support.microsoft.com/en-us/kb/895980 suggests the"usepmtimer" switch in boot.ini.

I disabled C1E and EIST in BIOS and set the *lower* frequency multiplier possible (9x), to avoid every possible switching.
Forced "gaming mode" in Process Lasso.

Will test this "usepmtimer" tweak.....

lowenz wrote:

My laptop processor is a dual core one, so I can say: affinity isn't the problem.

I don't think that follows. It's always possible that Windows 10 simply includes a new compatibility fix specifically for this problem. The only way to really establish that affinity isn't the problem is to set the affinity on your other computer and see if that fixes it.

Jorpho wrote:

lowenz wrote:

My laptop processor is a dual core one, so I can say: affinity isn't the problem.

I don't think that follows. It's always possible that Windows 10 simply includes a new compatibility fix specifically for this problem. The only way to really establish that affinity isn't the problem is to set the affinity on your other computer and see if that fixes it.

One desktop has Win10 64, the other Win7 SP1.
Either (HW-twin) systems show "105" MHz in Enclave console, launching "cpu_updatefreq".
Old Laptop+Win10 64 -> no problems.

Affinity set to 1 core for the Enclave process, no changes :p

ACT EmulateSlowCPU shim?

teleguy wrote:

ACT EmulateSlowCPU shim?

I will test!

But I fear that Enclave actually reads ANOTHER frequency in new systems, not the CPU one, maybe DMI or other clock sources.....

when i do cpu update_freq it says 2394mhz
thats a q6600 (2.4ghz) win 7x64
opengl renderer

Davros wrote:

when i do cpu update_freq it says 2394mhz
thats a q6600 (2.4ghz) win 7x64
opengl renderer

They are the last Intel processor series running correctly the game.

Tested now on a Virtual Machine (VMPlayer + WinXP 32 SP3/4).....same damn 105 MHz.

Enclave OpenGL renderer isn't complete, man (it has no shaders/fullscreen effects :p ). D3D path is the best option in this game.

what does cpu _disable / enable do ?
and have you tried resplendent resolver lie about cpu function ?

lowenz wrote:

They are the last Intel processor series running correctly the game. […]
Show full quote

Davros wrote:

when i do cpu update_freq it says 2394mhz
thats a q6600 (2.4ghz) win 7x64
opengl renderer

They are the last Intel processor series running correctly the game.

Tested now on a Virtual Machine (VMPlayer + WinXP 32 SP3/4).....same damn 105 MHz.

Enclave OpenGL renderer isn't complete, man (it has no shaders/fullscreen effects :p ). D3D path is the best option in this game.

I tried the game on my Ivy Bridge CPU. It correctly detected a clockspeed of 3500 MHz.

Does this tool show 105 MHz anywhere else, on the affected systems?

http://www.satsignal.eu/software/PCClockTiming.zip

teleguy wrote:

lowenz wrote:

They are the last Intel processor series running correctly the game. […]
Show full quote

Davros wrote:

when i do cpu update_freq it says 2394mhz
thats a q6600 (2.4ghz) win 7x64
opengl renderer

They are the last Intel processor series running correctly the game.

Tested now on a Virtual Machine (VMPlayer + WinXP 32 SP3/4).....same damn 105 MHz.

Enclave OpenGL renderer isn't complete, man (it has no shaders/fullscreen effects :p ). D3D path is the best option in this game.

I tried the game on my Ivy Bridge CPU. It correctly detected a clockspeed of 3500 MHz.

Oh! Good to know! I will test Enclave on a Skylake system soon.

teleguy wrote:

Does this tool show 105 MHz anywhere else, on the affected systems?

http://www.satsignal.eu/software/PCClockTiming.zip

No 105 Mhz
No 9.5 ms (1/105)

I will try disabling the overclock (actually 200x19 instead of 133x22) but I can't see why "105" 😒