Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
-
Did you try an older version to see if new version has issues? I did a quick check and people are working with millions of tris on 16GB ram:
https://blenderartists.org/t/... -
@Demolishun That's not a bad idea. I remember even on my old machine with way less RAM i was able to work with high poly meshes
Guess 4.2 alpha really is alpha lol -
@12bitfloat some dude in that thread said he was working with like 12M tris/polys. That was in 2022 so if "should" be able to handle that.
-
I used to edit videos and work with scenes in and around 1M tris in the v2.79 days, when all I had was decade old hardware; later versions were, invariably, absolutely unusable for the exact same workload.
This obviously shouldn't happen. I was mad enough at one point that I thought of just looking at the source to see what the fuck was going on -- then I looked at the source, vomited, and decided I was OK with the older version. -
@Liebranca I get models that need old versions to work. If you want to upgrade you have to install all major versions and slowly update. Hoping shit doesn't break. But at least you can still get all major versions.
-
@Liebranca @Demolishun It's still so weird though. I sit at 16 gigs RAM usage, load a model which in raw PLY format is literally just 32.3 MiB and then I try to add a default subdivision modifier and I can just see the memory slowly going from 16 gigs to 32 and then promptly crashes
I mean I get regressions and all, but like wtf. How can that operation in anyway shape or form take more than 16 gigs to perform... -
@12bitfloat Did you report this to Blender issue tracker? Looks like a recursion that should not happen...
-
@12bitfloat Not too long ago, the mere act of compiling shaders would cause an unrecoverable GPU crash on my end. Sometimes, just __launching__ Blender would cause this.
I thought my chip was fried, but no. This was (indirectly) fixed by a system update months later. There was a mesa incompatibility, *exclusive* to Blender; no other program I tested -- 3D game or editor -- was affected.
What I mean to say is this absolutely unreasonable how in the name of fuck could it even be possible is just par for the course, and for this reason, the devs have been sentenced to patching CMakeLists for the rest of their lives. Even Brecht. Specially Brecht.
I've taken my Dev rant over to Linked in. Fuck you recruiters!
How about no?
Fuck you.
Since when is blender utterly unusable for meshes > 500k tris. I have 32 gig RAM and it's literally unusable. You try to do anything and it fills up your entire RAM and dies. No matter what you do
Like fucking really? I can't add a subdivision surface modifier to a mesh with 800k tris? Is that too much to ask for
I'm so fucking pissed off right now. I've already wasted an hour trying to export ANY high res model and zero luck so far. Either blender just crashes. Or the exported model doesn't contain any geometry. Or the exported model doesn't contain tangents (even though I explicitely enabled them). Or I try do enter edit mode and it crashes. And then every damn time I have to renavigate to the blender folder (because of course you can't start blender just normally, no no that doesn't work) and when blender crashes it nukes my terminal as well. And then I have to reload the stupid model. And then I have to do what I'm trying to do hoping it doesn't crash. And then it crashes anyway
rant
blender
fuck you