Skip to content
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

Crash Tag Team Racing - All Dark Textures on Pi 3 #11491

Closed
developerrowan opened this issue Oct 26, 2018 · 12 comments
Closed

Crash Tag Team Racing - All Dark Textures on Pi 3 #11491

developerrowan opened this issue Oct 26, 2018 · 12 comments

Comments

@developerrowan
Copy link

What happens?

Textures in-game (meaning, not cutscenes or menus) are all black / dark. Some look fine, such as crash himself, arrows, buttons, and gears, but that is it.

What should happen?

Textures should be visible. According to the PSP compatibility list for RetroPie, PPSSPP supports CTTR on the Pi 3. I am running on the Pi 3, overclocked in fact, using default settings for PPSSPP, no hacks, and yet the textures are not properly visible.

What hardware, operating system, and PPSSPP version? On desktop, GPU matters for graphical issues.

Raspberry Pi 3 Model B+, Retropie 4.4, PPSSPP latest version as of 10/26/2018. GPU is only capable of running OpenGL but again, people have successfully ran the game in the past with no issues.

@LunaMoo
Copy link
Collaborator

LunaMoo commented Oct 26, 2018

If you can test, check which was the last one working/which was first broken, I would suspect v1.6.3-478-gacfd68864 as this is probably another case where vertex range culling will have to be disabled.

@developerrowan
Copy link
Author

I do not know how to test for that unfortunately. How would I disable this vertex range culling thing?

@AkiraJkr
Copy link

You can't really "disable" it, but more like, downgrade to a version before it was implemented.

You can check the full list of builds here. Just pick the one before the vertex range was implemented.

https://buildbot.orphis.net/ppsspp/index.php?m=fulllist

@developerrowan
Copy link
Author

Couldn't I manually just edit the file(s) related to that pull request? Can't really downgrade to any of those versions as I am on Linux and most of those versions dont support Android.

@hrydgard
Copy link
Owner

@rowanaut20 We should detect your GPU and turn it off. If you go to Settings / Tools / System Information, what does it say under "Vendor" and "Vendor (detected)"? Exact quotes or a screenshot should be fine.

@developerrowan
Copy link
Author

Vendor: Broadcom
Vendor (Detected): VENDOR_BROADCOM
Driver Version: VideoCore IV HW

ABI: armeabi

@unknownbrackets
Copy link
Collaborator

Find this line:

features |= GPU_SUPPORTS_VS_RANGE_CULLING;

And comment it out. If that makes it start working, then yeah, VideoCore is not liking the range culling code.

In the GPU extensions list, do you have EXT_clip_cull_distance / GL_EXT_clip_cull_distance?

-[Unknown]

@developerrowan
Copy link
Author

No, that didn't work. In fact, even if I go back to 1.5.4 it still does not work.

@unknownbrackets
Copy link
Collaborator

Ah, maybe this is a duplicate of #5468? It seems like if you set the hack to change the CPU clock, that can cause it to lock up.

-[Unknown]

@developerrowan
Copy link
Author

I did not touch any sort of PSP hacks.

@unknownbrackets
Copy link
Collaborator

Has this changed or improved at all? We have fixed other bugs related to the Pi 3.

-[Unknown]

@unknownbrackets
Copy link
Collaborator

This issue is being closed because it hasn't been updated with feedback.

It's hard to tell when fixes in PPSSPP might fix other games, and sometimes certain settings or cheats may cause bugs that can't be fixed.

If you have more information or can confirm it still happens in the latest git builds, please reply to this issue and it'll be reopened. If you have a new issue with the same game, just create a new issue instead.

-[Unknown]

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

No branches or pull requests

5 participants