FreeCAD / FreeCAD/FreeCAD

Draft: unexpected behavior when drafting in a view that is parallel to the working plane

Open
#21,834 3 comments 0 reactions 0 assignees View on GitHub
Mod: Draft no-auto-close Status: Confirmed Type: Bug
Dominant language
C++
Stars
33.6k
Forks
6k
Avg merge
3d 15h
Merged PRs (30d)
196

Description

### Is there an existing issue for this?

- [x] I have searched the existing issues

### Problem description

Steps to reproduce:

- open the file (remove the zip file extension)

[FC-draft-from-side.FCStd.zip](https://github.com/user-attachments/files/20637836/FC-draft-from-side.FCStd.zip)

- make sure snaps are turned off
- set view to `Front`
- start `Draft_Rectangle` or any other Draft tools
- click first point above the `Top` working plane
- click second point above the `Top` working plane
- Rectangle is created at an unexpected location very far from the origin
- This probably leads to graphical artefacts (faces are rendered in a corrupted way)

See behavior in the video:

https://github.com/user-attachments/assets/fbd50e7e-3803-4d83-84d0-238eb5170359

I can reproduce the issue in FreeCAD 1.0.1

### Full version info

```shell
OS: Windows 10 build 19045
Architecture: x86_64
Version: 1.1.0dev.42006 (Git)
Build date: 2025/06/02 16:32:08
Build type: Release
Branch: main
Hash: db1b5a877314f8d21514680421649fd9dc65acde
Python 3.11.12, Qt 6.8.3, Coin 4.0.3, Vtk 9.3.1, boost 1_86, Eigen3 3.4.0, PySide 6.8.3
shiboken 6.8.3, xerces-c 3.2.5, IfcOpenShell 0.8.2, OCC 7.8.1
Locale: English/United States (en_US)
Navigation Style/Orbit Style/Rotation Mode: CAD/Rounded Arcball/Window center
Stylesheet/Theme/QtStyle: FreeCAD Light.qss/FreeCAD Light/
Logical DPI/Physical DPI/Pixel Ratio: 96/92.6073/1
```

### Subproject(s) affected?

Draft

### Anything else?

I am not sure what the behavior in this case should be. But the current behavior is confusing and should be handled in a different way in my opinion. Users should not be allowed to create 'corrupted' geometry so easily, even if it is their own mistake (I think this mistake can happen quite easily).

### Code of Conduct

- [x] I agree to follow this project's Code of Conduct

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.