Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
Tags

Hi Dennis, I'm not seeing much that indicates the program itself is frozen in any way, particularly because it still appears to shutdown normally when you close it, which leads me to think something is interrupting it from accessing the program window for render output.

To help narrow it down I can have you generate a log file with more details about everything happening under the hood if you start up PixelCNC and go into the Config menu to enable the "log extra-info" option and then re-create the project again. This time send the complete contents of the resulting log file so I can see other aspects like GPU/system capabilities that may be playing a role in the issue. If you feel the need to remove any personal details like user directory path etc.. please just replace the characters with something else. Also, can you also show me the CNC/CAM settings you're using in PixelCNC?

One thing you might want to try, just to help narrow things down, is disabling GPU image convolution from the config menu too and then seeing what happens. But if you haven't had any problems previously then I'm wondering if it's a very specific situation with the project itself you're trying to create and not related to the image processing functionality utilizing the GPU. Could you also try a different project size, add an inch, shift the machine origin, etc.. so we can narrow it down between either this specific project or your specific settings/configuration? Thanks. There's a chance that you've discovered some kind of rare edge case with these exact project settings that gets something caught in a loop, or that is somehow stalling out the rendering context. A log file with debugging info will help us make a determination.

It's very curious that the statusbar says "...set toolpath done" because that's not actually something PixelCNC ever says in the statusbar, it looks like somehow "...set toolXX" after creating the cutting tool is being overwritten only over the end by "spiral toolpath done" and somehow becoming visible before your GUI stops refreshing. Interesting.

We should be able to get this squared away and get you running pretty quick. Have you been able to re-create this problem in any other way before or was it just with this specific project and these specific parameters/setup?

Charlie