mirror of
https://github.com/open-goal/jak-project
synced 2026-08-21 23:00:45 -04:00
display loop runs
This commit is contained in:
@@ -0,0 +1,33 @@
|
||||
#include "game/graphics/sceGraphicsInterface.h"
|
||||
#include "common/util/assert.h"
|
||||
#include "game/graphics/gfx.h"
|
||||
|
||||
#include <cstdio>
|
||||
|
||||
/*!
|
||||
* Wait for rendering to complete.
|
||||
* In the PC Port, this currently does nothing.
|
||||
*
|
||||
* From my current understanding, we can get away with this and just sync everything on vsync.
|
||||
* However, there are two calls to this per frame.
|
||||
*
|
||||
* But I don't fully understand why they call sceGsSyncPath where they do (right before depth cue)
|
||||
* so maybe the depth cue looks at the z-buffer of the last rendered frame when setting up the dma
|
||||
* for the next frame? The debug drawing also happens after this.
|
||||
*
|
||||
* The second call is right before swapping buffers/vsync, so that makes sense.
|
||||
*
|
||||
*
|
||||
*/
|
||||
u32 sceGsSyncPath(u32 mode, u32 timeout) {
|
||||
assert(mode == 0 && timeout == 0);
|
||||
return 0;
|
||||
}
|
||||
|
||||
/*!
|
||||
* Actual vsync.
|
||||
*/
|
||||
u32 sceGsSyncV(u32 mode) {
|
||||
assert(mode == 0);
|
||||
return Gfx::vsync();
|
||||
}
|
||||
Reference in New Issue
Block a user