Why does DS ghost the .obj files?

I have many .obj files (with materials).

I can import them into Hexagon, Blender, ZBrush, and other apps without problems.

When I try to import into DS, I can't. The files are ghosted no matter which format is chosen at the bottom.

 

I can go from DS to Hexagon and back to DS, so I thought I could work around the .obj problem by loading the .obj into Hexagon and sending to to DS, but nothing happens when I tell it to go to DS.

 

Why is DS the only app that doesn't recognize these files and what do I do to import them?

Comments

  • fastbike1fastbike1 Posts: 4,078

    I've never had a problem w/ .obj files.

  • Do you use object files created by Maya or Max?

  • AscaniaAscania Posts: 1,855

    No problem importing them here. Do you import to the correct size?

  • Lothar WeberLothar Weber Posts: 1,611
    edited December 2019

    Try to change normals in a program like blender. Many internet OBJ seem to hassle with daz in their origin format. 

    Post edited by Lothar Weber on
  • jpetersen1jpetersen1 Posts: 148
    edited December 2019

    I can't import them because they are ghosted. They cannot even be selected.

     

    DS doesn't recognize them as object files. All the other programs do.

    Post edited by jpetersen1 on
  • Are you using MacOS Catalina, by any chance? There is a known issue with file import that has been fixed in the Beta version of 4.12.
  • I haven't upgraded to Catalina. I'm allergic to OS updates (I've invested in a huge library of expensive graphic apps and I don't want them to break, nor do I want to spend thousands more to upgrade them all) so I am still using Mojave.

  • ChoholeChohole Posts: 33,604

    I haven't upgraded to Catalina. I'm allergic to OS updates (I've invested in a huge library of expensive graphic apps and I don't want them to break, nor do I want to spend thousands more to upgrade them all) so I am still using Mojave.

     

    Rob says
    That does not mean you should not try the Public Build to see if it resolves the issue. Catalina (10.15) is known to have the issue, and the Public Build is known to fix it on Catalina. If a late update to Mojave (10.14) caused a similar issue in it (which is possible), and it hasn't been encountered/reported, then the fix in the Public Build may also resolve it there. Point being, absolutely no development will occur on earlier versions of the application - the *next* version is the only version that will be worked on, and the Public Build is a preview of said next version, so try it out to see if it resolves the issue for you and report the issue if it doesn't.
Sign In or Register to comment.