I use the above house with a custom c-plane on the roof to explain coordinate input (cplane, world, relative) to my students.
in current Version, a world-Coordinate Input will disrupt the next cp-plane input without a Z-value.
how to repeat:
set a cplane somewhere in space.
input one line after another, or as a macro:
_polyline
0
30,20
r10,10
; the next point in world coordinate (w) without a z-coordinate will tricker the Bug
w20,20
; the next point should be in cplane coordinate, it is previewed in cplane, but drawn in world
50,30
; the next point is the same, but is drawn correctly:
50,30,0
@Gijs can you please direct this issue to the correct person ? thanks.
Windows 11 (10.0.26100 SR0.0) or greater (Physical RAM: 32GB)
.NET 7.0.0
Computer platform: DESKTOP
Standard graphics configuration.
Primary display and OpenGL: NVIDIA GeForce RTX 3080 Ti (NVidia) Memory: 12GB, Driver date: 12-3-2024 (M-D-Y). OpenGL Ver: 4.6.0 NVIDIA 566.36
> Accelerated graphics device with 4 adapter port(s)
- Windows Main Display attached to adapter port #0
OpenGL Settings
Safe mode: Off
Use accelerated hardware modes: On
GPU Tessellation is: On
Redraw scene when viewports are exposed: On
Graphics level being used: OpenGL 4.6 (primary GPU’s maximum)
Anti-alias mode: 4x
Mip Map Filtering: Linear
Anisotropic Filtering Mode: High
Vendor Name: NVIDIA Corporation
Render version: 4.6
Shading Language: 4.60 NVIDIA
Driver Date: 12-3-2024
Driver Version: 32.0.15.6636
Maximum Texture size: 32768 x 32768
Z-Buffer depth: 24 bits
Maximum Viewport size: 32768 x 32768
Total Video Memory: 12 GB
are you sure ?
as far is i am aware the rule is, that we can omit z=0.
therefor 50,30
and 50,30,0
should result in the same final coordinate ?
or I am wrong ? - is it 50,30 (...let planar on/off decide about z)
EDIT:
ok
will result in the expected behaviour / points, 50,30 and 50,30,0 become the same points.
but please explain me the behaviour when planar is turned on.
( I don t see the logic behind it, why should w20,20 trigger a new z-height ?
why does keyboard input is affected in a strange why by “planar” but not by “project”)
maybe the changes from RH-20212@mikko do not cover all aspects ?