Skip to content
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

Armored Core 2: Floating/misplaced shadows #2400

Closed
Helium-4 opened this issue Apr 21, 2018 · 12 comments
Closed

Armored Core 2: Floating/misplaced shadows #2400

Helium-4 opened this issue Apr 21, 2018 · 12 comments
Labels
Replicated on Real HW Same behaviour on real hardware

Comments

@Helium-4
Copy link

Helium-4 commented Apr 21, 2018

PCSX2 version:
v1.5.0-dev-2334-gefc1274b2

PCSX2 options:
Default

Plugins used:
Default

Description of the issue:
Shadows often are misplaced or appear wrong, especially when moving near some pieces of geometry, in a few area they even float above you, standing directly below a piece of geometry can sometimes lead to your shadow being projected above you instead of below you.
gsdx_20180421145614
gsdx_20180421151206
Armored Core 2 floating shadows.zip
Armored Core 2 vertical shadows.zip

This problem also partially affects the other Armored Core games (up to Silent Line at-the very least) but in a much lesser way.

How to reproduce the issue:
1.Start a new game
2.Go near geometry and run against it, functional doors especially

Last known version to work:
None

PC specifications:
Intel i7 4770K
Nvidia GTX 1070 (390.77)
Windows 7.

EDIT: Still present and completely unchanged in v1.7.0-dev-332-g271bec0f1

@MrCK1
Copy link
Member

MrCK1 commented Apr 21, 2018

Does this happen in both HW and SW renderer? It could just be how the game handles shadows, there's always edge cases where they won't cast on the correct plane 😛

@Helium-4
Copy link
Author

It does happen in both renderer, but the first issue does not happen on real hardware (I pretty much checked everything I submitted against a real hardware play through I did alongside.), the second one I'm not 100% positive because it only triggers that badly in one specific case and I forgot to retest it exactly in the same conditions before putting my PS2 back in storage.

@MrCK1
Copy link
Member

MrCK1 commented Oct 30, 2020

@Helium-4 is this still an issue in current master?

@Helium-4
Copy link
Author

Yes

@refractionpcsx2
Copy link
Member

refractionpcsx2 commented Oct 31, 2020

Can you provide a savestate using the latest master please? Also make sure your pad plugin is lilypad, else I'm gonna have problems :P

@refractionpcsx2
Copy link
Member

Thanks for the savestates :) I checked some stuff out, it isn't what I was hoping it was so I'm kinda stumped :( Hopefully we can find out what it is at some point. No settings seem to affect it either.

@Mrlinkwii
Copy link
Contributor

how is this on latest nightly?

@Berylskid
Copy link
Contributor

Tested the scene of first pic on v1.7.4338, it looks still same as well.
Here are my GS dumps and Savestate:

@AmyRoxwell
Copy link

Is this still a thing on the latest nightly + could anyone post pictures straight from ps2 for comparison sake? Not a single person on this thread posted how this is suppose to look correctly lol

@wxvu
Copy link

wxvu commented Apr 6, 2024

Replicated on real hardware. Not an emulation issue.
Screenshot 2024-04-06 17-07-48
Screenshot 2024-04-06 17-00-37

@F0bes F0bes added Replicated on Real HW Same behaviour on real hardware and removed Bug - Unknown Source labels Apr 6, 2024
@F0bes
Copy link
Member

F0bes commented Apr 6, 2024

Replicated on real hardware. Not an emulation issue. Screenshot 2024-04-06 17-07-48 Screenshot 2024-04-06 17-00-37

Thank you!

@F0bes F0bes closed this as completed Apr 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Replicated on Real HW Same behaviour on real hardware
Projects
None yet
Development

No branches or pull requests

8 participants