-
Notifications
You must be signed in to change notification settings - Fork 81
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
42 Cam graphics choppy using VMware with an Ubuntu guest #45
Comments
It seems like the issue was introduced in this commit. f84857f |
I'm also seeing weird graphics on Ubuntu 20.04 native - the Cam view seems to go forward smoothly for a second, then kind of jump back a bit, then go smoothly for another second, then jump back, over and over. I could try to share a video if that would help. @chupalt's fix works for me too. It also has the nice side-effect of solving a different weird graphics bug I've been having where the Cam and Orrery windows resize uncontrollably whenever I try to drag the window around. I had gotten around that issue by commenting out line 6163 in 42GlutGui.c, but that removes the ability to resize the cam window at all: Lines 6162 to 6164 in e6862f6
I don't know enough about the graphics code here, but I'll keep using @chupalt's fix for a while and see how it goes. |
Also have same problem on host system, without vmware #52 |
I don't know why this works, but it does. I had no issues on OSX or msys, and my experience on Ubuntu isn't exactly what y'all are seeing, but it's clear to me that Ubuntu/xterm/whatever are happier without that call than with it. (And OSX and msys don't miss it when it's gone...) Look for a new code drop soon. |
Validated new Actuator Module and Thruster Processing with ZERO_TEST Mission Closes ericstoneking#32, ericstoneking#42, and ericstoneking#45 See merge request pavel.galchenko/deepthought!25
A recent commit has made the graphics choppy in the 42 cam when running in VMware with an Ubuntu guest. This problem seems to be recently introduced. An early September clone of the repo did not exhibit this behavior. Seeing the following error in the dmesg log.
[drm:vmw_stdu_primary_plane_atomic_update [vmwgfx]] ERROR Failed to update STDU.
We will continue to review recent commits to see if we see an obvious error and will report back if we do.
The text was updated successfully, but these errors were encountered: