Alright, you can download a custom build here: http://www.deftware.org/PixelCNC/PixelCNCv1.47aTrial(64bit).zip

Go ahead and place the EXE in your existing PixelCNC folder and run it instead of the existing "PixelCNC Trial.exe" file.

There's no guarantee that it will solve the problem but I made some changes that might fix the issue you're seeing. I also included some extra information output to the log file during startup that might help narrow things down, worst-case scenario, so if you're still seeing the INVALID OPERATION in the log file (or the console, just press the tilde '~' key to see the log output while in PixelCNC) then go ahead and pastebin the log file it produced so I can take another look.

 Charlie

EDIT: I did some more digging and I think that this will solve the issue you were seeing! There's an issue with Intel's shader compiler that prevents it from supporting a certain math operation and the custom build above removes it.

EDIT2: If everything works for you as intended I'll get a public v1.47a hotfix update out today.

Ah, it looks like your cut depth is set very very tiny, which is OK for horizontal finishing passes (i.e. horizontal milling operation with a cut stepover of zero) but for a parallel carving operation you'll want something more substantial. It looks like it's overflowing the Intel graphics  chipset with too many cutpath move geometry and crashing it. Try a larger cut depth. If your cutter and machine are rigid enough you should be able to use the entire flute length of your cutter for your cutting depth. For a 1.5mm diameter cutter I would use at least half of the flute length as a cutting depth here.

Another strategy is to use a roughing pass with a larger cutter that has a Leave Stock of a millimeter or two, a stepover about 30-40% of the cutter's diameter, and then come in with a parallel carving operation and the smaller tool for finishing - and you can set your cutting depth to the full depth of the project's canvas (or at least the cutter's flute length).

 Charlie

Glad to hear it, and thanks for the sale :)

I figure that the best I can do as an independent developer is provide top-notch support for users, especially while I'm still working on producing learning materials - tutorials and walkthroughs that explain everything. I'm just about to release the v1.48a update, which incorporates some fixes, including the one for the INVALID OPERATION error you were seeing in the log file. PixelCNC should let you know that an update is available the next time you launch it after I've pushed the updates to the web.

I'll be sending out a customer-wide email about tutorial videos that are released as I put them up, so keep an eye out for those.

In the meantime feel free to post any questions, even if they're only CNC related and not PixelCNC-specific, or provide any feedback you may have on the software, however big or small. A number of PixelCNC's features are the direct result of user suggestions.

Share your projects here on the forum for others to see! I just did one the other day that I should post, a V-carving on an ebony-stained board with gold-painted cuts. It came out really nice.

 Charlie

EDIT: I did fix the crash that occurs if a user creates an operation that produces too many cutpaths, right now it just outputs to the logfile that the toolpath is being overflowed with cuts. It's a bit of a placeholder that will prevent PixelCNC from crashing for now. I will add in a prompt soon that warns users that their parameters are creating excessive numbers of cuts for v1.49a.