Forums Technical Discussion [Possible Bug]DAE Import - Windows vs OSX?

[Possible Bug]DAE Import - Windows vs OSX?

   1642   1   0
User Avatar
Enivob
Member
2529 posts
Joined: June 2008
Offline
 
Hi All,

I have been working on a python based tool and have it in pretty good shape on Windows. I thought I would give it a try on OSX and now it appears to be broken.

What would cause a script to produce different outputs on different OS's using the same inputs? (i.e. the DAE file and it's textures)

PS: I updated to the latest daily build on OSX just to make sure it was not an old bug, but the results were the same, a bad import.
Edited by - Dec. 13, 2014 10:23:02

Attachments:
bad_import.png (965.0 KB)
good_import.jpg (124.7 KB)

Using Houdini Indie 20.0
Ubuntu 64GB Ryzen 16 core.
nVidia 3050RTX 8BG RAM.
 Report
User Avatar
Enivob
Member
2529 posts
Joined: June 2008
Offline
 
I think this might be an actual True bug. I took my python script out of the equation and just imported the DAE file using the standard File/Import and the same thing happens. It works fine on Windows but Fails on OSX.

The problem seems to be related to the transformational matrix of certain parts of the subnetwork.

I am attaching the problem DAE file if a developer or anyone has a chance to confirm.

Attachments:
problem.dae.zip (280.5 KB)

Using Houdini Indie 20.0
Ubuntu 64GB Ryzen 16 core.
nVidia 3050RTX 8BG RAM.
 Report
  • Quick Links