No betas are perfect releases, and much as we wish it weren’t true, this
applies to Radeon ProRender as well. Help us get the issues you report fixed,
by making sure your reported issue is as clear as possible. Here’s how:
First of all, a bug means the software misbehaves, or doesn't behave as you expected - we're talking typical behaviour such as:
- like crashing,
- not responding,
- the application not doing what you told it to, like applying a material, updating a scene, or something you’ve clicked not working or loading.
You'd help us even more if you could stick to the guidelines below - the clearer the report, the better the idea we'll have on what's going on your end, and the faster we can solve it:
- 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!
- Hardware, OS, and Drivers - if you're comfortable sharing these, please, please do, as it will help our elimination process
Expected Result: Radeon ProRender renders without a problem
- Opened 3DS Max
- Opened V-Ray scene
- Switched renderer to Radeon ProRender
- Started converting materials
- Did a test render
- Radeon ProRender crashed