Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Tales of the Abyss - Widescreen looking squashed
#1
I know these patches are just hacks and it's not official support, but I'm running the hacked version to get rid of ghosting.

But I remember trying this out a few years ago and don't remember it, is my memory wrong and this is just how forced Widescreen is for it? Squashed characters, I mean I saw this video earlier and it looked fine, but that was in Battle...: 

https://www.youtube.com/watch?v=JEhJinzTCNg

To get rid of the missing 1px on the side, I also zoomed in to 103% like someone recommended in the custom GDSx build thread.  Widescreen patch is enabled, the bios for PCSX2 have it set to 16:9 as well.

[Image: 6GGr1pw.jpg]

Just have the ToA hack on, 5x Native res, no speed hacks besides Multi-core.

Thanks for any help, ToZ got me interested in playing the best Tales game again, but I am just testing the waters really. The above video looks sexy and has none of the  1px off-set issues  of the custom GDSX build and still looks good. Hmm.

I looked into it more, at the video and it says Skipdraw 1 fixes the ghosting issue now? I'll try that in abit...so there's no longer a need for the custom GDSX?  - Hmm, nope, It ested that, Skidraw 1 or 2, still has the ghosting / dark issue, but it's fixed with the custom GDSX.  However, turning Skipdraw to 0, in the latest 1.31 builds of PCSX2, the dark issue is gone. There's also no ghosting.

So it seems the ghosting isn't a problem at ALL in the latest builds, no hardware hacks needed for it? Hmm. Oddly enough though, it is blurrier / less detailed than the custom GDSX - I can't select AF with this one. But disabling / enabling 8-bit textures and AF Doesn't seem to have much change on the game...

Now that you can hot swap plugins while playing, I switched between the two. The TOA Specific GDSX is definitely much more detailed. That must be the ghosting, no? But basically it looks to me like a blur filter has been removed. Hmm... enabling Half-Pixel Offset in a non ToA specific GDSX also gains the same non bluriness and I see no downsides. Virtually identical with Half-Pixel Off-set, so is there any reason to use the custom GDSX build anymore?
Core i5 2500K @ 4.5GHZ, 8GB RAM 1866MHZ, AORUS 1080 Ti, 128GB Samsung 830 SSD + 1TB Samsung 850 Evo SSD +  2 1TB HDDs.) Windows 7 64-bit Professional
Reply

Sponsored links

#2
That video was made by me, and at the time of recording the video I did indeed use Skipdraw 1 to get rid of the ghosting. As a side effect I had to increase the brightness due to the screen becoming super dark. (Which unfortunately resulted in yet another side effect where FMVs were SUPER bright, as well as skits).

Later on I found out about KrossX's patch that completely fixes the ghosting without altering anything else, but it was for an ancient version of GSdx. So I added that patch to the most recent 'working' version of GSdx (Which is May 5th 2015, any version after that seems to break the patch). The only side effect for this was that there was a small border of about 1 pixel created on the left and top side of the screen. But in the end it was worth it imo.


I haven't tested it on the latest GSdx whether the ghosting was fixed or not, but I don't think it's been 'perfectly' fixed. There would've been mention of that I'd say..

The main difference with Skipdraw 1 and the actual patched GSdx is that when using Skipdraw 1, you lose out the entire bloom effect in the game, making it less saturated and colorful and clear.

As seen here, this was Sheridan with Skipdraw:

[Image: gsdx_20140627215012.jpg]

And here it is with the patch:

[Image: ToA Gameplay - Ghosting Fixed 001.jpg]



Aaand, as you can also tell, it's not supposed to get 'squashed'. Tongue
Intel Core i5-4670K @ 3.40GHz | 16GB (2x8GB) DDR3-1866 G.SKILL Sniper Series
AMD Radeon R9 280 @ 3 GB | 120GB SSD | Windows 7 Ultimate x64 (SP1)
Reply
#3
Yes, so why is my game squashed, I have the default settings for many.

I did comparisons, yes, the bug is fixed, and you no longer need the fixed GDSX build, the screen does not go dark if you turn Skipdraw off and just use Half-Pixel off-set, it looks identical to the ToA GDSX, so that's cool to me, meaning it got fixed and not mentioned.

