Author Topic: Fix for super fast motorcycle? (FFVII) (Read 6099 times)

Trek234 · « **on:** 2003-07-26 20:46:02 »

Hi all,

I was wondering if someone could try this? I don't have a FFVII save near the motorcycle point to try my self.

Ok I am thinking of the refresh force in DirectX. Enable it like this. (for DirectX 9)

1. Go to Start Menu -> Run
2. Type DXDIAG and press enter.
3. Click "More Help"
4. Click "Override"
5. Choose "Override Value"
6. Type "60" in the box. With out "" of course.
7. Press OK.
8. Close DXDIAG.

Ok, then run FF VII and try the motorcycle. Does it go super fast still?

Synergy Blades · « **Reply #1 on:** 2003-07-26 21:17:17 »

Wouldn't that just make the screen flicker instead of being smooth?

Trek234 · « **Reply #2 on:** 2003-07-26 21:34:59 »

Quote from: Synergy Blades

Wouldn't that just make the screen flicker instead of being smooth?

A screen always flickers. This just defines the rate that it does so.

60hz will not visibly flicker.

The thing about 60hz is that it *should* lock the game at 60fps max.

In other words, you are enabling v-sync in another manner.

Qhimm · « **Reply #3 on:** 2003-07-26 21:41:20 »

50 Hz visibly flickers, while 60 Hz merely proves to be annoying as it becomes a strain on your eyes and is a never-ending source of head-aches.

Trek234 · « **Reply #4 on:** 2003-07-26 21:45:26 »

Quote from: Qhimm

50 Hz visibly flickers, while 60 Hz merely proves to be annoying as it becomes a strain on your eyes and is a never-ending source of head-aches.

<sigh> I never said 60hz didn't cause head aches.

The fact is though when you are locked at 60hz you are also locked at 60fps. I.e. motorcycle goes at 60fps instead of 200fps.

Synergy Blades · « **Reply #5 on:** 2003-07-26 22:27:19 »

Quote from: Trek234

Quote from: Synergy Blades
Wouldn't that just make the screen flicker instead of being smooth?

A screen always flickers. This just defines the rate that it does so.

60hz will not visibly flicker.

Erm.. thanks, but I did know that. Besides it does visibly flicker for me (I'm quite perceptable to bad refresh rates).

I think FF7 plays at 60Hz for me anyway, and it's still ridiculously fast.

Qhimm · « **Reply #6 on:** 2003-07-26 22:37:38 »

Quote from: Trek234

<sigh> I never said 60hz didn't cause head aches.

The fact is though when you are locked at 60hz you are also locked at 60fps. I.e. motorcycle goes at 60fps instead of 200fps.

Uhm... no it doesn't. Setting/locking the screen refresh rate doesn't affect the actual FPS of the game, unless it's a REALLY simple engine which always waits for vsyncs (which I don't believe FF7's does). If in doubt, consider Quake III running at 140fps. That doesn't mean 140 frames are pushed to the screen every second, merely to the graphics memory. Besides, locking DirectX's framerate is quite a ...uhm, crude way to fix a single game. No offsense.

Synergy Blades · « **Reply #7 on:** 2003-07-26 22:43:03 »

That's what I thought about not affecting the FPS.

Goku7 · « **Reply #8 on:** 2003-07-26 23:02:56 »

I'm startin' to think that we're probably gonna need someone to add a frame limiter "hack" of sorts, to the actual code that governs the minigames, in order to beat this thing.

Darn it, Jedwin (or whatever his name was that solved the XP Chocobo Race crash), we could REALLY use a miracle or two from you about now.

Trek234 · « **Reply #9 on:** 2003-07-26 23:16:09 »

Quote from: Qhimm

Quote from: Trek234
<sigh> I never said 60hz didn't cause head aches.

The fact is though when you are locked at 60hz you are also locked at 60fps. I.e. motorcycle goes at 60fps instead of 200fps.

Uhm... no it doesn't. Setting/locking the screen refresh rate doesn't affect the actual FPS of the game, unless it's a REALLY simple engine which always waits for vsyncs (which I don't believe FF7's does). If in doubt, consider Quake III running at 140fps. That doesn't mean 140 frames are pushed to the screen every second, merely to the graphics memory. Besides, locking DirectX's framerate is quite a ...uhm, crude way to fix a single game. No offsense.

No one said locking the screens refresh rate effects the actual FPS. Obviously you can run at 60hz and get 80FPS frames. You, of course, will get some tearing as a result.

However, we are locking the hz of the DD API *not* the monitor. This WILL cause the FPS to be equal to or less than the hz specified. This is identical to enabling Vsync in your Quake 3 example. At that point the game will NOT exceed the specified hz (FPS).

"Crude way to fix a single game". You realize this effects DD don't you? Not D3d. How many games do you play that use DD? (I'm not even sure if FF7 is using any kind of DD here... which is why I was not sure if this would work).

Besides, if it fixes it some people wouldn't mind the minor effort it takes to switch it and back.

Rubicant · « **Reply #10 on:** 2003-07-26 23:17:11 »

Underclock your video card, and maybe cpu if neccesary. At least until someone finds a way to fix it completely.