-
Notifications
You must be signed in to change notification settings - Fork 39
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
Stereoscopic configuration issues #13
Conversation
It would be very helpful if you could identify the commit you found that Thanks very much for doing this, provided you've actually tested this, I'm Harvey On Tue, Aug 5, 2014 at 7:51 AM, Kavon Farvardin notifications@github.com
|
Hi Kavon, I have a few questions I ask everyone that contributes code, basically If you can agree to the below, can you reply in an email containing the text: Signed-off-by: "Your Name" you@email.com Be aware this will appear in the public git record of the project, and Thanks!! Harvey harvey.harrison@gmail.com
|
Hi Harvey, Yes that is the commit I was referring to. (167369e On Tue, Aug 5, 2014 at 1:33 PM, Harvey Harrison notifications@github.com
|
Yes, the contribution agreement is fine by me. Signed-off-by: "Kavon Farvardin" kavon.farvardin@gmail.com On Tue, Aug 5, 2014 at 1:51 PM, Harvey Harrison notifications@github.com
|
I've pulled in the first two patches from your request and added you signed off by to them. I'm considering the swapEyes patch now, I'm thinking it will need to be reworked a little bit, we can't I'm thinking a getter in Canvas3D that returns the constant that is wanted. I'll push out a commit for your review by end of day, have a bit of work stuff I need to get done first. Harvey |
Kavon, I've pushed out an alternate approach to the swapfields branch, commit: c4f1134, could you take a look and see if that would be sufficient for your needs, the system property approach would make sure no existing user is impacted Harvey |
After looking into this further, whether you need to switch the left/right On Wed, Aug 6, 2014 at 1:00 AM, Harvey Harrison notifications@github.com
|
Sure, let's hold off for now, did the patch actually work for you? If it Harvey
|
I was trying to transition a piece of software that supports stereo 3d from 1.5.2 to 1.6, but found it wouldn't actually detect whether or not stereo is supported. The "best configuration" generated based on the specifications turned out to be the issue.
On systems which have support for stereoscopic 3D (most quadros, etc), even if the driver has specified that it is on, using getBestConfiguration does not yield a configuration that ever says that stereo is supported unless if it is created as stereo REQUIRED, which defeats the purpose of PREFERRED, because if it's REQUIRED and not actually available, it is expected to return null according to the documentation, which it doesn't seem to do either.
I fixed this issue by finding the commit that broke this, and it had to do with a graphics configuration change for mac (which was merged into your trunk from another fork). Most of the code in these commits were based on how the prior commit functioned. I thought you might want to integrate at least some of these changes.
Note: