Frame Rate Explosion : 273 Suspected! - This and more, coming up....
A forum for solving problems that might be encountered during installation, updating, or in game.
- :) Da Cid (: McCl
- Posts: 380
- Joined: Fri Jan 07, 2005 9:45 pm
- Location: Perth Australia.
Post by :) Da Cid (: McCl »
Whenever I'm on my PC and I'm playing with 273, it slows right down like a sonnuvagun. I was playing DoD today and at the beginning I was at 15 FPS, and when I looked at all the transparent trees it came down to 6.
Just me?
-TGP-
Just me?
-TGP-
Having fun with poser horses and pasted-on Warrior torsos since 1990!™
Try using the classic build and report back your results. Also the output from dxdiag would be good.
What rendering option do you use? (D3D / OpenGL?) What's your FPS like in other builds? What's your video card?
- :) Da Cid (: McCl
- Posts: 380
- Joined: Fri Jan 07, 2005 9:45 pm
- Location: Perth Australia.
Post by :) Da Cid (: McCl »
I checked 271, and I'm having the same problem. Although I went back back to 270 and the FPS of DoD shot up to 30 (still crap, but normal for my computer).
I'm using software, 1024x768.
Video card is (I believe) a NVIDIA GeForce 2 MX 400 or something like that.
Also, explain what a dxdiag is and I maybe I can tickle your fancy.
-TGP-
I'm using software, 1024x768.
Video card is (I believe) a NVIDIA GeForce 2 MX 400 or something like that.
Also, explain what a dxdiag is and I maybe I can tickle your fancy.
-TGP-
Having fun with poser horses and pasted-on Warrior torsos since 1990!™
dxdiag.exe is the, well, diagnostic tool for DirectX.
It should live in your System directory. It'll tell you all sorts of stuff about the DirectX setup and capabilities of your machine.
It should live in your System directory. It'll tell you all sorts of stuff about the DirectX setup and capabilities of your machine.
Interesting findings though
I wonder what could have happened to put more more strain on the processor.
Edited By Doobie on 1141664058
I wonder what could have happened to put more more strain on the processor.
Edited By Doobie on 1141664058
In Build 273 Installer, there's a choice (on Windows) between Classic Myth II and the default one, which is the windowed mode version. The Classic Myth II is very similar to 1.5.1 in terms of how it interacts with Windows. Try it, and see if it solves your problems.
- :) Da Cid (: McCl
- Posts: 380
- Joined: Fri Jan 07, 2005 9:45 pm
- Location: Perth Australia.
Post by :) Da Cid (: McCl »
I switched to windowed mode on 273 and it got worse. However, when I switched to D3D, it shot up really high (and looks nicer too. >_>)
Here's my DxDiag Mahwhatzit.
Thanks for the help, guys.
-TGP-
OH ALSO I can't use the scroll wheel anymore and when I press F4 it acts like the escape button.
Here's my DxDiag Mahwhatzit.
Thanks for the help, guys.
-TGP-
OH ALSO I can't use the scroll wheel anymore and when I press F4 it acts like the escape button.
Having fun with poser horses and pasted-on Warrior torsos since 1990!™
- William Wallet
- Posts: 1494
- Joined: Tue Mar 30, 2004 9:40 am
- Location: Perth Australia
- Contact:
Post by William Wallet »
Software mode.
David, if the authorities find out that I've been such an irresponsible uncle that I've let you use *software* mode... they'll hang me out to dry. They'll...
(sotto Dennis Quaid in Enemy Mine)
They'll take you away from me and we'll never see each other again.
David, if the authorities find out that I've been such an irresponsible uncle that I've let you use *software* mode... they'll hang me out to dry. They'll...
(sotto Dennis Quaid in Enemy Mine)
They'll take you away from me and we'll never see each other again.
Okay I got the models but now I'm too dumb to do anything with 'em
- :) Da Cid (: McCl
- Posts: 380
- Joined: Fri Jan 07, 2005 9:45 pm
- Location: Perth Australia.
Post by :) Da Cid (: McCl »
Well yah aknow but... last time I had Myth on the computer it went slow in anything BUT Software mode. I guess I forgot to put it back after teh computer was fixed.
-TGP-
-TGP-
Having fun with poser horses and pasted-on Warrior torsos since 1990!™
Wow, 273 has a Windowed mode checkbox? I hadn't noticed. There I was, waiting for Melekor to release a windowed version of build 273.
A difference between 273 windowed and Melekor's
"MythII_windowed_beta.exe" is that the windowed beta fixed the mouse recentering bug when running under Linux with Wine. 273 windowed still has the bug (like every fullscreen version).
So it seems that 273 windowed is still doing some nasty DirectX calls at startup. Stuff like
trace:dinput:mousedev_create_deviceA Creating a Mouse device (0x7da9eb68)
trace:dinput:SysMouseAImpl_Acquire Warping mouse to 326 - 274
which the windowed beta didn't do. Would it be possible to remove those DirectX calls from 273 in windowed mode?
A difference between 273 windowed and Melekor's
"MythII_windowed_beta.exe" is that the windowed beta fixed the mouse recentering bug when running under Linux with Wine. 273 windowed still has the bug (like every fullscreen version).
So it seems that 273 windowed is still doing some nasty DirectX calls at startup. Stuff like
trace:dinput:mousedev_create_deviceA Creating a Mouse device (0x7da9eb68)
trace:dinput:SysMouseAImpl_Acquire Warping mouse to 326 - 274
which the windowed beta didn't do. Would it be possible to remove those DirectX calls from 273 in windowed mode?
- William Wallet
- Posts: 1494
- Joined: Tue Mar 30, 2004 9:40 am
- Location: Perth Australia
- Contact:
Post by William Wallet »
Ah. Apology accepted.:) Da Cid (: McCl wrote:Well yah aknow but... last time I had Myth on the computer it went slow in anything BUT Software mode. I guess I forgot to put it back after teh computer was fixed.
-TGP-
Okay I got the models but now I'm too dumb to do anything with 'em
Yes Build 273 didn't include Melekor's rewrite of the input code. Trying turning DirectInput off and on in the prefs and see if your mouse problem goes away.