anyone have a problem where i3d files keep crashing Houdini?

For this case, nope.

Hey, is this tecnique not an legal or prefered one?

As it is mentioned, 504 can write the i3d files without a problem, but no luck whit the ones that are upper, including last production build.

I am asking this question, if this is a proper way of doing this, because, it seems there is no proceeding on sesi side, to fix this.

Has anyone logged a reproducible bug?

http://www.sidefx.com/index.php?option=com_forum&Itemid=172&page=viewtopic&t=15604 [sidefx.com]

Hi I did log the bug and has been fixed now latest build

Sorry to say bug still exists with mac vers 11.0.775 production build.

I'll try the rop rebuild fix… <crosses fingers>
:roll:

Seems like I just hit this same bug. Im running the production build of H11.0.775. on Win 7 x64. Im going to run a few more tests to make sure its not me doing something wrong.

Ive recreated the geo2i3d1 node as suggested, and ive completley rebuilt the eintire networks from scratch twice now, and still this is happening.

I apologise for the necro post, but this was the most valid thread whilst searching.

Edit: Perhaps I should have tried the daily build first…

Hi,

I'm also having the same issue with the export of the i3d files. Even tried viewing them via an iso-offset - nothing. I have examples of working i3d files that work fine within both the context of the cvex vop net for this particular tutorial, and also when viewing via an iso-surface node - but H11.581 will not export the i3ds correctly. Quite frustrating. Have tried rebuilding the geo2i3d node, but to no avail. Very vexing!

Hi,im a lil bit late,and im having this exporting i3d problem….(using the i3d file supplied here works)…whats the solution?

Having this problem on Houdini 12. I've added a sample file that reproduces this, on my machine at least.
Any idea what the problem is, or is it the workflow? Is this not the correct way to produce or use i3d files?