[GH-ISSUE #1283] Jeanne D'Arc - Invisible Dialogue Box and Models (GLES2) #414

New issue

Closed

opened 2026-03-17 12:09:35 +03:00 by kerem · 42 comments

kerem commented 2026-03-17 12:09:35 +03:00

Owner

Copy link

Originally created by @Antonio-Reikashi on GitHub (Apr 14, 2013).
Original GitHub issue: https://github.com/hrydgard/ppsspp/issues/1283

This game has some problems. While the in-game graphics were fixed in the latest builds, it is still impossible to play this game due to invisible dialogue boxes, characters' models, images and menus.
However you guys are amazing. Keep up the good work!!!

Device: iPhone 4S
PPSSPP Build: 7.5-3

Here there are two images that show the issues reported above. :)
In the first one there should be the Jeanne D'Arc logo and the opening menu (New Game, Continue, etc...). The latter is self explaining. :D

Originally created by @Antonio-Reikashi on GitHub (Apr 14, 2013). Original GitHub issue: https://github.com/hrydgard/ppsspp/issues/1283 This game has some problems. While the in-game graphics were fixed in the latest builds, it is still impossible to play this game due to invisible dialogue boxes, characters' models, images and menus. However you guys are amazing. Keep up the good work!!! Device: iPhone 4S PPSSPP Build: 7.5-3 Here there are two images that show the issues reported above. :) In the first one there should be the Jeanne D'Arc logo and the opening menu (New Game, Continue, etc...). The latter is self explaining. :D  

kerem 2026-03-17 12:09:35 +03:00

• closed this issue
• added the
  No Feedback / Outdated?
  Depth / Z
  labels

kerem commented 2026-03-17 12:09:51 +03:00

Author

Owner

Copy link

@sum2012 commented on GitHub (Apr 15, 2013):

The game will black screen when not use real psp font.
ppsspp font Log:
http://www.mediafire.com/?7f492q9xlkjzk1a
Real psp font log:
http://www.mediafire.com/?cwvmyuqm3a01298

<!-- gh-comment-id:16417813 --> @sum2012 commented on GitHub (Apr 15, 2013): The game will black screen when not use real psp font. ppsspp font Log: http://www.mediafire.com/?7f492q9xlkjzk1a Real psp font log: http://www.mediafire.com/?cwvmyuqm3a01298

kerem commented 2026-03-17 12:09:56 +03:00

Author

Owner

Copy link

@Krude commented on GitHub (Apr 23, 2013):

Yep, this issue sure exists.
This is PPSSPP currently, 7.6-48

This is what it SHOULD look like:

I can't comment on crashes when using non-psp fonts, but here's a log of the start screen with the localized version.
http://pastebin.com/iwDSDY8A

<!-- gh-comment-id:16874216 --> @Krude commented on GitHub (Apr 23, 2013): Yep, this issue sure exists. This is PPSSPP currently, 7.6-48  This is what it SHOULD look like:  I can't comment on crashes when using non-psp fonts, but here's a log of the start screen with the localized version. http://pastebin.com/iwDSDY8A

kerem commented 2026-03-17 12:10:01 +03:00

Author

Owner

Copy link

@unknownbrackets commented on GitHub (May 10, 2013):

Frame dump:

https://gist.github.com/unknownbrackets/5553127

By the way, I keep seeing alpha test using ff0107 and such. Probably the ff is a mask on the alpha value? Hopefully games don't use it...

Anyway, I guess this is probably beziers, but not sure...

-[Unknown]

<!-- gh-comment-id:17709980 --> @unknownbrackets commented on GitHub (May 10, 2013): Frame dump: https://gist.github.com/unknownbrackets/5553127 By the way, I keep seeing alpha test using ff0107 and such. Probably the ff is a mask on the alpha value? Hopefully games don't use it... Anyway, I guess this is probably beziers, but not sure... -[Unknown]

kerem commented 2026-03-17 12:10:06 +03:00

Author

Owner

Copy link

@hrydgard commented on GitHub (May 10, 2013):

Yes, I think the mask specifies which bits of alpha to use in the test (that is, the GPU will AND the alpha value with this mask before doing the compare). We can't really emulate that with OpenGL ES 2.0 shaders due to lack of bitwise ops (although we could simulate some bit patterns like 0xF0 with multiplication and rounding and 0x0F with modulo and rounding). You could make it report for non-0xFF values only.

<!-- gh-comment-id:17710343 --> @hrydgard commented on GitHub (May 10, 2013): Yes, I think the mask specifies which bits of alpha to use in the test (that is, the GPU will AND the alpha value with this mask before doing the compare). We can't really emulate that with OpenGL ES 2.0 shaders due to lack of bitwise ops (although we could simulate some bit patterns like 0xF0 with multiplication and rounding and 0x0F with modulo and rounding). You could make it report for non-0xFF values only.

kerem commented 2026-03-17 12:10:11 +03:00

Author

Owner

Copy link

@papel commented on GitHub (Sep 2, 2013):

Thank you, @raven02, the bezier problem is fixed.
However, this problem prevents the game from being playable.
http://forums.ppsspp.org/showthread.php?tid=1237&pid=46534#pid46534

<!-- gh-comment-id:23675071 --> @papel commented on GitHub (Sep 2, 2013): Thank you, @raven02, the bezier problem is fixed. However, this problem prevents the game from being playable. http://forums.ppsspp.org/showthread.php?tid=1237&pid=46534#pid46534

kerem commented 2026-03-17 12:10:16 +03:00

Author

Owner

Copy link

@dbz400 commented on GitHub (Sep 2, 2013):

Yep , it is well-observerd that those characters are missing however we still have no idea how to get around it unfornaturely.

<!-- gh-comment-id:23679007 --> @dbz400 commented on GitHub (Sep 2, 2013): Yep , it is well-observerd that those characters are missing however we still have no idea how to get around it unfornaturely.

kerem commented 2026-03-17 12:10:21 +03:00

Author

Owner

Copy link

@papel commented on GitHub (Sep 3, 2013):

Another bug with invisible characters, https://github.com/hrydgard/ppsspp/issues/1392, it may be related.

<!-- gh-comment-id:23686217 --> @papel commented on GitHub (Sep 3, 2013): Another bug with invisible characters, https://github.com/hrydgard/ppsspp/issues/1392, it may be related.

kerem commented 2026-03-17 12:10:26 +03:00

Author

Owner

Copy link

@dbz400 commented on GitHub (Sep 3, 2013):

That one should be more closely related to final fantasy one which character only shows in non buffered mode

<!-- gh-comment-id:23686511 --> @dbz400 commented on GitHub (Sep 3, 2013): That one should be more closely related to final fantasy one which character only shows in non buffered mode

kerem commented 2026-03-17 12:10:31 +03:00

Author

Owner

Copy link

@dbz400 commented on GitHub (Sep 3, 2013):

I did try to turn off stencil to see if it is hiding the character but it is not ..

<!-- gh-comment-id:23695376 --> @dbz400 commented on GitHub (Sep 3, 2013): I did try to turn off stencil to see if it is hiding the character but it is not ..

kerem commented 2026-03-17 12:10:36 +03:00

Author

Owner

Copy link

@unknownbrackets commented on GitHub (Sep 3, 2013):

I used DEBUG_TEXTURES, and there are a bunch of SetTexture() calls that are not visible. I'm guessing it's trying to draw them, one way or another.

-[Unknown]

<!-- gh-comment-id:23695475 --> @unknownbrackets commented on GitHub (Sep 3, 2013): I used DEBUG_TEXTURES, and there are a bunch of SetTexture() calls that are not visible. I'm guessing it's trying to draw them, one way or another. -[Unknown]

kerem commented 2026-03-17 12:10:42 +03:00

Author

Owner

Copy link

@unknownbrackets commented on GitHub (Sep 12, 2013):

Vertex decoders active while missing models should be visible:

P: 3 T: 3 Verts: 278760  (size: 20) - float UVs, float coords
P: 3 N: 3 T: 3 I: 2 Verts: 127794  (size: 32) - float UVs, float normals, float coords, u16 indexes
P: 3 N: 3 C: 7 T: 3 I: 2 Verts: 768913  (size: 36) - float UVs, ABGR 8888 colors, float normals, float coords, u16 indexes
P: 3 N: 3 T: 3 W: 3 I: 2 Verts: 114736  (size: 36) - float UVs, float normals, float coords, float weights (0), u16 indexes
P: 3 N: 3 T: 3 W: 3 I: 2 Verts: 152712  (size: 40) - float UVs, float normals, float coords, float weights (1), u16 indexes
P: 3 N: 3 T: 3 W: 3 I: 2 Verts: 80093  (size: 44) - float UVs, float normals, float coords, float weights (2), u16 indexes
P: 3 N: 3 T: 3 W: 3 I: 2 Verts: 8181  (size: 48) - float UVs, float normals, float coords, float weights (3), u16 indexes
P: 3 N: 3 T: 3 W: 3 I: 2 Verts: 27472  (size: 52) - float UVs, float normals, float coords, float weights (4), u16 indexes
P: 3 N: 3 T: 3 W: 3 I: 2 Verts: 45955  (size: 56) - float UVs, float normals, float coords, float weights (5), u16 indexes
P: 3 N: 3 T: 3 W: 3 I: 2 Verts: 124331  (size: 60) - float UVs, float normals, float coords, float weights (6), u16 indexes
P: 3 N: 3 T: 3 W: 3 I: 2 Verts: 515807  (size: 64) - float UVs, float normals, float coords, float weights (7), u16 indexes
P: 2 C: 7 Verts: 3232  (through) (size: 12) - through, ABGR 8888 colors, u16 coords

