MCX2 MR1 shows extra surface

[Nils N]

I created this is X2sometime ago. Today I needed to open and check some dimensions. Since I had just installed X2 MR1 and hadn't open a file yet I thought this would be a good first file. When I opened it I got an extra surface shooting off from it as you see in the picture. I opened it then in X2SP1, though it was created in X2 and no extra surface. Any ideas as to why this would happen?

 

Opened in MCX2 MR1

 

Opened in MCX2 SP1

[Pete Rimkus from CNC Software Inc.]

Nils,

Can you send that MCX file in to QC and cc: me ([email protected])?

[Nils N]

Sure thing Pete, you have mail

[Redfire427]

Funny thing. I had the exact same thing happen to me today as well. Almost identical result. The original part was machined in X2 SP1 and looked great. I opened the file in X2 MR1 today to make another part and I had the same problem. Not only that, I had two small surfaces missing. I tried importing the original ProE file in and those same surfaces were missing as well. Very strange, because the original was perfect.

[Nils N]

Prosin, sent it to Pete and send him the original ProE file too it should help him find any problems

[Chris Parish]

I had it happen with just a "CAD" file (DWG)... same thing ... Pete you have mail as well

[JohnW@Kauffman]

I had a similar thing happen; opened a small part and had an extra surface running off at an angle. So I closed the file, closed and restarted Mastercam MR1 and reopened the file. The file was fine when I opened it after restarting. So far, it has only happened that one time.

[Colin Gilchrist]

I've had it happen to my vector lines on a 5 axis toolpath that was created in X2. When I opened it up, some of the vector lines endpoints had moved to the system origin. It was very strange looking. I'll see if I can find the file and send it in.

 

Thanks,

[Pete Rimkus from CNC Software Inc.]

Prosin,

Yes - please send me the file(s) if you can.

 

Chris P,

You're issue was different - it sort of looked the same (lines did shoot into space) but it was dimensions, not surfaces.

 

John W (and everyone else)

This may look like it appears and then disappears, but we narrowed Nils' problem down to a problem introduced when shading the surfaces. If you open it up in Wireframe, it looks fine. If you then Shade it, it looks bad. Switch back to Wirefram and it still looks bad. Shading is actually tweaking the surface NURB data.

 

We're looking at it...