Great
Let's wait until that is merged and then give it a try in the newest nightly after the commit.
If the issue still persists, don't hesitate to tell me, bud, so that I can open a proper Issue on GitHub in case it happens
Great
If you use shaders the issue will be always there, as retroarch.cfg stores the last used shader here: video_shader = "" and apply that shader to the RA menu (on background), on top of built-in shaders (ribbon, bokeh, snow, etc...) so it become slow because is processing both shaders (or at least that's how I understand it).
If you use a shader even once you are screwed lol.
(you still can delete that line from retroarch.cfg from your PC, but it will appear again if you use a shader)
This is something only the devs themselves could answer @rioray @Radius4 @QuarkTheAwesome @aliaspiderI'm going to stop with the Commodore 64, can't seem to get anything load, even after getting the .d64 romset.
I have a performance question regarding retroarch, which has been buried within is thread.
Will there ever be some sort of cache feature, for when you scroll through a playlist with boxarts? When I cycle through individual playlists, it is so sluggish. And when I scroll through whichever playlist, it is so sluggish, taking time to sift through the list.
Those familiar with WiiFlow, it had a cache feature where instead of reading the .png files over and over and over again, you just needed to view the image once, and it created a cache file of the png, incredibly small in size, so that when you scroll back to the previous/previously viewed boxart(s) it would flow perfectly, no sluggishness at all.
Is this something the developers would take into consideration?
Well maybe the Wii U simply isn't meant for shaders then.
Oh I wasn't aware of your issue with C64.I'm going to stop with the Commodore 64, can't seem to get anything load, even after getting the .d64 romset.
I have a performance question regarding retroarch, which has been buried within is thread.
Will there ever be some sort of cache feature, for when you scroll through a playlist with boxarts? When I cycle through individual playlists, it is so sluggish. And when I scroll through whichever playlist, it is so sluggish, taking time to sift through the list.
Those familiar with WiiFlow, it had a cache feature where instead of reading the .png files over and over and over again, you just needed to view the image once, and it created a cache file of the png, incredibly small in size, so that when you scroll back to the previous/previously viewed boxart(s) it would flow perfectly, no sluggishness at all.
Is this something the developers would take into consideration?
Post a picture of your folder structure.Anyone can help me ? I can't get RetroArch to load up at all, always end up with a black screen.
I've tried both RPX and non-RPX version. Tried booting from the Homebrew Launcher and the Channel, both just end up with a black screen.
Also tried with and without the assets pre-downloaded.
I have no clue why this isn't working and I've been wasting hours into this, I'm clueless and I just want some help.
Running on 5.5.2 with CBHC.
Post a picture of your folder structure.
We have to be sure everything is in the right place.
Oh I wasn't aware of your issue with C64.
So you couldn't get any ROM to load with the VICE core?
As for your second question.
When going from left to right in the Playlists (shifting from a console's core to another) I don't have that sluggish issue.
I DID have it with previous versions of RetroArch, but not with the latest nightlies since a week or so.
However, I do have the issue that you mention with Boxarts.
What I ended up doing was reducing the size of each individual image to a size around 160x240 (Height X Width).
That way, when the boxarts are loaded into the playlists, they load rather quickly to the point you don't even feel it stuttering to load the PNG.
Try doing that, reduce your boxarts to around 160x240 for rectangle boxarts, and perhaps 240x240 for square/CD boxarts.
The cache suggestion you recommend is rather interesting, and would surely benefit RetroArch, perhaps that would be better to point out in the GitHub so that perhaps they take it into consideration.
No need to, everything is working as I expected, so the size issue is none of my business. If I had to guess I'd say that libretro's buildbot doesn't use any compression at all when making the rpx. Kinda like an archive zip file.So decompressing the RPX does give you a DRPX of the same size as the original?
That's weird, unless the RetroArch ones don't really do decryption to some extent.
Try with RPX files of VC titles or things like that, maybe then you can see the difference.
If you look at one of my posts (buried somewhere in this thread.) I asked the same exact question (I even asked for it on the official libretro forums).I have a performance question regarding retroarch, which has been buried within is thread.
Will there ever be some sort of cache feature, for when you scroll through a playlist with boxarts? When I cycle through individual playlists, it is so sluggish. And when I scroll through whichever playlist, it is so sluggish, taking time to sift through the list.
Those familiar with WiiFlow, it had a cache feature where instead of reading the .png files over and over and over again, you just needed to view the image once, and it created a cache file of the png, incredibly small in size, so that when you scroll back to the previous/previously viewed boxart(s) it would flow perfectly, no sluggishness at all.
Is this something the developers would take into consideration?
I did that, way back when. It actually doesn't improve things by that much, if at all.As for your second question.
When going from left to right in the Playlists (shifting from a console's core to another) I don't have that sluggish issue.
I DID have it with previous versions of RetroArch, but not with the latest nightlies since a week or so.
However, I do have the issue that you mention with Boxarts.
What I ended up doing was reducing the size of each individual image to a size around 160x240 (Height X Width).
That way, when the boxarts are loaded into the playlists, they load rather quickly to the point you don't even feel it stuttering to load the PNG.
Try doing that, reduce your boxarts to around 160x240 for rectangle boxarts, and perhaps 240x240 for square/CD boxarts.
The cache suggestion you recommend is rather interesting, and would surely benefit RetroArch, perhaps that would be better to point out in the GitHub so that perhaps they take it into consideration.
What do you mean by "specific titles"? You can resize EVERYTHING (not only the boxarts, though SS and titlescreen are irrelevant due to their size)Correct, still got the READY with the blinking cursor, no kind of autostart when loading a .d64 game.
As for the boxart images, id really like to refrain from resizing only specific titles boxarts, since my playlists are setup with each consoles complete romset.
The stuttering from left to right, only happens for me once reach my playlists, since it's not loading just the boxart, but also the number of files. I don't know how to use GitHub, which Is why I hope someone will submit my suggestion to some sort of cache setup to help with the stutterness.
It’s been like that for a while. All shooters are upside down and the option to change it isn’t working.
no, it's not upside down anymore, and then you could rotate the screen under video settings, now the screen oriented to horizontaly the top of the game is in the right side the bottom on the left side, rotating it on video settings only allow change the the orientation from left to right.It’s been like that for a while. All shooters are upside down and the option to change it isn’t working.
Mmm weird. So C64 ROMs do not load up automatically, you have to type in the command to run them?Correct, still got the READY with the blinking cursor, no kind of autostart when loading a .d64 game.
As for the boxart images, id really like to refrain from resizing only specific titles boxarts, since my playlists are setup with each consoles complete romset.
The stuttering from left to right, only happens for me once reach my playlists, since it's not loading just the boxart, but also the number of files. I don't know how to use GitHub, which Is why I hope someone will submit my suggestion to some sort of cache setup to help with the stutterness.
@infidelity .D64 format C64 roms are working here.. They take a long time to load though and performance is not great, I remember it running 100% before?Mmm weird. So C64 ROMs do not load up automatically, you have to type in the command to run them?
Or do they simply stay there without booting up no matter what?
The stuttering between Playlists might be because of the huge amount of ROMs.
I do have like 20-30 tops for each console, so that might be why I get them to load without any hitch.
As for the boxarts, I think there is a tool called Scraper or something which downloads them, but still I do understand why a cache would be a time saviour here.
I'll try to open up a suggestion as an Issue in the GitHUb page for RetroArch to recommend them to implement a cache option for these cases.
Damn, a min or 2?.D64 format C64 roms are working here.. They take a long time to load though and performance is not great, I remember it running 100% before?
This is the screen after loading the D64..View attachment 112842and you can see the FPS is 42 (supposed to be 60?)
It takes a min or 2 before the game loads from there