Configuration Lost #49745

New Issue

Abed · 2016-10-16T16:53:37+02:00

Abed commented

2016-10-16 16:53:37 +02:00

There are two issues under the same topic "loosing settings". The first maybe disclosed later as an addon bug but the second issue is certainly blender's matter.

Open the .blend file, delete tree in layer 3 then add a tree from the sappling addon. (make sure to not select anything except the tree or leaves otherwise properties will disappear)
Render the scene and mark down the slot number of your render.
Change exposure or gamma to any value.
Now increase number of leaves or any other value of the tree.
The color values changed up and any settings your modify will reset to default ones before altering tree settings.
Slot you rendered the scene on will become empty as well as all other slots except one, in my case slot 3.

Regarding the second issue, normally you can restrict blender to use an arbitrary number of CPUs which can be done in task manager if you're windows user, but whenever scene is rendered blender be reassigned to use all CPU thread you have.
If I am right, new instance of blender is created in background every time you hit the render button thus making you assign the amount of CPUs to be used.
test.blend

steps.zip
Windows 8 i7-4500U 8 GB Intel HD Graphics
Blender v2.78 Sappling Tree Gen v0.3.2

There are two issues under the same topic "loosing settings". The first maybe disclosed later as an addon bug but the second issue is certainly blender's matter. 1. Open the .blend file, delete tree in layer 3 then add a tree from the sappling addon. (make sure to not select anything except the tree or leaves otherwise properties will disappear) 2. Render the scene and mark down the slot number of your render. 3. Change exposure or gamma to any value. 4. Now increase number of leaves or any other value of the tree. 5. The color values changed up and any settings your modify will reset to default ones before altering tree settings. 6. Slot you rendered the scene on will become empty as well as all other slots except one, in my case slot 3. Regarding the second issue, normally you can restrict blender to use an arbitrary number of CPUs which can be done in task manager if you're windows user, but whenever scene is rendered blender be reassigned to use all CPU thread you have. If I am right, new instance of blender is created in background every time you hit the render button thus making you assign the amount of CPUs to be used. [test.blend](https://archive.blender.org/developer/F379396/test.blend) [steps.zip](https://archive.blender.org/developer/F379404/steps.zip) Windows 8 i7-4500U 8 GB Intel HD Graphics Blender v2.78 Sappling Tree Gen v0.3.2

Abed commented

2016-10-16 16:53:37 +02:00

Changed status to: 'Open'

Abed commented

2016-10-16 16:53:37 +02:00

Added subscriber: @Sam1500

Bastien Montagne commented

2016-10-16 18:54:10 +02:00

Added subscriber: @mont29

Bastien Montagne commented

2016-10-16 18:54:10 +02:00

Changed status from 'Open' to: 'Archived'

Bastien Montagne closed this issue

2016-10-16 18:54:10 +02:00

Bastien Montagne self-assigned this 2016-10-16 18:54:10 +02:00

Bastien Montagne commented

2016-10-16 18:54:10 +02:00

Thanks for the report, but no bug here. As long as you still can edit sappling settings, it means no other undo step has been saved, i.e. any change post-spalling will be undone if you go back to pre-sappling state (which is what happens when you tweak an operator's property - undo, and redo operator).

Abed commented

2016-10-16 19:17:42 +02:00

What about the second issue, it always happen and not related to sappling at all. Annoying to set what processor's blender must use in task manager every time i render the scene. That was my main problem and you didn't point it out.
See the attachments 7 and 8 in steps.zip.
Thanks again.

What about the second issue, it always happen and not related to sappling at all. Annoying to set what processor's blender must use in task manager every time i render the scene. That was my main problem and you didn't point it out. See the attachments 7 and 8 in [steps.zip](https://archive.blender.org/developer/F379404/steps.zip). Thanks again.

Julian Eisel commented

2016-10-16 19:20:54 +02:00

Added subscriber: @JulianEisel

Julian Eisel commented

2016-10-16 19:20:54 +02:00

You can select the number of threads to use for both Cycles and Blender Internal in the Performance panel of the Properties Editor (Render context).

Bastien Montagne was unassigned by Abed

2016-10-16 20:18:44 +02:00

Abed commented

2016-10-16 20:18:45 +02:00

Changed status from 'Archived' to: 'Open'

Abed reopened this issue

2016-10-16 20:18:45 +02:00

Abed commented

2016-10-16 20:18:45 +02:00

Yes you're right but there are critical components that ignores or maybe not designed to use the threading limitation under performance panel and can be restricted only by assigning processors outside blender, the BVH building which can consume lot of time in complex scenes in addition to cloth, fluid and smoke simulations.

Note: before 2.78 I was able to set threads in task manager only once but don't know now if the above are capable of respecting the limiting that user selects in performance panel.

Yes you're right but there are critical components that ignores or maybe not designed to use the threading limitation under performance panel and can be restricted only by assigning processors outside blender, the BVH building which can consume lot of time in complex scenes in addition to cloth, fluid and smoke simulations. Note: before 2.78 I was able to set threads in task manager only once but don't know now if the above are capable of respecting the limiting that user selects in performance panel.

Bastien Montagne was assigned by Abed

2016-10-16 20:19:17 +02:00

Abed commented

2016-10-16 20:19:53 +02:00

Changed status from 'Open' to: 'Archived'

Abed closed this issue

2016-10-16 20:19:53 +02:00

Abed commented

2016-10-16 20:19:53 +02:00

oops. Sorry!

Bastien Montagne commented

2016-10-16 20:22:25 +02:00

Easiest way to set global thread limitation in Blender (beyond the rendering options) is to use the command line -t <number of threads> option, -t 4 e.g. to limit to four threads (and -t 0 to disable multi-threading completely)…

Easiest way to set global thread limitation in Blender (beyond the rendering options) is to use the command line `-t <number of threads>` option, `-t 4` e.g. to limit to four threads (and `-t 0` to disable multi-threading completely)…

Sign in to join this conversation.

No Label

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

Configuration Lost #49745