If I make it skip all draws that have a weightcount/weight type, nothing visible changes. The read weight values are all between 0.0 and 1.0, inclusive. They don't appear to be using spline/bezier stuff.

-[Unknown]

<!-- gh-comment-id:24331530 --> @unknownbrackets commented on GitHub (Sep 12, 2013): Vertex decoders active while missing models should be visible: ``` P: 3 T: 3 Verts: 278760 (size: 20) - float UVs, float coords P: 3 N: 3 T: 3 I: 2 Verts: 127794 (size: 32) - float UVs, float normals, float coords, u16 indexes P: 3 N: 3 C: 7 T: 3 I: 2 Verts: 768913 (size: 36) - float UVs, ABGR 8888 colors, float normals, float coords, u16 indexes P: 3 N: 3 T: 3 W: 3 I: 2 Verts: 114736 (size: 36) - float UVs, float normals, float coords, float weights (0), u16 indexes P: 3 N: 3 T: 3 W: 3 I: 2 Verts: 152712 (size: 40) - float UVs, float normals, float coords, float weights (1), u16 indexes P: 3 N: 3 T: 3 W: 3 I: 2 Verts: 80093 (size: 44) - float UVs, float normals, float coords, float weights (2), u16 indexes P: 3 N: 3 T: 3 W: 3 I: 2 Verts: 8181 (size: 48) - float UVs, float normals, float coords, float weights (3), u16 indexes P: 3 N: 3 T: 3 W: 3 I: 2 Verts: 27472 (size: 52) - float UVs, float normals, float coords, float weights (4), u16 indexes P: 3 N: 3 T: 3 W: 3 I: 2 Verts: 45955 (size: 56) - float UVs, float normals, float coords, float weights (5), u16 indexes P: 3 N: 3 T: 3 W: 3 I: 2 Verts: 124331 (size: 60) - float UVs, float normals, float coords, float weights (6), u16 indexes P: 3 N: 3 T: 3 W: 3 I: 2 Verts: 515807 (size: 64) - float UVs, float normals, float coords, float weights (7), u16 indexes P: 2 C: 7 Verts: 3232 (through) (size: 12) - through, ABGR 8888 colors, u16 coords ``` If I make it skip all draws that have a weightcount/weight type, nothing visible changes. The read weight values are all between 0.0 and 1.0, inclusive. They don't appear to be using spline/bezier stuff. -[Unknown]

kerem commented 2026-03-17 12:10:47 +03:00

Author

Owner

Copy link

@unknownbrackets commented on GitHub (Sep 30, 2013):

If I disable depth testing, then I see the models drawn on the white surface (although this causes them to be incorrectly drawn on top of each other.) It still doesn't work, but I see why. Yay.

In a frame:

Primary framebuffer: 0x00044000 (512 stride) 5551
Depthbuffer: 0x00088000 (512 stride)
Clear stencil/depth/color

Model framebuffer: 0x000cc000 (512 stride) 5551
REUSE depthbuffer
Clear stencil/color NOT depth
Draw stuff - expect existing depthbuffer <-- failure

So as far as I can tell, this game REQUIRES shared depthbuffers to work properly.

-[Unknown]

<!-- gh-comment-id:25339732 --> @unknownbrackets commented on GitHub (Sep 30, 2013): If I disable depth testing, then I see the models drawn on the white surface (although this causes them to be incorrectly drawn on top of each other.) It still doesn't work, but I see why. Yay. In a frame: Primary framebuffer: 0x00044000 (512 stride) 5551 Depthbuffer: 0x00088000 (512 stride) Clear stencil/depth/color Model framebuffer: 0x000cc000 (512 stride) 5551 REUSE depthbuffer Clear stencil/color NOT depth Draw stuff - expect existing depthbuffer <-- failure So as far as I can tell, this game REQUIRES shared depthbuffers to work properly. -[Unknown]

kerem commented 2026-03-17 12:10:52 +03:00

Author

Owner

Copy link

@dbz400 commented on GitHub (Oct 14, 2013):

