Dekopon - (Mostly) Fullspeed 3DS Emulation on Nintendo Switch

[fildicio96]

Both of those will be in the next update and should be super easy to implement. Alongside maybe a 3D UI for those that use that feature.

It may be because a lot more of the shaders are cached on the device, so they need to be replayed before starting a game rather than computed during game time. I could make an option to turn of disk cache, but that'll make games a lot more stutter-y. Also I never had 5 second loads. Mine have always been slow. Maybe SD Card speed?

3Beans port incoming when?

I'm looking into this issue now for anyone running into it. Apologies for the worse performance. If anyone could say which update it was that decreased performance in these games it would be very helpful for my debugging.

Both of those will be in the next update and should be super easy to implement. Alongside maybe a 3D UI for those that use that feature.

It may be because a lot more of the shaders are cached on the device, so they need to be replayed before starting a game rather than computed during game time. I could make an option to turn of disk cache, but that'll make games a lot more stutter-y. Also I never had 5 second loads. Mine have always been slow. Maybe SD Card speed?

3Beans port incoming when?

I'm looking into this issue now for anyone running into it. Apologies for the worse performance. If anyone could say which update it was that decreased performance in these games it would be very helpful for my debugging.

I found the version that broke it is the v2.0.0, not the release candidate which I just tried, the Async GPU made first crash pokemon oras and then the second time the game I loaded the game it worked.

One thing I want to underline is that there wasn’t any performance boost with the Async GPU on version 2.0.0-RC1

Yesterday I used version 1.3.0 which was working as well

So I’m pretty sure is the latest version you uploaded which had the bug.

Thanks!
@PalindromicBreadLoaf

 

[babthedog]

Hey there. Amazing work. I found a minor issue. In ocarina of time 3D while looking at the sun ( or when a lens flare is created ) the frame rate drops really low, which is weird since it's mostly a consistent 30 fps. Any changes to the resolution or the enhancements don't help, for me a least. Thanks.

 

[PalindromicBreadLoaf]

Hey there. Amazing work. I found a minor issue. In ocarina of time 3D while looking at the sun ( or when a lens flare is created ) the frame rate drops really low, which is weird since it's mostly a consistent 30 fps. Any changes to the resolution or the enhancements don't help, for me a least. Thanks.

There’s some WIP stuff behind the scene to fix some of the performance issues introduced by the latest update. Hopefully they can fix the issue. Are you playing with right eye disabled? If not that could help some.

 

[kazenohibi]

Updated from 1.3 to 2.0 pre-release.

I had to delete the shaders first because games weren't booting after this update.

- Kirby Triple Deluxe: I noticed shader compilation is faster. Before this update, I was considering lending my shaders to another person so they could play this game without so many hiccups. Now I don't think it's necessary to do that.

- Smash Bros. for 3DS: Since a very early update, this game may crash at random (not while idle). With this update, it didn't crash at all, but on three occasions the game froze for several seconds with CPU 3 at 100%. Then it continued as normal, although it took a little while to recover. Once it happened during a loading screen, and twice during Smash Run. Perhaps these are situations where it used to crash before. I also noticed smoother shader compilation.

After reading some comments, I'll stay on this update for now.
(Clocks used: 2400/921/2300, x3 and x2 resolution. No right eye.)

 

[BETA215]

Awww... playing Animal Crossing, at a random point in the game the whole emulator freezed. HOS kept working, as every other overlay and submodule. I guess I'll refrain from playing any games where a crash or a freeze will involve losing hours of progress, at least for a significant period of time.
Hey, this emu is amazing already for what it is, so I can't complain much!

 

[PalindromicBreadLoaf]

Awww... playing Animal Crossing, at a random point in the game the whole emulator freezed. HOS kept working, as every other overlay and submodule. I guess I'll refrain from playing any games where a crash or a freeze will involve losing hours of progress, at least for a significant period of time.
Hey, this emu is amazing already for what it is, so I can't complain much!

It appears that the freeze goes away if you wait a few minutes, but I don’t know what could be causing that. And idea how long you played before it happened?

Updated from 1.3 to 2.0 pre-release.

I had to delete the shaders first because games weren't booting after this update.

- Kirby Triple Deluxe: I noticed shader compilation is faster. Before this update, I was considering lending my shaders to another person so they could play this game without so many hiccups. Now I don't think it's necessary to do that.

