Tweet
Issue reporting guide
Hello everyone!
Thank you for reporting back any issues you encounter. We want to resolve them as quick as possible. It will greatly help us if you include as much information regarding the problem as possible. i.e. as many of the following as you can:
Of course you can post bug reports without them! But it more complicated scenarios it will be difficult for us to track the issue. You can also write to us at support@chaosgroup.com
Either way, please post any issue you encounter and we will try our best to fix it.
Once again, thank you for your feedback!
Best regards,
Alexander
Thank you for reporting back any issues you encounter. We want to resolve them as quick as possible. It will greatly help us if you include as much information regarding the problem as possible. i.e. as many of the following as you can:
- The log from the Output window (Unreal editor/Windows/Defeloper Tools/ Output Log), preferably filtered by "VRayLog". See the documentation
- Content of PROJECT_NAME/Saved/Crashes and Logs folders+
- VRay.dmp located in %temp% (if existing)
- KernelBase.dll and ntdll.dll located in C:\Windows\System32
- Screenshot(s) of the Unreal editor's viewport
- Screenshot(s) of the V-Ray settings panel, details panel, or any other UI that is appropriate for the issue
- Screenshot(s) of the VFB
- Test project/scene that reproduces the problem
- Steps to reproduce the problem
- Hardware specs of your workstation
Of course you can post bug reports without them! But it more complicated scenarios it will be difficult for us to track the issue. You can also write to us at support@chaosgroup.com
Either way, please post any issue you encounter and we will try our best to fix it.
Once again, thank you for your feedback!
Best regards,
Alexander