Interesting that skipping GE_COMP_GEQUAL , all characters show up though overlapped somehow.

        if (gstate.getDepthTestFunction() != GE_COMP_GEQUAL)
            glstate.depthFunc.set(ztests[gstate.getDepthTestFunction()]); 

<!-- gh-comment-id:26246343 --> @dbz400 commented on GitHub (Oct 14, 2013): Interesting that skipping GE_COMP_GEQUAL , all characters show up though overlapped somehow. ``` if (gstate.getDepthTestFunction() != GE_COMP_GEQUAL) glstate.depthFunc.set(ztests[gstate.getDepthTestFunction()]); ``` 

kerem commented 2026-03-17 12:10:57 +03:00

Author

Owner

Copy link

@hrydgard commented on GitHub (Oct 14, 2013):

That just seems to turn off depth testing, look how broken they look. However, that clearly points in the direction that this is a depth buffer issue somehow.

<!-- gh-comment-id:26246909 --> @hrydgard commented on GitHub (Oct 14, 2013): That just seems to turn off depth testing, look how broken they look. However, that clearly points in the direction that this is a depth buffer issue somehow.

kerem commented 2026-03-17 12:11:02 +03:00

Author

Owner

Copy link

@hrydgard commented on GitHub (Oct 14, 2013):

There's one annoyance if we are to implement shared depth buffers btw - on most devices, the fastest and sometimes only depth buffer format is D24S8 where you interleave stencil and depth, which locks a specific stencil buffer to a depth buffer, while on the PSP, stencil should really be associated with the color buffer as it overlays alpha.

I guess one could hope that the games that rely on shared stencil buffers might not also do stencil tricks...

<!-- gh-comment-id:26246989 --> @hrydgard commented on GitHub (Oct 14, 2013): There's one annoyance if we are to implement shared depth buffers btw - on most devices, the fastest and sometimes only depth buffer format is D24S8 where you interleave stencil and depth, which locks a specific stencil buffer to a depth buffer, while on the PSP, stencil should really be associated with the color buffer as it overlays alpha. I guess one could hope that the games that rely on shared stencil buffers might not also do stencil tricks...

kerem commented 2026-03-17 12:11:07 +03:00

Author

Owner

Copy link

@dbz400 commented on GitHub (Oct 14, 2013):

I see. I tested few other games that used GE_COMP_LESS or GE_COMP_LEQUAL and they all look fine however except GE_COMP_GEQUAL .Feel strange or may be just concidence

<!-- gh-comment-id:26257256 --> @dbz400 commented on GitHub (Oct 14, 2013): I see. I tested few other games that used GE_COMP_LESS or GE_COMP_LEQUAL and they all look fine however except GE_COMP_GEQUAL .Feel strange or may be just concidence

kerem commented 2026-03-17 12:11:12 +03:00

Author

Owner

Copy link

@unknownbrackets commented on GitHub (Oct 15, 2013):

Yeah, that is annoying.

When creating a buffer, we should also be "within" its first draw. So if clearmode is on and includes depth, it's likely we don't need to share anything ever.

One way or another this'll probably end up being hacky... ugh.

-[Unknown]

<!-- gh-comment-id:26311150 --> @unknownbrackets commented on GitHub (Oct 15, 2013): Yeah, that is annoying. When creating a buffer, we should also be "within" its first draw. So if clearmode is on and includes depth, it's likely we don't need to share anything ever. One way or another this'll probably end up being hacky... ugh. -[Unknown]

kerem commented 2026-03-17 12:11:17 +03:00

Author

Owner

Copy link

@unknownbrackets commented on GitHub (Dec 14, 2013):

Is it possible to just blit the depth when switching if we can detect this accurately enough? Seems like glBlitFramebuffer won't work on gles2, but maybe will on gles3.

-[Unknown]

<!-- gh-comment-id:30564221 --> @unknownbrackets commented on GitHub (Dec 14, 2013): Is it possible to just blit the depth when switching if we can detect this accurately enough? Seems like glBlitFramebuffer won't work on gles2, but maybe will on gles3. -[Unknown]

kerem commented 2026-03-17 12:11:22 +03:00

Author

Owner

Copy link

@hrydgard commented on GitHub (Dec 14, 2013):

Yes, it should be. But sharing depth buffers between FBOs is also possible, so maybe we should try to extend the api in native/gfx_es2/fbo and do that first. We should add a depth buffer cache just like the frame buffer cache, and create FBOs for the combinations that we see. Might be a little complicated.

<!-- gh-comment-id:30564325 --> @hrydgard commented on GitHub (Dec 14, 2013): Yes, it should be. But sharing depth buffers between FBOs is also possible, so maybe we should try to extend the api in native/gfx_es2/fbo and do that first. We should add a depth buffer cache just like the frame buffer cache, and create FBOs for the combinations that we see. Might be a little complicated.

kerem commented 2026-03-17 12:11:27 +03:00

Author

Owner

Copy link

@unknownbrackets commented on GitHub (Dec 14, 2013):

Well, Jeanne d'Arc is also using various stencil INCRs on a 5551 texture when it expects the depth to have been reused (it uses this primarily for the alpha though, so maybe that's okay...)

-[Unknown]

<!-- gh-comment-id:30564466 --> @unknownbrackets commented on GitHub (Dec 14, 2013): Well, Jeanne d'Arc is also using various stencil INCRs on a 5551 texture when it expects the depth to have been reused (it uses this primarily for the alpha though, so maybe that's okay...) -[Unknown]

kerem commented 2026-03-17 12:11:33 +03:00

Author

Owner

Copy link

@hrydgard commented on GitHub (Dec 14, 2013):

Well on the PSP, depth is "independent" of stencil as stencil is in the color buffer as alpha so that shouldn't be any more of an issue than it already is.. well, except that on PC we do use combined 24/8 depth stencil on some gpus...

Anyway, feel free to try glBlitFramebuffer, it is very likely to be available on your PC GPU. If it fixes it on PC but not old mobile devices then so be it for now. For example I will soon add dual source alpha blending which will fix a lot of the alpha problems without multipassing, but it won't work on mobile as no mobile GPU supports that extension.

<!-- gh-comment-id:30564565 --> @hrydgard commented on GitHub (Dec 14, 2013): Well on the PSP, depth is "independent" of stencil as stencil is in the color buffer as alpha so that shouldn't be any more of an issue than it already is.. well, except that on PC we do use combined 24/8 depth stencil on some gpus... Anyway, feel free to try glBlitFramebuffer, it is very likely to be available on your PC GPU. If it fixes it on PC but not old mobile devices then so be it for now. For example I will soon add dual source alpha blending which will fix a lot of the alpha problems without multipassing, but it won't work on mobile as no mobile GPU supports that extension.

kerem commented 2026-03-17 12:11:38 +03:00

Author

Owner

Copy link

@thedax commented on GitHub (Jan 27, 2014):

Should this be closed then? The issue's been worked around/fixed for almost a month. Or are most mobile devices still out of luck, in which case this issue is basically for GLES only?

<!-- gh-comment-id:33341452 --> @thedax commented on GitHub (Jan 27, 2014): Should this be closed then? The issue's been worked around/fixed for almost a month. Or are most mobile devices still out of luck, in which case this issue is basically for GLES only?

kerem commented 2026-03-17 12:11:43 +03:00

Author

Owner

Copy link

@pinguallyj commented on GitHub (Jan 27, 2014):

Its fixed, but game itself has wrong fps
https://github.com/hrydgard/ppsspp/issues/5154

<!-- gh-comment-id:33361078 --> @pinguallyj commented on GitHub (Jan 27, 2014): Its fixed, but game itself has wrong fps https://github.com/hrydgard/ppsspp/issues/5154

kerem commented 2026-03-17 12:11:48 +03:00

Author

Owner

Copy link

@thedax commented on GitHub (Jan 27, 2014):

That has nothing to do with this issue, though.

<!-- gh-comment-id:33361291 --> @thedax commented on GitHub (Jan 27, 2014): That has nothing to do with this issue, though.

kerem commented 2026-03-17 12:11:53 +03:00

Author

Owner

Copy link

@Antonio-Reikashi commented on GitHub (Jan 27, 2014):

This hasn't been fixed on iOS, so I guess on mobile in general. While dialogues are visible, those characters models are still invisible. I'm using the latest revision available (0.9.6-594-g7ed88ce). Is it fixable?

<!-- gh-comment-id:33362196 --> @Antonio-Reikashi commented on GitHub (Jan 27, 2014): This hasn't been fixed on iOS, so I guess on mobile in general. While dialogues are visible, those characters models are still invisible. I'm using the latest revision available (0.9.6-594-g7ed88ce). Is it fixable?

kerem commented 2026-03-17 12:11:58 +03:00

Author

Owner

Copy link

@ppmeis commented on GitHub (Apr 7, 2015):

Tested with latest build. LGTM:

<!-- gh-comment-id:90465660 --> @ppmeis commented on GitHub (Apr 7, 2015): Tested with latest build. LGTM: 

kerem commented 2026-03-17 12:12:03 +03:00

Author

Owner

Copy link

@sum2012 commented on GitHub (Apr 7, 2015):

I remember some people who reported in chinese ppsspp forum that still see invisible because their phone does not support opengl es 3.0

