🔴LOW-FI v0.57 is LIVE
@Anticleric16K followers
11,084 views
49 Comments
Comments from the original post on X (Twitter)

@chandlerriggs
this is awesome. congrats on the engine upgrade, no small feat
33 likes

@Anticleric
Thanks man! Appreciate it 🙏
2 likes

@shenmeowzo
I am so happy this project is back on track. Counting the days till PSVR2. Please use eye tracked foveated rendering to max out performance, hopefully you can get it running at 90htz native. Also capacitive touch for holding items, and full use of HDR. Thank you please. :)
7 likes

@Anticleric
Yes boss! Lol
5 likes

@WilliamPPenha
PSVR2 plans??
7 likes

@Anticleric
Yes! *pats the PS5 devkit beside me
10 likes

@LeeGTOV6
Honestly can't wait to play this on PSVR2! Looks epic!
4 likes

@Heasmo
Nice choice of music, channeling that Wipeout energy :)
2 likes

@Anticleric
I basically listened to the wipeout soundtracks all weekend while working on it 😅
2 likes

@LucaColonnello
Any chance we could get a vision pro release, or at meast full open xr compatibility? 🙏
2 likes

@Anticleric
I does now have full OpenXR compatibility. I'm not sure what that means for vision pro though. I assume it still runs a version of iOS/Linux? Are there any other PC VR game ports available for it?

@LucaColonnello
You can play half life alyx now on vision pro, and it works sooo well!! On PCVR streaming though, vision pro can use nvidia streaming, you can check KRVR. Open XR would be a must for the future.
1 like

@bmfshow
Racing looks awesome
2 likes

@Anticleric
🙏Still needs a bit of work, especially with other ship collisions, but the sense of speed is great. And I'm really happy with how it looks so far.
2 likes

@AppsPs4
Congrats!
2 likes

@its_iio
Saw your reply about Claude Code + MCP being the big win. What has it been most useful for in LOW-FI so far: scene setup, debugging, or the migration cleanup?
2 likes

@Anticleric
Literally anything painful that I would have to argue with a programmer about. Sometimes right before I go to bed I just give it a list of "this would be nice to wake up to". And it usually works. The other night it was things like screen space UI in flat mode, camera bob for flat mode, speed boost pads on the race track, some weird traffic flocking behavior in the open city, etc. The best part is that when I report a bug, it doesn't talk back and say "I tested that" until I rub its nose in it. It just goes and fixes it. Lol But to answer your question.cthe migration was definitely the biggest win, but I didn't even need the MCP to start that.
4 likes

@its_iio
Thanks, that helps explain the workflow. Do you keep the overnight changes separate so you can test and revert them one by one, especially across flat and VR modes?
1 like

@Anticleric
I usually ask it for a full report to wake up to. It will make a nice HTML page with a list of things to test at the end. I tell it to do commits and its own in editor testing along the way also. So if something gets borked, it can just pull back what it needs from git. But that very rarely happens. Usually it's just a missunderstanfing and it fixes it pretty quickly. Having a technical director and desogn background is a huge advantage for prompt engineering.

@its_iio
The test checklist at the end makes the morning review much more concrete. Thanks for breaking the workflow down!
1 like












