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
Regressions caused by zcull implementation (#3135) #3165
Comments
Well, this is new: |
After this PR games have a hell of a slowdown before to render ingame graphics, like something being cached, when it stops fps going back to normal, but the games like Condemned 2 caching smth every second and slowdowns don't stop, what could it be? |
Another regression in game Saw II, some parts of the game are blacked out |
The vertex rewrite builds have hitching due to increased time used to generate graphics pipelines. If the issue is actually present in naster that would be great actually since it makes deployment much easier once fixed. |
Actually after looking at the commit you identified, looks like a trivial fix for saw which is a relief. Any other games misbehaving this way? |
@kd-11 look's like stuttering is actually in the master now searching the commit which is after this, will give info is a few minutes |
Sorry about the wrong info, there are no stutters in master, they caused by some of early commits after master ones |
Its ok. Can I get a trace of before and after the commit that ruined saw II? |
If you mean the log |
Please check if #3168 fixes the issues |
[ Saw 2 ] |
still look like this with #3168 i dont know how to use renderdoc |
@money123451 RDR works perfectly for me although I now suspect a driver issue. It all comes down to how reliable the driver is at generating occlusion reports without notice. |
@kd-11 |
Yes. I have however pushed another commit to be a little more strict with how things work now since I did not initialize the pipeline with defaults anyway. Saw is very broken on master I'm surprised it even works. Vertex rewrite solves most of those issues, but thats a different problem. |
same on 5e12f9c |
Are these two games the only ones affected? |
Looks like RDR also regressed again. I'll keep checking but I dont think the commit listed is the one that breaks visuals. I suspect its zcull itself. It may also affect the skate game if it uses zcull to decide where the sun is visible like demons souls |
Can you check the log for |
the log is spammed with |
@SakataGintokiYT Does that message also appear in SAW? |
@kd-11 |
I pushed another commit. Not sure if it does anything for saw since that rdc is blank for some reason. Its probably just a renderdoc bug though |
it seems like build 0.0.3-870 commit c4ee280 fixed lots of the issues in RDR with opengl still has a few things pop out that should be loaded in but a step in the right direction. 👍 |
Thats a persistent image from the previous frame. Checking actual draws shows no output but the result is already there for some reason. Clear before pass also doesnt work so I cant actually tell which parts of the command stream actually affect output. Also, index buffers are not properly scoped so during playback renderdoc ends up with out-of-range access errors (You can check mesh output - its missing/empty on most passes) |
no changes with latest commit for skate 3 and tony hawk |
Ok, so after taking a deeper look there are several minor bugs introduced by the restructuring. Will update soon |
Should be fixed now |
tony hawk's project 8 fixed. skate 3 still the problem occur |
The problem was always there in skate 3. Its a known issue |
Confirm last commit fixed saw ii, thanks, don't have regressions in my other games |
@Luffykun007 its not related to this topic and you use vulcan, zcull is opengl only atm |
Right understood! |
yap that is why I have been testing with opengl here even if I have a RX 480 I didn't want to ignore the regression that might make its way into vulkan. |
@SakataGintokiYT The TVs in the screenshot you posted are white, is that a regression? |
@Asinin3 Nope |
I have found a regression with zcull in Ni No Kuni: zcull ( RPCS3 v0.0.3-8-7ae1117 ) - latest master Restarting fixes the above issue with weird textures however the clipping and pop-in issues remain. I can confirm that all of those issues do not appear in the master without zcull after extensive testing. @SakataGintokiYT Yeah, I know but I noticed that the TVs went white and thought maybe it was a regression you didn't notice. |
Should be fixed in vertex_rewrite. Its a bug in the game itself that we did not check for. |
It's still not fixed in latest vertex_rewrite: https://ci.appveyor.com/project/kd-11/rpcs3/build/0.0.3-891 |
It seems to be triggered by the re-enabling of depth clamping if its only on openGL. Another issue already tracks the issue so I'll close this one since the other issues are fixed. |
@kd-11 While I don't get the pop-in or clipping issue in Vulkan I can't say whether or not the black/white/invisible texture bug exists or not because the game crashes so quickly for me with vulkan that I don't have enough time to attempt to reproduce it. However I haven't hear of anyone else having that issue with Vulkan yet. Edit: Are you saying that the depth clamping is causing all of the issues or just the bug with the textures? It may not have been obvious with my earlier post but the clipping and pop-in issue still exists in the latest vertex_rewrite builds. |
Ni no kuni issue is tracked separately. Closing this. |
This ticket is here to track any regressions introduced by #3135
The text was updated successfully, but these errors were encountered: