tain.totalcodex.net

This topic (a LONG one, so please bear with it) is about the same problem reported in both of these ones:

http://www.projectmagma.net/forum/viewtopic.php?t=1898

http://www.projectmagma.net/forum/viewtopic.php?t=1896

I have the SAME problem, exactly as described by them. I don't even remember how long this has been happening on my machine. If you pay attention, you will notice that this occurs on Windows XP SP 2 fully upgraded. I will get back to this later.

Anyway, what happens is that when I run Myth normally, the game is locked up on a refresh rate of 21 FPS. This applies to BOTH Myth TFL and Myth SB. And I'm not only talking about the in-game graphics, ALL the menus, projectiles,screens, everything is locked up on 21 FPS. When i scroll through the list of maps, it's possible to see that the menus aren't smooth at all.

Strangely enough, the in game FPS function shows a value of 100+. So I came to a conclusion that the game actually renders those frames (in case of Myth 2 1.6), but somehow my screen is locked up on 21 FPS (I got this value using FRAPS, but it's easy to see that the games are not running on 30+ FPS). The monitor will just render 21 FPS.

This has a "limited" fix though. If you leave Windows Media Player (or any other similar video aplication, although it's easier with WMP), the game smooths up right away, includind the menus. When I do this, FRAPS shows the game locked up on 30 FPS (for Myth TFL. M2 goes higher since 1.6), and it drops down EVERY 4 seconds to 26, then goes up. This behaviour goes FOREVER, for both games. But it's still better then the chopiness from 21 FPS.

Annoyed by this, I did a lot of tests, so I will share the results and I what I know abot this strange issue:

- This is not a problem of renderer type.

I have the same issue on ALL renderers (Software, OpenGl, Direct3D, even 3DFX). The fix also works for all of them.

- This is not a drivers problem

I tested a lot of drivers, old, new, non-official. To further confirm this, I uninstalled all my video drivers and ran Myth TFL and M2 on software mode. The problem persists, and the Windows Media Player fix still works.

- This is not a spyware/virus/CPU sucking problem.

I periodically check for viruses and spyware, and have more then one software to cover this. I can guarantee that there's nothing sucking up CPU cycles from Myth. Ironically, Myth seems to run better when there are other processes running in the background.

- This is not a hyperthreading problem.

My PC is an old P4 2.0. It doesn't have hyperthreading (AFAIK).

- This is not a Version Problem.

The same behaviour, issue and fix applies to ALL MYTH VERSIONS. I tested a couple, even the unpatched Myth 2 game right out from the box.

- This is not happening only to me.

Besides the 2 topics I mentioned, I also tested this on another machine with a different graphics card and different drivers. The thing in commom was that it was also running Windows XP SP2. The problem was the SAME, and the Windows Media Player fix worked as always.

- This happens only with Myth, on ALL resolutions. All other games run fine.

So, I came to the following assumption:

Something in Windows XP doesn't like the way the Myth engine outputs graphics to the monitor. It's a Myth only issue, that happens in both games, since they share some code (AFAIK). It seem to me that it treats Myth output like a video file output, who knows, I'm no expert.

Of course, I could be totally wrong, and there's an obscure setting or configuration that fixes this permanently, but I'm totally clueless. But the WMP fix tells me that it's something tricky.

Also, if anyone has a similar machine to mine (see below) and DOESN'T have this problem, please post here and maybe we can find a definitive solution. Until then, I will leave Windows Media PLayer Open, at all times, hehe.

My Machine:

Windows XP Service Pack 2
Pentium 4 2.0 GHz
256 MB RAM
HD 80 GB
GPU : Nvidia Fx5200

Thanks for all who read this rather long post.[/url]

Nice investigating. The weird thing is that Myth doing stuff in OpenGL and in Direct3D and in Software Renderer is completely different code. It draws stuff differently. Also, do you still get the same problem in Windowed mode?

I also know for a fact that not everyone experiences that. Your myth isn't set to use an old Windows version compatibility mode by any chance?

If its none of those, and since different settings cause Myth to draw stuff differently, the only thing I can think of is some Windows call that Myth does when it starts up somehow causes Windows to cap Myth at 21fps on some machines. Not sure what that may be, but that's the only thing I can think of that would only affect Myth yet still apply to all rendering modes.

EDIT: I did a quick search and found a post that might be a similar problem about the game Oblivion (but it's hard to tell if it is, since Oblivion needs a lot more resource than Myth, but replies to the person still suggest he should be getting more than 21fps, which makes me think it may be the same bug..). Also, he says it likewise doesn't change for different resolutions. http://forums.guru3d.com/showthread.php?t=181767

I still get the same problem using windowed mode. Actually, I'm using it right now.
It's not using any form of compability mode.
I looked into this link, and after reading the guys problem, I'm almost sure that this issue with Myth is either a processing problem or a screen refresh problem.
Why Windows Media Player fix this, i have no idea.
If I find more info I will post it.

A small update:

I started Myth 2 with FRAPS on... the menus were jerky as usual, but when I started a level, the FRAPS FPS count went to 60. But to my surprise, the game was still jerky like when it showed 21 FPS (Myth 1.5.1 and previous versions). Very strange indeed.

Also, it seems that I'm the only one having this issue... There isn't anyone with the same problem?

I can confirm this problem, and the odd media player solution.

I'm glad I came across this topic, good to know I'm not the only one with the problem.

It does seem to be a Windows XP problem, because it doesn't affect a computer I had Windows 98 SE running on.

Whoa, I'm glady my topic helped someone.
A strange problem indeed... I guess It will never be fixed

Has anyone heard of a fix for this yet? The windows media player thing doesn't fix the camera hesitation for me.

Are you sure it's the same problem? Try using FRAPS and see if you ingame FPS is locked at 21.

Actaully mine hovers around 26 to 30 / never gets above 30 though. It's simply a jerkiness with the camera.

Here's my specs

AMD Dual Core 2200+
Radeon x1300
1GB DDR2

but I have the EXACT same issue with my pentium.

I'm just running the 1.5.1 demo because I am still waiting on my copy of soulblighter to arrive. Do you think the 1.6 update could fix this? I've read that update has many improvements.

Well I got my Soulblighter CD today and loaded it up with 1.5.1 and then 1.6. Still have the choppines with the camera tho. Weird. Anyone have any suggestions? This is the only game I have this issue with from Starcraft to Supreme Commander.

Have you tried changing the rendering method from Direct3D to Open Gl and vice versa? Or upgrading your video drivers?

There's nothing much else I can think about.

Yeah, latest Omega drivers and I went ahead and tried the latest ATI in case it was that. I even tried software rendering. Yeah I hear you. I'm out of ideas. I even went so far as trying a single core in case it has something to do with dual-core.

Are you using Windows Vista by any chance? I know Myth runs poorly on it for some people.

No, Im running XP SP2. It's like I'm capped at 30fps for some reason. I played with those CapFPS settings but ultimately just left it unchecked. It's definately a bummer.