Game Development

@mrjj Thank you for the link and regarding the multiplayer my teacher said that i can do either over the internet or LAN , i believe LAN is a much simplier thing to work with so i'd probably go with that if there are any stuff regarding this topic, for my graduation project it's required for game to be played by ( for example 4 ) players, but each player has to play the game on their own PC. @jksh ye i wanted to implement that into my game and of course like i said player vs the pc, but my professor said that i should put a multiplayer option in there aswell if i want to get a better grade.

Hi and welcome to devnet, You should add: Qt version used Linux distribution used Device connected How did you install Qt

Can you try with the latest Qt 5.13 version ?

for anyone interested. Here is the link to the bug report on Jira: https://bugreports.qt.io/browse/QTBUG-75373 you can upvote it there to give it more attention

Apparently. This was working before. Looking through the documentation it seems this was not the best use case for the tree view so it looks like a safe change on our side.

@hskoglund I drew hexagons on a UNIX box more-years-ago-than-I-care-to-admit. I doubt I used floating point sine/cosine calculations. Don't the vertices come out at some nice integer coordinate values for 60 degrees if you pick a suitable integer for the side lengths? a slight complication in those days was the x/y ratio for the screen pixels, it wasn't 1:1 That's not your problem as a programmer! 60 degrees is 60 degrees. The user can go buy a different monitor/graphics card if his ratio is not right :)

I've got the same issue with Qt3DExtras::QText2DEntity. But I found the workaround. Look like there is a bug? in implementation of Qt3DExtras::QText2DEntity that prevents internal initialization (QText2DEntityPrivate::setScene is never called). This happens when scene is already visible and Qt3DExtras::QText2DEntity is created with parent entity passed to constructor. The workaround I used to make it work is to pass nullptr (which is default) as parent in constructor and call ->setParent(parentEntity) in separate call. m_text2dLabel = new Qt3DExtras::QText2DEntity(); m_text2dLabel->setParent(parentNode);

@mrjj Haha, I suppose it does. I think if it were in circles or odd shapes it'd look more like it. hehe.

Well... You are technically writing to a closed QIODevice. So how can you expect to get something out of that buffer ?

Hi and welcome to devnet, Sounds like QCommandLineParser would be a good start.

I saw terrain rendering in this old video, but I couldn't find the code to it: https://www.youtube.com/watch?v=bYgSxoXgSU8 Maybe you have more luck.

@KillerSmath Nothing happens... XInput starts its thread as it have to, but no device is detected when the joystick is connected.

Hi, You have QGraphicsObject which combines a QGraphicsItem and QObject.

@Chris-Kawa On Qt5.5 this is still very effective! Thanks

Hi Well the question is very broad. You could look into Qt3D. https://doc.qt.io/qt-5/qt3d-index.html https://doc.qt.io/qt-5/qt3d-overview.html You could also use a game engine like https://unity.com/ which has tons and tons of tuturial. Or https://godotengine.org/ Which i found very easy to use.

I'm not sure if this is best idea. But try to store pointer to that context. Then you could utilize QOpenGLContext::makeCurrent and QOpenGLContext::doneCurrent

Apparently there is some black magic involved. If I copy and open the configureButtons example, it works. If I rename the example folder and pro file to configureButtons2, it does not work anymore. This means, following the example code line by line will not make it work in your application. What helps though is to just rename your project to configureButtons ... That way the gamepad works as expected. -_-