Label moving

[daniel]

Strange... it works on my side, and on both of my displays (4K and not 4K...).

What is weird, is that you don't even need to select it to move it... Just pressing (and holding) the left button on the label will move it.

When you SHIFT+click on a point (or a mesh), does it create a label at the right place? The only reason why it wouldn't select or move labels is that the click is not detected at the right position in the view...

[Steve L~]

Yes, Its odd I've just tried on a different PC running on CC ver 2.10 and its OK on there so it must be my PC setup - maybe because I use a spacemouse? A shift-click on a point creates it on the correct point.

[daniel]

Hum, are you using a space mouse even for clicking and moving the label? How does it work?

[Steve L~]

No, I use a normal mouse as well Daniel. Its just I wondered that as the camera was being controlled by the spacemouse then perhaps it was affecting the 'normal' mouse clicking but I tried unplugging it and it makes no difference. I think it maybe a graphics card issue - my diagnostics show me its an Intel card, but the rest of the text means nothing to me! ;)

This Direct3D graphics driver is Microsoft WHQL certified
Graphics Hardware Description:
Intel Corporation Intel(R) HD Graphics Family

The display is using 32-bit color

System Information:

Operating System: 64-bit Microsoft Windows 10 Home (Build 9200)
Language: English
System Manufacturer: HP
System Model: HP Spectre Notebook
BIOS: F.43
Processor: Intel(R) Core(TM) i7-7500U CPU @ 2.70GHz (1 processor, 2 physical cores, 4 logical cores)
System Memory: 7.887 GB RAM

Graphics Device Information:

Renderer: HAL
Manufacturer: Intel Corporation
Chip Type: Intel(R) HD Graphics Family
DAC Type: Internal
Graphics HW Memory: 128 MB
Display Mode: 1920 x 1080 (32 bit) (60 Hz)

Graphics driver file: C:\WINDOWS\System32\DriverStore\FileRepository\ki124757.inf_amd64_b607c305e0c4e0a1\igdumdim64.dll,C:\WINDOWS\System32\DriverStore\FileRepository\ki124757.inf_amd64_b607c305e0c4e0a1\igd10iumd64.dll,C:\WINDOWS\System32\DriverStore\FileRepository\ki124757.inf_amd64_b607c305e0c4e0a1\igd10iumd64.dll,C:\WINDOWS\System32\DriverStore\FileRepository\ki124757.inf_amd64_b607c305e0c4e0a1\igd12umd64.dll
Driver file version: 22.20.16.4815
Driver Date: 26 September 2017 0:00:00 UTC (Coordinated Universal Time)

Direct3D Graphics Device Information:

Adapter Description: Intel(R) HD Graphics 620
Vendor ID string: 0x00008086
Device ID string: 0x00005916
VendorID: 8086
DeviceID: 5916
SubSystemID: 8255103c
Revision: 2


Direct3D 10 / DXGI System Information:

Dedicated Video Memory: 128 MB
Dedicated System Memory: 0 MB
Shared System Memory: 3.943 GB


DxDiag System Information:

Operating System: Windows 10 Home 64-bit (6.2, Build 9200) (17763.rs5_release.180914-1434)
Language: English (Regional Setting: English)
System Manufacturer: HP
System Model: HP Spectre Notebook
BIOS: F.43
Processor: Intel(R) Core(TM) i7-7500U CPU @ 2.70GHz (4 CPUs), ~2.9GHz
System Memory: 8192MB RAM
Page File: 9979MB used, 3216MB available
DirectX Version: DirectX 12
DxDiag Version: 6.02.17763.0001


DxDiag Graphics Device Information:

DirectX Version: 12.0
DDI Version: 12
DDI Version Number: c
DxDiag WHQL Level: 0
Driver Signed Valid: True
Driver Signed: True
Manufacturer: Intel Corporation
Chip Type: Intel(R) HD Graphics Family
DAC Type: Internal
Revision: Unknown
Graphics HW Memory: 4165 MB
Display Mode: 1920 x 1080 (32 bit) (60Hz)

[daniel]

I would need to output more information when switching the 3D "debug" mode (CTRL+D). For now it's only useful for stereo rendering...

[Steve L~]

Daniel,
I'm beginning to think its spacemouse related - If I start up my PC and CC without having a spacemouse connected, normal label selection and moving is back to how it should be.

[daniel]

Ah! That's still very confusing ;)

[WargodHernandez]

I believe it's quadro driver related, at the enterprise I work we have dell laptops with engineering models having the quadro. On all of the quadro models none of the 2d Interactors function (labels, clipping box, etc..). But the non quadro models everything functions as it should.

I can force them to work by using CPU point picking but CC will become unresponsive if you use CPU picking on a large point cloud. I've just learned to go without the interactors at work :(

The only weird thing about this in my mind is some things still work that I would have suspected would fail, specifically alt-dragging on the screen will let me select point clouds


Ok now I am really confused, I just opened up CC to detail further what worked/didn't.
But all of the labels/interactors are now functioning for me. its been a few weeks since the last time I tried (I tried to show a co-worker the clipping box controls while he was working on the advanced graphical translation interface, but they weren't working for us at that time).

[WargodHernandez]

Ahh nevermind, its not working for me... sort of.

If I start CC and open the file Daniel posted (maquette_with_planes.bin)
I can use all the interactors like normal.

When I load scans that I work with (proprietary so I can't share :( ) the interactors stop functioning at that point and will not work again until CC is closed and restarted, deleting the cloud or using close all does not fix the issue. There are no labels (or anything other than clouds/sensors in the bin file).

Here are some interesting differences between a working cloud and one that breaks all the interactors.
working cloud:

Code: Select all

Box dimensions
X: 10710.3
Y: 7588.1
Z: 2921.39
Shifted box center
X: 254.808
Y: 17364.7
Z: -12911.9
Global box center
X: 254.808350
Y: 17364.677734
Z: -12911.931641
Points 207,894
Global shift (0.00;0.00;0.00)
Global scale 1.000000
[BIN] Version 5.0 (coords: float / scalar: float)

An example cloud that breaks interactors:

Code: Select all

Box dimensions
X: 6.95995
Y: 9.9717
Z: 90.5773
Shifted box center
X: 0.108011
Y: 0.37
Z: 49.8173
Global box center
X: 0.108011
Y: 0.370000
Z: 49.817314
Points 29,142,789
Global shift (0.00;0.00;0.00)
Global scale 1.000000
[BIN] Version 4.8 (coords: float / scalar: float)

Another difference is the cloud that breaks the interactors started life imported from the PCL (*.pcd) file, and includes a sensor object.

The thing that makes me a bit suspicious is the overall size difference

Code: Select all

X: 10710.3		X: 6.95995
Y: 7588.1	vs	Y: 9.9717
Z: 2921.39		Z: 90.5773

[daniel]

How strange... I don't think it's related to the cloud size though... I never encountered this issue with any cloud I have.

Maybe because of another type of entity. Do you have specific entities other than clouds?