1. Are there any better alternatives to creating parts over PartDesigner? Namely, PartDesigner has issues when processing models of very high face counts, and it seems to attempt to apply some sort of geometry modifier on import, which when combined with what I presume to be similar modifiers passed upon starting a photorealistic render, results in models looking... iffy, to say the least.
   
2. Is there a relatively simple way for modelers in Blender, Fusion360, and other programs who are accustomed to making parts for 3d printing to apply primitives to things like axles, studs, and pin holes? A big problem when working with these models is the lack of consistency between the connection points of parts, so this would definitely be a huge step forward if a (relatively) painless solution exists.
   
3. Since a majority of our community uses Stud.io for building and rendering their Bionicle MOCs due to ease of use, is there anything you have learned about Stud.io that we may have not?
   

(2022-04-01, 2:07)Violet Barrett Wrote:

1. Are there any better alternatives to creating parts over PartDesigner? Namely, PartDesigner has issues when processing models of very high face counts, and it seems to attempt to apply some sort of geometry modifier on import, which when combined with what I presume to be similar modifiers passed upon starting a photorealistic render, results in models looking... iffy, to say the least.
   
2. Is there a relatively simple way for modelers in Blender, Fusion360, and other programs who are accustomed to making parts for 3d printing to apply primitives to things like axles, studs, and pin holes? A big problem when working with these models is the lack of consistency between the connection points of parts, so this would definitely be a huge step forward if a (relatively) painless solution exists.
   
3. Since a majority of our community uses Stud.io for building and rendering their Bionicle MOCs due to ease of use, is there anything you have learned about Stud.io that we may have not?
   

1. Most of us use LDparteditor to create LDraw parts (https://nilsschmidt1337.github.io/ldparteditor/). Fair warning: powerful, but steep learning curve (and scarce documentation to say the best). Unfortunately you will still need PartDesigner to add connectivity/process collision...
   
2. Fredrik Hareide is working on such a tool (https://forums.ldraw.org/thread-24153-post-45043.html#pid45043). But that's a complex project, don't hold your breath
   
3. I do agree that Studio is great for rendering or creating building instructions, but for model building it's a big meeehhh for me... Especially for Technic building I prefer a lot LDCad. Caveats: "the best tool is the one you know how to use" and "doesn't solve the lack of Bionicle parts"!
   

(2022-04-01, 7:11)Philippe Hurbain Wrote:

1. Most of us use LDparteditor to create LDraw parts (https://nilsschmidt1337.github.io/ldparteditor/). Fair warning: powerful, but steep learning curve (and scarce documentation to say the best). Unfortunately you will still need PartDesigner to add connectivity/process collision...
   
2. Fredrik Hareide is working on such a tool (https://forums.ldraw.org/thread-24153-post-45043.html#pid45043). But that's a complex project, don't hold your breath
   
3. I do agree that Studio is great for rendering or creating building instructions, but for model building it's a big meeehhh for me... Especially for Technic building I prefer a lot LDCad. Caveats: "the best tool is the one you know how to use" and "doesn't solve the lack of Bionicle parts"!
   

1. I'll have a look at that! Part of the issue is that Bionicle parts, being as they are, are not exactly friendly to the types of processes designed to make bricks.
   
2. That's definitely going to be tricky to get people on board with, but I may be able to start bothering people about it! I'll definitely look into that, and see if I can start learning something about this.
   
3. Keep in mind that the average Bionicle digital MOCist is not the average Lego or Technic MOCist - there's a high need for easy building, posing, and rendering, which LDCad is not necessarily designed for. The usual user who does the kind of stuff that the Biopack is made for is not likely to use other LDraw programs, and if they do, it's more of a means to an end than anything else. 
   

1. Is it possible to add new primitives without extending the LDraw spec? A number of Bionicle parts have a consistent attachment point - the stud for mask connections in the first few years - that differs from the usual stud connection. Could a primitive be added to a LDraw program that's not a part of the official spec and read properly, even if only in that program?
   
2. Are there any tools or recommendations to optimize .dat filesize in the meantime, without introducing primitives?
   

Quote:Max Murtazin



Oh, hi Voot, long time no see
If you are going to work on Biopack parts, better contact me somehow, I am already up to dealing with some of that and making them into LDraw

(2022-04-01, 18:46)Violet Barrett Wrote:

1. I'll have a look at that! Part of the issue is that Bionicle parts, being as they are, are not exactly friendly to the types of processes designed to make bricks.
   
2. That's definitely going to be tricky to get people on board with, but I may be able to start bothering people about it! I'll definitely look into that, and see if I can start learning something about this.
   
3. Keep in mind that the average Bionicle digital MOCist is not the average Lego or Technic MOCist - there's a high need for easy building, posing, and rendering, which LDCad is not necessarily designed for. The usual user who does the kind of stuff that the Biopack is made for is not likely to use other LDraw programs, and if they do, it's more of a means to an end than anything else. 
   

(2022-04-01, 18:46)Violet Barrett Wrote:

1. Is it possible to add new primitives without extending the LDraw spec? A number of Bionicle parts have a consistent attachment point - the stud for mask connections in the first few years - that differs from the usual stud connection. Could a primitive be added to a LDraw program that's not a part of the official spec and read properly, even if only in that program?
   
2. Are there any tools or recommendations to optimize .dat filesize in the meantime, without introducing primitives?
   

(2022-04-01, 19:19)Orion Pobursky Wrote: If you are looking to get into authoring, there are quite a few Constraction/Bionicle parts on digital-bricks.de that haven't been processed for the library. Note that these pulls from LDD are quite rough and may require extensive editing to get to Library standards. You are right in that Constraction/Bionicle are are not easy to model, hence the conspicuous absences of these parts from the library.


For primitives, if you can make a case for a need, pretty much anything goes.
For optimization tools, have a look at DATHeader. It's the tool most of us use to combine triangles into quads.

(2022-04-01, 18:46)Violet Barrett Wrote: Keep in mind that the average Bionicle digital MOCist is not the average Lego or Technic MOCist - there's a high need for easy building, posing, and rendering, which LDCad is not necessarily designed for. The usual user who does the kind of stuff that the Biopack is made for is not likely to use other LDraw programs, and if they do, it's more of a means to an end than anything else. 

(2022-04-01, 19:37)Violet Barrett Wrote: The issue is the fact that a lot of high quality parts exist already, but having been traditionally 3d modeled, are not up to spec with LDraw. Is there a way to take these models and introduce primitives where connection points exist without remodeling the whole thing?

Also, I'll definitely want to raise a few questions regarding the next spec revision. Apologies if this is a stupid question, but where can I go to propose additions to the standard? I'm new to this forum, and having a bit of a tricky time navigating it!