You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I tried this but it was after the graphics was setup and it crashed. I think this will have to be done right when the graphics are initially setup and I'm not quite sure where that's at.
The text was updated successfully, but these errors were encountered:
OSG isn't setting up the graphics contexts (plural - two per stereo display
at least, I think), VR Juggler is. I'm pretty sure I asked a question on
the VR Juggler mailing list and/or on their bug tracker - in any case, that
would be the way to go. (And yes, I agree that antialiasing should be used)
On Mon, Jul 23, 2012 at 12:10 PM, Patrick Carlson < [email protected]
wrote:
This may be something easy that may improve the visualization. Based on
this:
I tried this but it was after the graphics was setup and it crashed. I
think this will have to be done right when the graphics are initially setup
and I'm not quite sure where that's at.
Reply to this email directly or view it on GitHub: #93
Ryan Pavlik
HCI Graduate Student
Virtual Reality Applications Center
Iowa State University
Changing the number of samples to 4 and 8 didn't seem to do much but actually testing this is difficult because it's such a minute adjustment. I don't think I can distinguish when it's on or off. :) I will read up to see if these are documented in VRJuggler.
This may be something easy that may improve the visualization. Based on this:
http://www.mail-archive.com/[email protected]/msg24993.html
It looks like enabling anti-aliasing in OSG is fairly straightforward. Perhaps something like:
I tried this but it was after the graphics was setup and it crashed. I think this will have to be done right when the graphics are initially setup and I'm not quite sure where that's at.
The text was updated successfully, but these errors were encountered: