We have reached BETA. Everything should work, although the help files may be inconcistent.
Version 1.0.5.0
Found a problem that appeared only in 32 bit build using DirectX 9 although no reason it should not have occurred in other builds.
Was using an array of XMMATRIX values, the XMMATRIX uses registers and this seems to have been the issue. Converted any non local storage using XMMATRIX to XMFLOAT4X4 instead.
For DirextX11 version for design preview made machined areas lighter than uncut areas. This makes it easier to see cuts. This takes place in the shaders. Will be enhancing the shader in next release. Also playing with the line antialias setting. Turned it off on this build, debating whether the enhanced look is worth thicker toolpath lines.
Increased default jog speed.
Version 1.0.4.0
Fixed ASSERT in rotate editor when command is finished. Fired when multiple cuts being rotated.
Changed ASSERT test when generating a simple polygon that has holes when it shouldn't to a ATL trace message.
When computing contour based pocket toolpaths, the failsafe value calculation now uses abs value when computing distances.
Found special case in pocket contours toolpath where the cut is so small that no pocketing occurs, was ASSERTing but this is a valid case.
When importing adobe illustrator and eps files, now have option of specifying filled areas will have the toolpath be on inside of area, not just on the outline of the area.
Version 1.0.3.0
The toolpath direction (climb versus conventional) was wrong in some instances.
The displayed toolpath direction in the preview had direction arrows backwards.
Improved the way toolpath direction symbols look. Fixed normal calculation for direction symbols.
For DirectX11 users, will now display rapid toolpath movement direction symbols.
Version 1.0.2.0
Big change in the 3D preview, will now use DirectX11 (on Windows 7) and then downgrade to DirectX9 on other systems.
Installer saying its 64 bit in title on 32 bit install.
When creating a continous boundary toolpath could get duplicate points. Most often seen with circle cuts.
Removed assertion test on toolpath direction symbols scaling value, now shows a trace message.
Version 1.0.1.0 (First BETA Release!)
Added speed and feed calculator accessed from tool configuration dialog.
Updated all help files related to dialogs.
Changed toolpath cut direction to be set on as a configuration parameter in the tool description instead of being set on a toolpath cut level basis. Will cause change it tool library file format and design file format.
Was not saving that tool should use different settings for a non-default material.
Not able to set plunge type in tool geometry.
For drag type tools the boundary and interior direction can go either way.
Updated the tool library included with a better selection of tools.
Version 1.0.0.13
Under XP the 3D preview shows a DirectX not found message. Bug remains (need to find XP computer to run developer environment on in order to debug).
Was seeing a black background intermittently when showing the main button menu. Have switched the popup menu to initiallize to the system default animation, the default is no animation. Seems to have cured problem.
Showing "Pane 1" in the lower left pane. Not sure what we want here, for now it is blank.
In the ribbon we were showing true type fonts and device fonts. In the text cut dialog we showed only true type. The documentaion on device fonts is a little vague about their use in the way we do things, so we will only use true type fonts for text based cuts.
The rounded rectangle cut defaults to a filled style. Changed to unfilled for consistency with all other cuts.
With line cuts changed so that if an operation is performed that in turn results in the select operation becoming active, the select operation tab is NOT made active, although it will become visible.
Added information dialog when changing the fill state of a cut.
Getting an ASSERT under XP during Ribbon initialization testing. It showed 0 categories, which is weird but OK.
Cleaning up and adding various help files.
Version 1.0.0.12
Changed toolpath dialog so that you can only specify length units, instead of length and time.
The text editor has a font combo box that takes forever to load. The problem control is now initialized in a background thread at startup.
The preview for circle generated toolpaths could leave off the last circle.
The circle generated toolpaths when used with drag type tools can now have connected toolpaths.
Erroneous warning messag being generated with drag type tools, ZigZag toolpath, connected paths with boundary option.
Circle generated toolpaths can take a slightly too aggressive cut (rounding error problem).
Version 1.0.0.11
The circle generated toolpaths did not implement the non-connected toolpath option or the manually specified overide of stepover value. The do now.
Fixed error the zig zag style toolpaths could not be specified for circle geometry cuts.
Throwing warning to get newer version message.
Drag tool should work now.
For ZigZag toolpaths, the boundary of the path may have incorrectly been set to the non-finish quality in certain circumstances.
When previewing drag toolpaths, the paths will always be drawn above the part instead of the actual depth level.
Version 1.0.0.10
Toopaths will now use the GCode/ShopBot arc commands when generating circles. Should result in smaller toolpath files, marginally higher quality circles. Code will also use edge tool settings because with circles we can be sure when edge versus slot milling is occuring. Code is lightly tested, visiually inspect toolpaths.
A saved design uses ID information for tools and materials that are stored in separate configuration files. Application does checking at load time to see if tools and materials of a design make use of valid values. If not, user can udate.
Bug when generating toolpath where default material always used in feedrate.
Version 1.0.0.9
Previously the order of making cuts was to do all normal cuts first, then any drill type cuts no matter how they were ordered by the user. Now the order will be correct.
Slight change in file format, designs using previous versions will not work in this version.
Version 1.0.0.8
File format for part and tools has changed
Redesigned the toolpath point class to hold data with instructions to set spindle speed, type of milling. Previously the toolpath group class held this info.
Updated feed rate computation method for 3D movements.
Changed ramping angle from being hard coded, so being user setable on a tool by tool basis.
Change toolpath start method to have a tool level default value instead of machine level.
Changed some of the startup GCode commands.
Will now turn off spindle if a tool specifies 0 RPM speed, used in drag operations.
All ASSERTS in the toolpath generation will not fire if the abort flag is set.
Generation fo ZigZag toolpath allocated array sizes incorrectly.
Computing the time for machining was wrong when the speed units used seconds.
Version 1.0.0.7
The part preview will now utilize all cores on multi-core systems to render. Only doing it on preview, for real toolpath creation will continue to use a single thread.
Repaired errors in thread termination routines.
Now test for multi-core capability, if found the start of preview rendering will occur sooner.
Found possible error when using shared pointer accross threads, fixed.
Converted all dialogs that self destroy to Factory creation model.
Removed all references to AfxEndThread (turns out has significant memory problems).
Moved critical section variable to application object instead of document space.
Moved many objects that use shared pointers to be on heap instead of stack.
Using std::shared_ptr instead of boost::shared_ptr
When creating data for a threaded toolpath, now clone cuts and send that instead of polygon representations of cuts.
Selecting a round part geometry caused error.
Added abilty to turn off or select low quality previews.
Version 1.0.0.6
Finished implementing drilling type cuts.
Version 1.0.0.5
Adds a drilling capability that is not fully implemented. Specifically saving/loading of designs with a drill cut is not tested, but generating toolpaths should work. There was a reported bug creating an ASSERT when trying to save a toolpath that hopefully has been fixed.