[BUG]: Camera issue in Orientation Indicator processor

[mousse183]

Required prerequisites

• Make sure you've read the documentation. Your issue may be addressed there.
• Search the issue tracker and Discussions to verify that this hasn't already been reported. +1 or comment there if it has.
• Consider asking first in Slack or in a Discussion.

Problem description

Hello, I noticed a camera issue while working with the Orientation Indicator processor. To reproduce the issue :

1. Open the orientationindicator workspace in inviwo\modules\basegl\tests\regression\orientationindicator.
2. Right click on the canvas to open the menu and change the camera view (X+, X-, Y+, Y-, Z+, Z- or fit to data). OR change directly the view by using camera actions from the Mesh Renderer processor.

The volume will disappear and the position indicator mesh will start shaking. In order to restore the correct view, I use the camera actions (any button X+, X-, Y+, Y-, Z+, Z- ...) from Volume Raycaster or Entry Exit Points processors.

I also noticed that the Orientation Indicator processor is missing camera actions in its camera property, maybe linking it with camera property from Mesh Renderer processor is what causing the issue.

Inviwo version

0.9.11.1 cloned from master

Operating system?

Windows

Compiler / Version

Visual studio 17 2022 [Release]

Qt Version

6.3.1

Reproducible example code

No response

Inviwo log

No response

[petersteneteg]

Hi

Thanks for reporting, I have reproduced the issue and have think I know the issue at hand

Unfortunately I don't have good solution at the moment. The problem come from the fact that the system tries to fit the orientation indicator in to the center of the view not the raycasted image. And the orientation indicator will automatically adjust to the changed camera and move to the "side"... Hence we get some bad feedback... A workaround is to move the mesh renderer to be a background input to the ray caster instead... That will mean that the indicator will be in behind the raycastering and not infront, But in that case the fitting will be applied to the raycasting as expected. A better version might be to use an image overlay processor to add the orientation indicator instead.

But the fundamental problem of what to "fit" in the view remains... at this point we will just delegate that to the first camera that is found when propagation bottom up...

[mousse183]

Hi,

Thanks for answering, I tried to make the Position Indicator as background to the Raycaster processor, and it worked.