Hello everyone.
Q1. What are the best practices in monitoring performance and current browser tools to work with heavier scenes and physics engines with three? (plugins websites software)
Q2. I’m also a little afraid to ask why there are so few posts related to rapier? (did I choose a wrong horse because I just love it)
I’m a fan and lurker of three and you guys for a long time.
Suddenly, claude can fill the gap in my skillset by avoiding writing my own code at all costs, because I’m not a programmer. I’m a designer Bartek Biernacki
Finding teams to work with in a designer/coder combo is quite hard as you probably now these days so I figured that if I’m going to start do it all… let’s do this the right way and that’s why I’m asking.
I’ve build this during last few days building parts with claude and putting it together myself.
S N Y T E J
Sorry for lack of proper controls explanation but it’s just a test (awsd for movement and roll, lmb-fire, rmb-hl2magnetgun, space-jump, R for reset, and U for settings (these icons are pissing me off but deleting it every time claude throws them at me is pointless for tests)
I threw every problem I’ve had so far with three and most of my ideas are working and I’m happy with outcome.
I try to keep the code clean, I know what does what most of the time and I have a proper structure and tools to build but I could really use a guidance about how to track obstacles or potential fixes and I’m not sure if just a simple console and the fact that it’s working is the right way to go about it.
It’s a vibe coded project I really try to clean up from all it’s vibe 
Thanks in advance.
Have a great day.
One love three.js clique.