Emulator Issues #5342
closed
Muramasa: The Demon Blade Native Res Issue
0%
Description
Breakout from issue 5320.
When using the DX11 and OpenGL backends there is a dark pixel spot that appears in the hot springs map that stays in a fixed screen position. Think of it like a fly on your screen that isn't actually a fly on your screen. This only appears at 1x internal resolution.
I am unsure if the issue shows up in other parts of the game. The hot springs has a heavy fogging effect.
The spot will disappear in DX11 if External Frame Buffer Real is enabled.
In 433, when XFB Real is enabled and upon loading a hot spring save state the spot will be present briefly and then disappear. This disappearing spot will happen at all internal resolutions not just 1x. In 586, the entire screen will flash green with no spot with XFB Real enabled.
XFB Real or any other setting appears to have no affect on the spot in OpenGL.
The issue first appears in OpenGL in version 6960. Version 6954 does not have the issue. Please note that version 7090 is between these two versions in the Dolphin archive. 7090 has the issue FYI.
DX11 was not present in Dolphin at that time. If someone needs me to chase this I would be willing to locate the first version that the DX11 problem shows up in. However, I am guessing it is in the first verson that has the DX11 backend.
Also note that the disappearing dot was observed in version 433 which has the XFB Real issue 5251 which may be causing the "disappearing" part of the issue. If someone needs me to chase versions for the disappearing behavior just let me know.
http://imageshack.us/photo/my-images/406/rsfe7u5.jpg/
Dolphin 64-bit 433, 586, and more
Windows 7 64bit
i7 2600k at 4.6
Intel 320 SSD
16GB RAM
NVIDIA 560ti 285.62
Xi-Fi Titanium
Updated by TanukiTanuki13 over 12 years ago
To add, the flashing green in 586 happens briefly upon loading a save state, after that everything looks fine. It also looks like issue 5251 is not present in 586.
Updated by kostamarino over 12 years ago
Without trying to be an ass, you created an issue for a small dark dot in a certain scene of a certain game? Never mind you created various issues for the same game, most of which are from minor to non existent. It is a good thing to get feedback, but to flood the issue tracker with such stuff i don't know whether it helps or not really (it's like getting from one end to another, from no feedback at all, to so much unnecessary feedback that is practically not useful at all). I won't close it in case some developer wants to spend his time hunting a pixel, nevertheless please refrain from opening another issue in case you heard a clicking noise for a second after playing 70 hours Muramasa.
Emulation is not "perfect", it can only reach a certain point of accuracy, and those emulators that reach an extremely high point of accuracy trade it with an extremely low level of speed, which would make the emulator totally unplayable in this case (that is a necessary trade-off ). The only 100% accurate system to run the game is the Wii itself for which it was made for.
Updated by TanukiTanuki13 over 12 years ago
Sorry, I was not privy to the evaluation criteria for issue reporting. I had not intended to make work more diffucult for anyone here.
I posted the dot issue because in my experience with coding many seemingly unrelated problems are actually caused by the same thing. A smaller issue can be easier to troubleshoot than a more endemic one.
If you feel it is unhelpful, please by all means close it. I will spend my free time doing other, more enjoyable things.
Updated by kostamarino over 12 years ago
"I will spend my free time doing other, more enjoyable things."
Just enjoy the game itself ;-). Anyway you put too much work for a pixel making it too difficult for me to close the issue. And like i said feedback is welcome, just i suppose, put a brake somewhere to keep some balance? Don't treat this kind of thing like a job when it is not...
Updated by Billiard26 almost 12 years ago
- Issue type set to Bug
- Category set to gfx
Updated by Billiard26 almost 12 years ago
- Status changed from New to Questionable
Please provide a game save and instructions to get to the location with this issue.
Updated by Billiard26 almost 12 years ago
Is the issue even present in recent revisions?
Which revision?
Updated by Billiard26 almost 11 years ago
- Status changed from Questionable to Won't fix