2 ms·
with stuff like 3d modelling code you're kinda skipping straight to some of the more hardcore coding. 3d transformations and algorithms are no joke, thats unive
by RugnirViking 3y ago
with stuff like 3d modelling code you're kinda skipping straight to some of the more hardcore coding. 3d transformations and algorithms are no joke, thats university and master's degree level maths. Don't feel bad if you don't get it, a huge number of professional programmers wouldn't either. I write a lot of software myself close to the metal as a robotics engineer and ive tinkered with blender code but id definately need a lot of practise to feel comfortable doing that without glueing together tools
- iainmerrick 3y agoTotally. 3D geometry is hard and when you're coding there are a bunch of different ways a minor error can mean absolutely nothing appears on the screen. Just learning about those different failure modes takes a while. The other thing I find (but maybe this is the same with node-based approaches too!) is that there are a bunch of arbitrary coin-flip choices you have to make when doing 3D (e.g. left-handed versus right-handed coordinates). At a fundamental level it doesn't matter which choice you make, but your decisions have to be consistent, otherwise things can get flipped around, or often just vanish entirely. The sneakiest problem is when you unknowingly make two wrong choices, and they mostly cancel out except for some weird edge cases that happen to exercise the exposed code path.