Results 1 to 10 of 10

Thread: Obj exporter too slow

  1. #1
    Registered User Dennik's Avatar
    Join Date
    Jul 2003
    Location
    Winston Salem NC
    Posts
    202

    Obj exporter too slow

    I have a dense laser scanned object that I brought into modeler and tried to export back to OBJ format.
    The obj exporter is taking ages to save it. I'm talking 100kb per second speed on an SSD drive.
    I know it shouldn't take too long cause I've saved it from other applications as well.
    What's going on?

  2. #2
    TrueArt Support
    Join Date
    Feb 2003
    Location
    Poland
    Posts
    7,884
    OBJ exporter is storing indexes to vertexes and indexes to polygons (faces),
    so it has to convert internal LWPntID (pointer) to index,
    and internal LWPolID (pointer) to index.
    If functions of looking up points and polygons have not been optimized,
    the whole exporting tool will be very slow (and getting slower and slower with increasing amount of geometry).

    What is point and poly count of your object?

  3. #3
    Registered User Dennik's Avatar
    Join Date
    Jul 2003
    Location
    Winston Salem NC
    Posts
    202
    Its about 3.3mil polygons. About 1.6mil vertices.

  4. #4
    TrueArt Support
    Join Date
    Feb 2003
    Location
    Poland
    Posts
    7,884
    Maybe as a workaround try exporting it in some common file format, and then use 3rd party app to export from it..

  5. #5
    Registered User Dennik's Avatar
    Join Date
    Jul 2003
    Location
    Winston Salem NC
    Posts
    202
    Yep. I exported it already through STL. Lightwave has got me used to workarounds for decades now.

  6. #6
    I'm trying out Meshlab. Its free and also has import/export options. It has mesh optimizations/cleaning up, and uses the gpu to speed up things.

  7. #7
    Electron wrangler jwiede's Avatar
    Join Date
    Aug 2007
    Location
    San Jose, CA
    Posts
    6,471
    Quality matters. Few customers will tolerate endless "necessary" workarounds. Oh well.
    John W.
    LW2015.3UB/2018.0.7 on MacPro(12C/24T/10.13.6),32GB RAM, NV 980ti

  8. #8
    TrueArt Support
    Join Date
    Feb 2003
    Location
    Poland
    Posts
    7,884
    Quote Originally Posted by jwiede View Post
    Quality matters. Few customers will tolerate endless "necessary" workarounds. Oh well.
    During writing software you always deal with workarounds..
    Not talking about LWSDK. But generally.
    ...or maybe I am always dealing with nonstandard things, which authors of API didn't think about in advance..

    Workarounds on Android OS... entire code of app is just one big workaround..

  9. #9
    Electron wrangler jwiede's Avatar
    Join Date
    Aug 2007
    Location
    San Jose, CA
    Posts
    6,471
    Wavefront OBJ is among the oldest 3D formats out there, and still among the most-used. There's no acceptable excuse for any modern 3D pkg to lack efficient OBJ+MTL import/export, period.
    John W.
    LW2015.3UB/2018.0.7 on MacPro(12C/24T/10.13.6),32GB RAM, NV 980ti

  10. #10
    TrueArt Support
    Join Date
    Feb 2003
    Location
    Poland
    Posts
    7,884
    Quote Originally Posted by jwiede View Post
    Wavefront OBJ is among the oldest 3D formats out there, and still among the most-used. There's no acceptable excuse for any modern 3D pkg to lack efficient OBJ+MTL import/export, period.
    Efficiency is relative..
    With OBJ file format one desperate enough developer, could split parsing to separate threads and get ~8 times boost on 4 core (8 HT) machine etc. ..
    Obviously it would cost money.. money spend on programmer salary. The more often used functionality of app, the more import is optimization.
    How many times "average LW user" is loading/saving OBJ per day? Per month? Per year? I don't think so it is huge number.
    If I would be annoyed by speed of OBJ exporter, I would write my own OBJ exporter in this hour.

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •