Cache frame range does not go down to 0 in the "Scene Properties" for "Rigid Body World" when clicking the left arrow #76906

New Issue

Arken · 2020-05-20T11:46:29+02:00

Arken commented

2020-05-20 11:46:29 +02:00

System Information
Operating system: Windows-10-10.0.18362-SP0 64 Bits
Graphics card: Radeon RX 560 Series ATI Technologies Inc. 4.5.13587 Core Profile Context 20.4.1 26.20.15029.20013

Blender Version
Broken: version: 2.83 (sub 17), branch: master, commit date: 2020-05-19 23:15, hash: dfe8195dfe
Worked: (newest version of Blender that worked as expected)

Short description of error
In Blender 2.83 (and lower), the small arrow UI that appears on mouseover for the frame selection range for the Cache in the "Rigid Body World" in the "Scene Properties" tab does not work correctly.

Exact steps for others to reproduce the error
It cannot go down from 1 to 0 when clicking the left arrow. Unlike the timeline frame range arrows that work as they should.

blender 2.83 feedback rigid body cache range.blend

**System Information** Operating system: Windows-10-10.0.18362-SP0 64 Bits Graphics card: Radeon RX 560 Series ATI Technologies Inc. 4.5.13587 Core Profile Context 20.4.1 26.20.15029.20013 **Blender Version** Broken: version: 2.83 (sub 17), branch: master, commit date: 2020-05-19 23:15, hash: `dfe8195dfe` Worked: (newest version of Blender that worked as expected) **Short description of error** In Blender 2.83 (and lower), the small arrow UI that appears on mouseover for the frame selection range for the Cache in the "Rigid Body World" in the "Scene Properties" tab does not work correctly. **Exact steps for others to reproduce the error** It cannot go down from 1 to 0 when clicking the left arrow. Unlike the timeline frame range arrows that work as they should. ![blender-feedback-scene-properties-cache-frame-range.jpg](https://archive.blender.org/developer/F8544630/blender-feedback-scene-properties-cache-frame-range.jpg) [blender 2.83 feedback rigid body cache range.blend](https://archive.blender.org/developer/F8544632/blender_2.83_feedback_rigid_body_cache_range.blend)

Arken commented

2020-05-20 11:46:29 +02:00

Added subscriber: @Arken

Germano Cavalcante commented

2020-05-20 16:43:16 +02:00

Added subscriber: @mano-wii

Germano Cavalcante commented

2020-05-20 16:43:16 +02:00

We could change this:

diff --git a/source/blender/makesrna/intern/rna_object_force.c b/source/blender/makesrna/intern/rna_object_force.c
index 3317ae91f98..e220df6f576 100644
--- a/source/blender/makesrna/intern/rna_object_force.c
+++ b/source/blender/makesrna/intern/rna_object_force.c
@@ -934,12 +934,12 @@ static void rna_def_pointcache_common(StructRNA *srna)
   prop = RNA_def_property(srna, "frame_start", PROP_INT, PROP_TIME);
   RNA_def_property_int_sdna(prop, NULL, "startframe");
   RNA_def_property_range(prop, -MAXFRAME, MAXFRAME);
-  RNA_def_property_ui_range(prop, 1, MAXFRAME, 1, 1);
+  RNA_def_property_ui_range(prop, 0, MAXFRAME, 1, 1);
   RNA_def_property_ui_text(prop, "Start", "Frame on which the simulation starts");
 
   prop = RNA_def_property(srna, "frame_end", PROP_INT, PROP_TIME);
   RNA_def_property_int_sdna(prop, NULL, "endframe");
-  RNA_def_property_range(prop, 1, MAXFRAME);
+  RNA_def_property_range(prop, 0, MAXFRAME);
   RNA_def_property_ui_text(prop, "End", "Frame on which the simulation stops");
 
   prop = RNA_def_property(srna, "frame_step", PROP_INT, PROP_NONE);

But apparently this is intentional and not a bug.
It is important to know why this is so before changing blindly.
The manual and code don't say much.

We could change this: ``` diff --git a/source/blender/makesrna/intern/rna_object_force.c b/source/blender/makesrna/intern/rna_object_force.c index 3317ae91f98..e220df6f576 100644 --- a/source/blender/makesrna/intern/rna_object_force.c +++ b/source/blender/makesrna/intern/rna_object_force.c @@ -934,12 +934,12 @@ static void rna_def_pointcache_common(StructRNA *srna) prop = RNA_def_property(srna, "frame_start", PROP_INT, PROP_TIME); RNA_def_property_int_sdna(prop, NULL, "startframe"); RNA_def_property_range(prop, -MAXFRAME, MAXFRAME); - RNA_def_property_ui_range(prop, 1, MAXFRAME, 1, 1); + RNA_def_property_ui_range(prop, 0, MAXFRAME, 1, 1); RNA_def_property_ui_text(prop, "Start", "Frame on which the simulation starts"); prop = RNA_def_property(srna, "frame_end", PROP_INT, PROP_TIME); RNA_def_property_int_sdna(prop, NULL, "endframe"); - RNA_def_property_range(prop, 1, MAXFRAME); + RNA_def_property_range(prop, 0, MAXFRAME); RNA_def_property_ui_text(prop, "End", "Frame on which the simulation stops"); prop = RNA_def_property(srna, "frame_step", PROP_INT, PROP_NONE); ``` But apparently this is intentional and not a bug. It is important to know why this is so before changing blindly. The manual and code don't say much.

Ankit Meel commented

2020-05-21 10:50:39 +02:00

Added subscriber: @ankitm

Ankit Meel commented

2020-05-21 10:50:39 +02:00

Is it like hard min & soft min ? soft min is the barrier of the < button. you can get below that by manually entering the number in the box.

Is it like hard min & soft min ? soft min is the barrier of the `<` button. you can get below that by manually entering the number in the box.

Arken commented

2020-05-21 11:05:05 +02:00

For the record, I had reported the same issue with the Mantaflow cache and it got fixed.

https://developer.blender.org/T75210

For the record, I had reported the same issue with the Mantaflow cache and it got fixed. https://developer.blender.org/T75210

Richard Antalik commented

2020-05-25 11:34:08 +02:00

Added subscribers: @sreich, @iss

Richard Antalik commented

2020-05-25 11:34:08 +02:00

Changed status from 'Needs Triage' to: 'Archived'

Richard Antalik closed this issue

2020-05-25 11:34:08 +02:00

Richard Antalik self-assigned this 2020-05-25 11:34:08 +02:00

Richard Antalik commented

2020-05-25 11:34:08 +02:00

The issue with changes like this is that timeline starts at frame 1. You may want to reset value to start of timeline just by quickly clicking and dragging this value. If limit was 0, this may create users complaining that it should be 1 as default start of timeline instead.

We could use start and end frames programatically defined limits instead. I will tag project and developer @sreich and will leave decision up to him.

Thanks for the report, but the issue reported here is a request for modified/improved behavior and not a bug in current behavior. Closing as this bug tracker is only for bugs and errors.

For user requests and feedback, please use other channels: https://wiki.blender.org/wiki/Communication/Contact#User_Feedback_and_Requests

For more information on why this isn't considered a bug, visit: https://wiki.blender.org/wiki/Reference/Not_a_bug

The issue with changes like this is that timeline starts at frame 1. You may want to reset value to start of timeline just by quickly clicking and dragging this value. If limit was 0, this may create users complaining that it should be 1 as default start of timeline instead. We could use start and end frames programatically defined limits instead. I will tag project and developer @sreich and will leave decision up to him. Thanks for the report, but the issue reported here is a request for modified/improved behavior and not a bug in current behavior. Closing as this bug tracker is only for bugs and errors. For user requests and feedback, please use other channels: https://wiki.blender.org/wiki/Communication/Contact#User_Feedback_and_Requests For more information on why this isn't considered a bug, visit: https://wiki.blender.org/wiki/Reference/Not_a_bug

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

Cache frame range does not go down to 0 in the "Scene Properties" for "Rigid Body World" when clicking the left arrow #76906