PDA

View Full Version : Need input version 3.7 mr3


randy z
03-08-2006, 11:57 AM
Can anyone give me some feedback on 3.7mr3
I am ready to load it.
But am I doing the right thing currently running 3.5mr2

Thanks in advance for any advice

DaddyBluto
03-08-2006, 12:14 PM
I am enjoying 3.7 MR3. The only problem I have had is with one of the nifty new features where you can drag your points around in an auto feature. Occasionally it kicks me out when doing that. That minor inconvenience is far outweighed by the smaller .CAD files after translation and the ability to see where your touches are going to be on the CAD model. I am happy I upgraded from 3.5 MR2.

Jaime

Wes Cisco
03-08-2006, 12:30 PM
Give it a try. You will love the graphics screen enhancements. There have been more than enough positive posts to know it is not another 3.6. Personally, I have had zero problems with 3.7 MR3.:)

bob mappes
03-08-2006, 08:12 PM
"I am enjoying 3.7 MR3. The only problem I have had is with one of the nifty new features where you can drag your points around in an auto feature. Occasionally it kicks me out when doing that. That minor inconvenience is far outweighed by the smaller .CAD files after translation and the ability to see where your touches are going to be on the CAD model. I am happy I upgraded from 3.5 MR2.

Jaime"

3.7 MR2 "kicks" you out also when playing with the hit points in AutoFeature.
sometimes even screwing up your vectors

bob

BKulpa
03-09-2006, 01:29 PM
I'm having some problems with MR3 on 2 older B&S machines with Sharpe32 controllers, TP20 & TP200 stylus changers. With both machines they tend to skip wrist rotations after a stylus change while running a full execution. The machine with the TP200 cannot dock a probe in execution mode without a "Unexpected Probe Hit" error.:mad:

Wes Cisco
03-09-2006, 01:53 PM
I have had the same problem for years on an excel with Sharpe 32 controller. I use both TP20 & TP200 change racks. I have gotten into the habit of inserting a move point after the tip loads, *BEFORE* the tip rotation. This solves the problem, which has occured sporadically since version 3.5. HTH :eek: