Block user's stupid actions causing crashing of Blender
In many areas of Blender user can insert some values, causing crash of Blender for instance: entering high number of particles while turned on 100% preview. It would be nice to have some kind of prompt after inserting high number in some fields: "Such huge number of "X" can crash app or make it unusable for few minutes, continue?" Of course this numbers shouldn't be fixed limits, but it should be calculated for every user considering his hardware specification and system performance. Also in Blender's settings shouls be a checkbox to turn it off, but by default it should be ON. Progress bar for long taking actions would be a big PLUS, as for now user doesn't know what's going on.
8 Comments
Never open Cycles Rendering preview when you have loaded 20K hdri map to your texture environment node
Thing is its relative to system power. But blender most likely knows it within a couple of frames that we are getting ourselves into a stall. Agreed. would be nice if blender could failsafe out of system crashing user inputs.
Even better. Add a "butt out" feature. Where a crashing blender can instantly cancel out of the change causing the halt by pressing and holding escape for one second. Was it max that could do that back in the day? 🤔🤔 I've worked in a program many many years ago that could actually do this. It's crazy to think about given today's standards.
exactly!
Both of those sound really useful and a must-have!
Another future similar to those would be a button that we should click to execute different actions that involve setting a value.
So here is an example.
let's say that you have a really heavy file and you want to add a decimate>unsubdivide modifier. If you do that you will have to wait a long for the default value to complete computing and then you will need to add the desired value.
The same goes for dragging values. If the action needs some time to compute (even a few seconds) Blender will probably set a really high value after completing computing the default value
So having buttons to execute actions would help a lot with that.
On the other hand, having to click a button or a key for every single action sound idiotic
dunno, thoughts?
* @tasosgr01ker * Prompt box could be for some actions, and it should have toggle option in settings for sure. There are many areas in interface where different approach should be implemented. It's open idea, and how to implement it, there are many ideas, which can be discussed by community and gui creators.
* @vronahau * In general I think its a good idea, preventing the default values to compute because they can be a real pain in da butt !
* @tasosgr01ker * I just had a crash of Blender and hang of my WIndows 10 because typed some big numbers to subdiv modificator
* @vronahau * yep. The same will happen if you make the mistake to drag the value in the subdiv modf lol