I will backup my SD to try it.
But to understand fine, will you update all the SYSTEM from BIN ?
If i have some emulators or ES from SOURCE, will they be replace from BIN ? (After i must UPDATE them from SOURCE again)
Because you don't use RELEASE VERSION in RETROPIE-SETUP to update or not a PACKAGE. We can't know if we have the last one, or not ... and i think you can't know it too and you must force update to be sure?
Haha, yep I've had the same experience!
I'd like to add a warning for low batteries if I can find a way to check them after the controller has already connected. I think it's possible with a (clumsy) hack to one of the sixad files, but hopefully I can find a simpler way to do it.
@mxstar1 I dont think we have anyone working on it. I tried a simpler approach but it is a lot more complex. We have a distinct vision that is not aligned at all with Attract mode. So I dont know if this feature will be incorporated any time soon.
@dankcushions it's quite playable, although the sound isn't 100% correct, some minor artifacts as well. I did an update via source when I got the email it had released, and a binary just now which didn't seem to do anything more, so I wonder if it's worth doing another update from source. Hi-res works just as well as the normal emulator so that's most definitely the way to go)
I'll have to have a go on my Ubuntu build as well and see how that plays.
Good to see the ongoing support potential in your other post, I'll do that one once payday comes around, brassic this week:(
I think this is a good idea, though not one to be taken lightly. Refactorings and cleanups are often double-edged swords, and while I am always supportive of investing time in such endeavors, I fear that we may introduce new bugs and/or remove code that was put there for a reason, even though it might not be at all apparent.
If the scope is more or less well defined upfront (i.e. if we determine that we will look into the screensaver code, or something more), I'm fine with that.
I'm not sure this needs to necessarily be a cross-coordinated effort, though - these efforts are always welcome as long as they're well tested, I believe.
There are a few things on my plate that I'd like to look into, ES-wise, that don't fall into the "new developments" area but rather in the "fixing/improvements" area, namely (in no particular order):
Document OMX and collections features, namely Predictive Profile (High 4:4:4) not working [EASY-ISH]
Address textures defaulting to white after returning from an emulator. [MEDIUM?]
Improve texture cache to reduce texture pop-in. [MEDIUM?]
Fix or mitigate VRAM handling, especially on out-of-memory scenarios. [MEDIUM?]
Try to get rid of the two video player options, but rather have a default hardware accelerated player for the Pi that works as intended (i.e. respects the actual layers, rather than being a separate process). [HARD]
I honestly have no idea how to go about several of these, but I secretly hope that with a proper Windows and VS debugging environment I'd be able to make some progress here.
Thanks for starting this.
Looks like your connection to RetroPie Forum was lost, please wait while we try to reconnect.