Different results on Mac and Windows platforms reading .3ds files

Different results on Mac and Windows platforms reading .3ds files

tim
Participant Participant
527 Views
2 Replies
Message 1 of 3

Different results on Mac and Windows platforms reading .3ds files

tim
Participant
Participant

We're using the FBX SDK, version 2019.2, to read 3ds files into Rhino.  Both platforms share the same source code as well.  I have an example .3ds file, attached, where Windows reads it OK and Mac does not.  Several objects are transformed wrong and a few are missing. As I watch in the debugger I also notice that the Windows platform gives me 11 children on the root node and one of them has 2 children, whereas Mac gives me 13 on the root node and none of them have children.  Is there any chance you could have a look at this file and see why it's reading differently between the 2 platforms?  Thanks.

 

Tim

0 Likes
528 Views
2 Replies
Replies (2)
Message 2 of 3

regalir
Autodesk
Autodesk

Hi,

 

I know why sub02 is not a sibling of sub01 ! The first time the code looks for the parent ($$$DUMMY.ArchInter9) of sub01, it succeed. However, when processing sub02, the parent is now $$$DUMMY.ArchInter9\001\001". It looks like some memory shift/overwrite when compiled on MacOS. 

 

This may be a compiler "thing" and may take some time to pinpoint the exact cause. Considering that the code was written only for Windows long time ago, it is possible that some code statements are not compatible with modern compilers.

 

0 Likes
Message 3 of 3

tim
Participant
Participant

Thanks for the response.  I realize it may take some time, but is it safe to say that you guys are going to look into it and possibly fix it for future revisions of the SDK?

 

Tim

0 Likes