The PyBullet GUI ui issue - pybullet

Sample Displayed UI
I am trying to run a PyBullet project of my own. The terminal output seems okay with following messagelines. However, the UI is broken and very tiny. I am wondering if there is anything I am doing wrong or I didn't do.
argv[0]=--opengl3
startThreads creating 1 threads.
starting thread 0
started thread 0
argc=3
argv[0] = --unused
argv[1] = --opengl3
argv[2] = --start_demo_name=Physics Server
ExampleBrowserThreadFunc started
X11 functions dynamically loaded using dlopen/dlsym OK!
X11 functions dynamically loaded using dlopen/dlsym OK!
Creating context
Created GL 3.3 context
Direct GLX rendering context obtained
Making context current
GL_VENDOR=NVIDIA Corporation
GL_RENDERER=NVIDIA GeForce RTX 3070 Laptop GPU/PCIe/SSE2
GL_VERSION=3.3.0 NVIDIA 525.78.01
GL_SHADING_LANGUAGE_VERSION=3.30 NVIDIA via Cg compiler
pthread_getconcurrency()=0
Version = 3.3.0 NVIDIA 525.78.01
Vendor = NVIDIA Corporation
Renderer = NVIDIA GeForce RTX 3070 Laptop GPU/PCIe/SSE2
b3Printf: Selected demo: Physics Server
startThreads creating 1 threads.
starting thread 0
started thread 0
MotionThreadFunc thread started
ven = NVIDIA Corporation
ven = NVIDIA Corporation
I tried to use opengl2. The GUI ui is okay, but still tiny. And the plane lost transparency.

Related

glxBadDrawable when using bgfx

When using the following BGFX code:
#include "GLFW/glfw3.h"
#include <bgfx/bgfx.h>
int main() {
glfwInit();
GLFWwindow* window = glfwCreateWindow(800, 600, "Hello, bgfx!", NULL, NULL);
bgfx::Init bgfxInit;
bgfxInit.type = bgfx::RendererType::Count; // Automatically choose a renderer.
bgfxInit.resolution.width = 800;
bgfxInit.resolution.height = 600;
bgfxInit.resolution.reset = BGFX_RESET_VSYNC;
bgfx::init(bgfxInit);
}
A black openGL window pops up and appears fine for a second, however, a GLXBadDrawable error then pops up. I do not know what the cause of this error is, and the other question has no answers and has not been active for some time now.
I believe that this is not an issue with the code, but rather my machine, however, I may be wrong.
I currently have a Lenovo T400 laptop, with a Core 2 Duo P9500. I have 2 built-in GPUs, a Mobile 4 Series Chipset integrated graphics chip, along with an ATI Mobility Radeon HD 3450/3470. I am also running Artix Linux with the 6.0.7-artix1-1 kernel. I also am using the glfw-x11 and glfw packages if that helps, along with the i3-gaps window manager.
I have also attempted to use SDL2 instead of GLFW, and the same issue occurs. However, for GLFW a black window shows up, while in SDL2, a transparent(?) window instead shows up. Searching the github issues page also yielded no results.

Screen geometry transposed under Weston with fbdev transform=90 in Qt 5.9

I have an embedded device where I use Qt 5.9 and Weston. Weston has to use fbdev backend (reasons out of scope) and needs
transform=90
in its output section, otherwise the screen is rotated. It runs fine, but I am unable to get a propper screen size in Qt. To run my application in fullscreen in Qt 5.8 I used:
auto geometry = QGuiApplication::screens().first()->geometry();
view.setGeometry(geometry);
and it was ok. With Qt 5.9 the screen reports its size transposed, so I would have to use
auto geometry = QGuiApplication::screens().first()->geometry();
geometry = geometry.transposed();
view.setGeometry(geometry);
This runs fine again, but the application is no longer portable. I use it on other platforms as well, all work without correctly without transposing.
Looking into the weston log I see
fbdev output 480×854 px
which corresponds to what I get in Qt now. But how to properly detect the rotation caused by transform=90?

All QT applications on my windows machine have garbled GUI

Starting recently, all QT applications have problems with window sizing and offset, f.i. the window origin (0,0) seems to be moved left and up, so that the menu disappears.
This is how it should look:
And this is how it looks with the problem:
Any idea what setting might have gone haywire ?
I suspect this has happened after an update of Intel HD Graphics Drivers. Anyway, since I have NVIDIA graphics aswell I tried to force the use of it instead of the default Intel HD Graphics, and voila!, it works perfectly. I had the same problem within Qt Creator, and this solved that as well.
It should be noted that I changed the default choice to NVIDIA, and now all applications using Qt work fine.

Slow fade in and out in Qt applications

Did someone else experience slow fading in Qt applications, for example when opening a new dialog from a main window? I'm running Ubuntu 12.04. LTS and Qt 4.8.1.
The application where I noticed that does some opengl rendering in a qglwidget. When the application runs, also other windows not belonging to the qt app are affected by slow fading in/out. The thing is that the qt app only uses 20% CPU load (also compiz) so I assume it's not caused by a high CPU load...
Are yours videocard drivers up to date?I had the same problem (using opengl through QGLWidget) and updating solved the problem.
If this isn't the solution,paste us some code.
Hope it helps.

How can xming work with OpenGL?

I have an OpenGL (Java + applications) application deployed on a Linux machine. I need to start this application from a Windows machine, display and operate it on Windows.
My application shows a whole screen of 2D graphics which is constantly updated. Both machines are OpenGL capable (video cards and drivers). When not remote, the application runns ok on both the Linux and the Windows machine
I'm using ssh (putty) and an X server (xming 6.9) on the Windows. All is fine but when I display my graphics I get an "unsupported colour depth" error and nothing is displayed.
Questions:
1. Is there a way I can tweak xming to display my graphics?
2. Is there a better suited solution for my system?