<!-- gh-comment-id:90476745 --> @sum2012 commented on GitHub (Apr 7, 2015): I remember some people who reported in chinese ppsspp forum that still see invisible because their phone does not support opengl es 3.0

kerem commented 2026-03-17 12:12:08 +03:00

Author

Owner

Copy link

@hrydgard commented on GitHub (Apr 7, 2015):

Yup, that's still the case unfortunately. It does work on ES 3.0+.

<!-- gh-comment-id:90514097 --> @hrydgard commented on GitHub (Apr 7, 2015): Yup, that's still the case unfortunately. It does work on ES 3.0+.

kerem commented 2026-03-17 12:12:13 +03:00

Author

Owner

Copy link

@Neikiddo commented on GitHub (Sep 4, 2015):

Just recently redownloaded ppsspp 1.0.1. Loaded up Jeanne D' Arc just fine, before it was the issue with the sprites not showing up in battle (game play moving on their own, they would). Everything is runnign fine now, its great. But after the first battle, after the animated scene with the little prince and it goes back to showing Jeanne with a black background. It crashes right there.

Running:
Dell XPS 15
Windows 10 64 bit
8gb Ram
Intel Core i5 2.50 ghz

I didn't mess with any settings when i downloaded ppsspp, so it all should be defaulted already.

<!-- gh-comment-id:137826326 --> @Neikiddo commented on GitHub (Sep 4, 2015): Just recently redownloaded ppsspp 1.0.1. Loaded up Jeanne D' Arc just fine, before it was the issue with the sprites not showing up in battle (game play moving on their own, they would). Everything is runnign fine now, its great. But after the first battle, after the animated scene with the little prince and it goes back to showing Jeanne with a black background. It crashes right there. Running: Dell XPS 15 Windows 10 64 bit 8gb Ram Intel Core i5 2.50 ghz I didn't mess with any settings when i downloaded ppsspp, so it all should be defaulted already. 

kerem commented 2026-03-17 12:12:18 +03:00

Author

Owner

Copy link

@ofry commented on GitHub (Sep 4, 2015):

Neikiddo, try the latest dev version from http://buildbot.orphis.net/ppsspp/index.php?m=fulllist
Latest version is v1.0.1-865-g825662d now

<!-- gh-comment-id:137843896 --> @ofry commented on GitHub (Sep 4, 2015): Neikiddo, try the latest dev version from http://buildbot.orphis.net/ppsspp/index.php?m=fulllist Latest version is v1.0.1-865-g825662d now

kerem commented 2026-03-17 12:12:24 +03:00

Author

Owner

Copy link

@unknownbrackets commented on GitHub (Sep 4, 2015):

On Windows 10, make sure to update your video card drivers. There have been bugs and issues in them. Windows 10 was just released, and like with all new things, there have been bugs.

-[Unknown]

<!-- gh-comment-id:137874292 --> @unknownbrackets commented on GitHub (Sep 4, 2015): On Windows 10, make sure to update your video card drivers. There have been bugs and issues in them. Windows 10 was just released, and like with all new things, there have been bugs. -[Unknown]

kerem commented 2026-03-17 12:12:29 +03:00

Author

Owner

Copy link

@Neikiddo commented on GitHub (Sep 5, 2015):

I just did both of your guys suggestions (new dev came out today actually), still gettin that same crash.

<!-- gh-comment-id:137989021 --> @Neikiddo commented on GitHub (Sep 5, 2015): I just did both of your guys suggestions (new dev came out today actually), still gettin that same crash.

kerem commented 2026-03-17 12:12:34 +03:00

Author

Owner

Copy link

@Plusman28 commented on GitHub (Nov 21, 2015):

Hey!

I am using a GPD XD, which actually offers GLES 3.0. But there is still that problem with the partielly visible characters. Tested latest official and latest build. Why is that?

<!-- gh-comment-id:158606602 --> @Plusman28 commented on GitHub (Nov 21, 2015): Hey! I am using a GPD XD, which actually offers GLES 3.0. But there is still that problem with the partielly visible characters. Tested latest official and latest build. Why is that?

kerem commented 2026-03-17 12:12:39 +03:00

Author

Owner

Copy link

@hrydgard commented on GitHub (Mar 14, 2018):

@Plusman28 is this still a problem on GPD XD?

<!-- gh-comment-id:372949291 --> @hrydgard commented on GitHub (Mar 14, 2018): @Plusman28 is this still a problem on GPD XD?

kerem commented 2026-03-17 12:12:44 +03:00

Author

Owner

Copy link

@ghost commented on GitHub (Nov 7, 2018):

The issue still happen :'(

