Thu, Nov 14, 1:56 PM CST

Renderosity Forums / DAZ|Studio



Welcome to the DAZ|Studio Forum

Forum Moderators: wheatpenny Forum Coordinators: Guardian_Angel_671, Daddyo3d

DAZ|Studio F.A.Q (Last Updated: 2024 Nov 14 2:47 am)



Subject: strange import obj question


mtone ( ) posted Thu, 13 July 2006 at 8:29 AM · edited Sun, 28 July 2024 at 8:11 PM

I have a .obj model created from scratch.  I load it in DS and it loads OK.  I send my model over another person through email and the person can't load it in her DS (the person can't see it).

The strange part is that the model that is sent is 2.88 MB and she tried to re-send me what I sent to her and I recieved the model as 2.96 MB.  The file that I sent and the file that I recieved are not in a zip file.

Anybody had this problem before?


RHaseltine ( ) posted Thu, 13 July 2006 at 9:41 AM

Try zipping the OBJ file up - email does not preserve some formats, I suspect OBJ is one of them


mtone ( ) posted Thu, 13 July 2006 at 10:38 AM

I tried sending her a zipped version too and she still has the same problem.


RHaseltine ( ) posted Thu, 13 July 2006 at 2:37 PM

Are you both using the same version of D|S? Have you both done virus scans (file sizes changing is alarming)?     


HibernatusR ( ) posted Sat, 22 July 2006 at 10:10 PM · edited Sat, 22 July 2006 at 10:11 PM

Also check that she isn't importing the object with a scale of zero. If so it will be listed on the scene tab, but would be invisible and impossible to rescale.


Star4mation ( ) posted Tue, 08 August 2006 at 10:58 PM

Tell her to check the scale and also to make sure in the surfaces tab that Ambiant is set to black and not white. This happend to me once a very tiny invisable obj :)

If it ain't free, I can't afford it.


Privacy Notice

This site uses cookies to deliver the best experience. Our own cookies make user accounts and other features possible. Third-party cookies are used to display relevant ads and to analyze how Renderosity is used. By using our site, you acknowledge that you have read and understood our Terms of Service, including our Cookie Policy and our Privacy Policy.