Hi, It's possible that Windows did something in the latest updates, they do love to push changes, even those that people do not agree with. But I digress. The reason for publishing "new" installers is that I saw that bitbucket allowed, again, upload of large files, so I took advantage to relieve my own cloud space. So nothing new in those installers, they are just the older ones, uploaded again. As for what you can do, try to delete the Preferences files, through this resetting the app to a default state. See the Preferences for that. I recommend manually deleting the files, but only after the application was closed. It helps to open the folder with the pref. files, from the link (the cogwheel) from Preferences bottom section, before closing FlatCAM beta.
Hi Marius, it seems that installing Python (latest 3.11.2) enabling "Add to PATH" and "Remove PATH max lenght" during installing resolved the issue. I'll se how it goes. As for new changes, i see that you are working hard on it in the last month, will be a new version soon? i mean with installer for windows, i don't know how to install from source
HI my FlatCam 8.994b keeps crashing on almost anything too. Windows 10, Installed python 3.11.2 , have long path names enabled, delete all files in the preferences folder. Windows event log report a crash in ucrtbase.dll. Any ideas?
Hi, FlatCAM Windows installers do not rely on externally installed Python toolchain, they have Python embedded inside, including the required modules. FlatCAM beta 8.994 is made to work with Python 3.6 up to Python 3.9. Python 3.10 and 3.11 have breaking changes so when running from sources, they should not be used with the 8.994 sources. Also, some of the dependencies modules introduced breaking changes too, between then and now. Most notable are VisPy and Shapely. Obviously there is a need for a new version of FlatCAM beta, but now I'm involved in another project so time for FlatCAM is asymptotic to zero.
Thanks for you extremely quick reply!I am actually running the 64 bit installer, forgot to mentions that. Before updating pyhton(which maybe wasn't necessary, it crashed in Qt5.dll
Ok i looked again and it seemed that i installed x86 version this time (for mistake) while my CTD problems where on x64
thanks for the tip x86 works for me. x64 doesn't work on my desktop running w10 and my laptop w11
Up with this, down with the spammers.