<!-- gh-comment-id:436550188 --> @ghost commented on GitHub (Nov 7, 2018): The issue still happen :'(

kerem commented 2026-03-17 12:12:49 +03:00

Author

Owner

Copy link

@hrydgard commented on GitHub (Nov 7, 2018):

So does it look like any of the above screenshots, or can you provide a new one?

<!-- gh-comment-id:436604911 --> @hrydgard commented on GitHub (Nov 7, 2018): So does it look like any of the above screenshots, or can you provide a new one?

kerem commented 2026-03-17 12:12:54 +03:00

Author

Owner

Copy link

@unknownbrackets commented on GitHub (Nov 7, 2018):

Well, it requires depth copying which isn't supported on GLES2. So for a Mali-450, unfortunately it's expected that it would still happen.

It should work properly on GLES3 devices.

-[Unknown]

<!-- gh-comment-id:436656997 --> @unknownbrackets commented on GitHub (Nov 7, 2018): Well, it requires depth copying which isn't supported on GLES2. So for a Mali-450, unfortunately it's expected that it would still happen. It should work properly on GLES3 devices. -[Unknown]

kerem commented 2026-03-17 12:12:59 +03:00

Author

Owner

Copy link

@ghost commented on GitHub (Nov 7, 2018):

@unknownbrackets sad to hear that :'(

<!-- gh-comment-id:436670593 --> @ghost commented on GitHub (Nov 7, 2018): @unknownbrackets sad to hear that :'(

kerem commented 2026-03-17 12:13:04 +03:00

Author

Owner

Copy link

@hrydgard commented on GitHub (Nov 7, 2018):

Oh right. I think we can close this, anyway. It might be possible to hack around the issue by sharing depth buffers, but since stencil and color are tightly coupled that is sure to break many other effects.

<!-- gh-comment-id:436671473 --> @hrydgard commented on GitHub (Nov 7, 2018): Oh right. I think we can close this, anyway. It might be possible to hack around the issue by sharing depth buffers, but since stencil and color are tightly coupled that is sure to break many other effects.

kerem commented 2026-03-17 12:13:09 +03:00

Author

Owner

Copy link

@ghost commented on GitHub (Dec 20, 2018):

GPU: Fix curve breakage due to cull flipping #11674 fixed this even in OGL 2.0?

<!-- gh-comment-id:448866507 --> @ghost commented on GitHub (Dec 20, 2018): GPU: Fix curve breakage due to cull flipping #11674 fixed this even in OGL 2.0?

kerem commented 2026-03-17 12:13:14 +03:00

Author

Owner

Copy link

@hrydgard commented on GitHub (Dec 20, 2018):

No, at least it shouldn't have.

<!-- gh-comment-id:448927368 --> @hrydgard commented on GitHub (Dec 20, 2018): No, at least it shouldn't have.

kerem commented 2026-03-17 12:13:20 +03:00

Author

Owner

Copy link

@ghost commented on GitHub (Dec 20, 2018):

:'(

<!-- gh-comment-id:448942546 --> @ghost commented on GitHub (Dec 20, 2018): :'(

Sign in to join this conversation.

No Branch/Tag specified

Branches Tags

master

dependabot/cargo/Tools/langtool/rustls-webpki-0.103.13

readme-1.20.4

https-linux-poc

more-minor-fixes

adhoc-view

minor-bbox-opt

more-cleanup

readme-fix

more-ui

v1.19.10-beta

adhoc-server-mode

morph-jit-work

add-vsync-event

viewport-rework

separate-portrait-config-work

ui-notification-work

lua-work

http-split-headers

v1.19.5-beta

matrix-opt

rewind-zstd

rework-audio-queues

psn-login-params

v1.19.3-commits

atrac-work

jit-ir-fixes

bump-android-sdk-version

themable-slider-colors

some-bbox-work

sum2012-half-skip

auto-log

more-smart-2d-filtering

ingame-network-ui

reject-icmp

atrac-forward-port

atrac-ctx-2-work

background-raster

defer-ge-cycles

test

parallel-loop-max-threads

ir-work-2

text-draw-refactor-3

avoid-strlen-memblockinfo

hotfixes-1.16.6

merge-drawcalls-same-output

frame-timing-new

lost-device-work

drawengine-reduce-buffer-binds

drawarrays-avoid-rebind

opengl-delayed-readback

minor-readback-refactors

nvda-support

vertex-format-remove-uv-flag

spirv-dumper

neon-opts

remove-hardware-skinning

ridge-racer-more-lens-flare

event-profiler

md5

maintainance_1.13

mali-stencil-test

interpreter-nan-check

sdl-vulkan-work

vfpu-dot-experiments

mipmap-slope

loco2-video-alt-fix

v1.20.3

v1.20.2

v1.20.1

v1.20

v1.19.3

v1.19.2

v1.19.1

v1.19

v1.18.1

v1.18

v1.17.1

v1.17

v1.16.6

v1.16.5

v1.16.4

v1.16.3

v1.16.2

v1.16.1

v1.16

v1.15.4

v1.15.3

v1.15.2

v1.15.1

v1.15

v1.14.4

v1.14.3

v1.14.2

v1.14.1

v1.14

v1.13.1b

v1.13.2

v1.13.1

v1.13

v1.12.3+

v1.12.3

v1.12.2

v1.12.1

v1.12

v1.11.3

v1.11.2

v1.11.1

v1.11

v1.10.3

v1.10.2

v1.10.1

v1.10

v1.9.3-950-g4debff114

v1.9.3-428-g2a0a64e0e

v1.9.4

v1.9.3-338-ga488fe17b

v1.9.3

v1.9.2

v1.9.1

v1.9

v1.8.0-698-g5c8ce9018

v1.8.0-550-gdc4e00f5d

v1.8.0-538-g3b29b13fe

v1.8.0-506-g30d7b7cb5

v1.8.0-477-g4510fb1e7

v1.8.0-409-g06e90a74a

v1.8.0-368-g73f8878c3

v1.8.0-260-gc0d5b4be7

v1.8.0-205-gf932de55b

v1.8.0-203-gb7ec62dae

v1.8.0

v1.7.5

v1.7.4

v1.7.3.1

v1.7.3

v1.7.2

v1.7.1-175-g631bc7840

v1.7.1

v1.7

v1.6.3-644-ga49df7d71

v1.6.3-605-g05b92c62b

v1.6.3-604-g7e6b227b4

v1.6.3-526-gcc7f8d561

v1.6.3-441-g3f79e3e24

v1.6.3

v1.6.2

v1.6.1

v1.6

v1.5.4-1041-ga16a7f0

v1.5.4-924-g65ba116

v1.5.4-492-gacfd919

v1.5.4-468-g2363ca6

v1.5.4-300-ge658e74

v1.5.4-267-g3b1b1bb

v1.5.4-232-gbe2984c

v1.5.4-204-gaa49c6d

v1.5.4-136-g8ac5fbc

v1.5.4

v1.5.3-71-g3ebd810

v1.5.3

v1.5.2

v1.5.1

v1.5

v1.4.2

v1.4.1

v1.4

v1.3

v1.2.2

v1.2.1

v1.2

v1.1.1

v1.1.0

v1.0.1

v1.0

v0.9.9.1

v0.9.9

v0.9.8

v0.9.7.2

v0.9.7.1

v0.9.7

v0.9.6

v0.9.5

v0.9.1

v0.9

v0.8.1

v0.8

v0.7.6

v0.7.5

v0.7

v0.6.1

v0.6

v0.5

v0.4

v0.31

v0.3.1

v0.3

Labels

Clear labels   

Atrac3+

  

Audio

  

CPU emulation

  

D3D11

  

D3D9 (removed)

  

Depth / Z

  

Feature Request

  

Font Atlas

  

GE emulation

  

Guardband / Range Culling

  

HLE/Kernel

  

I/O

  

Input/Controller

  

MP3

  

Multithreading

  

Needs hardware testing

  

Networking/adhoc/infrastructure

  

No Feedback / Outdated?

  

OpenGL

  

PGF / sceFont

  

PSMF / MPEG

  

Platform-specific (Android)

  

Platform-specific (Windows)

  

Platform-specific (iOS)

  

PowerVR GPU

  

SDL2

  

Saving issue

  

User Interface

  

Vulkan

  

arm64jit

  

armjit

  

armv6

  

x86jit

No labels

Atrac3+

Audio

CPU emulation

D3D11

D3D9 (removed)

Depth / Z

Feature Request

Font Atlas

GE emulation

Guardband / Range Culling

HLE/Kernel

I/O

Input/Controller

MP3

Multithreading

Needs hardware testing

Networking/adhoc/infrastructure

No Feedback / Outdated?

OpenGL

PGF / sceFont

PSMF / MPEG

Platform-specific (Android)

Platform-specific (Windows)

Platform-specific (iOS)

PowerVR GPU

SDL2

Saving issue

User Interface

Vulkan

arm64jit

armjit

armv6

x86jit

Milestone

Clear milestone

No items

No milestone

Projects

Clear projects

No items

No project

Assignees

Clear assignees

No assignees

1 participant

Notifications

Subscribe

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/ppsspp#414

No description provided.