OBJ loading polygon order

  • I am writing a ptex importer and have a sneaky suspicion that the C4D OBJ loader does not maintain the order of the polygons as they are written in the file.

    Has anybody else come across this?

    I think I am going to have to write my own OBJ loader just to keep my own sanity about what is actually loaded and how the polygon object is created.

  • Cannot say it about recent versions but had exactly those troubles back in the day during production. We were using Riptide (IIRC) to import OBJ so that we could apply baked animation from point caches.

  • Thanks, everyone who takes part in this discussion.

    May I ask you in which version you get this issue? Because a similar bug was fixed in R17.
    If this bug is still valid for R20, could you please provide an obj that show the issue in order to create a proper bug report.


  • @kbar, @martinweber any news on that?

  • Hi Maxime,

    Sorry I have had no further time to look into this. Hopefully in the next few weeks. My issue was with R20. It was an obj from the Moana dataset. I expect the polygon indices to match up with the same values within the ptex files, but it doesn't look like they do. I will need to investigate further to determine if it is the OBJ loader or not. But since people have indicated issues before that does fit with what I am experiencing. The OBJ file format has many different paths regarding how it could be loaded and interpreted. So it doesn't surprise me if one of these paths doesn't respect the polygon order.


Log in to reply