[Wii] The Last Story

[Garteal]

This isn't the thread to discuss Ishiiruka stuff. Keep that stuff in its own thread.

[Kamikaze_Ice]

I'm posting to share my experience with the game thus far.
I use Ishiiruka ('cause texture scaling modes, more post-processing shaders and scaling shaders).
HOWEVER!
All of my testing for this post was done in the latest Master, Build 4.0-9237.  
I'm mentioning Ishiiruka because I don't follow Master changes and have no clue about what has been fixed, or to be fixed, regressed, broken or other changes to emulator behavior.

There might be an issue with a portion of the games' framebuffer effects. But this is only visible in Ishiiruka with Barrel shader and post-processing trigger="EFB Copy", which makes THIS FRAME visible (upper left corner). I don't know what belongs in the frame, but if you idle for a while (no touchy touch controller) the frame will go away for a few seconds and come back. I have no clue how to test this for Master, which is why I said this might be an issue and decided to cross post this.
If anyone wants to poke around, here's a FIFO RECORDING. I did my best to narrow down which frame this happens in. As for object, I think it's between objects 761 and 926. Hard to be more accurate when that part of the screen is black.


--

Settings:
Master Build = 4.0-9237
Audio = HLE (Xaudio2)
Dual Core = TRUE
Idle Skipping = TRUE
CPU = JIT Recompiler
3x Internal Resolution (1920x1080)
2xMSAA (not important)
16xAF (also not important)
Post-processing = Off
Scaled EFB Copy = TRUE
EFB Access from CPU = FALSE
Ignore Format Changes = TRUE
EFB Copies to Texture Only = FALS
Texture Cache = Normal (Middle. Not "Safe" or "Fast")       *is changing this from Fast, the default, to Normal required?
External Frame Buffer (XFB) = FALSE
Fast Depth = TRUE & FALSE (see below)
Bounding Box = FALSE
Progressive scan = TRUE
No custom textures.
No Dolphin Overclocking
No changes to game-specific properties (<gameid>.ini)



---

DirectX 11 *Can't use DX12 yet*

(03-12-2015, 03:55 PM)Blaze Wrote: D3d mode with 'Fast Depth Calculation' enabled seems to cause clipping issues in parts of the menus. At least on rev5738.

(09-25-2015, 06:58 AM)Bryson Wrote: Here you go. I believe I tried an earlier build ( 4.0-7528 ) and it had the same problem as the most recent one.

You'll notice the garbled letters where it says "equipment". This happens in both ISH and Master builds even using safe in the texture accuracy slider

Confirming, this issue is still present. Does not happen in OpenGL.
Fast Depth = TRUE -vs- Fast Depth = FALSE. As you can see, toggling Fast Depth fixes (or hides) the issue.
From what I've seen of this "corruption", it only effects alpha portions of textures, and only those without a seperate texture masking file.

---

OpenGL & Depth of Field
I don't know how the blur looks on a wii, and I'm to lazy to dig it out of storage to test , so keep this in mind.

After starting the game with OpenGL backend, we are greeted by a broken Depth of Field everywhere (broken, as in visible "banding" artifacts. I think it's related to that "frame" you can see with Ishiiruka and Barrel)
I have found two options to "fix" the blur. I say "Fix" because again I don't know how the blur should look on real hardware. If you do know how it should look, can you tell me how my screenshots compare to the real hardware?

I) Set Fast Depth = TRUE Fast Depth TRUE -vs- FALSE     *Fast Depth remains off*
II) Close the game (not emulator) and restart the game. Initial Run -vs- 2nd run     *Fast Depth can be on or off*

Can anyone explain option II? Why does Restarting the game (NOT restarting Dolphin/Ishiiruka) fix the blur? Or to put another way, why does the blur only work when this game is the first game loaded after starting the emulator (and only work once per emulator session, not game session). Is this related to the "normal" texture cache setting?

---

While grabbing screenshots in Master used above, THIS happened.
I wasn't paying much attention, since this happened while closing Dolphin, but there was A LOT of those dialog/crash boxes (they just kept duplicating for a few minutes and killed my ears with my custom error beep sound).
What I do remember is that I had the game running in the background (didn't stop emulation, just right-click task bar and close). I think the graphics options window was still up.
I'll try to see if I can reproduce when I get more free time or find a windows log/dump somewhere. If I wasn't trying to close the program I would have made more mental notes.


Another issue I have is sometimes only THIS SHIRT (In-game as "Body Trim") gets loaded wrong or doesn't want to load and what we see is a "fallback" image. It's a completely different color than shown and is ultra low quality (~26-30 pixels tall).
I've only seen this happen to Zael's shirt. I can just change the color and it goes back to the correct quality and color of the texture.




*Almost an Edit*
Since I'll probbably run across more things as I play the game, where should I be reporting issues? This thread? Bug Tracker (didn't see an "add" option anywhere), Github?
If this thread is fine, then I'll just use any game's thread in the future for their issues as I see them.

Just wanting to share my experiences to make this a better place

[JosJuice]

(04-26-2016, 09:50 AM)Kamikaze_Ice Wrote: Since I'll probbably run across more things as I play the game, where should I be reporting issues? This thread? Bug Tracker (didn't see an "add" option anywhere), Github?
If this thread is fine, then I'll just use any game's thread in the future for their issues as I see them.

If you're sure it's a bug in Dolphin, reporting it on the bug tracker is fine. Reporting things in forum threads is fine in pretty much all cases. Do not report issues on GitHub unless the issue is specific to an unmerged PR.

[Kamikaze_Ice]

Thanks JosJuice. I think I'll stick to game threads unless it is something totally broken, like a regression or otherwise changing the state of playability of the game from the the general tone as presented in the wiki (so far that's not this game, my nitpicking aside.)
[i]OT: Is that a Dolphin on the bounce house? At least it's not Pikachu or that children's slide.


To add to my previous post, I noticed another potential emulation issue, but it's easily visible if you have high resolution typeface textures.
http://i.imgur.com/YRDQiS8.png
The grey outline is made by the game. Does not matter the resolution of the actual text texture either.
I don't know if it's an actual broken effect or something that's not being emulated properly.
How I think is happening the border is made by a framebuffer effect of sorts that samples the text in one rendering pass and then begins offsetting each pixel a set distance in all 8 directions (90° and 45°). Because the offset is greater than 1 pixel, this causes "gaps" as seen in my screenshot.
So is this a game issue or emulation issue? I'm trying to use the original typefaces when possible, but this issue may cause me to alter the text to work around this issue.0

[jinkudo]

Hi,
I use version 830 x64 to play The last story game and the game plays very well but i have a problem, i can't save the game, everytime i save the message "Save Failed" is displayed, so can anyone help me please.
Thanks

[Garteal]

Please don't cross-post. And seeing as you're using an Ishiiruka build, your question should be posted in its thread (which you already did by now).

Have you tried using an official build?

[SolankiDS064]

Dolphin Emulator Can Run Wii U Games ?

[JosJuice]

(11-16-2016, 04:05 AM)SolankiDS064 Wrote: Dolphin Emulator Can Run Wii U Games ?

No.

[ev_brak]

I'm getting a doubling/blur effect as seen in the picture linked below. Anyone have any ideas on what is causing it? I have used many builds (4.0's, 5.0's, Newest Ishiiruka) and Backends (D3D11,12,OpenGL,Vulkan) with many settings on/off, but I can't seem to get rid of it. It is especially apparent in the menu's as shown, but does show up in other places in the game.
http://oi64.tinypic.com/5yhgf6.jpg

[elsword]

missing textures still can't be fix permanently ?