App closing right after intro in ttyd on sd835 note 8

[toastedgoast]

Hello I was wondering if anyone has had any luck playing paper Mario ttyd on a Note 8 sd835 on any of the recent dolphin builds. I am encountering a crash at the transition following the point in the intro where ramio and Luigi read peach's letter and the screen transitions to the ocean and once a button is pressed the boat moves to the right off screen and the screen fades to white. At this moment the screen will stay white and dolphin will close, sometimes just closing the game and sometimes closing the entire app.
I have tried both the most recent builds (5.0-6402/6400) as well as several builds from between 1 and 3 months ago. I cannot find one that will get past this instance on this device.

I have been able to run several other games with varying degrees of success. Has anyone else seen this error on this device or other devices and if so how if at all were you able to resolve it? I have tried adding the prefer stencil implementation code for bounding box in the gfx.ini folder but I'm not certain that this crash is related to that feature in the first place, as this did not resolve the issue. Thanks to anyone that can respond. Is there a setting that I should make sure to implement while trying to test this game?

[JosJuice]

If you've already tried both with and without preferring the stencil implementation, I don't think there's anything left to try. All the necessary settings for this game get enabled automatically by the included game INI nowadays.

[toastedgoast]

(03-02-2018, 07:18 AM)JosJuice Wrote: If you've already tried both with and without preferring the stencil implementation, I don't think there's anything left to try. All the necessary settings for this game get enabled automatically by the included game INI nowadays.

Perhaps I tried to implement this setting incorrectly, could you explain or link to an explanation of how to do this properly?

[toastedgoast]

I would be happy to attempt to find a solution, if I get any farther how can I properly report what was causing it to crash in this instance; I saw someone that experienced a similar crash (white screen into app close / fail) at this point in the game, and their issue was that thier intel cpu was not supported by dolphin, however I know it is not a blanket failure of the sd835; as I mentioned many games do work.

[JosJuice]

(03-02-2018, 08:13 AM)toastedgoast Wrote: Perhaps I tried to implement this setting incorrectly, could you explain or link to an explanation of how to do this properly?

In GFX.ini, there should be a line saying [Hacks]. If there isn't one, create one at the bottom. Then, right below it (or anywhere below it that's before the start of the next section), put this line:

BBoxPreferStencilImplementation = True

(03-02-2018, 08:25 AM)toastedgoast Wrote: I would be happy to attempt to find a solution, if I get any farther how can I properly report what was causing it to crash in this instance; I saw someone that experienced a similar crash (white screen into app close / fail) at this point in the game, and their issue was that thier intel cpu was not supported by dolphin, however I know it is not a blanket failure of the sd835; as I mentioned many games do work.

The first thought that entered my head was to install Android Studio and use its debugger after building Dolphin yourself, but then I remembered that that debugger also catches every segfault caused by fastmem... :/ So you would also have to disable fastmem, which is annoying (or is there some way to change which errors the debugger catches?). I'm not sure if there's any great suggestion I can give you here.

[toastedgoast]

(03-02-2018, 08:54 AM)JosJuice Wrote: In GFX.ini, there should be a line saying [Hacks]. If there isn't one, create one at the bottom. Then, right below it (or anywhere below it that's before the start of the next section), put this line:

BBoxPreferStencilImplementation = True


The first thought that entered my head was to install Android Studio and use its debugger after building Dolphin yourself, but then I remembered that that debugger also catches every segfault caused by fastmem... :/ So you would also have to disable fastmem, which is annoying (or is there some way to change which errors the debugger catches?). I'm not sure if there's any great suggestion I can give you here.

Thank you for the response; I was able to get the freeze/ crash to not happen by reverting to 5.0-4657. Perhaps something newer will work which I will continue to look for but for now that version does seem to work for the note 8 to clear this problem for whatever reason. <edit> also booting past prologue at least until 5.0-5181-- remarkable how much progress the modern dev versions achieve in regard to sound / speed over these older builds.-- game also works as of 5.0-5929, could the error be something small in the code of a later build?

[toastedgoast]

(03-02-2018, 09:38 AM)toastedgoast Wrote: Thank you for the response; I was able to get the freeze/ crash to not happen by reverting to 5.0-4657. Perhaps something newer will work which I will continue to look for but for now that version does seem to work for the note 8 to clear this problem for whatever reason. <edit> also booting past prologue at least until 5.0-5181-- remarkable how much progress the modern dev versions achieve in regard to sound / speed over these older builds.-- game also works as of 5.0-5929, could the error be something small in the code of a later build?

Can now confirm successfully getting past this up to 5.0-6000

[toastedgoast]

It did crash in 5.0-6101, I shall check versions between 6000 and 6101 to attempt to find what is causing this game not to run on note 8

[toastedgoast]

(03-02-2018, 10:26 AM)toastedgoast Wrote: It did crash in 5.0-6101, I shall check versions between 6000 and 6101 to attempt to find what is causing this game not to run on note 8

Now confirmed working up to 5.0-6074

[JMC47]

Please bisect it to an exact build.