Lee Johnson

Well this is weird.

I fixed it not showing up by taking it back into meshmixer, recentering and saving it again.

That says it wasn't my hardware all along, but somehow the way in which houdini loads objects ?

Its no longer ‘ not responding’ anymore, it loads at least, so thats a good first step.

I didn't know until just now , literally

Taking note for future refernce of your above comment.

Enivob
I can load your file on my Windows machine with nVidia GTX 2GB vRAM and on my MacMini using HD4400 with only 1.5Gb vRAM.

What is going on is the OBJ is so large that viewport clipping is removing it entirely from display. So it looks like the File node did not load anything.

Press the D-KEY to bring up the display options and activate the Viewport TAB. Set the clipping to Neither Clip Plane and crank up the far clip value. I set mine to 18,000 and the OBJ appeared in my viewport.

Or scale it down to a smaller size as Michael mentioned.

I"m afraid I can't even do that right now, as HOudini wont' respond at all ( says not responding in top frame of UI ), and I tried letting it go for a very long time , but I stopped it after 30 or so seconds, as it was taking up around 80% CPU .

Is it likely it would create a crash report after I purposely closed it ?

Not finding any houdini files in TEMP folder so unless I know for sure where to look I can't get that information ( assuming there is any, given Houdini didn't officially crash )

Artye
It's probably your graphics card ram causing issues. That mesh hits ~2.6gb Vram usage when editing full screen on a 4k monitor. It's totally smooth to work with on Nvidia 980, OsX.

No, its not my hardware. This mesh loads just fine in all other 3d apps , even blender which atm is dog slow in edit mode due to OLD gl code usage