No betas releases are perfect , and much as we wish it weren’t so, this applies to FireRender as well. Help us get the issues you report fixed, faster, by checking these short submission guidelines for reporting an issue into the issue-tracker.
Here’s the short version:
First of all, a bug means the software misbehaves, or not as expected. So if you want added functionality, that would be a feature request, and not a bug report – but we’ll accept those, too! However, buggy behaviour is typically stuff like crashing, not responding, or the application not doing what you told it to, like an applied material not rendering, a scene not updating, or something you’ve clicked not working or loading. If in doubt – post it as a bug, and we’ll take it from there!
If possible, please post in the following format – it helps us SO much if we know what you expected to happen when we chase down a problem!
- Expected Result:What you expected to happen
- Actual Result:What actually happened.
- Optional:You’d help us even more if you could write a step by step, but as long as we understand what you expected to happen vs what actually did, we’re good.
- Plugins:If you were working with i.e ForestPack, GrowFx, Ornatrix, RayFire, PullDownIt, Automodeller, etc, please tell us!
- Crashlogs– If Max crashed, we’d appreciate it if you attached a crashlog
- Attachments– If you’re experiencing other issues, like slow renders or hangs, please see if you can’t share your file with us. We promise not t0 share its content with anyone but the developers!
Want the long version? Check out our knowledgebase article!
Introducing the FireRender forums!
Please feel free to come and join the conversation: Whether you want to share a render, or vent over something which still hasn’t made it out of beta, or want to ask for new features or featurettes to be implemented.
All we ask, is that you behave yourself – which means the usual terms and conditions apply: Play nice, and if you can’t play nice, leave off on the swearing and derogatory remarks, and stick to the facts you’re discussing. We don’t believe in policing, but we do retain the right to remove the disruption of people who break this simple rule.
If you chose to share images in the forum, copyright stays firmly with you or the owner of the image, but we hope it’s OK if we contact you, and ask to use your render, if we see one we’d like to use for tutorial or marketing purposes – and we hope of course to see tons of renders and other images. In addition, if you have tips or tricks to share – please do!
In any case, come on over, join the discussion!
Terms and conditions
- The promoter is: 3DTotal Ltd (company no. 5198320) whose registered office is at Foregate Street, Worcester, Worcestershire, WR1 1DS, UK.
Employees of3DTotal, Advanced Micro Deviceor their family members or anyone else connected in any way with the competition or helping to set up the competition shall not be permitted to enter the competition.
- There is no entry fee and no purchase necessary to enter this competition, but a new, unique bug submission is required to enter. Each unique bug submitted will count as an additional entry to raffle.
Only new, unique bugs will be considered. Unique bugs are defined as: A bug or issue we previously weren’t aware of, and which we can reproduce. To win the raffle, the report needs to be non-trivial – typos in our beta UI, for example are not a bug. In addition, the report must provide enough info to help us track the problem down. We ask you provide a bare minimum based on our bug reporting guidelines, and a crash dump in case Max crashes. We reserve the right to unilaterally determine which bug reports are meaningful and which are not.
Five (5) winners will be chosen at random by3DTotalfrom all entries received and verified byAMD.3DTotal and AMDreserve the right to give away less than fiveAMDFirePro Graphics cards if insufficient eligible bugs are reported. TheAMDFirePro Graphics cards that constitute as a prize for this raffle are: five (5) AMD FirePro W8100 graphics cards. The winners will be shipped the GPU only; Delivered safely but without product box and contents.
- The winners will be notified by email and/or letter within 14 days of the closing date. If a winner cannot be contacted or does not claim the prize within 14 days of notification, we reserve the right to withdraw the prize from the winner and pick a replacement winner. AMD will ship the prize to the winner worldwide within 14 days of notification.
- Closing date for entry will be July 07th 2016. After this date no further entries to the competition will be permitted.
- AMD reserves the right to cancel or amend the competition and these terms and conditions without notice in the event of a catastrophe, war, civil or military disturbance, act of God or any actual or anticipated breach of any applicable law or regulation or any other event outside of the promoter’s control. Any changes to the competition will be notified to entrants as soon as possible by the promoter.
- No cash alternative to the prizes will be offered. The prizes are not transferable. Prizes are subject to availability and we reserve the right to substitute any prize with another of equivalent value without giving notice.
- The promoter’s decision in respect of all matters to do with the competition will be final and no correspondence will be entered into.
- By entering this competition, an entrant is indicating his/her agreement to be bound by these terms and conditions.
- The competition and these terms and conditions will be governed by [UK] law and any disputes will be subject to the exclusive jurisdiction of the courts of [UK].
- The winner agrees to the use of his/her name and image in any publicity material. Any personal data relating to the winner or any other entrants will be used solely in accordance with current [UK] data protection legislation and will not be disclosed to a third party without the entrant’s prior consent.
- Entry into the competition will be deemed as acceptance of these terms and conditions.