X7 Verify issues

[Justin Beebe at Folsom Tool]

I just started using X7 and I really like a lot of the new features. However verify is giving me some issues. The main issue is a long lag time up to 30 for verify to launch. I get the message "processing nci data" and the verify screen is frozen for up to 30 seconds. This time increases if I use a saved STL file and it also increases when I add more tool paths. Is anyone else experiencing this or does anyone know of a fix.

 

Other general questions I have about the new verify interface are:

 

How do I designate a solid model as a fixture.

 

How do I make the left over stock one color for each tool.

 

What is the recommended precision setting.

 

What are the recommended settings for moves before and moves after.

 

If I get three monitors can I have my op manager and level manager on one monitor, my mastercam workspace on one monitor, and dock verify and backplot on it's own monitor

 

Thanks in advance

[Justin Beebe at Folsom Tool]

By the way my computer specs are:

 

Dell T7400 with Windows XP 64 bit

16 Gigs of Ram,

Quadro FX4800

Xeon 3.2 Gig processor ( I think its a quadcore)

 

I can't figure out how to change my sig.

[K2csq7]

As for the lag at startup, I can't really help, mine is never more than like 6 seconds.

I don't know how to designate a fixture, but there must be a way because there is a checkbox to toggle on or off the display....

For the lefover stock one color for each tool, on the Home tab, push the button for "color loop" (change the settings by going to, file, options, graphics.

I jack my precision settings all the way up, you could keep it low (speed things up a bit maybe?) then just use accurate zoom when you need it.

Yes, you can move verify to a different monitor (it works with 2 monitors, not sure about 3).

[Justin Beebe at Folsom Tool]

K2csq7

 

Thanks for the info. What are your computer specs. I'm starting to think my lag issues may be caused by my computer. It originally came with 32 bit XP and I upgraded it to windows 7 64 bit to try to save the company some money. I have a Dell M6600 lap top that was out performing this computer with X6. I also have MCX5 and MCX6 installed along with MCX7. Maybe that is an issue. Anyway I'll try your suggestions.

 

Thanks again

[JoelEllis]

Is there a way to make the X7 verify more like the X6 verify?

 

I machine a lot of weldments, so I have to make a stock model for each and every one to ensure I don't miss any machining. I like to verify in X6, then compare.

 

X7 verify is useless in my opinion. Perhaps I have some settings wrong, but I don't want to "accurate zoom" when verifying. I want to be able to roll my mousewheel in and out on details to VERIFY that stock is getting removed where and in the manner that I have meant to program.

 

I can't stand X7 verify and won't be using X7 unless it gets cleaned up or simplified.

 

Any suggestions would be appreciated.

[K2csq7]

K2csq7

 

Thanks for the info. What are your computer specs. I'm starting to think my lag issues may be caused by my computer. It originally came with 32 bit XP and I upgraded it to windows 7 64 bit to try to save the company some money. I have a Dell M6600 lap top that was out performing this computer with X6. I also have MCX5 and MCX6 installed along with MCX7. Maybe that is an issue. Anyway I'll try your suggestions.

 

Thanks again

I have a M6600

i7 with 2.5GHz

16GB Ram

 

 

I don't want to "accurate zoom" when verifying. I want to be able to roll my mousewheel in and out on details to VERIFY that stock is getting removed where and in the manner that I have meant to program.

 

You don't have to accurate zoom.... unless you want to see the scallops leftover from your 3/16" ball end mill..... or you could zoom out and accurate zoom the whole thing! Then it would take about the same amount of time to verify as X6 did.

[Justin Beebe at Folsom Tool]

Thanks for the specs. I'm going to install X7 on my M6600 this weekend and see how it performs.

[Cambrey]

I was having some serious lag issues with X7 verify and realized I was running it off the integrated graphics on my laptop instead of the Nvidia GPU. I made the change and all my lag issues vanished (shocking!) hahaha.

 

Oh btw...I'm running Windows 8 Pro 64bit on a Dell M4700 laptop.

[Justin Beebe at Folsom Tool]

Cambrey how do I check that. I have a Quadro FX4800.

[Jeff Kemper_2725]

>I can't figure out how to change my sig.

 

Top of the screen, right side, click down arrow to the right of your name, >My Settings >Signature

[Justin Beebe at Folsom Tool]

Thanks Jeff

[Justin Beebe at Folsom Tool]

When I change my sig the changes won't stick. I did a search but couldn't find any info on this subject. Anyone else have this problem?

[Jayson Kramer]

Cambrey how do I check that. I have a Quadro FX4800.

You should not have this issue on the desktop. some of the newer laptops have this as a power saving mode when using the battery.

[gcode]

One thing you can check,

go to System Config/Screen and make sure

"Disable hardware acceleration" is NOT checked

"and

"Open GL" IS checked

 

if you change either of these settings, you'll need to restart Mactercam

[Justin Beebe at Folsom Tool]

Jay and gcode

 

Thanks for the info. I checked my screen settings and disable hardware acceleration was not checked and open GL was checked. I also installed SP2 this morning and it doesn't seem to help the lag issues. I just had to go back and open an X5 file with MCX5 and it verified really fast. I'd like to get these issues fixed with X7 because I really like it aside from poor performance with verify.

[Jeff Kemper_2725]

>When I change my sig the changes won't stick...

 

I changed my sig, only added text.

 

You have to click "Save Changes", at bottom, center; for each page?

[Justin Beebe at Folsom Tool]

Jeff,

 

I was clicking save the issue was with the size of my picture. When I deleted it everything worked.

 

Thanks for the info.

[fillingdave]

I have the same issues with verify lag here also (5axis sim)... super slow... verify set to 3 axis caused the verified graphic part to be hacked up.