m0usecat.bsky.social @m0usecat.bsky.social · 04/04/2025Sync server stays online as much as it can. But the cold storage routine needs serious updates. 010
m0usecat.bsky.social @m0usecat.bsky.social · 01/04/2025RTO actually means "Return To Orifice", so they can shit all over you. 000
m0usecat.bsky.social @m0usecat.bsky.social · 31/01/2025Everything done right, it should be very possible to run things well on Quest 1. But it does mean aggressive culling, so much so that you may even want to avoid Landscape and go for bespoke modeled terrain. Still, old consoles showed that it's very viable, and Q1 had so more memory than they did. 000
m0usecat.bsky.social @m0usecat.bsky.social · 31/01/2025Kinda wish Unreal had more exposure of lighting tech under the hood, or at least access to lighting data in materials. Still, creative use of fully rough and unlit materials should've done the job for Quest 1 very effectively. But UMG UI was very heavy, had to config to not redraw every frame. 100
m0usecat.bsky.social @m0usecat.bsky.social · 31/01/2025I recently learned about simpler pre-PBR lighting techniques after Quest 1 was already obsolete lol. Those workflows would've been perfect for it, leaving scenes at full resolution with a ton of extra CPU and GPU headroom. N64 to 3DS heavy use of vertex paint and such topo would've been perfect lol.noclip.websitenoclipA digital museum of video game levels 120
m0usecat.bsky.social @m0usecat.bsky.social · 10/01/2025I'm using the original with @bgolus.bsky.social 's optimizations, and exposed a few params I needed. pastebin.com/9AeTXvG3 I ran out of samplers for a terrain material on mobile, so this is a lifesaver to avoid distorting the cliffside. The seams can be covered, and it doesn't require TAA/TSR. 000
m0usecat.bsky.social @m0usecat.bsky.social · 08/01/2025Sadly, not any less accountable than the "opposing" party would. 000
m0usecat.bsky.social @m0usecat.bsky.social · 07/12/2024Mobile keyboard default settings are horrifically bad. Default should've only ever been to have to tap a suggestion for autocomplete. 010
m0usecat.bsky.social @m0usecat.bsky.social · 24/11/2024Overall, this topic is a whole can of worms, and studios need to do vigorous profiling and research to assess that their implementations are acceptable. No one forces developers to use Lumen/Nantite, and you have to study them before attempting to use in production. 010
m0usecat.bsky.social @m0usecat.bsky.social · 24/11/2024My own concerns on the engine atm are whether I can integrate an old SMAA implementation from somewhere, and whether I can get a performant dynamic GI setup going with just Lumen config, or perhaps I need the RTXGI branch. Practices considered unacceptable in VR, I also apply to non-VR as well. 120
