itch.io

Yeah, I kinda figured - and I said in the first post - I'm well aware that I'm probably far from the usual use-case that this softare was intended for =)

Anyway, I bit the bullet and spent the day learning the CAM inside FreeCAD. Struggled a lot, but finally managed to write a macro that makes it possible for me to do what I want (basically; pocketing that is able to use the gap between parts, something I did in pocketCNC by merging an offset path of the part with the pocket outline).

So, I'll continue to use PixelCNC for any 3d reliefs in the future, but for now I have a more suited workflow for this specific usecase. 

And to clarify, I also agree that trying to load an existing codebase into an LLM isn't (at least not yet) a feasonable idea as it will clog the context space. I meant to use it more for boilerplating and to help you get going with a new codebase - but I totally understand that it's not what pays the bills. It's a shame though, considering the price that Vectric charges for their software - it's clear that the market is in dire need of some competition =)

Anyway, good luck and again - thank you for you work.

Ah, I see. 

Could you perhaps explain the relationship between DPI of canvas, quality setting and supersampling setting? I mostly import stl files and trace them to paths - but I've noticed that quite often I need to increase the DPI higher than it allows me (and I've learnt the hard way not to auto-press "yes" on that pesky popup that reverts back to factory settings whenever I hit the ceiling) - in order for the outline toolpath to realize that the tool diameter does indeed fit inbetween two objects. I assume this has to do with edges not lining up exactly on edges? So basically - with a monster computer (running on a 48 cores, Nvidia 5090 GPU, 128gb ram) - what are the important settings to keep in mind? keep in mind I'm mostly using 2500x1200mm sheets (~8x4feet).

I also have had my fair share of projects "made for me - by me" that got traction and had me rewamp the whole project instead of trying to maintain an unmaintanable code-base, so I know it sucks - but you have the most difficult part already worked out: the scope of the software. When the scope is set, it's much easier to build a sustainable codebase around it, especially with the tools that are available today. Not saying you should "vibe-code" it, but using ai tools to build montonius tasks from your own clear requirements is like having a team of lighning fast junior developers - you still need to check the code it produces, but you can focus on the overall structure and quality aspects. My two cents if you decide to go that route is that having the ui seperated from the core functions is usually the best way to making it maintable in the long run. I understand that it might not be that easy since I assume that a lot of the tracing is actually taking place in the game engine itself.

Hi,

Quite new to PixelCNC, but I like it - even though I am probably far from the optimal use-case for a software like this, I mostly use it to cut out 2.5D parts from large sheets on our full size CNC.

One of my main "pet-peves" is that I quite often find myself in a situation where I quickly realize that I should have had "inverted" checkbox clicked, and have to wait for a long time for toolpaths to generate - and sometimes this can take minutes if I have a small stepover size and it wants to fill large areas.

TL:DR; Is there a way to cancel the current toolprocess generation?`

Another quite annoying thing is the wierd keyboard handler. I use a swedish keyboard layout and our "+" is in the same location as the us-keyboard "-" (minus/dash), and our "-" key will output a "/" in the software. Beeing a developer myself, I must admit I'm more baffled over why the software needs it's own keycode/press management?  could you maybe shed some light on the issue you faced when deciding on going this route?

Best regards, and thank you for an amazing software for a reasonably price.

Ludvig
Qruxel Productions,