Just to sum up this thread for anyone else having this issue, this would be the correct way to do it:

QImage img; unsigned char* data; data = new unsigned char[4*width*height*sizeof(unsigned char)]; img = QImage((uchar*)(data),width,height,QImage::Format_RGBA8888);

Make sure you allocate the appropriate space needed. E.g. if image format is RGB, size of the data array will be 3 * width * height * sizeof(unsigned char) and the QImage format will be QImage::Format_RGB888.

Thanks all for your help.

Hi and welcome to devnet,

From the looks of it you are using both glu and the fixed pipeline.

Since you are starting a new project, may a suggest taking a look at the Qt OpenGL examples and their use of current technologies like shaders ?

Hi
Hmm, nope. it looks very much like the sample
with some code from TriangleWindow::initialize()
in the render() function.

@SGaist

My solution is heavily inspired by: this old ogre wiki post (should have linked it as well, forgot about it until now).
I mostly slimmed it down to what I posted as my solution, but I agree if I have time I'll try to make an example/entry.
There are some things that need to be updated from the linked post to fit Ogre 2.1 since the post is old.

@HW-Developer
OK, I don't want to discourage you, maybe you just want to play with it, I've said I have no knowledge. But maybe if that sort of thing was freely available from 2005 there are some more recent ones which might be better?

@kenchan I want to draw it on QOpenGLWidget and i want to relate it to an audio file so i can position it wherever i want

https://drive.google.com/file/d/1SHw3k6gY9pz8cL7skhDUPUf2NrwF4xeE/view

@HW-Developer Start here http://doc.qt.io/qt-5/qtxml-index.html

Off the top of my head, I am not sure if fbo::save() is valid while the FBO is still bound as the target for drawing. Try releasing it first and then calling save. An FBO can only be used as a texture when it is not bound as a target -- I think that applies to all readback operations.

Also, you have a glClearColor, but you never glClear(). If there is garbage in the depth buffer of the FBO, maybe your stuff is never getting drawn. glClear() the depth buffer and the image buffer before you draw. At very least you should be able to see the clear color in the FBO when you save it, so you know the binding is working at that point.

Alright,
with much time and an extensive amout of google search I managed to cobble a working QOpenGLWidget program together.

I used this official Qt-Example as a basline:
http://doc.qt.io/qt-5/qtopengl-cube-example.html

here is the combination with my Tesseract code
https://github.com/DeiVadder/Tesseract-Challenge-OpenGL

It's working, yeah me!!, but I have the feeling that it's far from ideal. I'm just glad I managed to draw something in 3d.

Anyway, closed and solved.

@SGaist
Thank you so much! Your response was much helpful!

Before crossing that feature definitively, I'd recommend asking on the interest mailing list. You'll find there Qt's developers/maintainers. This forum is more user oriented.

@dalishi
You should not mix painter and gl calls like that. You should put gl calls between calls to beginNativePainting() and endNativePainting(), which are painter functions. It might also help to save the painter state before and restore it after depending on how it messes up your gl stuff.
the docs here tell you what the painter does to the states.

@Ilja
Super good to hear.
Thank you for the feedback.
happy programming.

Hi and welcome to devnet,

What version of Qt are you using ?
On what OS ?
Which architecture ?
What type of image is that ?

Hi,

What version of Qt did you install ?
What graphics card are you using ?
Did you check whether you had up to date drivers ?

If found the way by myself, if this can help to someone, is a question of attaching the texture again and change it before the fbo generation.

Like:
```
glBindTexture(GL_TEXTURE_2D, d->fbo->texture());
glTexParameteri(GL_TEXTURE_2D, GL_TEXTURE_MIN_FILTER, GL_LINEAR); // Linear Filtering
glTexParameteri(GL_TEXTURE_2D, GL_TEXTURE_MAG_FILTER, GL_LINEAR); // Linear Filtering

@seyed As I understand things, you need to get hold of the item's transform and do whatever your rendering needs to do with it for it to have effect... see https://stackoverflow.com/questions/28535528/how-can-i-get-transform-matrix-for-qquickitem . (Similarly, nothing will implement the opacity property for you... you have to bring it into your OpenGL code and use it in your fragment shader.)

Hi,

IIRC, since 5.8 or 5.9, QtMultimedia has OpenGL (vertex/fragment shaders) support for that kind of format. You should take a look there.

Hi,

What graphic hardware are used on these machines ?
Version of the driver ?

Also note that 5.7 is outdated, you should consider updating to the current LTS which is Qt 5.9.4 or even 5.10

I fixed this issue by my nvidia driver to recent version from this PPA

ppa:graphics-drivers/ppa

I think you have to add a QMultiSampleAntiAliasing to either a QRenderStateSet or a QRenderPassFilter. Did you also enable it in the OpenGL format that you set?

If you don't need to render to anything else but to that texture you receive from the Oculus SDK, then you actually don't need anything Qt-related. Just use OpenGL C API provided by the platform.

@SGaist
I use Qt 5.9.2.
The problem is that any opengl scene isn't visible where it should be. Instead scene I see a captured part of the desktop under an application window - part of Qt Creator text editor window for example.
I'm not sure but I haven't noticed this effect in early 5.x. I check 5.6 tomorrow.

@Kart said in Cross compile QtWebengine 5.9.1 on embedded linux:

I came to know that QtWebengine can use software renderer such as QtQuick2drenderer in Qt 5.7. What are the possibilities that i can do the same in Qt 5.9.1 ?
I cross compiled QT5.9.3 for raspberry pi CM3 with X11 support. but when runining qtwebengine example ( demobrowser) I find a problem : mouse click isn"t handled
i dont know if this related to my corss compilation or to QT5.9.3 it self.
here is a link ( you could enable or disable X11 support before starting the compilation)
https://github.com/chschnell/build-qt5-rpi

@SGaist My experience is different. The computer reported having DirectX 12 but it didn't work. Anyway, I am no longer worried about this particular computer.
Thanks