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
Ps3eye fixes in Windows and OSX. #162
Conversation
Oh, by the way - you can force-push changes over an existing branch, thereby updating a pull request and replacing the commits, no need to always open and close pull requests, as it makes it hard for me to follow along where we are at the moment (I think I just commented in a commit in a closed pull request). |
Sorry about that. I'll look into force-push. Do you want me to work on the closed PR or is it OK to keep this one for this time? |
Yes, let's keep this one for this time. No problem, just a suggestion for the future :) |
Setting red and blue balance values does not work well with PS3EYEDriver. Comment out for now.
|
||
char *intrinsics_xml = psmove_util_get_file_path(INTRINSICS_XML); | ||
char *distortion_xml = psmove_util_get_file_path(DISTORTION_XML); | ||
camera_control_read_calibration(tracker->cc, intrinsics_xml, distortion_xml); | ||
camera_control_read_calibration(tracker->cc, intrinsics_xml, distortion_xml); // Crashes if cc is NULL |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This shouldn't happen anymore, now that you return NULL
above for when tracker->cc
is NULL
.
This should be ready now. |
Looks good now, thanks a lot :) |
This replaces PR #152
-tracker fails gracefully when PS3EYE specified at compile time but not plugged in.
-exposure and gain parameters passed through to PS3EYE when using PS3EYEDriver. This greatly improves the performance of the tracker in well-lit environments.