I just stumbled across an inconvenience for a rendering some weeks ago, where I wanted to export models with more than 10k parts. My goal was to render on my GPU (which incredibly worked :D), and had found that beyond a certain triangle amount my GPU would run out of VRAM. So I found myself importing several models into Blender just to get to know their triangle counts, and for every import into Blender with the Advanced add-on takes a mere 30 seconds per model, I found myself waiting a pretty long time just to get the triangle counts.
TL😉R: I would really like to have a geometry statistic within the workshop, which states the amount of triangles and/or faces (and maybe vertices and edges) for the current model, similar to how Blender does it in the info panel. That should be quite easy to implement from my POV, and would help some poeple (or at least me) out for some projects. And it's a nice geek function! 😎
I will update the Advanced add-on for Blender 2.80 when it will be released and the import time will be greatly reduced.
What you suggest would be a nice to have feature. Not just a 2 second implementation as I'd need to keep track of the changes to avoid recalculating the whole thing every time something happen in the viewport.
@Scrubs
Well, it could be a function you have to update in order for it to calculate the tris/faces/vertices/edges. That way it won't update all the time and you won't have to struggle with it too much. Thanks for reading through by the way, and looking forward to the update! 😃 👍
Just thinking out loud. The stats given in the viewport would not include the LEGO logo on studs. So exported model data would be slightly different.
@Scrubs
Just thinking out loud as well, for I'm not the creator of MB and have no clue how the exporter brings in the logo meshes into the file (me coding noob :P): If the geometry statistic function would be a feature the user has to update, it could receive the information about how many stud logos are in the scene from the exporter code and then add the amount of geometry data of the logo multiplied by the number of stud logos in the scene to the amount of geometry data without stud logos. At least if the exporter actually counts how many logos are in there, I dunno, maybe the stud logos get positioned by pivots or there are extra files for them which we don't even see. 😕
So "geometry statistic without logo" + ("geometry data of logo" * "number of logos in the scene [by exporter?]"), something like that would come in my noob mind (IF the exporter/any code knows about the number of stud logos of course). Also, if a function like this would make it into the workshop at all, it would be nice to have a statistic for either with or without logos, to be able to compare them, or - if stud logos are unable to count - at least without logos. 😃
LEGO, le logo LEGO, la minifigurine et les configurations des briques et tenons sont des marques déposées de LEGO Group of Companies. ©2024 The LEGO Group.
Mecabricks, le logo Mecabricks et tout le contenu non couvert par les droits d'auteur du groupe LEGO sont, sauf indication contraire, ©2011-2024 Mecabricks.