I'm running 5x resolution, PS2 bios are set to 16:9, GS window is set to Stretch, I've also tried 16:9, maybe it's that location? I dunno.


Thanks for your work on the GDSX build for ToA, I don't know when, but it appears to be fixed in the 1.31 build I have for PCSX2, using the normal GDSX with Half Pixel, fixes the problem. Since you can hot swap plugins as I said, you can test this yourself if you want.


*** I also just tried switching to "Full" in the PCSX2 Bios versus the 16:9 option, no change.

Here is the default GDSX2 Plugin, AVX, DX11, Half-Pixel Offset

[Image: W9ytmMr.jpg]


See? Looks the same as yours above.
Core i5 2500K @ 4.5GHZ, 8GB RAM 1866MHZ, AORUS 1080 Ti, 128GB Samsung 830 SSD + 1TB Samsung 850 Evo SSD +  2 1TB HDDs.) Windows 7 64-bit Professional
Reply
#4
Just gave it a test whirl. The half-pixel offset hack seems to be improved for ToA, but it's not a 100% fix. The 'bloom' layer is still slightly off the correct place. You can clearly tell this looking at the main menu screen (with the giant window).


(And I have no idea why, but the border is there for me with HP-Offset..)

Offset Hack
[Image: 2015-10-21 00143.png]

Patch
[Image: 2015-10-21 00144.png]


[Engaging Battle]
Offset Hack
[Image: 2015-10-21 00146.png]

Patch
[Image: 2015-10-21 00145.png]


It's a small difference, but it's still there. The offset hack is slightly misaligned to the left.


Aand, I just went to the area you're at:

[Image: 2015-10-21 00147.png]


Which version of the game are you running? If you're running the undub patch, then the CRC will be different, so you'll have to update the WS pnach file to match this new CRC.
Intel Core i5-4670K @ 3.40GHz | 16GB (2x8GB) DDR3-1866 G.SKILL Sniper Series
AMD Radeon R9 280 @ 3 GB | 120GB SSD | Windows 7 Ultimate x64 (SP1)
Reply
#5
Oh ok. Gotcha, yeah I patched the game undubbed, damn, I remember doing that too a few years ago. Haha, I actually don't use PCSX2 as much as I used to when I first started, so these things happen.

The border isn't there for me with off-set. I also just took two screenshots of the main menu(Used GDSX screen capture this time). The first one is with normal GDSX. The second is with your modified GDSX. Looks the same to me...21MB Screenshots though lol, Imgur is having trouble...

I also found the CRC in the PCSX2 log, and renamed the normal Tales of Abyss CRC to it's CRC: 0x045D77E9 (I removed the 0x0, that's correct, right?), so I renamed the pnach that Tales normally uses to that, however...still squished.

Had to convert them to JPG, as you can see, no difference!

http://imgur.com/a/706Vc

Except yours has the border issue.
Core i5 2500K @ 4.5GHZ, 8GB RAM 1866MHZ, AORUS 1080 Ti, 128GB Samsung 830 SSD + 1TB Samsung 850 Evo SSD +  2 1TB HDDs.) Windows 7 64-bit Professional
Reply
#6
Maybe I need an even newer PCSX2 again... this one is 1.3.1-1251.

I'll get the latest one from Buildbot later and test it on that.
Intel Core i5-4670K @ 3.40GHz | 16GB (2x8GB) DDR3-1866 G.SKILL Sniper Series
AMD Radeon R9 280 @ 3 GB | 120GB SSD | Windows 7 Ultimate x64 (SP1)
Reply
#7
My PCSX2 is 1051-1.31

I don't know.

Any idea on why it's not loading the Widescreen pnach?

Ok, I found out why. I  should've kept one of the 0''s, put it at the front. Correctly rendered now.
Core i5 2500K @ 4.5GHZ, 8GB RAM 1866MHZ, AORUS 1080 Ti, 128GB Samsung 830 SSD + 1TB Samsung 850 Evo SSD +  2 1TB HDDs.) Windows 7 64-bit Professional
Reply




Users browsing this thread: 1 Guest(s)