Hi,

not sure why did is so hard or what I do wrong, but I couldn't find any info anywhere. 

1.) Sculpted a custom character (OBJ)
2.) Uploaded to Mixamo 
3.) Exported an animation as FBX
When importing into Daz3D, all hell breaks lose.I can neither see the character, nor is the animation working. But when importing into Blender everything is working propertly. 
Can someone help out? 

George
PS: I really like the way Daz3D renders, that's why its my preferred software for rendering animations
 

You have a template at

\DAZ\MyRenderosity Library\Templates\CCox\80s Rad Swimwear\80s Rad SwimwearUVs.png

Load this into a layered graphics editor like gimp or photoshop.

Create a new transparent layer above that template and import the logo and place it where you want it to be.

Delete the layer with the template. Create a new layer under the logo - layer and fill it with the color you want the rest of bottom surface to have.

Export as .png and load into the base color slot.

You should be done.

Again, did you check the strands orientation ? You may post a picture of the hair uv map.

Some PAs may use mixed strand orientations within the same hair style. If this is the case you have to check the uv map and separate the hair by strand orientation before converting. In general a good conversion to particle hair is not straightforward you have to spend time on conversion, optimization and strands editing. Unless the hair is SBH or dforce that will come the same as daz studio. So you may end up using the mesh hair if conversion to particle is not practical for this specific hair style.

update.

Just tried and I can't reproduce the issue, it works fine here. The wild loop is top-down so no need to change anything. I also added a note in the wiki to explain better what strand orientation is. Be sure to update to 1.7.2 since there's many bug fixes.

https://bitbucket.org/Diffeomorphic/import_daz/wiki/Setup/Hair/Make Hair

steps:

1. import G8F with wild loop
2. merge rigs
3. separate the scalp
4. convert thair
5. pose the figure

p.s. It is possible that you selected the figure instead of the scalp for the hair conversion, in that case the hair follows the figure pose and deformations happen as in your picture. You have to separate and select the scalp, not the figure.

I don't ever want to sign in inside Daz Studio, unless it has an option to disable automatic metadata updates and Daz Connect installation.

Oh yes, fiber mesh stuff can make DS crawl, too. 

A 13700 is perfectly fine. There really isn't much you can do from a hardware standpoint. Software is the bottleneck. You can try some of the display options Zarcon mentioned, but all of the lag is coming from what you have in your scene. Dense mesh can do it, even without textures, it depends on what sort of mesh it is.

You can always hide things in the scene tab until you are ready to render. Hide the denser mesh objects. Maybe even just hide hairs in general. Some Daz hairs are very heavy even if they are not mesh based. If you didn't know, you can hide everything parented to an object by holding down CRTL when hitting the button to hide it. This makes hiding and unhiding stuff a lot easier. So you can hide a character and all of their clothes and hair with just one click. Some 3rd party content can be very unoptimized and problematic in DS. If something is not rigged properly, that can cause some issues in a scene. This goes back to what I said above, it depends on what the mesh is. If this mesh was like quickly converted from some other software it may not be optimized for Daz.

If importing stuff into Daz, you can try reducing the poly counts before import and making it so the object can be subdivided in Daz at render time rather than the viewport. Daz also has a product called Decimate, though I have not used it in forever and forget how to use it. I don't even know if Decimator still works, if you are interested in it, you can search for some forum topics on it (in you favorite search engine, not the forum search.)

And again, smoothing can be performance killer. A lot of Daz products have smoothing enabled by default. It is worth looking to see if any items have it.

You could in theory export a hi-res Base figure from DS into Blender and then re-import the .obj and transfer the rigging from the original figure, essentially giving you a higher res version of your DS figure that you could try to import the morph target within DS

Or you could try to export the High Res figure into Blender, add subdivision or anything else you might need then sculpt your morphs and export the whole thing as a Collada file or an FBX file along with the created shapekeys (morphs) which means if you re-import the DAE or FBX into Daz Studio you will get a figure shaped prop with morphs included which you could then try to rig using the Transfer Utility (at least as a starting point) 

