Title: Easier to convert to .obj Post by: cyseal on December 06, 2015, 09:44:18 PM I tried to make and 3d object in Blender but I failed with voxel data technique.
Is it possible to make .obj without using other older software? Could you implement some technique to make it easier using only Meshlab or Blender? Thanks Title: Re: Easier to convert to .obj Post by: Sockratease on December 06, 2015, 10:01:33 PM I tried to make and 3d object in Blender but I failed with voxel data technique. Is it possible to make .obj without using other older software? Could you implement some technique to make it easier using only Meshlab or Blender? Thanks Hi cyseal. Have you tried FIJI? Blender is a great program, but notoriously difficult to use. You can also convert MB3D's Voxel Stacks to obj files using JWildfire's Mesh Generation feature. They both take some getting used to, and practice, but results are worth it! This bulb was created in FIJI from MB3D's voxels and rendered in Cararra: (http://i106.photobucket.com/albums/m278/sockratease/cowbulb_zpsbec7bc40.gif) Title: Re: Easier to convert to .obj Post by: thargor6 on December 06, 2015, 11:48:54 PM I tried to make and 3d object in Blender but I failed with voxel data technique. What exactly was your problem? What step was too complicated? Title: Re: Easier to convert to .obj Post by: cyseal on December 07, 2015, 05:53:15 AM What exactly was your problem? What step was too complicated? @Sockratease , @thargor6 Fiji has stopped working in the middle of the process. I tried it again over a day with small sample and nothing. Is it possible to update algorithm Fiji uses and implement it in MB3D? So, I'm looking a way to overstep the use of Fiji. Title: Re: Easier to convert to .obj Post by: Sockratease on December 07, 2015, 11:39:40 AM @Sockratease , @thargor6 Fiji has stopped working in the middle of the process. I tried it again over a day with small sample and nothing. Is it possible to update algorithm Fiji uses and implement it in MB3D? So, I'm looking a way to overstep the use of Fiji. FIJI often gives the illusion it has stopped working, but is in reality still doing things in the background. Often you have to just wait a while for it to finish writing the file. Have you gone back and checked again on any files that may have given the appearance of failing? Have a read through the Voxel Image Stack And Then What? thread for other people confirming this (sorry, a lot of the images I posted in there are lost from an old problem on the site I was hosting them). There are several options in there for the process. The thread is here : http://www.fractalforums.com/tutorials/voxel-image-stack-and-then-what/ Be aware that these will be HUGE files - often over 1 GB each (which is where MeshLab comes in for decimation) - so the extra lag time and appearance of freezing up are understandable. Good luck with it! Title: Re: Easier to convert to .obj Post by: thargor6 on December 07, 2015, 11:49:58 AM Fiji has stopped working in the middle of the process. I tried it again over a day with small sample and nothing. You should use for this step JWildfire instead, the results are almost the same, but it is much faster (because of multithreading) and gives more feedback, and you get a simple preview of the generated objectTitle: Re: Easier to convert to .obj Post by: Snicker02 on December 07, 2015, 06:03:52 PM @Sockratease , @thargor6 Fiji has stopped working in the middle of the process. I tried it again over a day with small sample and nothing. Is it possible to update algorithm Fiji uses and implement it in MB3D? So, I'm looking a way to overstep the use of Fiji. As thargor6 said JWildfire works way better than fiji for working with voxel stacks ...... I have done a tutorial on how to do this located here-- youtu.be/HP_zCyuMEao Title: Re: Easier to convert to .obj Post by: cyseal on December 08, 2015, 09:22:39 PM Thank you thargor,Snicker02 and Sockratease !
When importing voxel data and generating mesh in JW, is 4GB ram enough? Title: Re: Easier to convert to .obj Post by: JohnVV on December 08, 2015, 09:41:30 PM there is a blender plugin
https://github.com/NMEMine/BlenderFractals it is 2 years old and it dose run on the current blender 2.76 do to the calculations and mesh HUGE size this script takes a LONG time to run -- single threaded Quote Blender is a great program, but notoriously difficult to use. no harder than 3D Max or using Renderman it just takes time to learn just like The Gimp or Photoshop Title: Re: Easier to convert to .obj Post by: visual.bermarte on December 09, 2015, 02:37:47 PM In the past I have used Clemency to create 3D meshes.
http://www.fractalforums.com/3d-fractal-generation/opencl-marching-cubes-source-code-release/?PHPSESSID=f402997676de433ed96c55dd5158fa69 http://bit.ly/1YYuFv1 http://bit.ly/1REmKRs Title: Re: Easier to convert to .obj Post by: cyseal on December 09, 2015, 08:07:28 PM In the past I have used Clemency to create 3D meshes. I need to start it within cmd? How to set a path to voxel data? there is a blender plugin https://github.com/NMEMine/BlenderFractals Is it possible to implement whole MB3D as Blender plugin or renderer within Cycles or Internal ? Title: Re: Easier to convert to .obj Post by: thargor6 on December 10, 2015, 12:06:16 AM How to set a path to voxel data? As far as I understood the post (had no time to test the program yet) it not generates a mesh from a stack of voxels, but by evaluating an opencl-fragment which you have to create/adopt. Because it has this way some kind of the "formula", it may be much more clever than the standard MC algorithm which just works on a fixed grid size.At least the Mandelbulb as shape is supplied as example (mandelbulb.cl), you may start having a look at this. |