step open edges and sewing crash

[kimgar]

hi!

i am very keen on finding a way to incorporate the translators in our workflow, but it is hard to convince the others since i'm having a lot of trouble making them work.

i'm using the latest demo on max 2009 x64, and i'm trying to import a step file that is generated from inventor. there seems to be a problem with open edges, it comes in like this :

http://www.kimgar.com/_files/npower01.png

so, i tried importing as 'single nurbs brep - sew trimmed surfaces' it imports ok, but max crashes instantly when i switch from wireframe to shaded or even flat shading. it also crashes if it is merged into a scene with shaded surfaces in viewport. and most important, it crashes on render...

i am new to the translators, is there some setting i could try out?

[PiXeL_MoNKeY]

You could try importing and then combining/sewing the object(s) using Pwr_Join.

-Eric

[nPower_Dave]

Originally Posted by kimgar

hi!

i am very keen on finding a way to incorporate the translators in our workflow, but it is hard to convince the others since i'm having a lot of trouble making them work.

i'm using the latest demo on max 2009 x64, and i'm trying to import a step file that is generated from inventor. there seems to be a problem with open edges, it comes in like this :

http://www.kimgar.com/_files/npower01.png

so, i tried importing as 'single nurbs brep - sew trimmed surfaces' it imports ok, but max crashes instantly when i switch from wireframe to shaded or even flat shading. it also crashes if it is merged into a scene with shaded surfaces in viewport. and most important, it crashes on render...

i am new to the translators, is there some setting i could try out?

It looks like there may be a tolerance issue. Try increasing the tolerance and see if it will sew the whole thing together. But regarding the crash after forcing the sewing, could you send us the import file (or the model)?

[PiXeL_MoNKeY]

I wonder if this is related to the crashes I was getting, I think with STEP and SW in 64bit. I think you resolved it in one of the latest customer updates, and the demo is only at version 5.10.

-Eric

[nPower_Dave]

Originally Posted by PiXeL_MoNKeY

I wonder if this is related to the crashes I was getting, I think with STEP and SW in 64bit. I think you resolved it in one of the latest customer updates, and the demo is only at version 5.10.

-Eric

Eric, I think you are correct. We'll have to post the 5.3 demo version up on the download page.

[PiXeL_MoNKeY]

Looks like the 5.3 demos are available, but the links haven't been updated on the demo page. To get the 5.30 demo:
1) Copy the path to the version you need
2) Replace the 64Bit_R510_Demo.exe in the path with 64Bit_R530_Demo.exe

Then you should be able to download the latest version of the demo.

-Eric

[kimgar]

thanks for the link pixel, but unfortunately it didn't help, max still crashes on shading/rendering. and increasing tolerance values still produces the open edges

as usual i can not distribute the model, but i will try and recreate the issue and send something over

[kimgar]

ok, that was a bit harder than expected, but i managed to do some cutting in inventor and isolate the problem. i've sent dave a PM with download for step and max files.

thanks alot for having a look at this

[nPower_Dave]

Originally Posted by kimgar

hi!

i am very keen on finding a way to incorporate the translators in our workflow, but it is hard to convince the others since i'm having a lot of trouble making them work.

i'm using the latest demo on max 2009 x64, and i'm trying to import a step file that is generated from inventor. there seems to be a problem with open edges, it comes in like this :

http://www.kimgar.com/_files/npower01.png

so, i tried importing as 'single nurbs brep - sew trimmed surfaces' it imports ok, but max crashes instantly when i switch from wireframe to shaded or even flat shading. it also crashes if it is merged into a scene with shaded surfaces in viewport. and most important, it crashes on render...

i am new to the translators, is there some setting i could try out?

Hello Kimar,

Thanks for sending me the files. I was able to quickly import the file, change to different display settings (shaded, wireframe, etc.). I also rendered it (see the email that I sent you) in several orientations. I'm wondering if maybe you haven't turned off the steering wheel tool (see our FAQ page), or something like that. Try all of the suggestions that we make there from the "start up screen". Maybe your graphics card is the issue. But I don't have any problems at all with your model.

[nPower_Dave]

Originally Posted by nPower_Dave

Hello Kimar,

Thanks for sending me the files. I was able to quickly import the file, change to different display settings (shaded, wireframe, etc.). I also rendered it (see the email that I sent you) in several orientations. I'm wondering if maybe you haven't turned off the steering wheel tool (see our FAQ page), or something like that. Try all of the suggestions that we make there from the "start up screen". Maybe your graphics card is the issue. But I don't have any problems at all with your model.

Kim,

Here's a little more information that might help. Your model is an assembly. You shouldn't use the "import as single brep" anyway on that model because it should actually be separate parts. So chosing that option isn't a good idea on an assembly. What you can do is import using the standard options, then select the assembly, and click on the "EXPLODE" button, then delete the original assembly. That will give you a flattened hierarchy (with separate parts). Then you will see that only one of the parts is actually not sewn together. You can select that part and click on the "Join All" button. This will take a while, but it will result in sewing it together into a single element. However, you will still have 6 volumes and a bunch of Open Edges.

[kimgar]

hi!

and thanks for a swift reply! all is ok at your end? even the max file? my steering wheel is definately off, i've got a quadro gfx card with maxtreme drivers, i'll try directX and proper units. i won't be back at work until monday, but i'll follow the faq then and see if i can find a solution - in the meantime have a good weekend!

[PiXeL_MoNKeY]

Make sure you have the service pack, this address the View cube/Steering Wheel issues most users were running into. I personally would highly reccommend against the maxtreme drivers, in the past when I have tried them they have been extremely buggy with just Max let alone the constant updates thrown by the nPower tools. I would definitely give directx or opengl a try. Beyond that I have had no crash issues with 64bit, directx cache, viewcube/steering wheel, and imports with the latest release (5.30).

Hope that helps some,
-Eric

[kimgar]

ok, i've followed all the tips i could find, turned off degradation culling and use cached d3d meshes. renamed autcam.gup to make sure. drivers changed to opengl/direct3d but still no go.

taking another approach and following dave's tip on a standard import and 'join all' on the trouble part works fine though! thanks!

dave, you have seen the model, what do you think my chances are to make a successful cross section in max? did some very quick tests with proboolean and powercutter without any luck, should i even bother to try, or should i just cut it in inventor and export another step (should be fairly quick, but the nurbs work would be lost...)

[kimgar]

ok, i just fiddled around a little more with the model and did some sewing and splitting, not sure yet why or what happened, but the pwr_cutter suddenly worked extremely well. i've got a beautiful cross sectuion now!

i think it is time to get a license

[nPower_Dave]

Yes, you should get a license. Then you can use the wonderful tools all the time.