|
Post by blaze53 on Feb 27, 2017 14:41:23 GMT
Does anyone even know what causes the zoom window in my video to freak out at all? I frankly can't figure out what does it, even after 95% CPU grabber and frame rate cap. Have you tried changing your resolution? Maybe get teleguy's HD patch and increase the resolution past 800x600. It's not that. I've managed to get it to stop doing that before somehow on a vanilla 1.0 install, but now I can't for the life of me figure out what it was. [EDIT]So seemingly with a combination of dgvoodoo, CPUGrabber, framerate cap and compatibility (works with dgvoodoo anyway, it seems), I've solved the zoom window issue, but the game chugs despite maintaining a steady 30FPS.
|
|
|
Post by StoneWall on Mar 1, 2017 22:00:26 GMT
I am going to quote your reddit post just incase it gets deleted somehow in the future here.
|
|
|
Post by blaze53 on Mar 2, 2017 0:02:04 GMT
So I'm putting up with the chug, but...
SIGH.
I'm not entirely certain CPUGrabber (95%-99% does not seem to make a difference, unless I'm not using it correctly? O.o) and framerate limiters are the solution to some of the problems. Without the FPS counter even moving below or over 30, the game slows down and then speeds back up and repeats. I also can't progress past mission 2. The second missile launcher refuses to spawn.
|
|
|
Post by AncientxFreako on Mar 2, 2017 11:18:29 GMT
So I'm putting up with the chug, but... SIGH. I'm not entirely certain CPUGrabber (95%-99% does not seem to make a difference, unless I'm not using it correctly? O.o) and framerate limiters are the solution to some of the problems. Without the FPS counter even moving below or over 30, the game slows down and then speeds back up and repeats. I also can't progress past mission 2. The second missile launcher refuses to spawn. The basic formulas for fixes are there to help in general, but there are bound to be fixes you have to taylor to your rig. Don't give up. The Op1 M2 turret has happened before, I do recall that someone had a solution for it back in the days of the 'Mech3.org help section but I can't remember what it was. I have personally had it happen to me but it seemed to fix itself. Maybe it's just a glitch. Try making a new pilot and starting over after you've done your latest game fixes, then make sure you get the village objective first before you advance to the hill...that might fix it.
|
|
|
Post by StoneWall on Mar 2, 2017 12:11:30 GMT
I'm not sure what you mean by 95% in CPU Grabber. When I slide the toggle on my version, I move it to 30 frames per second.
|
|
|
Post by blaze53 on Mar 3, 2017 18:37:17 GMT
I'm not sure what you mean by 95% in CPU Grabber. When I slide the toggle on my version, I move it to 30 frames per second. Considering it went from 1 to 99 I figured it had something to do with actual percentages of how much of the CPU that would be "grabbed." I think my logic was backwards. Anyway, setting it to 30 seemingly has outright fixed everything major for me. No physics bugs, the game runs very smoothly... except for the slow down, speed back up, slow back down issue, that is. It's weird though, because I ran it at 30 the first time I used it but nothing changed.
|
|
|
Post by StoneWall on Mar 3, 2017 21:52:00 GMT
I'm not sure what you mean by 95% in CPU Grabber. When I slide the toggle on my version, I move it to 30 frames per second. Considering it went from 1 to 99 I figured it had something to do with actual percentages of how much of the CPU that would be "grabbed." I think my logic was backwards. Anyway, setting it to 30 seemingly has outright fixed everything major for me. No physics bugs, the game runs very smoothly... except for the slow down, speed back up, slow back down issue, that is. It's weird though, because I ran it at 30 the first time I used it but nothing changed. I had that problem when I installed the Quadrilogy Pack for the MechWarrior games. I eventually uninstalled and deleted everything and bought an actual CD copy. But if you run over 30 FPS, you will see bouncing enemy vehicles, your jump jets won't work right, and when you jump off a hill - you will shoot up in the air.
|
|
|
Post by herby on Jul 9, 2017 5:26:36 GMT
dgVoodoo not working correctly??? No AA??? No Hi Res??? Z-fighting or texture flickering??? "MY" game is in: C:\Users\herby\Games\Mechwarrior\MechWarrior3... also in MW3-PM... Originally the dgVoodoo.config was in the same folders as the EXE's. I deleted dgVoodoo.config from both folders and they defaulted to: C:\Users\herby\AppData\Roaming\dgVoodoo..... It works. It's all good.
If dgVoodoo.config tries to bounce back to the MW3 or MW3-PM folders just delete it/them again. There may be a setting that causes it to bounce back to the MW3 directory. Mine bounced once. I deleted it again and it has not moved since. dgVoodoo is working flawlessly now. No more Z-fighting or texture flickering. AA and hires are working wonderfully.
|
|
|
Post by herby on Jul 9, 2017 5:33:10 GMT
windows has detected that your computer's performance is slow: What to do??? Right click on the shortcut and go to compatibility. Check [Disable Desktop Composition] This will default to basic while game is running, thus eliminating that annoying popup and ruining your game.
|
|
|
Post by StoneWall on Jul 14, 2017 11:56:36 GMT
dgVoodoo not working correctly??? No AA??? No Hi Res??? Z-fighting or texture flickering??? "MY" game is in: C:\Users\herby\Games\Mechwarrior\MechWarrior3... also in MW3-PM... Originally the dgVoodoo.config was in the same folders as the EXE's. I deleted dgVoodoo.config from both folders and they defaulted to: C:\Users\herby\AppData\Roaming\dgVoodoo..... It works. It's all good. If dgVoodoo.config tries to bounce back to the MW3 or MW3-PM folders just delete it/them again. There may be a setting that causes it to bounce back to the MW3 directory. Mine bounced once. I deleted it again and it has not moved since. dgVoodoo is working flawlessly now. No more Z-fighting or texture flickering. AA and hires are working wonderfully. that's good to know
|
|