Would you be interested in a new series of wiki tutorials, covering making various game genres using ogre?
I've worked on three diferent genres using Ogre so far - Platformer, 2.5D adventure game and a 3D strategy game and would be glad to document their development process.
The idea is to document every relevant technique used and any major problems encountered in realizing the project in order to help others making a game of the similar genre not having to invent the wheel, or at least being able to see a different approach (and hopefully suggest a better one
Absolutely - any and all tutorials & educational material are welcome in the wiki, so long as they're connected with Ogre. Very practical experiences like this are especially useful.
I'm working on it right now, where should i put a link to the genre page? I was thinking either in the main wiki page under Using Ogre or under the tutorials section
I've put it in Using OGRE on the main page. If you allow, I'd also change the name from Genres ot Experiences and create a category for it.
I think Experiences fits better than just Genres as the title.
And btw: Thank you for sharing your experiences with the community!
Ogre Admin [Admin, Dev, PR, Finance, Wiki, etc.] | BasicOgreFramework | AdvancedOgreFramework Don't know what to do in your spare time? Help the Ogre wiki grow! Or squash a bug...
A database query syntax error has occurred. This may indicate a bug in the software. The last attempted database query was:
(SQL query hidden)
from within function "SearchMySQL4::update". MySQL returned error "1194: Table 'wiki_searchindex' is marked as crashed and should be repaired (localhost)".
edit: it seems to save the page but it reports the same problem every time I try to save the page.
I renamed the Genres page to Experiences. I would also name the pages describing one certain project not with the genre in the title, but just Experiences:Projectname. As the whole catergory grows by the time we can put the projects in different categories to structure them.
If I'll get your OK I'll change that too.
Ogre Admin [Admin, Dev, PR, Finance, Wiki, etc.] | BasicOgreFramework | AdvancedOgreFramework Don't know what to do in your spare time? Help the Ogre wiki grow! Or squash a bug...
Well, I personally prefer long ones, as all the information is then on one page and so you can e.g. easily have a look at another part of this page to check something. Nowadays, it shouldn't be a problem regarding the bandwith of the users (concidering page loading times).
I don't know what's about bandwith on the server side. From this perspective, smaller pages could perhaps be better, but only if people only want to check out a certain part of the page. If they go through all parts of a project and have to load several pages, the load for the server is probably bigger than if it was with just one big page.
EDIT: Changed the project page names and created a new category for them. As soon as there are more pages, I'll create a template that can be added at the bottom of each page for a quicker navigation in this wiki area.
Ogre Admin [Admin, Dev, PR, Finance, Wiki, etc.] | BasicOgreFramework | AdvancedOgreFramework Don't know what to do in your spare time? Help the Ogre wiki grow! Or squash a bug...
It's really nice! Many interesting information on the techniques that stand behind such a games. I'm really looking forward to see more of them!
Ogre Admin [Admin, Dev, PR, Finance, Wiki, etc.] | BasicOgreFramework | AdvancedOgreFramework Don't know what to do in your spare time? Help the Ogre wiki grow! Or squash a bug...
No, there is something left: TODO: write other cpu optimisations
I prefer no divided pages for Experiences.
This would be bad for overview. Only for massive source code I would externalize.
Loading time doesn't matter, because everybody can see the top of the text quickly. The rest will be loaded by reading.
Help to add information to the wiki. Also tiny edits will let it grow ... Add your country to your profile ... it's interesting to know from where of the world you are.
Beauty wrote:
No, there is something left: TODO: write other cpu optimisations
yes, that hasn't been done at the time of writing the article, I will tend to that as soon as I find the time. and write the other two articles as well.