-
Notifications
You must be signed in to change notification settings - Fork 27
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
linux part of Precisiontimer is buggy. #89
Comments
Any update on this? |
I'm moving this to 0.5, want to close this milestone to few awesome :) |
…to compare advanced tutorial 01 to win / mac before closing Issue #89
I think this one is fixed, but I need a running reference i.e either WIN or OSX to compare with, or a video of it. |
I'll try to make a video during this week. |
Added movie |
@M-F-K Status update on this please? |
…n see the timer is correct, but THere are 2 things that mess this tutorial up. 1) The placement location of the Draco image is wrong, - it is not centered on the screen but is instead spinning in the lower right corner. 2) The timer is ok. As you can see in the screenshot the number starts with 13 ... and this is the seconds .... but there is no rounding so we got the complete number : 13222053. This becomes a problem in the tutorial line: // Update Draco position each second mDraco->setAngleXYZ(0, 0, mSecond + 10); I will investigate part 2 further.
Ok, there is another issue for this. The coordinates are f***ed up now because of a change I made a week ago (some fix about hotspot). See issue #113 |
Sorry, closed accidentally (want to go too fast XD) |
Coordinates are fixed now. |
Yep - coordinates is good in linux, - now I only need to truncate the timervalue. |
Tested with basic tutorial 16 (timer tutorial), - compared it against DarthMike's movie (in the results folder). As far as I can see, it is exactly the same. Closing. |
Implemented the linux part of the precisiontimer, but it is still buggy. This can be seen in the avanced 01 test with surface grid (it probably plays to fast - jumps).
The text was updated successfully, but these errors were encountered: