Emulator

Are you sure that's not just the rampant heatwave effect in the game???

JMC4789 wrote:

Are you sure that's not just the rampant heatwave effect in the game???

I'm pretty sure it's an issue with Dolphin because the heatwave effect applies to distant objects. This is very close to the camera. I tested on real hardware just to be absolutely sure and no, the real hardware doesn't have this issue.

I'm standing on the bridge right now and it's not shaking, so, I'm going to need more clear instructions.

JMC4789 wrote:

I'm standing on the bridge right now and it's not shaking, so, I'm going to need more clear instructions.

Try jumping on the cables. There's also cables below the bridge. I jumped on the below cables while the camera was pointing to the bridge. I think the effect is a bit more noticeable there. Try with the very first scenario of Bianco Hills.

I'll look into this more when I get a few moments, hold tight. There are apparently other reports of stuff like this happening, but, through all my playthroughs of the game I've never seen it. Can you try various accuracy settings while you wait for me?

JMC4789 wrote:

I'll look into this more when I get a few moments, hold tight. There are apparently other reports of stuff like this happening, but, through all my playthroughs of the game I've never seen it. Can you try various accuracy settings while you wait for me?

Already did. It seems like enabling the bounding box fixes the issue initially but when I close Dolphin, open Dolphin, make sure to enable bounding box, and then start Super Mario Sunshine, the problem is back.

Are you sure it's not opening the graphics menu (and overriding some setting) that's actually "fixing" it?

JMC4789 wrote:

Are you sure it's not opening the graphics menu (and overriding some setting) that's actually "fixing" it?

Following settings as stated on the Dolphin Wiki.

JMC4789 wrote:

I cannot reproduce the issue. The game does shake a bit when you move the c-stick (bad deadzone?) but, that also happens on console.

Unless you can pin the bug on Dolphin, I'm going to have to close this issue.

I have smooth camera motion that isn't the bridge when using the c-stick or bouncing on the wires as I have said. You said it yourself; there are reports of this behavior before. Can I get a different person if you can't reproduce the issue? I swear the issue is there and it is just a minor cosmetic blemish on an otherwise 4-star rated game for Dolphin compatibility. I can play the game just fine. I can see this being a potential issue for others if it doesn't get fixed; the ones that get motion-sick more easily.

wildgoosespeeder wrote:

Can I get a different person if you can't reproduce the issue?

We are not customer support. This is a game bug that is on console as well.

Issue closed.

Looks like it does this on console here. If you're still unsure, try using FPRF.

JMC4789 wrote:

Looks like it does this on console here. If you're still unsure, try using FPRF.

That doesn't work. I uploaded a demonstration.

Here is what the bridge should be doing (video from 2008 from real hardware):
https://www.youtube.com/watch?v=QZXA_IcF_Uo

I can reproduce this issue, but only at higher internal resolutions. I start seeing it a 3x and it gets worse as I go higher.

Using 4.0-8163
intel i7-3770
GTX 560 Ti
Windows 10

My testing (and likely MaJoR1's knowing how we all use accuracy settings for testing) were on 1x IR.

If Marzipan can only confirm at higher IRs, I'd like to reclose this issue.

Wildgoosespeeder: Can you try this at 1x IR?

JMC4789 wrote:

My testing (and likely MaJoR1's knowing how we all use accuracy settings for testing) were on 1x IR.

If Marzipan can only confirm at higher IRs, I'd like to reclose this issue.

Wildgoosespeeder: Can you try this at 1x IR?

Everything was at default settings and GameINIs overrode settings automatically where necessary. My hardware isn't powerful enough and slows down emulation significantly if I go above 1x native. This bug is quite strange because of its possible inconsistency. I don't know what is causing it.

After further testing I find that I can only reproduce when dolphin is struggling to keep up. Setting higher IR or anti aliasing usually works.

The issue also seemingly goes away if you run in Single Core mode.

JMC4789 wrote:

This is a dualcore desync issue due to your computer not being powerful enough, cool. At least this is solved.

What settings should I manipulate? Should I manipulate disabling dual core mode or should I enable sync GPU thread?

I always prefer using single core mode over syncGPU for testing.

Basically, it seems as though this issue manifests itself when the threads are stressed/desyncing due to one thread falling behind the other. On a faster PC under no lag, it would make sense for it to not happen even in Dualcore. Considering we already know Mario Sunshine is dualcore sensitive... yeah, this all makes sense.

If you can still reproduce it on single core, then I'll be pretty shocked.

JMC4789 wrote:

I always prefer using single core mode over syncGPU for testing.

Basically, it seems as though this issue manifests itself when the threads are stressed/desyncing due to one thread falling behind the other. On a faster PC under no lag, it would make sense for it to not happen even in Dualcore. Considering we already know Mario Sunshine is dualcore sensitive... yeah, this all makes sense.

If you can still reproduce it on single core, then I'll be pretty shocked.

For the Wiki's sake, you flagged this as a duplicate issue. Where is the earliest known bug report of this kind of behavior?

I flagged it as a duplicate because there are billions of dualcore issues in Dolphin. It's the biggest hack in the emulator as far as I'm concerned. Issue 7143 is my master issue for dualcore stuff.

JMC4789 wrote:

I flagged it as a duplicate because there are billions of dualcore issues in Dolphin. It's the biggest hack in the emulator as far as I'm concerned. Issue 7143 is my master issue for dualcore stuff.

Anyways, thanks for the help. I am not experiencing that shaky bridge anymore but at a cost of having the emulation run more slowly for disabling dual core mode or syncing GPU thread. Is there any way to fix the code to not require the setting or is that impossible?