World values not updating in real time #72371

New Issue

KiJeon · 2019-12-12T03:26:13+01:00

KiJeon commented

2019-12-12 03:26:13 +01:00

System Information
Operating system: Windows-10-10.0.17763 64 Bits
Graphics card: GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 419.67

Blender Version
Broken: version: 2.81 (sub 16), branch: master, commit date: 2019-11-20 14:27, hash: 26bd5ebd42

Short description of error
Unsure exactly what I did, but a file I was working on refuses to update changed values in the World Properties tab in real time in the viewport.
If I turn toggle "Use Nodes", the values update.

I was messing with the Easy HDRI weeks ago in this scene. I don't know if that caused the glitch out, but I thought I'd note it just in case.

Here's the file stripped down to the essence to test.
LightingGlitchTest.blend

Exact steps for others to reproduce the error

Open up the above .blend file
Try changing/modifying the world values/nodes.

**System Information** Operating system: Windows-10-10.0.17763 64 Bits Graphics card: GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 419.67 **Blender Version** Broken: version: 2.81 (sub 16), branch: master, commit date: 2019-11-20 14:27, hash: `26bd5ebd42` **Short description of error** Unsure exactly what I did, but a file I was working on refuses to update changed values in the World Properties tab in real time in the viewport. If I turn toggle "Use Nodes", the values update. I was messing with the Easy HDRI weeks ago in this scene. I don't know if that caused the glitch out, but I thought I'd note it just in case. Here's the file stripped down to the essence to test. [LightingGlitchTest.blend](https://archive.blender.org/developer/F8210970/LightingGlitchTest.blend) **Exact steps for others to reproduce the error** 1. Open up the above .blend file 2. Try changing/modifying the world values/nodes.

KiJeon commented

2019-12-12 03:26:13 +01:00

Added subscriber: @0o00o0oo

Jacques Lucke commented

2019-12-29 15:58:00 +01:00

Added subscriber: @JacquesLucke

Jacques Lucke commented

2019-12-29 15:58:00 +01:00

Changed status from 'Needs Triage' to: 'Needs User Info'

Jacques Lucke commented

2019-12-29 15:58:00 +01:00

I don't understand the issue, yet. I tried changing the world values and now what?

Please describe the expected and actual behavior. A short screen recording might also help to make your case more clear.

I don't understand the issue, yet. I tried changing the world values and now what? Please describe the expected and actual behavior. A short screen recording might also help to make your case more clear.

Dalai Felinto commented

2020-01-13 18:17:11 +01:00

Added subscriber: @dfelinto

Dalai Felinto commented

2020-01-13 18:17:11 +01:00

Changed status from 'Needs User Info' to: 'Archived'

Dalai Felinto closed this issue

2020-01-13 18:17:11 +01:00

Dalai Felinto self-assigned this 2020-01-13 18:17:11 +01:00

Dalai Felinto commented

2020-01-13 18:17:11 +01:00

No activity for more than a week. As per the tracker policy we assume the issue is gone and can be closed.

Thanks again for the report. If the problem persists please open a new report with the required information

No activity for more than a week. As per the tracker policy we assume the issue is gone and can be closed. Thanks again for the report. If the problem persists please open a new report with the required information

KiJeon commented

2020-01-15 09:08:17 +01:00

Whoa, I didn't know that was a policy. My apologies for not getting around to this until now.

I have to say, it seems dangerous to assume a problem's been resolved just because there's been no activity for over a week.

In any case, new report: #73131

Whoa, I didn't know that was a policy. My apologies for not getting around to this until now. I have to say, it seems dangerous to assume a problem's been resolved just because there's been no activity for over a week. In any case, new report: #73131

Dalai Felinto commented

2020-01-16 12:36:59 +01:00

It was a non-written rule I believe, but I made sure to add to the bug report form this week (or last week). It is an unnecessary procedure unfortunately otherwise reports linger forever in the tracker (and we are putting an extra amount of effort to get rid of the backlog at the moment).
All said and done, thanks for the new report :)

It was a non-written rule I believe, but I made sure to add to the bug report form this week (or last week). It is an unnecessary procedure unfortunately otherwise reports linger forever in the tracker (and we are putting an extra amount of effort to get rid of the backlog at the moment). All said and done, thanks for the new report :)

KiJeon commented

2020-01-21 09:56:49 +01:00

Understood, lingering bug reports that have no way to verify would be an issue.

The policy is the one under "No reply after a week ", correct? I'd like to suggest a wording change if I could. Instead of assuming the issue is gone (which sounds like it could mean baselessly assuming a problem magically resolved itself, which makes no sense, and frankly does sound a bit insulting to the person who took the time to write the original report), it could be something like...

"No activity for more than a week. Report will be closed until further needed information regarding the issue can be provided."

And as @JacquesLucke suggests here , I propose additional information in response to a threaded conversation triggers a reopening of the closed task with maybe a rewording of the original post to reflect any important clarification (which seems less messy than creating a duplicate report).

Understood, lingering bug reports that have no way to verify would be an issue. The policy is the one under "[No reply after a week ](https://wiki.blender.org/wiki/Process/Bug_Reports/Triaging_Playbook)", correct? I'd like to suggest a wording change if I could. Instead of assuming the issue is gone (which sounds like it could mean baselessly assuming a problem magically resolved itself, which makes no sense, and frankly does sound a bit insulting to the person who took the time to write the original report), it could be something like... "No activity for more than a week. Report will be closed until further needed information regarding the issue can be provided." And as @JacquesLucke suggests [here ](https://devtalk.blender.org/t/tracker-policy-concern/11297/2), I propose additional information in response to a threaded conversation triggers a reopening of the closed task with maybe a rewording of the original post to reflect any important clarification (which seems less messy than creating a duplicate report).

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

World values not updating in real time #72371