LG v30 snapdragon 835

Haze89 · 02-19-2018, 12:39 PM #1

I am having random panic alerts showing up on the 5.0-1626 build for baten kaitos eternal wings. The game flies on 1626, but runs like a slug on the current build. I am getting panic alerts around 20 mins into the game it's panic alert invalid write 0x00000.... Any help at all would be greatly appreciated

**Helios** · (This post was last modified: 02-19-2018, 01:43 PM by Helios.)

The reason why it's slow now is because we started shipping gameini on android, our "database" of settings for various games that need specific settings to work properly.

For that game, we turn off dual core mode (massive perf hit) and turn off EFB to texture (large perf hit on Android) - so that's why it's slow for you.

As for why it's crashing, I don't know.

EDIT: It's because this game is known to crash on dual core mode

Haze89 · 02-19-2018, 01:03 PM #3

(02-19-2018, 12:57 PM)Helios Wrote: The reason why it's slow now is because we started shipping gameini on android, our "database" of settings for various games that need specific settings to work properly.

For that game, we turn off dual core mode (massive perf hit) and turn off EFB to texture (large perf hit on Android) - so that's why it's slow for you.

As for why it's crashing, I don't know.

I'm using the 1626 build it runs noticeable faster than the current build. Is there a way to fix the panic codes? Or is my best option just waiting till a build comes out that supports it? Also, I am a huge tales of Symphonia fan, are you guys working for the in-game glitches that appear for that title?

**Helios** · 02-19-2018, 01:06 PM #4

Yes, because in 1626 we didn't ship GameINI on Android. You'll probably also find that the game will randomly freeze on that build because it doesn't like dual core mode.

There's no real way to fix the panic codes unless somebody bothers to look into it. The aarch64 JIT hasn't been touched in 3 months according to github, so I wouldn't hold your breath.

As for Symphonia, nobody has looked into it.

Haze89 · 02-19-2018, 01:11 PM #5

(02-19-2018, 01:06 PM)Helios Wrote: Yes, because in 1626 we didn't ship GameINI on Android. You'll probably also find that the game will randomly freeze on that build because it doesn't like dual core mode.

There's no real way to fix the panic codes unless somebody bothers to look into it. The aarch64 JIT hasn't been touched in 3 months according to github, so I wouldn't hold your breath.

As for Symphonia, nobody has looked into it.

I see thank you for your responses. I do hope someone looks into tales of Symphonia soon. It was one of the golden titles for the GameCube

Haze89 · 02-19-2018, 01:15 PM #6

(02-19-2018, 01:06 PM)Helios Wrote: Yes, because in 1626 we didn't ship GameINI on Android. You'll probably also find that the game will randomly freeze on that build because it doesn't like dual core mode.

There's no real way to fix the panic codes unless somebody bothers to look into it. The aarch64 JIT hasn't been touched in 3 months according to github, so I wouldn't hold your breath.

As for Symphonia, nobody has looked into it.

There are a lot of EFB settings which one in specific? Or is it all of the EFB settings?

Haze89 · 02-19-2018, 01:32 PM #7

(02-19-2018, 12:57 PM)Helios Wrote: The reason why it's slow now is because we started shipping gameini on android, our "database" of settings for various games that need specific settings to work properly.

For that game, we turn off dual core mode (massive perf hit) and turn off EFB to texture (large perf hit on Android) - so that's why it's slow for you.

As for why it's crashing, I don't know.

Yea, the panic code goes away when turning off dual core mode, but then the sound gets really choppy even lowering the emulation speed from 50 to 30 it's still choppy. Is the EFB to texture the one in the enhancements menu?

**Helios** · 02-19-2018, 01:42 PM #8

I don't actually know why we turn off EFB to texture for that game. It's not documented anywhere. I wouldn't worry about it.

But yeah, that game is probably going to be unplayably slow for you if you want it stable. You have to play with dual core off to not crash

Haze89 · 02-19-2018, 02:44 PM #9

(02-19-2018, 01:42 PM)Helios Wrote: I don't actually know why we turn off EFB to texture for that game. It's not documented anywhere. I wouldn't worry about it.

But yeah, that game is probably going to be unplayably slow for you if you want it stable. You have to play with dual core off to not crash

You mentioned a game database earlier? Do you have a link to that? I would be interested in seeing what settings are most optimal per title, also you claimed it hasn't really been updated on GitHub for 3 months, does that mean the most stable build is from 3 months ago?

**Helios** · 02-19-2018, 03:06 PM **#10**

The aarch64 JIT hasn't been updated in 3 months. That's what Android uses. And no. The time of the last code change to the aarch64 JIT has nothing to do with stability. I was just saying that nobody is really working on the core parts of dolphin on Android right now so you shouldn't get your hopes up.

To your other question, the gameini directory is just a set of files that force certain options for games to make them work correctly. This is done automatically on the latest build and you don't need to do anything. If you're really interested, just go to dolphins GitHub and search the game name you're interested in in the top bar of the site. It's an ini file.