Cybermonk opened this issue on Oct 07, 2014 · 21 posts
RobynsVeil posted Sat, 11 October 2014 at 12:50 AM
Quote - Well I been using the 2.72 nightly build and so far it has been ok and have not been able to recreate the bug I usually keep 2 previous versions to run from their folders and only actually install a stable release. I have a few add ons that won't work in 64 bit version and only work in 32 bit versions of Blender. By keeping a veiw version on my system I am able to usually better help since there is always some change with in releases maybe something is moved to a different area or tools are on different panels am able to help others if I can replicate what they see
That's pretty much what I do as well, Lobo. Well, one, anyway. I build-my-own 64-bit version from git, which I do every so often (once you've done it once, all dependencies will be satisfied, and from then on, it's just running the same commands from Terminal). Kind-of fun to mess with the latest-greatest commits.
But yeah, every now and then, they break things. Oh well... at least we get to keep both pieces... :biggrin:
Monterey/Mint21.x/Win10 - Blender3.x - PP11.3(cm) - Musescore3.6.2
Wir sind gewohnt, daß die Menschen verhöhnen was sie nicht verstehen
[it is clear that humans have contempt for that which they do not understand]