when i import my obj into daz it is not visible. its there becuase i can see the silouheete.
Shawn Giovanni Art
Posts: 0
i made an item in 3ds max and saved it as an obj, i imported it into daz but the item is invsible.. as i said in the title i know its there because the name of the item is in the scene and also i can select it. when i select it i see the silohuete of the itme. .but it is invisible. i tried to assign it the materials i saved out for it but still nothing
Title Edited by MOD for breaking Forum Formatting.
Post edited by Jaderail on
Daz 3D is part of 
Connect
DAZ Productions, Inc.
7533 S Center View Ct #4664
West Jordan, UT 84084
Licensing Agreement | Terms of Service | Privacy Policy | EULA
© 2024 Daz Productions Inc. All Rights Reserved.
Comments
You need to make sure its got a uvmap then it will show up...
Something else to try — the materials might be set transparent. Select the object after loading it, then look at the Surfaces tab and select the material names. What's the %age value of the Opacity parameter?
If you're using 3d max 2010, it exports .obj files with Opacity set to 0%. You need to set it in Daz Studio to 100%.
I've no idea why this happens, and I can't find a fix for it in the export options. If anyone has a solution, I'd be interested to hear it.
mac
Have you tried deleting the mtl file, assuming it isn't carrying otherwise useful settings? Not that an improvement over just resetting the opacity.
Have you tried deleting the mtl file, assuming it isn't carrying otherwise useful settings? Not that an improvement over just resetting the opacity.
I've tried everything, Richard. Deleting the .mtl file just means the .obj imports with no settings - so DS imposes Spec 153/153/153 and Ambient 51/51/51 - forcing me to apply a blank MAT to see it correctly. That's the same solution as having an invisible .obj - apply a blank MAT.
mac
Actually it does not need the UVMap, I test models I'm working in all day without UVMaps, they load fine. you only need the UVMap when your applying a texuture, otherwise surfaces can be used. I have seen some material settings be translated to Daz Studio as Opacity 0% which will show the silhouette of the model when you roll your pointer over the surface, but it will not show the model surface until the Opacity is turned back up. Maclean and Spotted already called it but I get this using Blender as well.
I haven't used 3D Studio Max since college, but I think this happens because Max uses Transparency where DAZ Studio uses Opacity.
You do want a 0% Transparency, which equals a 100% Opacity, and I suspect they are getting confused in the translation.
Why can't everybody just call it Alpha?
When I import an object to daz that I created in Poser, I have to bump up the import scale to at least a 1000 to get it closer to the proper size and visible.
Are you using the scale presets in the import dialog? There ought to be one for Poser, which should give you pretty much the same size as the item appears in Poser. Unless it was scaled up or down from 100% in Poser, which might throw the preset off.
Okay, I didn't look at those presets closely enough. I had always left it on custom and worked from there. Thanks for your help.
Check the .mtl file for a "d" or "Tr" parameter. if "Tr" is set to 0 you will have an opacity value of 0 on your surfaces tab. Try setting Tr to 1 and see if that fixes the opacity issue. If there is a "d" parameter and not "Tr" try setting that to 1, as well.
The UV maps will likely be part of a "map_Ka", "map_Kd", "map_bump", or "bump" parameters. The directories paths for these must be set correctly. Also, the parser does not like spaces in the texture names.
That was one of the first things I checked, and as you say, Tr is set to 0. But it's more time-consuming to edit the .mtl file than it is to apply a white MAT to the object. I have a white preset on my toolbar, so it's just one click. But in fact, I mostly use 3d max 8 anyway, and it works perfectly well on export, so it's not an issue for me.
mac
May have been few years ago but this fixed my issue so cheers :-D
Waaayyyy late here, but I experienced the same problem. I checked the object's cutout opacity...it was set to 0%. Put it to 100% and that fixed the issue.