It took a surprising amount of effort to achieve this crappy result.
-
It took a surprising amount of effort to achieve this crappy result. It's rendering 4000 views simultaneously per frame (effectively 120000 fps), on a Pi 4. Complicated by no viewport arrays or layered rendering support, and clipping in the fragment shader added seconds to render time.
-
It took a surprising amount of effort to achieve this crappy result. It's rendering 4000 views simultaneously per frame (effectively 120000 fps), on a Pi 4. Complicated by no viewport arrays or layered rendering support, and clipping in the fragment shader added seconds to render time.
@ancientjames I still don't quite get how those work. Also, how tf did u manage to render that many FPS?
-
It took a surprising amount of effort to achieve this crappy result. It's rendering 4000 views simultaneously per frame (effectively 120000 fps), on a Pi 4. Complicated by no viewport arrays or layered rendering support, and clipping in the fragment shader added seconds to render time.
@ancientjames
Sure but like...
That's crazy! -
It took a surprising amount of effort to achieve this crappy result. It's rendering 4000 views simultaneously per frame (effectively 120000 fps), on a Pi 4. Complicated by no viewport arrays or layered rendering support, and clipping in the fragment shader added seconds to render time.
Now you may say, James, did you know that faster computers exist? But I like embedding a cheap SBC. When I abandon this project and move on to something else, I want it frozen in a state that Just Works. I don't want to turn it on a year from now only to wait 30 minutes while it enshittifies itself.
-
R relay@relay.mycrowd.ca shared this topic