- Smash Bros. for 3DS: Since a very early update, this game may crash at random (not while idle). With this update, it didn't crash at all, but on three occasions the game froze for several seconds with CPU 3 at 100%. Then it continued as normal, although it took a little while to recover. Once it happened during a loading screen, and twice during Smash Run. Perhaps these are situations where it used to crash before. I also noticed smoother shader compilation.

After reading some comments, I'll stay on this update for now.
(Clocks used: 2400/921/2300, x3 and x2 resolution. No right eye.)

When you say CPU 3, do you mean the second to last or last core in the list on the overlay?

 

[BETA215]

It appears that the freeze goes away if you wait a few minutes, but I don’t know what could be causing that. And idea how long you played before it happened?

When you say CPU 3, do you mean the second to last or last core in the list on the overlay?

Oh, no no. I waited for more than a few minutes, to no avail. And I had been playing for quite some time, maybe like half an hour?
I *tried* to check the logs, but the file is so huge that barely anything can kinda open it on my phone. I think there was a lot of something about trying to access out of bounds RAM? Really can't check it.

 

[PalindromicBreadLoaf]

Oh, no no. I waited for more than a few minutes, to no avail. And I had been playing for quite some time, maybe like half an hour?
I *tried* to check the logs, but the file is so huge that barely anything can kinda open it on my phone. I think there was a lot of something about trying to access out of bounds RAM? Really can't check it.

That log is very helpful, thank you. Is there a reason why your clock speed is set to 105% and not 100%? I've fixed two issues regarding the potential cause of the freeze. I'll try to get a new pre-release version out today to hopefully fix the issue.

 

[kazenohibi]

8

It appears that the freeze goes away if you wait a few minutes, but I don’t know what could be causing that. And idea how long you played before it happened?

When you say CPU 3, do you mean the second to last or last core in the list on the overlay?

Hehe, I thought It could be intérpreted in two ways
Cpu 1, 2, "3", 4
Which would be a more precise way to say it? Core 3?

 

[PalindromicBreadLoaf]

8
Hehe, I thought It could be intérpreted in two ways
Cpu 1, 2, "3", 4
Which would be a more precise way to say it? Core 3?

Technically it'd be core 2, since counting starts at 0, but it's hard to distinguish without clarification. The freeze may be something related to logging. Do you have the log still from when you the freeze happened or have you played other things since then? If you have it, would you be willing to share?

 

[kazenohibi]

Technically it'd be core 2, since counting starts at 0, but it's hard to distinguish without clarification. The freeze may be something related to logging. Do you have the log still from when you the freeze happened or have you played other things since then? If you have it, would you be willing to share?

Fortunately, I only played Kirby after Smash. Here are three logs: one from Kirby, one from Smash, and one from an older version of the emulator that I had saved from a previous Smash crash.


edit. the old log is more like from version 1.1.0

 

[BETA215]

That log is very helpful, thank you. Is there a reason why your clock speed is set to 105% and not 100%? I've fixed two issues regarding the potential cause of the freeze. I'll try to get a new pre-release version out today to hopefully fix the issue.

I'm really glad to hear that! Hopefully it's fixed soon.
Since this is random and I can't reproduce this issue consistently, sadly it'll be hard to tell if it could happen again. But I'll see it as I use the emu.
Clock speed at 105%, it probably was a mistake. Using the analog stick, it's easy to change parameters by accident while going through the entries in the settings menu.

Also, on a different note, I've been trying to make copies of the save files, but Checkpoint won't work. I don't need it to be through that app, but I just would like to know if there's any way to manage it. Copy, restore, stuff like that.

 

[PalindromicBreadLoaf]

I'm really glad to hear that! Hopefully it's fixed soon.
Since this is random and I can't reproduce this issue consistently, sadly it'll be hard to tell if it could happen again. But I'll see it as I use the emu.
Clock speed at 105%, it probably was a mistake. Using the analog stick, it's easy to change parameters by accident while going through the entries in the settings menu.

Also, on a different note, I've been trying to make copies of the save files, but Checkpoint won't work. I don't need it to be through that app, but I just would like to know if there's any way to manage it. Copy, restore, stuff like that.

The randomness is what makes it so annoying to deal with. Save management shouldn't be too hard to implement into the emulator itself. Maybe I'll make the settings only changeable with the dpad instead of the analogue stick.

 

[albarapa]

The randomness is what makes it so annoying to deal with. Save management shouldn't be too hard to implement into the emulator itself. Maybe I'll make the settings only changeable with the dpad instead of the analogue stick.

Yeah it happened to me also occasionally that I changed settings without noticing it. I personally like to change settings with a and b but dpad should also be a good solution