Hello sometimes I use a workflow where I will make an initial base mesh using Curvy 3D and then continue in either ZBrush or Blender. More recently I have been using Blender to block things out but occasionally I will go back into Curvy to add shapes with the tools there because I like the simplicity of them.
It is very good that my scene matches up when I re-import objects back into Blender. One thing I was wondering about though is the performance of Curvy 3D (I am using the Beta 6 version) regarding imported geometry from Blender.
I find that with larger meshes it can load them in very slow or even crash if they are too big. Can you give me a guideline on the sort of polycount that is a good idea to decimate a lower res reference mesh in this process please.
Curvy_Z7CBLSD3iY_smaller.jpg (70.34 KiB) Viewed 70 times
Thanks for raising this. In my workflows I mostly export high poly from Curvy, not import, so I have not seen this sort of crash. I'll need to do some testing. In general less than 100k is a fairly small model and should work fine, I'd guess issues might come up with over a million polies - what size are you trying to import?
The object(s) in this screen shot took around 1minute 40 seconds to import into Curvy. Once imported the program worked fine for adding new objects (toes mainly in this case). The size of the object is 39.6 MB. Quite a bit larger than 100k.
I admit I probably could have reduced the size quite a lot if I had created a lower res mesh but I had reduced it quite significantly from a file I tried prior to this which didn't load (or might have done but obviously waiting more than 2 minutes is a bit too much on the "did it crash" scale in my mind).
This is a screen shot of the file in Blender that was 39.6 MB. showing the vertex count for you.
blender_HCVC31NAD6_smaller.jpg (47.34 KiB) Viewed 63 times
I run a pretty expensive process on OBJ import that merges parts that share vertices (This was important for importing segmented models) but is probably not needed if you have a single continuous model.
The cost of merging goes up with the size of the model and could certainly look like a crash because it takes so long - just leaving it a few minutes might work.
I could add a choice somewhere of whether to merge of not when importing.
OK thanks I understand. I think it works OK for my needs- usually if I am going between Blender and Curvy I am still in block out stages so I can always make a lower res merged placeholder for use in Curvy if I have to. Whether or not you add the choice of merging that is of course up to you I am OK with it either way- I could always merge everything in Blender first to save the computational step Curvy has to go through.