New Citra Canary Crash to Menu

Citra was working fine last time I played. I just now updated the core and everytime I try to play a game, go goes right back to the retroarch menu. What’s up with that?

The core was updated to keep up with upstream, and that required updating the toolchain that we build it with, and that means it stopped working with 1.7.1 stable. You can get it working again if you download a nightly build and updated redist for RetroArch (or just get the nightly full package).

ok thanks. is this for every new core or just this one?

Not all of them. Just this one.

ok, now I can only use glsl shaders with citra and not my usual cg shaders :frowning:

Also, my favorite glsl conversion of that same shader is not working. Were the shaders updated or something? And how can I resolve this?

I just talked to j_selby and he said the GL requirements haven’t changed with the updates. Dunno what could be going on for you. Anything helpful in the logs?

I turned on logging and have it on 0 debug yet I don’t see a log file. But here is the shaderset again so you could load the preset on your end to see if you can identify the issue.

https://docs.libretro.com/guides/generating-retroarch-logs/

Opened retroarch, loaded game with 3ds core, loaded shader preset and applied. went back to menu with no shaders loaded:

https://mega.nz/#!S4ETTZCI!w9e5Hl2ZxtJ-pDLBnKqyZmQsUhJFqOXjtBi0odcue04

So is that enough to tell you what’s going on?

I don’t see any shader errors in there, just some warnings. Can you try reducing the internal resolution of the core and see if that helps?

changed core res to x1:

this Cg shader goes back to menu unloaded default cg shader of scalefx9x goes back to menu unloaded

glsl default shader of scalefx9x works but makes the game 1fps.

When’s xbrz going to be implemented in the recent builds of citra? That way I can exclude this shader from the preset. I remember it being in a 2016 standalone build and was pretty fast.