The Bug Reports Forum Rules

[Murphy]

This forum is intended to be an index of bugfixes, patches, and feature requests for Irrlicht.



Before posting a bug report, please help us to help you by doing the following:

• Read the output on the debug console, or your debugger's output window to see if it contains any information on the problem. Look in particular for messages about being unable to load meshes or textures: these are usually EBKAC errors.
• Read the Beginner's Help FAQ to see if your issue is answered there.
• Search the forum to see if your issue has already been answered.
• Look at the SDK examples to try and determine if your 'bug' is an unexpected feature.

One you have done that, and you are convinced that you have found a real bug, please construct a bug report that contains all or most of the following:

• The version numbers from the start of the console or debugger output, i.e. Irrlicht version, operating system, renderer, and device (and driver / GLSL versions if available).
• A clear, concise description of what you expected to happen, and what actually happened.
• If you are reporting a crash or error message, post the exact text of the message or error.
• Where appropriate, a screenshot of the bad behaviour. Either upload them to a free hosting platform, or (preferred) use the SourceForge trackers.
• A code snippet that produces the bad behaviour. A small self contained compilable example is ideal.
• If the problem is with a specific mesh or texture, please provide resources so that others can replicate the problem and verify the fix.

Posting fixes: fixes are always welcome. They are likely to be committed much faster if they contain:

• A description of why the old behaviour was wrong and why the new behaviour is better.
• A small standalone test application that demonstrates the old, bad behaviour and the new, fixed behaviour.
• A Subversion patch containing the new code. Patches are best hosted by the SourceForge trackers. The code will be always accessible and can be updated as well.

After you've submitted your bug and/or fix, the following things will happen:

• If the bug can be confirmed then it will be posted to the bug tracker and a link added to the thread.
• Once a fix is applied to SVN the bug will be closed and the text [fixed] will be prefixed to your topic title.
• If it is not a bug, it will be prefixed with [no bug], any tracker item will be closed as invalid.
• If you are reporting a bug which has a thread but is not marked as [fixed], [no bug] or a tracker item, feel free to add it to the tracker as per these instructions.

[hybrid]

Please always use the SourceForge Bug Tracker (http://sourceforge.net/tracker/?group_id=74339) so we can keep track of the open bugs, feature requests, and patches. Please post reports to one of the trackers if:
1. You posted a bug report to this bug forum in accordance with the rules for posting in here (see first post in this thread)
2. You include the url of your bug forum posting in the bug tracker report

The trackers can also host patches and screenshots, simply upload those files to the tracker when submitting the ticket. If you have a SF login and post the ticket logged in you will laso be noticed about changes to the tickets.
You can also subscribe to a mailing list at https://sourceforge.net/mail/?group_id=74339 to be informed about all tracker activities (or SVN activities...)

[rogerborg]

(I've updated the first post with some hopefully helpful guidelines)