saindd Posted July 2, 2015 Share Posted July 2, 2015 How can we properly report engine crashes? Should we record a video with the steps? Or just a console.log and a few breadcrumbs on how to reproduce it? Quote Link to comment Share on other sites More sharing options...
buckmaster Posted July 3, 2015 Share Posted July 3, 2015 Video isn't necessary, but a list of steps is essential. Having a console.log may be helpful, so it pays to include it if in doubt. Quote Link to comment Share on other sites More sharing options...
saindd Posted October 27, 2015 Author Share Posted October 27, 2015 I would like to bump this thread and hear a little more about the steering committee on how to help them properly as far as reporting crashes go. I've been having lot's of crashes when working with terrain and terrain materials in 3.8. How can i provide decent information for you guys?A console.log? Should i build a DEBUG version? Is there a specific report that i can send? Quote Link to comment Share on other sites More sharing options...
JeffR Posted October 27, 2015 Share Posted October 27, 2015 We don't have a form, if that's what you mean, but creating a thread here or an issue on the github page'll work.As for the information, if you can do a video or the like, that's provide a lot of information, but really all we need are the steps to reproduce the problem. Anything beyond that just makes things easier.And yeah, if you compile the engine as debug, that tends to give you a bit more information as to whats going wrong, so it's usually a good idea to do that when you're noting issues.A console.log is always help, too. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.