-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
GameDB: Add SkipDraw Range to 'Tales of the Abyss' #6269
Conversation
hmm, it would be nicer to use upscaling fixes like align sprite and round sprite etc. do none of those fix it? can you upload a GS dump showing the problem? |
I think the squares/grid effect is unfixable via regular upscaling fixes as of now. Last hurdle to make this game play perfectly. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not a fan of skipdraw since it will break the effects on native resolution, maybe try using tc offsets.
Here is a gs showing the "grid" if anyone wants to play around. Also the way autofixes are set up now (hpo: special) you need to play at 6x specifically to not get ghosting. |
I've tried all of them, including TC offsets like lightningterror suggested |
Use of tc offsets seems to have no notable effect except shifting the grid a little and causing a pixel width line at the top if values above 20 are used - similar to pixel lines that appear when using HPO Normal (Vertex). Testing the SkipDraw range on Native, the only effects it seems to have is misaligning the bloom effects of the window at the title screen and the fan within the factory in Baticul |
The grid looks a bit like the one in the Taiko drum game whose issue was closed as a won’t fix |
Does this only happen in places where the game is trying to make things look blurry/dreamy? |
I think it's a side effect of using HPO Special (Vertex), but doesn't show up in all instances where it causes the blurry/dreamy effect. For example the blurry/dreamy effect happens in Tataroo Valley, but the grid doesn't show up at all. It seems to pop up more near areas with effects in place - like the wind effect with the trees and flags outside Baticul Castle, the moving Windmill in Engave, the waves for Kaizur Port, the snow and waves of Keterburg Bay and the panning and spinning globe effect with the Title Screen |
Turns out I'm wrong. Whatever broke the HPO for the Title Screen also broke it for Tataroo Valley and the skyboxes for the Cutscene where Van trains Luke, and Tear attacks Van for the first time |
Grabbed more gs dumps for known instances of the grid effect within the game. Seems the skybox is now broken for the cutscene where Tear attacks Van after he was done introducing Combat to the player and within Tataroo Valley after being teleported there. All instances are corrected by the above SkipDraw Range, but hopefully by providing these gs dumps a better way can be found to correct this issue |
I'll close this as it isn't a good solution. |
Description of Changes
Adds the SkipDraw range 355, 359 that fixes the grid effect present in the Title Screen, Engave, Kaitzur Naval Port, Baticul Castle, Keterburg Port and possibly other instances within 'Tales of the Abyss'
Rationale behind Changes
A recent commit that corrected an issue within Engave eliminated the need for the extreme SkipDraw range (100, 361) called for on the Wiki, but it also broke HPO on the Title Screen resulting in the return of the grid effect it originally corrected.
This drove me to find a more reasonable range (355, 359) that fixes the same issues, but doesn't come with the flickering, darkening and texture stripping issues that the old range created. It also seems to correct some minor ghosting in the instances that the grid effect would be present in. It does still introduce a visual glitch into the Desert Oasis, but I feel it's an acceptable compromise for what the range corrects - at least until a future commit removes the need for SkipDraw entirely
Before:



After:



Visual bug introduced into Desert Oasis:

Suggested Testing Steps
Test the game to see if all possible instances of the grid effect has been corrected