The Irrlicht Game - every1 involved
-
DarkDepths
- Posts: 126
- Joined: Sun Apr 02, 2006 1:21 am
- Location: Canada
ok overclocked my PC to do some devving
here is PNS http://project-ninja-star.googlecode.co ... 3-6-09.zip and it will be the backbone for the client ( a bit like the quake 3 engine used in 993042094204830252395 games )
amd sempron 3200+ 1.8ghz stock @ 2.14Ghz
Nvidia 9600 GT XXX edition factory overclocked GPU = 740 VRAM = 1000
and now @ 807 and 1079 respectively
P.S. I know I can squeeze out more, I just need to crank up the voltage... and anyway what is the point I am getting an Athlon X2 6400+ or Phenom X2 3.2Ghz
here is PNS http://project-ninja-star.googlecode.co ... 3-6-09.zip and it will be the backbone for the client ( a bit like the quake 3 engine used in 993042094204830252395 games )
amd sempron 3200+ 1.8ghz stock @ 2.14Ghz
Nvidia 9600 GT XXX edition factory overclocked GPU = 740 VRAM = 1000
and now @ 807 and 1079 respectively
P.S. I know I can squeeze out more, I just need to crank up the voltage... and anyway what is the point I am getting an Athlon X2 6400+ or Phenom X2 3.2Ghz
I read through the source and one thing i can really say that this is nothing like the quake3 engine.devsh wrote:ok overclocked my PC to do some devving
here is PNS http://project-ninja-star.googlecode.co ... 3-6-09.zip and it will be the backbone for the client ( a bit like the quake 3 engine used in 993042094204830252395 games )
Major thing i can see is no real api. No coding convention, its just loose system of functions!!(you should tell everyone that your idea about programming in c++ is not OO).
I don't see gamestate managment, no entity management. And i really don't see the point in starting with that as source. Oh and btw when the project grows u really don't want to have class or function implemantations in your header file bc that forces u to recompile the whole project each time u change something.
We're programmers. Programmers are, in their hearts, architects, and the first thing they want to do when they get to a site is to bulldoze the place flat and build something grand. We're not excited by renovation:tinkering,improving,planting flower beds.
- The glory days.Devsh, you should learn about source files and header files. Having everything in the header is a bad idea. Heck, you probably don't care anyway. Also, your code is very difficult to read. You should format it better. (Naming functions, classes, member variables etc) Take a look at Irrlicht's source.
When you said your project would be a bit like Quake 3, it implies that your codebase should be re-usable (like Quake 3 is). At its current state I would find it simpler to write everything from scratch ..
Everything starts from a proper design, otherwise you will find yourself re-writing everything at one point because it's too difficult to use. I know, because I spent 2 days rewriting and debugging my character class because I was adding things as I went along without any actual design or system and it all got out of hands. So don't take it as a criticism but advice.
But whatever you choose, keep on going. I wish you luck.
When you said your project would be a bit like Quake 3, it implies that your codebase should be re-usable (like Quake 3 is). At its current state I would find it simpler to write everything from scratch ..
Everything starts from a proper design, otherwise you will find yourself re-writing everything at one point because it's too difficult to use. I know, because I spent 2 days rewriting and debugging my character class because I was adding things as I went along without any actual design or system and it all got out of hands. So don't take it as a criticism but advice.
But whatever you choose, keep on going. I wish you luck.
Well u said its gonna be the backbone and that it is a bit like the quake 3 enginedevsh wrote:did I say the source has to look like Quake 3.
Maybe u should take a look at Sirrf and use that as a backbone. It is for sure better than what u have. And the shaders and stuff can be used whereever.devsh wrote:( a bit like the quake 3 engine used in 993042094204830252395 games )
Last edited by sudi on Sun Jun 14, 2009 8:55 pm, edited 1 time in total.
We're programmers. Programmers are, in their hearts, architects, and the first thing they want to do when they get to a site is to bulldoze the place flat and build something grand. We're not excited by renovation:tinkering,improving,planting flower beds.
Well i might be right that Sirrf is not completly done but thats a decision by the author....anyway at least it supports gamestate management, a working entity implemantation and even scripting for all these components.
So that project way farther than yours bc u have no gamestatemanagement and no entity management.
Maybe atleast consider coping when you don't want to use the lib.....bc that will save u some time and a lot of headeck
So that project way farther than yours bc u have no gamestatemanagement and no entity management.
Maybe atleast consider coping when you don't want to use the lib.....bc that will save u some time and a lot of headeck
We're programmers. Programmers are, in their hearts, architects, and the first thing they want to do when they get to a site is to bulldoze the place flat and build something grand. We're not excited by renovation:tinkering,improving,planting flower beds.
-
ZCCdark203
- Posts: 47
- Joined: Fri May 15, 2009 3:26 pm
- Contact:
And I didn't want to get involved in this thread anymore... 
Anyway, on to Sirrf. I think we can all agree that Sirrf is not finished. But don't let you be mislead by the beta status. In my opinion, Sirrf is already usable. It should be quite easy for a moderately experienced programmer to get started with Sirrf. A complete beginner might have some problems, though. But that can be resolved with good documentation.
As for the reason why Sirrf has already been released. I think it's important for open source projects to "release early, release often". That way you get a clear idea of the needs of the community. Also, the community can often help to find bugs and maybe even better implementations of ideas. You too can help; if you miss something, please tell me.
Just wanted to make that clear as I'm the author of Sirrf. Whether you'll use it or not is not up to me.
Anyway, on to Sirrf. I think we can all agree that Sirrf is not finished. But don't let you be mislead by the beta status. In my opinion, Sirrf is already usable. It should be quite easy for a moderately experienced programmer to get started with Sirrf. A complete beginner might have some problems, though. But that can be resolved with good documentation.
As for the reason why Sirrf has already been released. I think it's important for open source projects to "release early, release often". That way you get a clear idea of the needs of the community. Also, the community can often help to find bugs and maybe even better implementations of ideas. You too can help; if you miss something, please tell me.
Just wanted to make that clear as I'm the author of Sirrf. Whether you'll use it or not is not up to me.