N
I just found that the library would wipe out the GLUT.That's what happens when you accept the first reply you have met, you get the wrong GLUT 3.7 information not to be used, but http://freeglut.sourceforge.net/ is completely compatible with him.But your question concerns another matter. GLUT and his analogs are not appropriate to create a game. He doesn't give you control over the main cycle, and you really need him in the game. http://freeglut.sourceforge.net/ has a way to run the main cycle, but it's very uncomfortable. GLUT is intended to write graphic demonstrations. It's very important to test new graphic effects, so if necessary, it should be in your toolbox. But your core game code should never use it. https://www.glfw.org/ - it's an easy GLUT, game-oriented alternative. It provides basic support for things other than the establishment of the OpenGL window. It allows you to inject data, download texture images and stuff. http://www.libsdl.org/ ♪ https://www.sfml-dev.org/ and https://liballeg.org/index.html - it's multimedia. They can create OpenGL windows, but they do. much. More. They provide full support for the introduction, sound and other things needed to create the game. If you're playing, either one of them is a good starting point. I personally like Allegro 5, but it's just my bias towards good documentation and clean API.It is also worth mentioning that all AAA producers do not use any of the proposed games. Well, they don't use anything with an open source code. They could, but if they're gonna use the library, they'd prefer to use the library. There are some exceptions like ODL or Bullet.GLUT is not only a library, but also an application software interface (API). The reference library is really outdated. API is another case, it was a good start, it just needs to be refined to overcome constraints and meet new needs. Main ongoing implementation - http://freeglut.sourceforge.net/ which is maintained and not outdated.The above problem with " managing the main cycle " is not correct. With the new versions of GLUT, you can better control the game cycle (if this is important to you). The limitation was corrected by the function glutMainLoopEvent()♪ These and other restrictions are considered here: http://en.wikipedia.org/wiki/OpenGL_Utility_Toolkit " With new versions of GLUT, you can better control the game cycle.
(if important to you) " . It's a game, so, yeah, it's important to you.
Moreover, glutMainLoopEvent is hardly a good way.
Main cycle control. He still uses the model,
Managing events, reporting to you, not a survey model where
You get the data you need when you want it.Says Nikolai Bolasov.I have to say that a model managed by events is bigger.
It's more effective than a survey, unless you're asking for data,
stored on the basis of events (which is perfectly normal). To question
Systems resources should be carefully managed.Operates Ingemar Germans.Qt supports OpenGL. Look at this. https://www.openinventor.com/ And think about whether it makes sense for you to go straight to the top 3D API.The interpreter ' s notes, in practice, observed that 2D and 3D primitives can easily be painted in Qt (from Qt 5) for the drawing rules (conveyer) I can't answer, but for my tasks, I've had enough power and I haven't noticed any difference. I will also mention that Qt 6 has done a lot of work towards 3D graphics and visualizations.
