.dot hack / Infection missing geometry.
#1
The game runs and sounds great. Amazing how in only 6 months, a game has gone from non-playable, to pretty much perfect. Good job.

Though occasionally, when I turn the screen, or during a cut-scene, some geometry goes missing. Sometimes it's just the floor, other times I can notice reflection maps missing(Which makes see-through walls)

I'm using the latest PCSX2 build, latest GSDX, and latest ZerSPU2.

using 1.5x Cycle rate, INTC Sync hack, IOP x2, Idle-Fast forward, status flag hack, and level 1 VU Cycle stealing.

both MicroVU's enabled, or else the old TLBhack error presents itself. Flush to Zero / DaZ, Clamp is Normal.

GSdx default settings save for Internal resolution are on.

Thank you.
|| Core i7 8700K @ 5.0GHZ || Gigabyte AUROS 1080 Ti 11GB @ 2050MHZ/12GHZ Memory || 32GB DDR4 @ 3000MHZ || 1TB Samsung Evo 850 SSD + 128GB 830 SSD || 4TB HDD + 1TB HDD || Windows 10 64-bit Professional || EVGA G3 850w PSU || MB: Z370 AORUS Gaming 5 ||
Reply

Sponsored links

#2
I've noticed that the floor occasionally drops out and I think it's the status flag hack. You should tun most if not all of those hacks off though. .hack infection isn't a terribly demanding game.
Reply
#3
I tried turning off the Status flag hack, and the other hacks one by one to try and troubleshoot the problem. No avail.
|| Core i7 8700K @ 5.0GHZ || Gigabyte AUROS 1080 Ti 11GB @ 2050MHZ/12GHZ Memory || 32GB DDR4 @ 3000MHZ || 1TB Samsung Evo 850 SSD + 128GB 830 SSD || 4TB HDD + 1TB HDD || Windows 10 64-bit Professional || EVGA G3 850w PSU || MB: Z370 AORUS Gaming 5 ||
Reply
#4
Hmm I noticed less drop out without the status flag but maybe it was just the slight build differences. I haven't run .hack infection with the latest build today.
Reply
#5
Ah, well then, I guess nothing I can really do about it. It doesn't effect much, just makes some scenes look rather odd...

Thank you for your help though.
|| Core i7 8700K @ 5.0GHZ || Gigabyte AUROS 1080 Ti 11GB @ 2050MHZ/12GHZ Memory || 32GB DDR4 @ 3000MHZ || 1TB Samsung Evo 850 SSD + 128GB 830 SSD || 4TB HDD + 1TB HDD || Windows 10 64-bit Professional || EVGA G3 850w PSU || MB: Z370 AORUS Gaming 5 ||
Reply
#6
If you grab the latest SVN revision and compile PCSX2 yourself,there have been some really good improvements on the microVU clamping,so now setting clamp to normal in r1601 should eliminate all these problems you describe.
[Image: newsig.jpg]
Reply
#7
I was using 1592, I just tried r1601 and the problems still remain. Thank you, though.

Console does say "GSdx: m_merge is NULL!"

EDIT: I disabled the "Staus Flag Hack" and it appears to be good now...

It's weird, it must be the new revision as you said, and with the hack disabled, it appears perfectly, though the console message is still there.

Though I am noticing other, weird graphic errors now, like shadows appearing a few feet away from the character. Hmm...and it just appears some of the Geometry doesn't bug now. Still, it's better than before. Thanks again.
|| Core i7 8700K @ 5.0GHZ || Gigabyte AUROS 1080 Ti 11GB @ 2050MHZ/12GHZ Memory || 32GB DDR4 @ 3000MHZ || 1TB Samsung Evo 850 SSD + 128GB 830 SSD || 4TB HDD + 1TB HDD || Windows 10 64-bit Professional || EVGA G3 850w PSU || MB: Z370 AORUS Gaming 5 ||
Reply
#8
Try disabling MicroVU1 while leaving MicroVU0 turned on. That solved every one of my graphic issues in 1474-1580 (haven't tried any newer revisions lately)
Reply
#9
Are you using the MSAA in the ini. I noticed for Persona4 using MSAA causes bugs with shadows
Reply
#10
No, no MSAA. It's pretty much perfect with what I did now, except for the occasional weird graphic glitch. Koji, doing that causes it to get the TLB error for me.
|| Core i7 8700K @ 5.0GHZ || Gigabyte AUROS 1080 Ti 11GB @ 2050MHZ/12GHZ Memory || 32GB DDR4 @ 3000MHZ || 1TB Samsung Evo 850 SSD + 128GB 830 SSD || 4TB HDD + 1TB HDD || Windows 10 64-bit Professional || EVGA G3 850w PSU || MB: Z370 AORUS Gaming 5 ||
Reply




Users browsing this thread: 1 Guest(s)