Another option (the non free approach) is exporting to Blender, adding subdivisions and sculpting, then exporting the end result and use a software like Wrap3DS (not free) and project your HD morph to the Genesis (or any figure you're working with) from the High Resolution mesh so you can use Morph Loader normally

ok uuh i used echo 8.1 with oot wild loop tail hair on this one, exported them to blender using diffeomorphic imported into blender using the import daz button,then i merged rigs, seperated the scalp from the hair and used the addon to convert the hair,added a pose to the caracter and that happands.

Geometry nodes don't always work fine they are experimental thus removed from easy import. But you can always do it by hand with the standard menus.

In daz studio hairs are figures so they may have morphs and jcms for posing. If this is the case you can import them as custom morphs or via daz favorites with easy import. Otherwise you can do an example of a specific hair that doesn't work with exact steps to reproduce the issue.

Light shedder, sometimes shredder lol ... okay, to import .obj files into D/S with textures:

1. name the .obj at export "one word" with no spaces or weird symbols, "-" "_" are okay. It's not that the name of the .obj matters so much as the name of the .mtl file. If one needs to edit the name of the .mtl file, be sure to rename it inside the .obj file, near the top of the codes. Have the export packaging up the textures AND the .obj to the SAME folder. This should import into D/S with the textures applied.

If planning to save this as a D/S file, I would recommend having that texture with .obj file inside the desired destination folder for the textures: i.e. Main Content folder > Runtime > textures > your handle > subfolder. Then you won't have to put them there and reapply them inside D/S so it can find them all.

n.b. "shaders" are program specific. If texturing with shaders, apply the D/S shader presets.

I have just begun my journey into importing stuff to Daz and trying to make them work inside the software. However, every model I import from Blender is always without textures, and I need to spend significant time putting the imported models "back together" so to speak. Now, I am not a technical guy when it comes to fbx and obj formats, or any format for that matter, but from what I understand, this issue appears to exist solely in Daz if I am not greatly mistaken...

So what I am wondering is if this is something Daz could improve upon in future updates. Or if someone who understands this stuff far better than me could shed some light on me whether I am asking impossible and why that is.

I would love to see a day when I can import stuff to Daz and start using them right away without having to retexture them. Resizing I can manage, but sometimes importing environments can have dozens and even hundreds of assets in them, thus making the retexturing process somewhat of a nightmare.

If you are knowledgeable about this subject, I would appreciate greatly someone to educate me about this subject to know if there are far better ways to import assets in Daz and still have all the textures in place.

Nope. Any mesh you import into DS needs to be rerigged

Hello guys, as I mentioned in the title, I am faced with a very strange problem. When I render with CPU it is very slow, any help suggestions?

This my options: https://imgyukle.com/i/r15fwc

And here it is my video card LOG

2023-07-25 21:15:42.967 Iray (Scene Update) : Updating LPE labels

2023-07-25 21:15:42.968 Iray (Scene Update) : Updating geometry

2023-07-25 21:15:42.968 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Updating geometry.

2023-07-25 21:15:42.968 Iray (Scene Update) : Retrieving geometry

2023-07-25 21:15:42.968 Iray (Scene Update) : Updating motion transform data

2023-07-25 21:15:42.968 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Updating motion transforms.

2023-07-25 21:15:42.968 Iray (Scene Update) : Updating section objects

2023-07-25 21:15:42.969 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Importing scene graph.

2023-07-25 21:15:42.970 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Importing geometry for motion time 0

2023-07-25 21:15:46.978 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Geometry import (1 triangle object with 54 M triangles, 0 fiber objects with 0 fibers (0 segments), 1 triangle instance yielding 54 M triangles, 0 fiber instances yielding 0 segments) took 4.008 s

2023-07-25 21:15:46.978 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Updating section objects.

2023-07-25 21:15:46.979 Iray (Scene Update) : Updating materials

2023-07-25 21:15:46.979 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Updating materials.

2023-07-25 21:15:47.618 Iray [INFO] - MATCNV:RENDER ::   1.0   MATCNV rend info : found 265 textures, 0 lambdas (0 unique)

2023-07-25 21:15:47.625 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Computing 2 flux compensation factors took 0.001 s

2023-07-25 21:15:47.625 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Emitter geometry import (54 light sources with 2598 triangles, 1 instance) took 0.002 s

2023-07-25 21:15:47.626 Iray (Scene Update) : Updating volumes

2023-07-25 21:15:47.626 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Updating volumes.

2023-07-25 21:15:47.626 Iray (Scene Update) : Updating environment

2023-07-25 21:15:47.626 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Updating environment.

2023-07-25 21:15:48.636 Iray (Scene Update) : Updating lens data

2023-07-25 21:15:48.636 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Updating lens.

2023-07-25 21:15:48.636 Iray (Scene Update) : Updating lights

2023-07-25 21:15:48.636 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Updating lights.

2023-07-25 21:15:48.637 Iray (Scene Update) : Updating instance topology

2023-07-25 21:15:48.637 Iray (Scene Update) : Updating flags

2023-07-25 21:15:48.637 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Updating object flags.

2023-07-25 21:15:48.638 Iray (Scene Update) : Updating backplate

2023-07-25 21:15:48.638 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Updating backplate.

2023-07-25 21:15:48.638 Iray (Scene Update) : Updating portals

2023-07-25 21:15:48.638 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Updating caustic portals.

2023-07-25 21:15:48.638 Iray (Scene Update) : Updating decals

2023-07-25 21:15:48.638 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Updating decals.

2023-07-25 21:15:48.652 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Using iray core convergence estimate.

2023-07-25 21:15:48.652 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Allocating 1-layer frame buffer

2023-07-25 21:15:48.656 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Using batch scheduling, caustic sampler disabled

2023-07-25 21:15:48.657 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Initializing local rendering.

2023-07-25 21:15:48.658 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Available GPU memory has increased since out-of-memory failure. Re-enabling CUDA device 0 (NVIDIA GeForce RTX 3060 Laptop GPU)

2023-07-25 21:15:48.661 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Initializing OptiX for CUDA device 0

2023-07-25 21:15:49.588 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Rendering with 1 device(s):

2023-07-25 21:15:49.588 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : CUDA device 0 (NVIDIA GeForce RTX 3060 Laptop GPU)

2023-07-25 21:15:49.588 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Rendering...

2023-07-25 21:15:49.588 Iray [INFO] - IRAY:RENDER ::   1.10  IRAY   rend progr: CUDA device 0 (NVIDIA GeForce RTX 3060 Laptop GPU): Processing scene...

2023-07-25 21:15:49.589 Iray (Scene Access) : Retrieving geometry

2023-07-25 21:15:49.589 Iray (Scene Access) : Retrieving device geometry

2023-07-25 21:16:00.343 Iray (Scene Access) : Retrieving volumes

2023-07-25 21:16:00.344 Iray (Scene Access) : Retrieving textures

2023-07-25 21:16:21.452 Iray (Scene Access) : Retrieving device textures

2023-07-25 21:16:22.224 Iray (Scene Access) : Retrieving flags

2023-07-25 21:16:22.225 Iray (Scene Access) : Retrieving device flags

2023-07-25 21:16:22.226 Iray (Scene Access) : Retrieving lights

2023-07-25 21:16:22.237 Iray [INFO] - IRAY:RENDER ::   1.13  IRAY   rend info : Importing lights for motion time 0

2023-07-25 21:16:22.242 Iray [INFO] - IRAY:RENDER ::   1.13  IRAY   rend info : Initializing light hierarchy.

2023-07-25 21:16:22.269 Iray [INFO] - IRAY:RENDER ::   1.13  IRAY   rend info : Light hierarchy initialization took 0.026 s

2023-07-25 21:16:22.271 Iray (Scene Access) : Retrieving device lights

2023-07-25 21:16:22.271 Iray (Scene Access) : Retrieving section objects

2023-07-25 21:16:22.271 Iray (Scene Access) : Retrieving device section objects

2023-07-25 21:16:22.271 Iray (Scene Access) : Retrieving materials

2023-07-25 21:16:22.277 Iray (Scene Access) : Compiling custom code

2023-07-25 21:16:22.277 Iray (Scene Access) : Retrieving environment

2023-07-25 21:16:22.386 Iray (Scene Access) : Retrieving device environment

2023-07-25 21:16:22.483 Iray (Scene Access) : Retrieving backplate

2023-07-25 21:16:22.483 Iray (Scene Access) : Retrieving device backplate

2023-07-25 21:16:22.483 Iray (Scene Access) : Retrieving portals

2023-07-25 21:16:22.484 Iray (Scene Access) : Retrieving decals

2023-07-25 21:16:22.486 Iray (Scene Access) : Retrieving device decals

2023-07-25 21:16:22.489 Iray (Scene Access) : Retrieving motion transform data

2023-07-25 21:16:22.490 Iray (Scene Access) : Retrieving device motion transform data

2023-07-25 21:16:22.490 Iray (Scene Access) : Retrieving lens data

2023-07-25 21:16:22.490 Iray (Scene Access) : Retrieving device lens data

2023-07-25 21:16:22.599 Iray [INFO] - IRAY:RENDER ::   1.10  IRAY   rend info : CUDA device 0 (NVIDIA GeForce RTX 3060 Laptop GPU): Scene processed in 33.007s

Exactly how DS handles unsurported, seems to me to be guesswork. If there is significant difference on source and target I think it will fail, i.e. end up looking very wrong.

In order to use autofit you need a clone. I don't think that has been made.

You could take the clothing into a modeller and the fit to your new target and then import and use transfer utility.

I haven't tried resizing Pocket's costume, the concept would be to size it up etc., then export out the .obj [remember to hide everything else before exporting so only the garment exports], delete the garment from the scene, import in the resized obj and use the transfer utility to fit it to Horse 3. If it stays where you want it, then select it and save the file as Figure/prop to your own folders [i.e not the same folders as Pocket's outfit] so nothing gets overwritten.

Update: "concept": does not work with Horse 3

I am exporting daily and I don't get errors. I'm also using Blender 3.6 and I also use the updated OBJ import (not the legacy). As suggested - a screenshot of your settings might help.

Neither have I. I'm using Blender 3.6.1 Release Candidate and DS 4.21.1.48 Public Build. I just export OBJ from DS and import as Wavefront (.obj) in Blender. No errors.

Is it possible to import a static but rigged .fbx human character model from CGTrader into Daz? If so, what are the steps? When I import the model it comes in as a huge mess.

crosswind said:

Actually Hanfu (汉服) is pretty unique... Transfer Utility cannot well project it with proper weight even on a Base figure, especially in the areas of armpits (with long and wide sleeves), crotch (inner thigh), etc...

Opt1: Create projection template(s) base on typical Hanfu designs if you frequently make Hanfu(s), then use the template(s) in TU.

Opt2: Send it back to MD to re-simulation or fix it with Blender or Zbrush, etc. and import to Daz to update the Base geometry of Hanfu.

Besides, there're still some more tricks in the workflow from MD to Daz, depending on your expectation...

PS: As for the weird result from the poses, you better add dForce modifier and simulate it with a timeline or at least from memorized pose... and some pJCMs fixing have to be needed as well.

Thank you for your suggestion. It sounds like making Hanfu for Daz is really complicated. Perhaps I should start with some simpler clothes. Is there any place to purchase Hanfu project templates? By the way, what is pJCM? Forgive my ignorance.

I do backup. And I tried to import that cms into the daz system. Still having the same issue afterwards.