Загрузка видео...
Не удалось загрузить видео
To me, native visualization tools are key for a speedy development cycle! By native I mean "inside the application". For example, this is the importance sampling visualization for the light controls I posted yesterday:
19,167 просмотров • 2 лет назад •via X (Twitter)
Комментарии: 10

One thing that I did at a point is a "debugDraw(...)" which takes a lambda and allows to draw whatever in the lambda to a separate window. As simple as printf but graphical!

Yeah, that’s useful! I calls these mini-apps within the app “tools”. They are playpens more than anything else. But from there I can access data in the engine if I want to. So, a tool can be completely independent, like the one I am showing, or work with the rest of the app.

This always pays off! Sometimes I try to skip this, or don't bother and it always bites me. Way better investment than tests, imo (if you have to pick one or the other).

If some R&D project, visualization is king. For a product, tests are… but likely need both.

Besides your incredible technical ability, you have an unusually good eye for UX and Manipulator visualization. WYSIWYG might sound like a 2000's buzz word but is incredibly important from setup to final builds. It is a pleasure reading your posts.

Hehe, thanks. WYSIWYG, that’s a term I haven’t seen in a while!

Pleasant in small things, in fact such things can really speed up the work and improve the user's work with the program 🥰

Stop playing around Max, textures next come on I wanna do some testing 😅😛

Yeah, it’s the missing elephant in the room, isn’t it?

That is amazing to see
