Project

General

Profile

Emulator Issues #7594

Super Mario Sunshine, Buggy Sirena Beach with Save States

Added by jefipnz over 6 years ago. Updated about 1 month ago.

Status:
Accepted
Priority:
Normal
Assignee:
-
% Done:

0%

Operating system:
N/A
Issue type:
Bug
Milestone:
Regression:
No
Relates to usability:
No
Relates to performance:
No
Easy:
No
Relates to maintainability:
No
Regression start:
Fixed in:

Description

Game Name?
Super Mario Sunshine

Game ID?
GMSE01

What's the problem? Describe what went wrong in few words.
When using save states in sirena beach at the speedrun, the goo starts to create strange things.

What did you expect to happen instead?
The goo continue normaly after loading the save.

What steps will reproduce the problem?
1.Go to Sirena Beach (World 5, red pipe in the top of a building)> Scrubbing Sirena Beach(Episode 6).
2.Save State (Shift+F1)
3.Load State (F1)

Dolphin 3.5 and 3.5-367 are old versions of Dolphin that have
known issues and bugs, so don't report issues about them and test the
latest Dolphin version first.
Which versions of Dolphin did you test on?
4.0-2496

Does using an older version of Dolphin solve your issue? If yes, which
versions of Dolphin used to work?
No, in the other side, at version 3.5 after loading the save state the game inutilize the memory card...

What are your PC specifications? (including, but not limited to: Operating
System, CPU and GPU)
OS: Win7 Ultimate x64 SP1, OS Version: 6.1.7601.18409 (Win7 RTM), Processor: Intel Core i3 2100 3.1GHz dual-core, Graphics: Nvidia Geforce 210 1GB(overclocked: Core 692 MHz, Shader 1650 MHz, Memory 700 MHz), 4GB DDR3 RAM

64 or 32 bit Dolphin?
x64

In rare cases, an issue may only appear on a 32-bit version or only on a 64-bit version of Dolphin, so please list which you're using so that we're all using the same type of build.

64 or 32 bit Operating system?
x64

Is there any other relevant information? (e.g. logs, screenshots,
configuration files)
*Clock bugged...
-http://imgur.com/a/iLmzQ/embed

History

#1 Updated by OMEGA345 over 6 years ago

I have tried and noticed something too. the edges of the GOO are jagged and pixled. Enabling EFB Copies to Texture fixes the jagg but the GOO dissapears slowly melting away. If you pause the game while it is melting away, it's still moving till it's all gone. You can even get the Star. Also if you walk where the GOO was, Mario will get shocked even though it's showing not visible.

I attached an image :)

http://imgur.com/OFYdhXd
http://imgur.com/QIyMIrZ

#2 Updated by pauldacheez over 6 years ago

For the goo-related issues, uncheck Scaled EFB Copies and make sure you're using EFB to RAM. IIRC, the former makes the goo edges jaggy.

The savestate issues sound legitimate for once – Dolphin's likely not including certain perfquery-related variables with the savestates.

#3 Updated by OMEGA345 over 6 years ago

Just tried what you said, the goo went smooth but melted away again. However i no longer get shocked.

#4 Updated by pauldacheez over 6 years ago

So you mean it's working as intended? You're not making it completely clear. >_>

#5 Updated by OMEGA345 over 6 years ago

I believe what I'm talking about, is the same issue that is happening in ticket, 6580.
But that "PerformanceQueriesEnable = True" is already there by default, so there is still a bug?

#6 Updated by pauldacheez over 6 years ago

It should be "PerfQueriesEnable = True", but if it's written incorrectly in your .ini, either you're using an outdated version of Dolphin or that's your user .ini, which should be empty aside from random stuff you've set yourself. If it's not automatically completing the level, the shit's working anyway, so no need to worry about that.

Either way, this issue's about savestates fucking with the level. Whatever issues you're having are likely irrelevant, Omega. Try the forums if you need any other help...

#7 Updated by OMEGA345 over 6 years ago

I understand pauldacheez, thanks for your input. :)

#8 Updated by JMC4789 over 6 years ago

Well, it could be that the savestates aren't saving something, which could be fixed. The other possibility is that it can't save something (without a lot of work), which means it can't be fixed.

#9 Updated by JMC4789 about 6 years ago

  • Status changed from New to Questionable

I'm thinking this may become a wontfix for the reasonable future.

#10 Updated by rachelbryk about 6 years ago

  • Status changed from Questionable to Accepted

No it won't.

#11 Updated by JMC4789 about 6 years ago

Okay, that's why I CC'd you, thanks.

#12 Updated by Billiard26 over 1 year ago

Is this issue present in recent revisions after the major VideoCommon cleanups?

#13 Updated by JMC4789 over 1 year ago

Should still happen, we haven't tried to fix it.

#14 Updated by Miksel12 about 1 month ago

I can't reproduce this issue on the latest master. I did multiple saves and loads but nothing weird happend.

Also available in: Atom PDF