New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

DQ2 short graphics freezes while dragging map #13

Closed
Nathan-P-B opened this Issue May 29, 2014 · 4 comments

Comments

Projects
None yet
2 participants
@Nathan-P-B

Nathan-P-B commented May 29, 2014

version: pre-alpha "aleph" א release 0.0.0 (files dated 2014-05-07)
OS: Windows XP 32-bit and Windows 7 64-bit
CPU: AMD and Intel, dual-core (forcing single core made worse)

(This is from http://discourse.leveluplabs.com/t/dq2-pre-alpha-aleph-0-0-0-bugs-and-comments/329/2 .)

When dragging the map, I sometimes get about a quarter-second to half-second graphics freeze. I can't find any relationships between the area of the map, the delay length, or the drag length. The freeze can also happen when the map is scrolling while following Azra's movements between waypoints. When moving directly from the very start to start of the final cave and back a few times, I saw the freeze happen one to three times (and again, with the freeze not happening at any particular time). This is in the default 800 by 600 windowed mode.

This is under 32-bit Windows XP on a dual-core AMD Athlon 64; the freezes seemed to take longer when I forced the game to use a single core. I also tested this under 64-bit Windows 7 on a dual-core Intel E7500 . Again, the freezes seemed to take longer when I forced the game to use a single core.

@Nathan-P-B

This comment has been minimized.

Show comment
Hide comment
@Nathan-P-B

Nathan-P-B Jun 12, 2014

At least on Windows XP (Windows 7 untested), this is still a problem in:

  • DQ2 0.0.2 / TDRPG 0.0.2 (files dated 2014-06-11)
  • DQ2 0.0.4 / TDRPG 0.0.4 (files dated 2014-06-13)
  • DQ2 0.0.4 / TDRPG 0.0.5 (files dated 2014-06-18)
  • DQ2 0.0.5 / TDRPG 0.0.8 (files dated 2014-06-27)

Nathan-P-B commented Jun 12, 2014

At least on Windows XP (Windows 7 untested), this is still a problem in:

  • DQ2 0.0.2 / TDRPG 0.0.2 (files dated 2014-06-11)
  • DQ2 0.0.4 / TDRPG 0.0.4 (files dated 2014-06-13)
  • DQ2 0.0.4 / TDRPG 0.0.5 (files dated 2014-06-18)
  • DQ2 0.0.5 / TDRPG 0.0.8 (files dated 2014-06-27)

@Nathan-P-B Nathan-P-B changed the title from DQ2 (2014-05-07) short graphics freezes while dragging map to DQ2 short graphics freezes while dragging map Jun 28, 2014

@larsiusprime

This comment has been minimized.

Show comment
Hide comment
@larsiusprime

larsiusprime Jul 17, 2014

Owner

Strange. Wonder if it's a GC or something. Does this happen with the latest builds still, and does anything like it happen on any other screen?

Owner

larsiusprime commented Jul 17, 2014

Strange. Wonder if it's a GC or something. Does this happen with the latest builds still, and does anything like it happen on any other screen?

@Nathan-P-B

This comment has been minimized.

Show comment
Hide comment
@Nathan-P-B

Nathan-P-B Jul 29, 2014

I used FRAPS to record some frame rate timings for DQ1 0.0.6 / TDRPG 0.1.1 (released 2014-07-18). (I've not used FRAPS for this, so I don't know how accurate it is, but the recorded long frame times seemed to correspond with what I could see.) For each of the five below recordings, the reported average (I'm guessing the mean) frame rate was between 50 and 55 FPS, with maximum 61 to 62 FPS.

  • The title screen was recorded for 25 seconds. The highest frame length was 42 ms.
  • The load-game screen was recorded for 35 seconds. The highest frame length was 268 ms, but it looks like that was only one frame. The next-highest frame length was 44 ms.
  • The stationary world map was recorded for 40 seconds. This showed some pearls and the current Azra position. I did not move the world map or Azra at all, but I did hover the mouse over various buttons and pearls (the mouse hovers did not seem to affect the timing). The highest frame times were 1163 ms and 1096 ms (a little more than a second). The next four highest were ~270 to 500 ms, followed by three more 52 to 96 ms. After that a bunch of frames were 43 ms or shorter.
  • The slightly moving world map was recorded for 47 seconds. I had the map in the upper-right corner and kept dragging it short distances, keeping the view in the upper-right corner. The highest frame times were 488, 362, 313, 272, 255, 97, and 53 ms. The other frame lengths were under 50 ms.
  • A moving world map was recorded for 48 seconds. I kept dragging the map around to follow the outer perimeter of the map area. The highest frame times were 930, 599, 582, 549, 502, 394, 366, 187, 94, and 92 ms. The other frame lengths were under 50 ms.
    So it appears that even keeping the map screen had some long frame rates. The problem is more obvious when dragging the map, though.

Nathan-P-B commented Jul 29, 2014

I used FRAPS to record some frame rate timings for DQ1 0.0.6 / TDRPG 0.1.1 (released 2014-07-18). (I've not used FRAPS for this, so I don't know how accurate it is, but the recorded long frame times seemed to correspond with what I could see.) For each of the five below recordings, the reported average (I'm guessing the mean) frame rate was between 50 and 55 FPS, with maximum 61 to 62 FPS.

  • The title screen was recorded for 25 seconds. The highest frame length was 42 ms.
  • The load-game screen was recorded for 35 seconds. The highest frame length was 268 ms, but it looks like that was only one frame. The next-highest frame length was 44 ms.
  • The stationary world map was recorded for 40 seconds. This showed some pearls and the current Azra position. I did not move the world map or Azra at all, but I did hover the mouse over various buttons and pearls (the mouse hovers did not seem to affect the timing). The highest frame times were 1163 ms and 1096 ms (a little more than a second). The next four highest were ~270 to 500 ms, followed by three more 52 to 96 ms. After that a bunch of frames were 43 ms or shorter.
  • The slightly moving world map was recorded for 47 seconds. I had the map in the upper-right corner and kept dragging it short distances, keeping the view in the upper-right corner. The highest frame times were 488, 362, 313, 272, 255, 97, and 53 ms. The other frame lengths were under 50 ms.
  • A moving world map was recorded for 48 seconds. I kept dragging the map around to follow the outer perimeter of the map area. The highest frame times were 930, 599, 582, 549, 502, 394, 366, 187, 94, and 92 ms. The other frame lengths were under 50 ms.
    So it appears that even keeping the map screen had some long frame rates. The problem is more obvious when dragging the map, though.
@larsiusprime

This comment has been minimized.

Show comment
Hide comment
@larsiusprime

larsiusprime Jul 31, 2014

Owner

Wow that is super detailed. And in the tiny resolution, too? I guess I need to do some serious profiling and find out if I have some inefficiencies. I'll also try to run my own tests to see if I get similar slowdowns.

Owner

larsiusprime commented Jul 31, 2014

Wow that is super detailed. And in the tiny resolution, too? I guess I need to do some serious profiling and find out if I have some inefficiencies. I'll also try to run my own tests to see if I get similar slowdowns.

@larsiusprime larsiusprime added the 1 label Apr 1, 2015

@larsiusprime larsiusprime added the ready label Dec 22, 2015

@larsiusprime larsiusprime removed the ready label Dec 22, 2015

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment