Array modifier: Count value doesn't increase over 1000 when using arrow icons. #108040

Open
opened 2023-05-18 11:41:45 +02:00 by Łukasz Paraszka · 2 comments

System Information
Operating system: Windows-10-10.0.19045-SP0 64 Bits
Graphics card: NVIDIA GeForce GTX 745/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 516.94

Blender Version
Broken: version:
3.5.1, branch: blender-v3.5-release, commit date: 2023-04-24 18:11, hash: e1ccd9d4a1d3,
3.4.1, branch: blender-v3.4-release, commit date: 2022-12-19 18:11, hash: 55485cb379f7
Worked: N/A

Short description of error
This is a minor bug but hopefully easy to fix:
When changing the "Count" value in Array modifier using arrow icons it is impossible to pass a value higher than 1000, it simply doesn't change. However, any value can be set using keyboard and then the arrow icons work as intended (eg. setting the value using keyboard to 1001 enables the arrow icons to set values 1002, 1003...).
This seems to be happening when trying to pass over values eg. 1000, 2000, 5000. When trying to pass over values eg. 3000, 4000, 6000, 7000 the icons work as intended.

Exact steps for others to reproduce the error

  1. Open blender
  2. Select default cube (or any newly created object)
  3. Go to Modifier Properties
  4. Add Array modifier
  5. Manually change Count to 998
  6. Press the right arrow icon until the Count value reaches 1000 and keep pressing to see if the value increases
  7. Manually change Count to 1001 and check if the right arrow icons changes the value
**System Information** Operating system: Windows-10-10.0.19045-SP0 64 Bits Graphics card: NVIDIA GeForce GTX 745/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 516.94 **Blender Version** Broken: version: 3.5.1, branch: blender-v3.5-release, commit date: 2023-04-24 18:11, hash: `e1ccd9d4a1d3`, 3.4.1, branch: blender-v3.4-release, commit date: 2022-12-19 18:11, hash: `55485cb379f7` Worked: N/A **Short description of error** This is a minor bug but hopefully easy to fix: When changing the "Count" value in Array modifier using arrow icons it is impossible to pass a value higher than 1000, it simply doesn't change. However, any value can be set using keyboard and then the arrow icons work as intended (eg. setting the value using keyboard to 1001 enables the arrow icons to set values 1002, 1003...). This seems to be happening when trying to pass over values eg. 1000, 2000, 5000. When trying to pass over values eg. 3000, 4000, 6000, 7000 the icons work as intended. **Exact steps for others to reproduce the error** 1. Open blender 2. Select default cube (or any newly created object) 3. Go to Modifier Properties 4. Add Array modifier 5. Manually change Count to 998 6. Press the right arrow icon until the Count value reaches 1000 and keep pressing to see if the value increases 7. Manually change Count to 1001 and check if the right arrow icons changes the value
Łukasz Paraszka added the
Priority
Normal
Status
Needs Triage
Type
Report
labels 2023-05-18 11:41:45 +02:00
YimingWu added
Module
User Interface
Status
Confirmed
Interest
User Interface
and removed
Status
Needs Triage
labels 2023-05-18 13:29:41 +02:00
Member

This is a rather weird behaviour. Can confirm, but all my versions have this weird behaviour back to at least 2.93.

The 1000 limit is an UI limit, it should clamp to 1000 but once you set it past that it should allow you to go higher, but not sure why it only clamps 1000,2000,5000 while 3000,4000,6000,7000 is not clamping.

This is a rather weird behaviour. Can confirm, but all my versions have this weird behaviour back to at least 2.93. The 1000 limit is an UI limit, it should clamp to 1000 but once you set it past that it should allow you to go higher, but not sure why it only clamps 1000,2000,5000 while 3000,4000,6000,7000 is not clamping.

At first I thought 1000 is just an UI limit too, which isn't a big deal actually. However, for other modifiers/settings operating on integers, this bug doesn't occur. That made me think this is specifically related to the Array modifier.

At first I thought 1000 is just an UI limit too, which isn't a big deal actually. However, for other modifiers/settings operating on integers, this bug doesn't occur. That made me think this is specifically related to the Array modifier.
Sign in to join this conversation.
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset Browser
Interest
Asset Browser Project Overview
Interest
Audio
Interest
Automated Testing
Interest
Blender Asset Bundle
Interest
BlendFile
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
Interest
EEVEE & Viewport
Interest
Freestyle
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
ID Management
Interest
Images & Movies
Interest
Import Export
Interest
Line Art
Interest
Masking
Interest
Metal
Interest
Modeling
Interest
Modifiers
Interest
Motion Tracking
Interest
Nodes & Physics
Interest
OpenGL
Interest
Overlay
Interest
Overrides
Interest
Performance
Interest
Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds & Tests
Interest
Python API
Interest
Render & Cycles
Interest
Render Pipeline
Interest
Sculpt, Paint & Texture
Interest
Text Editor
Interest
Translations
Interest
Triaging
Interest
Undo
Interest
USD
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Interest
Video Sequencer
Interest
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
Legacy
Blender 2.8 Project
Legacy
Milestone 1: Basic, Local Asset Browser
Legacy
OpenGL Error
Meta
Good First Issue
Meta
Papercut
Meta
Retrospective
Meta
Security
Module
Animation & Rigging
Module
Core
Module
Development Management
Module
EEVEE & Viewport
Module
Grease Pencil
Module
Modeling
Module
Nodes & Physics
Module
Pipeline, Assets & IO
Module
Platforms, Builds & Tests
Module
Python API
Module
Render & Cycles
Module
Sculpt, Paint & Texture
Module
Triaging
Module
User Interface
Module
VFX & Video
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Priority
High
Priority
Low
Priority
Normal
Priority
Unbreak Now!
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Info from Developers
Status
Needs Information from User
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Design
Type
Known Issue
Type
Patch
Type
Report
Type
To Do
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: blender/blender#108040
No description provided.