-
Notifications
You must be signed in to change notification settings - Fork 2.2k
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
Outrun 2006: Various tracks have graphical issues (black/missing geometry) #5507
Comments
If you'd like me to capture videos or GE debugger info for any of these tracks, let me know which and I'll try my best to accomodate. |
Do these issues also occur in the software renderer? -[Unknown] |
That looks like a possible clipping bug to me (in the sw renderer), although could also be some overflow in the triangle rasterizer I guess. |
In regards to the black skies, here is an info dump from all of the tabs as it renders the black sky, on the Palm Beach track (assuming I captured it at the right time..): I captured it when it looked like this: The other choice is to capture it like this, which is just before the big black rectangle (should I grab the info here, too?): |
Most of the issues in this ticket are now fixed; all that's left is the black/missing geometry, and those stages where the polygons obscure the screen. |
Ah, good to have the skies fixed. Those bizarro polygons are worrying me though. It's obviously drawing bogus geometry, the question is where it came from, and if that geometry would actually render on the real PSP. It could actually be a bug in the game that went unnoticed since the triangle clipper on the PSP is quite limited and might just throw them away or something. |
Think it might help if I grab some GE debugger screens of when the weird polygons come up? |
Hard to say, maybe there's something obviously broken visible. Perhaps NaNs in morph weights or something similarly obscure, like the fog stuff... |
There are only a couple issues remaining here:
Here's a Youtube video demonstrating the warped polygon problem (happens closer to the end of the video, so skip in to around the 45-50 second mark if you don't want to watch the entire thing): https://www.youtube.com/watch?v=pElWBqRaRV4 Other than that the rest of them appear to be fixed. |
Has any of this improved recently? I wonder if it's using beziers or etc. -[Unknown] |
I don't think Outrun uses beziers - it's a port, so not that likely. I think those are a case of bogus geometry due to some bug that wasn't noticed because the vertices ended up outside the 4096x4096 coordinate box, and the triangles got discarded. |
Hmm, in #2159 we have a bug because we /aren't/ discarding things outside the 4096x4096 box. Maybe it's the same here, then? -[Unknown] |
@unknownbrackets, all of the remaining issues (e.g. wild polygons and the missing geometry/water) with the three tracks: Cloudy Highland, Cape Way, and Imperial Avenue still exist. However, they all have skies now and are looking better than I remember them looking a year ago. |
Also worth mentioning is that Vulkan suffers from the same issues, so it's common to all three video backends. |
Just a quick update to this, with the latest commit of PPSSPP ( 562c5f6 ): along with #9527 applied locally, the issues on Cloudy Highland, Cape Way, and Imperial Avenue no longer have the glitched polygons. Each backend has other problems, though (except Vulkan):
|
Are those additional issues gone without #9527 merged, or are they issues either way? If the software renderer works (it's probably too slow to conclusively tell on all those tracks...), then it probably means the guardband approach in software (which is different from #9527) is a good way to go. The approach is at the same time simpler and more complicated, but I think it may actually be how the hardware really does it. -[Unknown] |
From what I saw in testing, the issues exhibited by OpenGL, D3D9 and D3D11 were happening only with #9527 applied. I can give the software renderer a try, but it'll take some time since I highly doubt it'll be very fast, haha. |
Here's what I found with software rendering, with #9527 not applied (not that it should affect this anyhow, but I'm just keeping the build clean): The software renderer has other graphical issues with the game, but the main issue at hand doesn't seem to be present. Off-topic: it actually wasn't that slow to be honest. I was getting around 17%-25% speed on these tracks, so while it took a significant amount of time, it wasn't unbearable. |
I expect this to work now - on all backends - now that #11393 is merged. How's it look? -[Unknown] |
Vulkan and Direct3D11: No issues. Glitched polygons are gone, and all UI elements are present. NB: The below information and screenshot are unrelated to the information above. |
In the interest of posting more info, here are two framedumps from OGL: |
This is 100% fixed on d3d9/opengl now, but the minor issue of water reflections on the Imperial Highway remains. I'll make a new issue about it when I get around to it (super low priority, lol). |
As a continuation of #2603, it makes more sense to begin parsing out the game's remaining separate issues into their own issues instead of one mega issue for everything wrong.
In this issue's instance, the title explains it all.
The sky is black/missing on most stages, orthere is missing geometry/the geometry is black.Like the car colour issue, I need to investigate if it's always been this way.
Affected courses:
* Palm Beach: missing sky* Deep Lake: black/missing geometry in some areas, flickering on the screen, might need a video to explain it* Alpine: missing sky* Castle Wall: entire stage is black* Coniferous Forest: entire stage is black* Industrial Complex: missing sky* Snow Mountain: missing sky* Tulip Garden: missing sky* Metropolis: missing sky* Ancient Ruins: missing skymissing sky, sometimes geometry/glitched polygons come up on the screen, covering it nearly completelymissing sky, sometimes geometry/glitched polygons come up on the screen, covering it in some areasHere's a sample screenshot of what I mean by "polygons come up on the screen":
The text was updated successfully, but these errors were encountered: