To whom it may concern, the first release candidate for FreeCAD 1.0 is out 
I switched to freecad a while back for personal use (mostly 3d printing) so its great to see the progress they’re making.
I suggest downloading the appimage and giving it a shot. Just run:
$ chmod +x ./FreeCAD_1.0.0RC1-conda-Linux-x86_64-py311.AppImage
$ ./FreeCAD_1.0.0RC1-conda-Linux-x86_64-py311.AppImage
if your’re on x86 Linux 
Don’t forget to report any issues you find on their github issue tracker!
Ooooh!
From the changelog, what do you find most exciting?
Always wanted to learn it, but always found it to cumbersome when i knew my way on fusion.
Maybe this will be the kick in the butt i need to switch 
I wish i could import the timeline between tool ><
the biggest pain point has been the “topological naming issue”, where surfaces, edges etc would get renamed when changing previous features.
that would often move stuff like fillets to completely different edges, which was cumbersome to say the least
now that should mostly be fixed.
the best tool is always the one you know
fusion is probably the better program right now, freecad is great but still a bit rough around the edges.
Its more than enough for most people!
my main reason to learn it was to finally get rid of windows completely 
that would be sick! tho i imagine that being a pita to implement lol
I don’t even think that fusion export any format that contain that data …
Also, the best tool isn’t the best if you can’t run it because you’re to butt hurt to reboot to windows
my 3D printer is collecting dust because i’m to lazy to open fusion again ><
oh well then definitely give it a shot!
the freecad wiki needs some work but its still a good help.
start with the “Part Design” workbench, its the most similar to what you’re used to from fusion.
the “Part” workbench, which works more with boolean operations also exists but i’m not much of a fan of that one.
stick to one or the other unless you have a really good reason not to 
there’s now also a native assembly workspace (instead of 3 different extensions lol) but i havent had time to try that one out.
yup thats pretty much what was happening to mine as well 
I don’t like that it doesn’t work on wayland. I haven’t gotten around to setting up a “burner” VM with GPU passthrough (VM for productivity, VM for gaming etc.). I’m still using it on my Win10 VM with GPU passthrough. I’ll eventually switch it over to linux.
What I don’t like about it is just my lack of knowledge and my inability to find good, understandable documentation around it. Maybe I don’t like myself, rather than freecad, because I’m ok with freecad in general (I can’t say I bear any self-hatred, because I feel nothing of the kind - as for freecad, it’s among the few programs that I just use and don’t feel like there’s anything to really make me hate it or to begrudgingly use). I haven’t updated it in a while though.
So far I’ve built a loft bed in freecad and I’m still building a trailer bed. I’m using parts design for starters (for each part), then using A2plus add-on to combine the parts. What I don’t get is how to fix “constraint conflicts.” I have no idea how, after I combine multiple parts and make a part dependent on the previous part, I eventually end up with conflicts.
In my mind, if part A corner 4 (A,4) has a coincident point with part B corner 1 (B,1), then part C corner 1 (C,1) has a coincident point with part B corner 4 (B,4), then there should be absolutely no conflict.
(A,4) = (B,1) and (C,1) = (B,4)
No conflict what-so-ever, but a2plus reports it as a conflict (with more parts, usually when I go past 8 or 10 parts). At that point, I just start deleting constraints for parts that are already in place.
I don’t really care about parts being unmovable, / fixed in space all I care about is for my final design, to have the final measurements, so I know how many materials I should buy and how much to cut from them. It makes me save money on the parts I buy, by allowing me to “see” how the build will look like.
From there, I can calculate how many (e.g.) 2x4s and 3/4 OSBs I need, by dividing the number of perfectly sized pieces by a common length (say 8 ft for 2x4s and 4x8 ft for OSBs). I can cut an 8 ft piece into a 5 and 3 ft and if I need 4x 2 ft pieces, I make sure that I get them from the remnants from other pieces, instead of buying more lumber and be left with a ton of scrap.
It’s kinda annoying that I have to spend so much time dealing with constraint management and a2+ not moving parts as I want it to, instead of actually getting things done.
I draw a rough sketch in kolourpaint on my main PC, to see how I’d like things arranged, sometimes take quick text notes (on the same paint image), then I start designing the parts.
If I’d be in a rush to get things done, I’d spend less time thinking about it, make a rough sketch, buy the parts, make some rough measurements and start having at it. But because I have some time, I prefer to spend the time instead of my money. As a counter example, I built a wall-hanging dryer and I didn’t plan it in freecad. I bought a couple pieces of 1x2s and started building. I could’ve saved a bit of materials (like a single piece of lumber) if I had designed it before, but the time was not worth it. I’m left with a bit of excess wood, but don’t care (because I found the very little money I spent there less valuable than my time - I was in a slight rush to finish the project and move on to better things).
Looking forward to more freecad and a2plus releases to come.
It does work on wayland.
It’s not running in wayland.
Gave me the impression we gotta log into an X session to run it lmao
It runs under wayland, until you try even a basic task, like creating a new project.
(qt.qpa.wayland) Wayland does not support QWindow::requestActivate()
Program received signal SIGSEGV, Segmentation fault.
#0 /usr/lib/libc.so.6(+0x3f8c0) [0x7f1a100d38c0]
#1 /usr/lib/libX11.so.6(XDefaultScreenOfDisplay+0) [0x7f1a0e44c620]
#2 /usr/lib/libCoin.so.80(+0x458c2e) [0x7f1a0fc2dc2e]
#3 /usr/lib/libCoin.so.80(glxglue_init+0x3c) [0x7f1a0fc2e4dc]
I had to look that up, I thought programs get launched under xwayland automatically if they don’t support wayland and I thought that was what was making it to crash.
Launched it with env -u WAYLAND_DISPLAY FreeCAD and now creating a new project worked without a segfault.
Thank you for your guidance!
I could run freecad just fine in Ubuntu wayland, Debian wayland it crash and burn as soon as I try to open anything. 
This is the 21.2 version though…
Try to launch it the same way I did?
That actually helps. Steps taken:
These were the two outcomes:
$ freecad
FreeCAD 0.21.2, Libs: 0.21.2R
© Juergen Riegel, Werner Mayer, Yorik van Havre and others 2001-2023
FreeCAD is free and open-source software licensed under the terms of LGPL2+ license.
FreeCAD wouldn't be possible without FreeCAD community.
##### #### ### ####
# # # # # #
# ## #### #### # # # # #
#### # # # # # # # ##### # #
# # #### #### # # # # #
# # # # # # # # # ## ## ##
# # #### #### ### # # #### ## ## ##
QSocketNotifier: Can only be used with threads started with QThread
QOpenGLFunctions created with non-current context
(qt.qpa.wayland) Wayland does not support QWindow::requestActivate()
freecad: ./src/glue/gl.cpp:2234: const cc_glglue* cc_glglue_instance(int):
Assertion `current_ctx && "Must have a current GL context when
instantiating cc_glglue!! (Note: if you are using an old Mesa GL version,
set the environment variable COIN_GL_NO_CURRENT_CONTEXT_CHECK
to get around what may be a Mesa bug.)"' failed.
Aborted
$ WAYLAND_DISPLAY=1 freecad
FreeCAD 0.21.2, Libs: 0.21.2R
© Juergen Riegel, Werner Mayer, Yorik van Havre and others 2001-2023
FreeCAD is free and open-source software licensed under the terms of LGPL2+ license.
FreeCAD wouldn't be possible without FreeCAD community.
##### #### ### ####
# # # # # #
# ## #### #### # # # # #
#### # # # # # # # ##### # #
# # #### #### # # # # #
# # # # # # # # # ## ## ##
# # #### #### ### # # #### ## ## ##
Failed to create wl_display (No such file or directory)
And then proceeds to open the document. Interesting. Thanks for that, I’ll see if I feel like cadding more this autumn, but if I do, there is now a way to boot it at least. Otherwise, I might just wait for 1.0 to land in Debian Unstable.
Huh? its been working fine on my machine
Definitely sounds like opening an issue on github would be good
How can I check if its running through xwayland?
Edit:
Pretty sure its running on wayland directly
With the custom opening command, it’s been working fine swaywm. I’ve just finished a small project yesterday. Time to make the parts list.
by unsetting WAYLAND_DISPLAY? So its likely just Qt segfaulting on purpose then, no?
There have been issues with Qt in the past, like the AUR building with Qt 6 while not being officially supported yet, or some other mismatch with the runtime libs. Might be something like that again.
This GitHub Issue sems simmilar. Maybe you can provide them with more data points for figuring this out
I’m not using arch, btw.
I’ll try this later, thanks!
SHUN THE NON BELIEVER!!! /s
The AUR issue was just an example because I encountered it myself… Now that I think about it I think it was the official arch maintainers that broke it lol
You’re welcome!
It werked with that xcb var. It’s good to have options, in case one of them breaks.
