Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

GUI: Head not turning anymore #135

Closed
chris-hld opened this issue Jan 30, 2019 · 7 comments · May be fixed by #140
Closed

GUI: Head not turning anymore #135

chris-hld opened this issue Jan 30, 2019 · 7 comments · May be fixed by #140

Comments

@chris-hld
Copy link
Contributor

chris-hld commented Jan 30, 2019

The latest master commit is not updating the GUI head orientation, when connected to a head tracker.
Updating the TCP interface and sound output works, it's only the GUI.

@mgeier
Copy link
Member

mgeier commented Jan 30, 2019

I guess the reason is that I changed the trackers to manipulate the "reference offset" instead of the "reference". See "collateral changes" in #127.

Ideally the head in the GUI should show both pieces of information, but I'm not sure how this can be achieved.

For loudspeaker-based renderers, there is a little cross symbol that shows the reference offset.

@chris-hld
Copy link
Contributor Author

Ah, yes, that might be it!
I agree with the change. Even if listeners turn their head, the scene coordinate system stays the same.
But in this case the GUI Head should reflect the "reference offset"!

@chris-hld
Copy link
Contributor Author

BTW, there is also a little cross on top of the GUI head. So maybe it is even possible to show both?
image

@JensAhrens
Copy link
Contributor

This cross marks the origin of the global coordinate system. It is not movable.

In qopenglplotter.cpp, there is an if/else statement:

if (_plot_listener)
{ 
    (...)
}
else
{
    (...)
    // draw cross (showing the reference offset)
    (...)
}

This would needed to be changed (it's here) for the reference offset also to be visible when a listener is apparent.

@mgeier
Copy link
Member

mgeier commented Jul 19, 2023

I think this has been fixed in #358 and #360.

@HaHeho
Copy link
Contributor

HaHeho commented Jul 20, 2023

I think this has been fixed in #358 and #360.

The latest release indeed fixed such an issue with a Polhemus tracker for me.

@chris-hld
Copy link
Contributor Author

Closing since seems to be fixed in the meantime.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants