Part Union differences FC 0.17 vs 0.18

[juless]

If I do a Part > Union of two intersecting cylinders in FC 0.17, the face/wire where the two cylinders intersect in the fusion was selectable. I've used this to create a fillet between the two cylinders.

In FC 0.18, the same operation also results in a fusion, but the intersection of the cylinders is not selectable.
On closer inspection though, it is almost impossible to see, but I can select and fillet. It's very finnicky though.

Opening the 0.17 file in 0.18 and vice verse affords the same results. Both contain the same number of shapes.

There don't seem to be config differences between the two versions (e.g. automatically refine part).

Can someone guide me to where this difference originates from, or how to make 0.18 behave as 0.17?

I'm not quite sure what the correct nomenclature I need to be honest, and I'm sure it's not exclusive to Part > Union but this is my use-case, so a picture is worth a thousand words.

Loving the FC community and support so far (it's only been a week) - keep it up!

difference.png (168.74 KiB) Viewed 811 times

OS: Windows 10
Word size of OS: 64-bit
Word size of FreeCAD: 64-bit
Version: 0.17.13528 (Git)
Build type: Release
Branch: releases/FreeCAD-0-17
Hash: 5c3f7bf8ec51e2c7187789f7edba71a7aa82a88b
Python version: 2.7.14
Qt version: 4.8.7
Coin version: 4.0.0a
OCC version: 7.2.0
Locale: English/UnitedStates (en_US)

OS: Windows 10
Word size of OS: 64-bit
Word size of FreeCAD: 64-bit
Version: 0.18.16110 (Git)
Build type: Release
Branch: (HEAD detached at upstream/releases/FreeCAD-0-18)
Hash: f7dccfaa909e5b9da26bf50c4a22ccca9bb10c40
Python version: 3.6.6
Qt version: 5.6.2
Coin version: 4.0.0a
OCC version: 7.3.0
Locale: English/UnitedStates (en_US)

[openBrain]

No problem here with the 0.18 RC. The edge is clearly visible & selectable.

fusion_edge.png (18.71 KiB) Viewed 806 times

I'll update to 0.18 final to see if there is a difference.
---
OS: Windows 7
Word size of OS: 64-bit
Word size of FreeCAD: 64-bit
Version: 0.18.16093 (Git)
Build type: Release
Branch: releases/FreeCAD-0-18
Hash: 690774c0effe4fd7b8d2b5e2fb2b8c8d145e21ce
Python version: 2.7.14
Qt version: 4.8.7
Coin version: 4.0.0a
OCC version: 7.2.0
Locale: French/France (fr_FR)

[openBrain]

Exactly same with 0.18 final. No problem at all.

Could you try to reset your configuration by renaming the config files ?
---
OS: Windows 7
Word size of OS: 64-bit
Word size of FreeCAD: 64-bit
Version: 0.18.16110 (Git)
Build type: Release
Branch: (HEAD detached at upstream/releases/FreeCAD-0-18)
Hash: f7dccfaa909e5b9da26bf50c4a22ccca9bb10c40
Python version: 3.6.6
Qt version: 5.6.2
Coin version: 4.0.0a
OCC version: 7.3.0
Locale: French/France (fr_FR)

[juless]

I've deleted the user.cfg and system.cfg files and opened the project in 0.18. Still doesn't show the edge (new config files were created).
Opening the project in 0.17 with the config files created with 0.18 still works ok as before.

Then I deleted the config files again, and opened the project in 0.17 to allow 0.17 to create new config files.
Shows up ok in 0.17, and still problematic in 0.18.

The status bar at the bottom does give me information that an edge is under my cursor, but I just can't see the damn line...

I will try a full uninstall of both versions and reinstall only 0.18 again. Thanks for thinking with me so far!

Am I right in thinking this has something to do with shape refinement?

[NormandC]

Hello juless,

Welcome to the forum.

I don't think this has anything to do with shape refinement, which only removes edges between co-planar faces and along cylindrical faces. This is an intersecting edge that should always remain.

I rather suspect a graphics issue. The difference between 0.17 and 0.18 is the Qt version used, it was upgraded from Qt4 (which is long deprecated) to Qt5.

What is your graphics card/chipset?

[juless]

I'm currently working on my laptop, with onboard Intel HD Graphics 5300. I will give it a go on my desktop with a beefier graphics card (NVIDIA GTX 960).

EDIT: Yes, there the edge seems to show up, so thank you for pinning that down!

Please let me know if there is any detailed information I can provide to debug this, or is it a known issue with Qt5?

A fresh installation of 0.18 on the laptop didn't give a different outcome by the way.


Cheers for all the assistance!