SOLVED: A 3rd time. Issue with Fraps recording of FF7

  • Thread starter Thread starter DLPB_
  • Start date Start date
Status
Not open for further replies.
I always use aali as well.  I need to know if this happens with the non aali game (so I can see if this problem is exclusive to 1.02 or aalis driver) and if other people experience this issue with fraps.
------

The field is hardly a massive drain on resources.  It is a still image for starters and not even 3d aside from the characters so what can be causing a 2 fps drop there and no issue on world map (even overhaul world map) and no issue in battle or anywhere else.  It is just the field of ff7. It doesn't make any sense unless for some reason fraps is having a severe issue with the game (or 1 part of it or aalis driver). There is definitely something up here....
 
Last edited:
I have always experienced this issue, no matter what the computer. My computer's are no slouches either.
 
I have always experienced this issue, no matter what the computer. My computer's are no slouches either.
Well hopefully someone can shed some light on it... there are only some possibilities really:

1. Fraps has some issue with aalis driver or changes
2. Fraps has an issue with aspects of how the field maps are drawn/rendered.

But since FF8 field is fine, there has to be something else going on here...

Do you use win 7 sl1982?
 
i installed the latest version of fraps 3.4.5 (demo) and had a go at recording at 1280x720 at full-screen on my "AMD Phenom X6 1055T" + "ATI 5770 1GB CuCore" + 4GB of RAM and XP SP3 and had the exact same problem (28fps average but sometimes dropping down to as little as 26fps in field), then i tried messing with the settings in the openGL config for Aali's Custom driver and found that running in full-screen was the problem (for me atleast), using the exact same settings in window and full-screen gave me 2 different sets of results, in a window it ran at 30fps average and from time to time dropped to 29fps (for very short moments),
here is the video showing the difference
Windowed

Full-screen
 
Does it on windowed to me, too :(

Which options did you mess with?  Or was it just window mode that made it work for you?

Perhaps this is a resource problem and something is hogging a shit load when recording ff7 field?
 
Last edited:
Out of curiosity, has anybody tried it on a single core system, or setting the affinity of ff7 to only use one core? I've found this improves performance in quite a few older apps, especially when you're trying to run it alongside something else.
 
FF7 doesn't have multiple processes, and from what I understand (I haven't run FF7 PC in a while) likes to fill empty processor cycles with null instructions. I can an advantage in running FF7 on one core whilst hosting FRAPS on the other.
 
Did you try vsync off by any chance? If it records at a higher speed you can always edit the video. Or changing your refresh rate to lock at 30hrz might help :)
 
Forgive me for being retarded in advance,

Can this possibly be affected Aali's frame skipping/limiting. Could explain why it only affects FF7. hard to record @ 30fps if the object to record is less.
 
Last edited:
tried vsync (and remember fraps works fine with FF8).  Not sure about this frame skip thing though?  Again I would expect FF8 to have the same issue but it doesnt.

Editing isn't an option, I plan on putting the entire newly translated story on to youtube and that is enough work already :)
 
Forgive me for being retarded in advance,

Can this possibly be affected Aali's frame skipping/limiting. Could explain why it only affects FF7. hard to record @ 30fps if the object to record is less.
Maybe?

I dunno.  I am still having the problem.  Perhaps if I had a super computer?  If there is a frame skipping option, perhaps a way to disable it so I can test?

Something seems to be very different in field to world map and battle.  I wouldn't expect a field to be that cpu/gpu intensive?

looking at it, maybe my system has some sort of issue.  I think kranmer got it working with a much more powerful one.
 
Last edited:
Well today yesterday Kranmer and I concluded that the problem with FF7 and fps issue is not related to performance.  It is something else.

Kranmer found the memory addresses for the FPS limiter (8 byte floating point).  When set to 32.0, fraps will record (for me anyway) at 30 fps.  When set to 62, it will record 60 fps.

There is another reason why 2fps is being lost and it isn't lack of CPU or GPU or Harddisk speed.

You may check this yourself by changing the byte at 007B7846 (memory) from 3E to 40.  Make sure you enter the world map or battle before returning to a field.

If you want to change battle, this value is at 007C0B06

-------

I get a nice 30fps by ;letting fraps do the limiting (to 30), by setting field to 60fps (4e at 7b7846).

 
Last edited:
soo to fix it i have to insert this code "007C0B06"  to where? your video was smooth as hell
 
soo to fix it i have to insert this code "007C0B06"  to where? your video was smooth as hell
It is a memory Address, to use it grab a memory editor/disassembler (i use cheat engine for editing memory so i will tell you how to do it in cheat engine) run the game and attach cheat engine to FF7 then click on "Memory View" button, you should see a bunch of HEX values in the bottom half, right click in the bottom half and then and click on "Goto Address" then enter the value "007B7846"  then you should be able to edit the value to what you want and it will change the address in the game.
 
Status
Not open for further replies.
Back
Top