#Citra core problem
1 messages · Page 1 of 1 (latest)
is that the entirety of the log, or was the beginning omitted?
but i would be leaning towards a problematic driver update
or rollback
is this a desktop or a laptop?
either way, there are newer video drivers available (from 2020) - https://www.intel.com/content/www/us/en/download/18606/intel-graphics-driver-for-windows-15-33.html
so the question comes down to what did change between when it did work and when it stopped working.
to rule out changes on the RA end, you can rename retroarch.cfg and retroarch-core-options.cfg, fire up RA, and see if games will launch in Citra
(renaming those files will cause RA to recreate them with the default options set)
if there's no change, you can delete the newly-generated ones and rename the previous ones back
ok - so this indicates that the change lies elsewhere in your computer
either from an OS update, or another program that was installed/updated
out of curiousity, from the start menu run eventvwr.msc
in the left pane, expand Windows Logs and choose Application
are there two or three panes horizontally?
ok, in the bottom pane, go to the details tab
in the EventData section, what is the ModuleName?
(assuming it's present)
bah
well, if you use Filter Current Log to limit Event sources to Application Error and Application Hang, you should be able to see when the first RA hangs were
the legacy add / remove programs control panel (start/run appwiz.cpl) can be sorted by install date, see if something lines up
beyond that, see if something jogs your memory regarding another change on the machine.
best of luck!
that's the video driver
the integrated intel graphics
actually, check one other thing for me
look in the retroarch\shaders\presets folder
is there a Citra folder?
ok
if you have a default opengl shader config (retroarch.glslp) rename it to retroarch.glslp.bak to disable it and try again
don't touch that
those are the shader presets you browse through
any core-specific shader presets you save would be in shaders\presets<corename>
ok - so is there a retroarch.glslp in the shaders folder?
ok, so no shaders enabled (intentionally or otherwise) that are causing the hang