Experienced Rhino users who utilize laser cutters, particularly Epilog Fusion M2 lasers, may encounter an unforeseen issue with Rhino 8. Since Rhino 5, the printing workflow in Rhino has been crucial for laser cutting processes. However, recent updates in Rhino 8’s printing functionality appear to have introduced a problem where laser cut settings are unexpectedly reset to default values.
This issue specifically impacts workflows relying on Epilog lasers, which, unlike some other brands like Trotec, depend heavily on settings configured within the print preferences dialog rather than directly on the machine or through separate software. While printing to these Epilog lasers from Rhino 7 and other programs like Illustrator works seamlessly, Rhino 8 seems to discard configured settings.
When initiating a print job in Rhino 8, the primary print menu options appear to function as expected.
The problem arises when users proceed to the Print Properties to adjust specific Vector and Raster settings. These settings are intended to control parameters for different layers or object types within the design, such as vector cutting paths and raster engraving areas.
Despite correctly configuring these settings in the Print Properties dialog, upon reviewing the actual settings sent to the laser cutter, it’s evident that all custom values have been reverted to a default value of 50. This reset affects not only power and speed settings but also other parameters like engrave direction, hindering precise control over the laser cutting process.
The current hypothesis suggests that Rhino 8 might be unintentionally discarding the printer preference settings instead of correctly transmitting them to the printer driver. For users seeking to replicate this issue without a physical laser cutter, installing the Epilog laser drivers and the Epilog Job Manager software provides a way to inspect the settings passed from Rhino 8. These resources are available on the Epilog website under Fusion Driver and Firmware Updates. A sample Rhino file demonstrating this issue is also available for testing and review.
While this issue hasn’t completely halted workflows, it has caused disruptions, particularly in educational settings like Rhino workshops. Understanding and resolving software configuration issues like this is a critical aspect of many technical roles. For those considering What To Expect In A Career Of Program Config Configuration, this real-world example highlights the importance of meticulous attention to detail and troubleshooting skills required to ensure software interacts correctly with hardware. Further insights and potential solutions from the Rhino and Epilog community are highly appreciated.
