by spacegaier | Feb 7, 2011 | News
Are you a student? Do you have some weeks of spare time during the summer? Are you interested in Ogre and always searched for a chance to contribute? Well, guess what: Now is your time!
We are right now looking for some talented and interested people for this year’s “Google Summer of Code 2011” initiative. Honestly, we somehow lack really good ideas what to propose as tasks since many of the items on the general ToDo list are either too big or too small for the given time. So if anyone has either some ideas that might be tackled this year or is willed to participate on Ogre’s behalf this year (or perhaps even both?), we would very much appreciate a comment or thread in our GSoC subforum.
We are hoping for some good ideas and volunteers to once again successfully participate!
by spacegaier | Jan 31, 2011 | News
Over the last two weeks, there has again been a lot of buzz around Ogre. Here are some notable events:
- Ogre powered game APOX was finally released on Steam.
- Some impressions from the game Aquatic, created by our community member Praetorian for the 19th Ludum Dare competition.
- New testimonial by Compredia GmbH was added.
- Further development for the new instancing manager: HWInstancingBasic.
- Community member SongOfTheWeave published PolyViz, a N-Dimensional Polyhedral Visualizer.
- First preview of the upcoming innovative Ogre based puzzle game called ATOM.
- Great new wiki article on how to implement line charts within an Ogre application by Adis.
- The Final Tank Down was released in the Apple AppStore.
- First footage from the hobby MMORPG Amnov.
- Jacmoe installed automatic syntax highlighting for code snippets in the forums, however some tweaking is needed.
Also thank you all for the papercut entries on our tracker. There are so many, the development team can hardly keep up, but nonetheless keep them coming! Before the next Ogre release they will surely all be integrated…
by spacegaier | Jan 10, 2011 | News
This time we have good news for everyone trying to get started with Ogre: A new book covering the basics has just been published covering our latest stable version, Ogre 3D 1.7. It was created by our community member Felix <mirlix> Kerger and reviewed by some of our most respected and experienced users.
According to the author, the book covers topics ranging from the very simple beginnings, complex scene creation, post processing and Ogre extensions via plugins. In order to follow the book and its sample based approach you are only expected to already have some knowledge of C++.
More information about the book and a sample chapter can be accessed on the publisher’s homepage (“PacktPub”), where you can also directly buy the book.
Ogre 3D 1.7 Beginner’s Guide @ PacktPub.com
by spacegaier | Jan 2, 2011 | News
Since two weeks, we have now started our “papercut” initiative to quickly improve the Ogre code base before the release of Ogre 1.8 (Byatis). First community members have already participated and we are hoping for more to come.
If you haven’t heard about the initiative yet, here is a quote from the introductory thread in the newly created forum section dedicated to the papercuts:
What is a papercut?
A papercut is a minor issue with the Ogre API, like a missing function that you were expecting, an inconsistently named function, misleading or incorrect documentation, etc. Basically anything that slightly annoyed you at the time you had to figure it out, but not such a major issue that it kept you from doing what you wanted to do. A papercut should be trivial to fix.
Reporting papercuts
Please report any papercut you encountered in our bugtracker. Create a new report and prefix the title with “[Papercut]”. If you feel there is need for a discussion about a proposed change, then open a thread in this forum and link to the corresponding report in the tracker.
Resolving papercuts
We want to get rid of as many papercuts as possible for the next major Ogre release (Byatis 1.8). As such, we will try to regularly squash any reported papercuts in batches. Your report is immensely helpful, as it makes us aware of the issue and also documents it in a place where it’s easy to find and doesn’t get lost.
So in case you come across any of these little annoying things that you always wanted to get changed, this is the time to make your voice heard! Use it and help us to help you 😉 .
As usual direct patches are welcome very welcome, but a simple bug tracker item is already a very good start too!
