![]() ![]() ![]() However, blender’s algorythms produce cleaner results, as in this 90% decimation of the same model (left is slicer):Įxport to files works well for segments but that implies they don’t have any post-processing.Īnother problem from slicer’s obj write is exported colors get darker, for example R 255 G100 B 30 will become R85 G 33 B 10 (All values gets divided by 3), i had to script blender to revert it Other than those limitations the effect’s algorythms themselves are good in slicer, but it can be hard to dynamically find the best combination for a multitude of models. it is not possible to add a scripted reversible modifier stack then tune individual modifiers within the stack (modifiers in blender do not become definitively applied immediately and individually).It is not possible to dynamically (real-time) visualize the effect’s intensity on the 3d view with sliding a bar like with blender’s modifiers.It is not possible to undo the modifications.sometimes effects don’t work if a model made externally to slicer is loaded Models produced from slicer work fine though.there is a need to select models by name in the input/output section, there is no 3D view click to highlight the model (which is not necessary in slicer’s original purpose). ![]() Here are some limitations that i encountered with slicer’s surface toolbox: ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |