Game Development

What do you mean by not compatible ? If they have found a bug/regression build error, did they report it to the "bug report system":http://bugreports.qt-project.org ? If not it would be a good idea to, otherwise the Qt devs won't hear from it (unless it's talked about on e.g. the interest mailing list, but still a bug report would be best)

No grudges that I know of, as to why one is and the other is not, you would need to go back in the history of Qt.

I don't think it's nonsense, the classes are there to be used. However there might have been a change that broke something and it's important to fix it.

What I would recommend is: open a bug report (or several depending on your problems) with all infos needed (OS/Compilers etc.) and the errors you are getting.

OpenGL has support for 3D via draw buffers.

With the usual double buffering setup when swap is called the GL_FRONT and GL_BACK buffers are swapped and you always draw to GL_BACK.
For 3D OpenGL has separate buffers for left and right eye: GL_FRONT_LEFT, GL_FRONT_RIGHT, GL_BACK_LEFT and GL_BACK_RIGHT.

So this would be something like:

glDrawBuffer(GL_BACK_LEFT); //draw the scene for left eye glDrawBuffer(GL_BACK_RIGHT); //draw the scene for right eye

The thing with a 3D and OpenGL though is that for whatever reason industry decided that it's not your average consumer thing. To output 3D signal to your TV the graphics driver needs to allow it. Most consumer drivers don't support stereoscopic OpenGL. You need a "professional" card like NVidia Quadro or ATI FirePro 3D. It's actually the same hardware as the usual geforce or radeon except the drivers are different and for that you pay extra :(

That's why you don't see any OpenGL games work with things like NVidia 3D Vision and it's a shame really but that's how it is.

Didn't even know both ways existed :o
But thanks, it works now :)

With a pointer you don't "share" the object but you share the memory the object is in. So you always know you have the right object and the newest object.

Pointers and there effect are hard. I also struggle with them. But there is a good c++ "book online.":http://cppannotations.sourceforge.net/annotations/html/ Chapter 16. But there is more about pointers in this book.

I don't really know what you meant about collision but it's all in the same memory. So if you always want this object that's the way to go.

I know, and I do enjoy learning these things. I just wish I would spend a little less time coping with all sorts of errors and more time on actual coding :) But I guess that's a part of it too.

Well, just finished rewriting the code. All I have now is a bucketload of pointers and references and got rid of those errors I previously had. All thanks to you!

Yes, sometimes it's a simple thing :) But can be hard to track down :-D

Well, in Qt3D, a class named "QGLCamera" is available, you can use pan(), tilt() and rotate() method to rotate camera by different axis.

Isn't this thread a duplicate of "this":http://qt-project.org/forums/viewthread/39539/ ?

Thanks a lot vidar! I will study some QThreads. I will mark this thread as "solved", but more ideas and discussions are more than welcome!

Resolved the problem. It's necessary to configure the QSurfaceFormat, to use Double Buffer. I does not came by default.

Hi!

[quote]Is this approach alright? I dont want high-performance but it would be wondeful if this runs on mobile devices :)[/quote]The way you've split things between QML and C++ looks well-optimized to me. QML is optimized for graphics and user interaction, while C++ is best for number-crunching.

[quote]

QML Timers for events
[/quote]Use a QML Timer to drive QML functions, usea C++ QTimer to drive C++ functions.

[quote]

QMLEngine loads all relevant types (maybe 50-100?)
[/quote]Use a QQuickView, which is higher-level than a QQmlEngine. Also, you don't need to load the types individually. Just load your "main"/"top-level" .qml file, and it will automatically pull in the others that it depends on.

All the best with your project!