Mastercam X4 MU1 Verify Issue Fix

[Chris Bell CNC Software]

There is a bug in X4 MU1 which causes the stock and tool in Verify to display with no lighting, giving it a black appearance. We have a fix for this issue, and it has been posted on Mastercam.com. To use the fix:

 

1) Download the file mcverify-fix.zip from the above link.

2) Open your Mastercam X4 MU1 installation directory.

3) Close X4 MU1 if it is open.

4) Rename “MCVerify.dll”. This will prevent the file from being overwritten by the new *.dll.

5) Extract mcverify-fix.zip into the root of your X4 MU1 installation.

The new Verify *.dll will be incorporated into the next service pack or maintenance release for X4.

 

Thank you for your patience with this issue, we sincerely apologize for any inconvenience it may have caused. If you encounter any problems with this, please contact [email protected].

[Trevor Bailey]

how about making this flash across the screen when people login. in addition, how about an email notification to all users on emastercam. like the way it used to be when a new release or update was available. that was the main reason i signed up new customers during the install process.

[David Lowey]

did someone mention Service Pack?

[malibu]

thanks, verify works on my ati firegl 3100 pice of......

still have a problem on solids change color.

it is only working on my wireframe.

[malibu]

did a roll back driver and no luck, something still no good.

have one color on my solids for now.

[gcode]

quote:

---

have one color on my solids for now.

---

try this..

Settings/ System Config/Color

In the "Group Colors field, make sure

"use entity colors" is checked

not

"use group color"

[malibu]

entity was set thanks gcode.

fixed for now!

renamed mc config

let mastercam to create new and it works

[cadcnc]

Edit...

 

[ 10-28-2009, 10:50 AM: Message edited by: cadcnc ]

[Toonz]

quote:

---

4) Rename “MCVerify.dll”. This will prevent the file from being overwritten by the new *.dll.

---

Why do you have to do this if you're not going to use the original .DLL anyway???

[Lars Christensen]

In case something should go wrong with your downloaded .dll you have the old backed up. Chris is just looking out for you

[thanhsonnguyen]

too many prolem on this too...

[Bill H]

Downloaded MU1 and the new .dll file. Now MC locks whenever I try to verify. Tried going back to the original .dll file, but MC still locks. Help!

[gcode]

Open your Verify Settings in System Config

and see what you have set for default stock.

If its a file, try changing it to "stock"

[Bill H]

gcode: Thanks, but I already had 'stock' as the default. I've now found that the lock up happens only when I'm trying to verify to a solid. Any other suggestions?

[gcode]

Save the solid as an STL and use file instead.

are they big or complex solids?

[Bill H]

Yes, they're complex solids. I used to go the STL route, but had nothing but problems - that's why I started verifying to solid. The files I'm working on when the lock up happens are all ones that verified properly to solid before I installed MU1 and the new .dll file.

[gcode]

As you sure its really locking up..

The first time you start a verify session with a new solid, Mastercam needed to create a .lwn file

(lightworks native ????)

If its a complex solid, it may take a while to

get that done..

An off the wall thought.. if the solid resides

in a write protected folder, Mastercam can't create the .lwn file. That would cause a lockup.

 

also..

there are new settings in System Config/Verify

controlling how Mastercam handles bad STL files.

Try playing with them

[HEED]

Just a quick question.. Why do you need to rename the verify.dll? If the download is replacing it, it should just over write it? And if you rename, all associativity will be lost anyway??

[Midwest]

I remember reading about this, but hadn't had time to switch to X4............now I'm using X4 MU1..........ran into this black stock and black tool...........started to remember reading about this problem, then for some reason I tried doing a........ Alt S........(shading key strokes) and all the colors came back........ ........still haven't messed with changing the .dll file.

 

 

Wondering if this works for anyone else.........who hasn't done the .dll change.

 

 

 

 

Oh, I did this a few days ago.........but forgot to do a search until tonight.............I also used the Alt S today on a verify and it worked.

 

 

[Midwest]

Heed.........I think this answers your question.

 

 

quote:

---

In case something should go wrong with your downloaded .dll you have the old backed up. Chris is just looking out for you

---

[Midwest]

Correction.........

 

 

Have to type Alt S

 

twice.........then it works

 

 

[HEED]

Duhr... I guess I should read the posts above before I ask teh same questions. Apologies.