GSdx

[xstyla]

I am guessing most people don't get this. How about including actual figures?
As in, show up in the drop down menu as "6x Native (3072x2688)"

it doesn't really work to show the numbers without knowing what the actual native is.

and for the example if I did the math correct it's only 512MB at 4x FSAA.

[taltamir]

it doesn't really work to show the numbers without knowing what the actual native is.

and for the example if I did the math correct it's only 512MB at 4x MSAA.

So? vRAM isn't the biggest issue with such insane resolutions.
Also, did you account for double/triple buffering? (does PCSX2 use double/triple buffering?) And you vRAM to store game assets beyond just the finished image.

[Squall Leonhart]

Both Vram and Vram bandwidth are the limiting factors of high internal resolutions.

4xMSAA can not be compared to internally rendering the image at 4-5-6x the original.

[xstyla]

had to correct. sorry squall. I meant that old FSAA upscaling technique. that's the 512MB for a single frame.

as for the new solution it's only 32MB for a frame 64MB for double 96MB for triple buffering and the computational FXAA algorithm. I don't even know if this is comparable with MSAA. but for that FXAA sampling bandwidth and shader speed is really important.

the rest of the vram is free to use for whatever the plugin caches.

[abdo123]

had to correct. sorry squall. I meant that old FSAA upscaling technique. that's the 512MB for a single frame.

as for the new solution it's only 32MB for a frame 64MB for double 96MB for triple buffering and the computational FXAA algorithm. I don't even know if this is comparable with MSAA. but for that FXAA sampling bandwidth and shader speed is really important.

the rest of the vram is free to use for whatever the plugin caches.

OMG ~512MB for one frame !!!

was there a GPU at the time that capable of running it

[Bositman]

No, its not pirated. I have the D7273511 (US) version.
I have the r4857 version. The problem is random, sometimes i start pcsx2 and i have the shadow bug, but most of the time i have the see thru bug.

So you're using the GSdx that came with that build I guess? Are you using System->Boot CDVD (fast)? Do you also have 'Automatic Gamefixes' checked?

[zpinto]

So you're using the GSdx that came with that build I guess? Are you using System->Boot CDVD (fast)? Do you also have 'Automatic Gamefixes' checked?

I think the problem is solved. I was using Boot CDVD (FULL) and i tried Fast a couple of times and the see through bug was fixed.
So im guessing it was because i was using FULL boot.
Thanks for the help

[taltamir]

I think the problem is solved. I was using Boot CDVD (FULL) and i tried Fast a couple of times and the see through bug was fixed.
So im guessing it was because i was using FULL boot.
Thanks for the help

wait, there are problems in full boot that are avoidable by using fast? I thought fast would carry risks but never imagined full boot would too.

[Bositman]

wait, there are problems in full boot that are avoidable by using fast? I thought fast would carry risks but never imagined full boot would too.

It really shouldn't happen..I just tried it with my copy (which is the exact same, CRC and all) and Full Boot worked just as well as Fast...

[xstyla]

OMG ~512MB for one frame !!!

was there a GPU at the time that capable of running it

I think when FSAA was used for pc games the resolutions were a lil lower so it would have been less than 128MB for already double buffered 4xFSAA. I dunno if a card would have been able to do more than that.