Rpcs3: Armored Core: For Answer [BLUS30187] - No collision

[ghost]

The GIF below illustrates the problem with the first few seconds of gameplay, and why you can't progress any further: https://i.imgur.com/Y5LdZPz.gif

RPCS3 Discord's #help channel confirmed the issue is universal and not due to a setting or my specific hardware.

Compatibility Report here: https://forums.rpcs3.net/thread-194303-post-302749.html#pid302749

[ghost]

Sadly there's still no improvement with today's latest stable https://github.com/RPCS3/rpcs3/commit/d4591b15083b8ae8b3429c2616e677c9fc016aab or even the current stage of the big Fixes/Improvement PR https://github.com/RPCS3/rpcs3/pull/5565/commits/2d606c75703d0e56b7dc55657f9a3941119da45c

[ghost]

@kd-11 CPU label? Has something about this bug been discovered? I'd like to hear it if so.

[MSuih]

No. It's just a bug with physics or collision detection, not f.ex. graphics or controller input.

[elad335]

Can you test this with ppu precise interpreter and build https://ci.appveyor.com/project/elad335/rpcs3/builds/23202137?

[ghost]

@elad335 I'm afraid I don't have a compiling environment for RPCS3, I just typically use the AppVeyor artifacts. And looking at the dependencies, setting up a compiling environment would take quite a lot of work.

[Asinin3]

Pretty sure elad just wants you to use that build he linked. Click on the artifacts button and you can download the binary directly already compiled from appveyor.

[ghost]

@Asinin3 There are no binaries compiled from appveyor on what @elad335 linked.

..or at least there weren't 10 minutes ago.

[RainbowCookie32]

Yes, right there on artifacts https://ci.appveyor.com/api/buildjobs/ypn9hx4ohb2vya5u/artifacts/rpcs3-v0.0.5-7888-62507cd3_win64.7z

[ghost]

I swear on my mother that it said the compilation had failed and there were 0 artifacts listed 12 minutes ago.

[Asinin3]

is that why it says it finished building over 2 hours ago :D anyway, let's not spam this. Just test it and see if it's fixed

Edit: your latest post screenshot is from a different commit, which was a build elad linked 3 hours ago then changed his post. But you did say 10 minutes :stuck_out_tongue_winking_eye:

[ghost]

Oh thank goodness, I had the tab still open. Look @Asinin3

[RainbowCookie32]

Doesn't matter, just test as elad asked you and stop flooding the issue with those messages. Everyone involved gets a notification on each new message

[ghost]

@RainbowCookie32 I'm not going to apologize when my competency was being called into question. That makes my testing look unreliable. And I found proof, so it's pretty much settled now anyway.

As for the testing, I'm afraid there was no change. Still falling through the floor, same as before. Here's the log: https://cdn.discordapp.com/attachments/463890612559806496/557700096834273290/RPCS3.log.gz

[Asinin3]

Can be closed.