-
-
Notifications
You must be signed in to change notification settings - Fork 4.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open a file created in FC 0.21.2 containing Part workbench boolean cut operation in Dev 1.1.0 opens like Wireframe not a solid #18584
Comments
please attach file |
I believe it's the same faulty code as I've highlighted in #18575 |
I think I closed this by mistake, I'm sorry |
Confirm with 1.1.0dev.39673 FreeCAD 1.0.0.39109 (Git) makepkg, Arch Linux (KDE/plasma/wayland)
FreeCAD 1.1.0dev.39673 (Git) Conda AppImage, Arch Linux (KDE/plasma/xcb)
|
@wwmayer in order to correct this issue and #18575 I had to make changes as per main...Syres916:FreeCAD:Fix_Import_Step_021_Transparency |
I'm throwing the towel in on this one, I can get the models to load correctly but not with the CI tests pass and vice versa. If I use a 0.21 heavy Part based model and test for Transparency the test passes but because it's a heavy model you can see on screen it loads with Transparency @ 0 (hence pass) then a split second later it changes to 100. Every object in the tree does the same as I see the Transparency Property code repeatedly triggered. If anyone wants me to create a branch with the test model and the transparency test that I wrote, let me know. |
@kadet1090 maybe you can take a look? |
Is there an existing issue for this?
Problem description
Open FreeCAD 0.21.2, create a rectangle in sketcher, extrude it, create another rectangle or circle extrude it too, make cut boolean operation between those, save it. Open it in FreeCAD 1.1.0 , it appears to be wireframe.
I have a bunch of files with Part WB boolean cuts and all of them open
like that in Dev 1.1.0
Full version info
Subproject(s) affected?
None
Anything else?
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: