What needs to be done before having it enabled by default :
HAVE_OZONE on all relevant platforms, add HAVE_OZONE=auto in config.params.sh, always enable it in Makefile.commonconfiguration.cPlanned features :
Fancy shaders / menu display improvements :
Tried this out, and it's great! Very clear, and easy to understand what you're looking at. Looking forward to seeing how this evolves :+1:
@RobLoach make sure you try the dark theme too, it really is great.
When I set language to english, it works fine with ozone.
But fonts are crashing if I set it to korean.
https://ibb.co/kOxSsq
xmb is working fine with korean lang.
@newget this is a known issue, let me add it to the list
It's usable but Korean is not fully fixed yet.
It displays korean well in submenu, but not in header title.
Might be bold font problem?
Cheevos badges are now fixed, thanks for reporting
Drop shadow issue with the selector under Vulkan:

menu_display_draw_texture_slice is the culprit here. Unfortunately I don't own any PC compatible with Vulkan at the moment, I'm limited to GL as far as my testing goes. Maybe someone who knows Vulkan can look into that ?
How long before thumbnails are implemented? It's the only reason I haven't made the switch
I first need to add scaling support. For scaling support I need to replace all the hardcoded metrics by actual variables and calculations.
So, not soon.
I keep getting this missing asset error when using ozone on Windows nightlies despite updating my assets (just tested ac04c1bfc5ebba847557309aa6c55a55e0c05016):
[WARN] [OZONE] Asset missing: F:\Blue\Emulation\Emulators\RetroArch\assets\ozone\png\.png
[WARN] [OZONE] Assets missing
I wondered because it only recently appeared and I didn't touch ozone for a while now. I will fix it before starting working back on it, so no rush
scissor was added to d3d9/10/11 FYI
This will be my default when the DPI fix is in place. Amazing work. Right now I'd need 5x better eyesight to use it on a 4K TV :)
@natinusala Anything new about playlist thumbnails grid layout ?
I did a quick edit and it would be so beautiful !

I think this is definitely something that @jdgleaver has on his mind but it just takes a lot of time to refactor all the code in the menu driver to make this easily possible.
That being said, thanks for the mockup, and I do think something like that looks great, especially if we could even have additional size options so the user can control just how big the thumbnails should be.
I see, I'm looking forward to that option !
I think the groundwork has been done (for Material UI), the plan was to add it to ozone after adding it to MUI
Yes, we will most definitely be adding grid views. It'll take a little while, though - I still have to work out the required menu navigation changes, and then Material UI will be the first driver to get it (since this is already designed around the concept of multiple list view types). After that, it'll get ported to Ozone - this is quite a task, since it means replacing all of Ozone's thumbnail handling code with the routines we currently use in Material UI, and there will need to be some low-level redesign to support different view modes. But we'll get there, time permitting!
if Grid view gets added, plus a way to filter thousands of roms in a smart way (I discussed using Merged ROMs and only allowing the parent to show when adding a Playlist) it will make other frontends obsolete! :)
Most helpful comment
I first need to add scaling support. For scaling support I need to replace all the hardcoded metrics by actual variables and calculations.
So, not soon.