Paper and pen are the best tools for computer development. Better than any computer-aid design tool, IDE or anyelse, indeed.Originally Posted by azrael11
Welcome and good luck.
Paper and pen are the best tools for computer development. Better than any computer-aid design tool, IDE or anyelse, indeed.
Welcome and good luck.
No signature provided yet.
Maybe it's me, but I can't seem to get SDL working...
How do I add SDL to RAD STUDIO XE?
We are going to need more details to help you. We know that you are using Delphi XE, but what SDL headers are you using? JEDI-SDL or another packaged set of SDL headers?Maybe it's me, but I can't seem to get SDL working...
How do I add SDL to RAD STUDIO XE?
JEDI-SDL unfortunately has the disadvantage of needing extra code added to it's list of supported compilers to work. Something that needs to be fixed in a rewrite.
Jason McMillen
Pascal Game Development
Co-Founder
Hello LoPiTaL and welcome to PGD!
I think GLScene is a pretty good engine and it does seem to make some aspects of game development easy, however I still say it's not the best way to start. I say this simply because it does nothing to teach you about the basics of writing a game. You may not be new to a lot of the concepts that go into making a game, but most that come into game programming are and it helps to go through the steps or lessons in making some of the classic games before moving onto something 3D where there is so much material it distracts from the basics. How it's structured, how objects collide and how to make them interact the way you need.
Graphics and Physics Engines are an advanced state of a library, they take away much of the work that needs to go into the coding of many of the aspects of the graphics and the physics. This is great if you already have learned how this all works, but if you truly want to learn to become a game programmer, be able to code the missing pieces when something doesn't work right or even write your own, you need to learn the basics before you try learning how to do everything else.
You may have fun playing with GLScene and tinkering with it, but if you want to do something outside of what that specific engine can do, you may have to go much farther back than you would like just to do that.
All that said, if you are having fun playing with GLScene and are able to make some use out of it, that's not necessarily a bad thing, but it can be important to go back and learn the proper steps of game programming if you want to make a proper game and know how to go about it the right way. Especially if you want to continue making games for the long run...
Jason McMillen
Pascal Game Development
Co-Founder
GLScene is very good engine... A lot of good pieces of software writing from this engine....
It is simple and NOT... Has many advances and many dis... Like(Luck of support above OpenGL 2.0)...
But for startes and for advace users it is really a good choice...
When you choose an engine just look what you looking from the engine to fit in your program that you want to make...
I use GLScene combine with SDL the result is very good for me...
BUT all of this must have time and time and time to read and try codes...
So Good choise the GLScene Good Choise ZenGL on any other engine that it helps you to create the wonder you have in your mind...
Hope i help....
Will how about making a Page For All the newcomers to pascal community showing them (point them) pages,tips,engines,with simple advises from the makers of the engines... Just an Idea...
I think this could be an interesting discussion. Would you recommend a new aspiring game developer to start out with a low level or high level framework? You're for the low level. Let the programmer learn how all the aspects of a game work.Hello LoPiTaL and welcome to PGD!
I think GLScene is a pretty good engine and it does seem to make some aspects of game development easy, however I still say it's not the best way to start. I say this simply because it does nothing to teach you about the basics of writing a game. You may not be new to a lot of the concepts that go into making a game, but most that come into game programming are and it helps to go through the steps or lessons in making some of the classic games before moving onto something 3D where there is so much material it distracts from the basics. How it's structured, how objects collide and how to make them interact the way you need.
Graphics and Physics Engines are an advanced state of a library, they take away much of the work that needs to go into the coding of many of the aspects of the graphics and the physics. This is great if you already have learned how this all works, but if you truly want to learn to become a game programmer, be able to code the missing pieces when something doesn't work right or even write your own, you need to learn the basics before you try learning how to do everything else.
You may have fun playing with GLScene and tinkering with it, but if you want to do something outside of what that specific engine can do, you may have to go much farther back than you would like just to do that.
All that said, if you are having fun playing with GLScene and are able to make some use out of it, that's not necessarily a bad thing, but it can be important to go back and learn the proper steps of game programming if you want to make a proper game and know how to go about it the right way. Especially if you want to continue making games for the long run...
But why not recommend the other way? Give him a library and some instructions and he'll be able to make a Pacman clone in a day or so. As new to the field it must be encouraging to quickly get some results. In this first stage they will learn about game mechanics and how a game functions on a high level. Presumably the library they're using has been made by a veteran game developer (team) so they'll learn a sensible way to structure a game. They'll learn a lot on game development and be able to have something to show for it.
At some point they can then choose to delve into further low level stuff. Figure out to open your own window with hardware accelerated graphics, load textures and start rendering primitives. Their experience from the library they started out with will give them an idea about how to organize their low level stuff. And during this low level phase they don't have to worry about things like how to implement game mechanics as well because they already master that part.
Though I'm not sure which library I would recommend I would probably recommend a higher level one. Something where the programmer can open a hardware accelerated window and make a sprite move in four directions with no more than 50 lines of code.
Imagine I've written something clever here inspiring you to make something awesome. If that happens give me credits
with Allegro.pas for example
Current (and lifetime) project: FAR Colony
https://www.farcolony.com/
One of the other major things with picking up any new library or engine is documentation. Some of the developers of these like to hope that all you need to know is the list of functions, but sadly this is not so. If there is insufficient documentation, it's not a very good starter library, let alone an easy library to get to know how to use it well.
First and foremost a game library or game engine will live and die by it's documentation.Especially all those that are supposed to be all-encompassing. I'd have to warn away from libraries and engines that don't have proper documentation, especially for someone new.
Jason McMillen
Pascal Game Development
Co-Founder
Reply With Quote
Bookmarks