I'd be interested to know if bit optimization really solves the problem. I just went back and found that my design with this problem had bit optimization at best but did not think to try turning it off.
I'd be interested to know if bit optimization really solves the problem. I just went back and found that my design with this problem had bit optimization at best but did not think to try turning it off.
A good learning toole is to take such as that paw print and open in your designer and change the Optimization settings and see how each one changes it up. I found that that service one well.
The Bit Optimization setting dose not always have to be on a higher or high setting, study your ptn.
Happy Carving
Robert D.
rcdages
CarveWright START U Team Member.
The mightiest oak in the forest is just a little nut
that held it's ground.
The problem is that since it's a bug in the software, the step does not show up in the designer rendering. In my case I created a .25 deep carve region from a vector shape and added a flipped feather. For mine, bit optimization has no effect on the rendering of the carve so it should not matter if it's off or at best. However, if the bit optimization is somehow causing the unwanted condition to occur, then it's a good idea to leave it off unless it's actually needed.
Fair winds,
Capt Bruce
Kinney deSigns http://kinneydesigns.us
CarveWright START U Team Member.
30 year USN SEABEE, the original Weapons of Mass Construction.
Designer Ver 1.187 and 2.007, Ver.3.001 One 2009 B CW w ROCK and a 5th Year Anniversary C CW
Rotary Jig, 2D and 3D, Tracing Probe, DFX and STL Importers
.
So this is one of those rare occasions that no optimization is good?
Custom Stadium Coin Racks for displaying Military Challenge Coins, GeoCoins and the like- http://www.etsy.com/shop/stadiumdisplays
OR http://shop.ebay.com/stadiumdisplays...&_trksid=p4340
I guess but it was apparently a bug. Anyone know if or when it was fixed? Is it fixed in 2.0 ?
OK, I had to go test my previous design. Changed the bit optimization to "none" and the problem went away. Apparently LHR tech support hasn't yet learned that bit optimization is the root cause of this problem. Thanks Dick and others for pointing this out. No more superfluous usage of bit optimization for me.
What version of Designer are you running?
I'm using 1.187.