Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
[Bug Report] .hack//G.U. series [NTSC-U]
#1
[SLUS-21258][SLUS-21488][SLUS-21489]
# PCSX2 version: r5368+
# CPU options: "Safest" preset
# Plugins used: GSdx 5365, 5390 (SSE2, hardware and software, dx9, dx11), SPU2-X r5317, r5384 2.0.0
# Description: Some textures became transparent, some polygons became plain color-filled. Um... Just look at the screenshotsBlush
[Image: gsdx20120823083615.th.jpg][Image: gsdx20120823083520.th.jpg][Image: gsdx20120823083507.th.jpg][Image: gsdx20120823083457.th.jpg][Image: gsdx20120823083429.th.jpg]
* The first screenshot is made with software mode.

It seems like something wrong with emulation, because the bug appears when you start pcsx2.exe of revision higher (or equal) than 5368. No matter what mode (sw, hw) or plugins you use. Running earlier revisions fix this.

If it'll help I post my pretty ancient configuration:
AMD Athlon II X2 250 3.0GHz, 2.0GB RAM, Sapphire ATI Radeon HD5570 (Win7x64)
Reply

Sponsored links

#2
Confirmed this first appears with Ref's Vif optimisation/cleanup

bug logged here
Reply
#3
Ill check it out Smile
[Image: ref_sig_anim.gif]
Like our Facebook Page and visit our Facebook Group!
Reply
#4
* Squall Leonhart wishes he could like forum posts Tongue2
Reply
#5
(08-23-2012, 12:06 AM)RinceWND Wrote: [Image: gsdx20120823083429.th.jpg][/URL]

This screenshot was taken with r5371 (after the proposed bug appeared), presumably the same version/game as you.
I don't see anything wrong here...


Attached Files Thumbnail(s)
   
[Image: ref_sig_anim.gif]
Like our Facebook Page and visit our Facebook Group!
Reply
#6
hmmm.....

oh... crap, i was on an AMD laptop when i reproduced this >.<

keep mistaking my sisters intel laptop with my cousins amd laptop (toshiba used the same casing >.<)

My Main system runs it fine, nahalem just like yours Ref,

AMD setup was a AMD Phenom II X4 N950, so no SSE4/SSSE3 support

maybe your vif changes are tripping on SSE4a or something
Reply
#7
oh dear not another AMD bug... this is more likely to do with the point sampling thing sudo was playing with then...
[Image: ref_sig_anim.gif]
Like our Facebook Page and visit our Facebook Group!
Reply
#8
Tongue2 your vif changes did adjust SSE related thingymijigs, and like the op, i can introduce the issue just by moving from 5367 to 5368
Reply
#9
but only on amd? Blink
[Image: ref_sig_anim.gif]
Like our Facebook Page and visit our Facebook Group!
Reply
#10
only on amd!
Reply




Users browsing this thread: 1 Guest(s)