rotating hdri images even very low res ones is really slow in this version #71519

New Issue

michael campbell · 2019-11-12T16:47:26+01:00

michael campbell commented

2019-11-12 16:47:26 +01:00

System Information
Operating system: Windows-10-10.0.17134 64 Bits
Graphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 431.86

Blender Version
Broken: version: 2.81 (sub 16), branch: master, commit date: 2019-11-12 13:28, hash: 1252577580
Worked: (optional)

Short description of error
rotating hdri images even very low res ones is really slow in this version

Exact steps for others to reproduce the error
go into the world tab and use the mapping node to rotate a 4 k hdri. There's a really long pause compared to the previous daily builds. I haven't noticed this problem before, since intermittently upgrading daily builds from 2.80 upwards. Even happens with textures limited to 128 in the simplify tab. This is using cycles in the viewport render in gpu experimental mode. same for non experimental too. I used to be able to get almost instantaneous feedback in the viewport render, now the wait is too long to be able to interactively see the difference in lighting, just have to enter a number with the keyboard and wait now.

**System Information** Operating system: Windows-10-10.0.17134 64 Bits Graphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 431.86 **Blender Version** Broken: version: 2.81 (sub 16), branch: master, commit date: 2019-11-12 13:28, hash: `1252577580` Worked: (optional) **Short description of error** rotating hdri images even very low res ones is really slow in this version **Exact steps for others to reproduce the error** go into the world tab and use the mapping node to rotate a 4 k hdri. There's a really long pause compared to the previous daily builds. I haven't noticed this problem before, since intermittently upgrading daily builds from 2.80 upwards. Even happens with textures limited to 128 in the simplify tab. This is using cycles in the viewport render in gpu experimental mode. same for non experimental too. I used to be able to get almost instantaneous feedback in the viewport render, now the wait is too long to be able to interactively see the difference in lighting, just have to enter a number with the keyboard and wait now.

michael campbell commented

2019-11-12 16:47:26 +01:00

Added subscriber: @3di

michael campbell commented

2019-11-12 17:49:10 +01:00

I think the coding of the background shader or environment texture must have changed somehow, because adding new ones seem to be back working as expected....although I did think that the behaviour of the slider used to update the render as you moved, now it seems to only update the render on mouse release which takes away the interactivity somewhat (which is important when tweaking lighting).

Might want to add a bit of code to upgrade the old node to the new node to avoid any more bug reports?

I think the coding of the background shader or environment texture must have changed somehow, because adding new ones seem to be back working as expected....although I did think that the behaviour of the slider used to update the render as you moved, now it seems to only update the render on mouse release which takes away the interactivity somewhat (which is important when tweaking lighting). Might want to add a bit of code to upgrade the old node to the new node to avoid any more bug reports?

Dalai Felinto commented

2019-11-13 02:59:15 +01:00

Added subscriber: @dfelinto

Dalai Felinto commented

2019-11-13 02:59:15 +01:00

Can you confirm that the official 2.80 release does not present this problem?

michael campbell commented

2019-11-13 03:48:00 +01:00

2.8 was very fast to update modifications to the hdri rotation, strength etc (the same as 2.81 is now that I deleted and replaced the environment texture node and the background shader). I was mistaken regarding 2.81 not initiating the update until the mouse button is released though, it updates when mouse movement has stopped for a second or two whilst the mouse button is still depressed.

Just to clarify, 2.81 and 2.8 both began the update process at the same time, but 2.81 was taking around 10 seconds to restart viewport rendering, whereas 2.8 restarted the viewport render in under a second.

Not an issue now I deleted and replaced the nodes, so presumably the code for one of those two nodes has changed between versions.

2.8 was very fast to update modifications to the hdri rotation, strength etc (the same as 2.81 is now that I deleted and replaced the environment texture node and the background shader). I was mistaken regarding 2.81 not initiating the update until the mouse button is released though, it updates when mouse movement has stopped for a second or two whilst the mouse button is still depressed. Just to clarify, 2.81 and 2.8 both began the update process at the same time, but 2.81 was taking around 10 seconds to restart viewport rendering, whereas 2.8 restarted the viewport render in under a second. Not an issue now I deleted and replaced the nodes, so presumably the code for one of those two nodes has changed between versions.

Brecht Van Lommel commented

2019-11-13 14:28:03 +01:00

Added subscriber: @brecht

Brecht Van Lommel commented

2019-11-13 14:28:03 +01:00

Changed status from 'Open' to: 'Archived'

Brecht Van Lommel closed this issue

2019-11-13 14:28:03 +01:00

Brecht Van Lommel self-assigned this 2019-11-13 14:28:03 +01:00

Brecht Van Lommel commented

2019-11-13 14:28:03 +01:00

It's because background multiple importance sampling is now enabled by default, which requires a rebuild when rotating.

We would like to optimize this in the future, but it's not a bug.

It's because background multiple importance sampling is now enabled by default, which requires a rebuild when rotating. We would like to optimize this in the future, but it's not a bug.

michael campbell commented

2019-11-13 14:30:45 +01:00

In #71519#810297, @brecht wrote:
It's because background multiple importance sampling is now enabled by default, which requires a rebuild when rotating.

We would like to optimize this in the future, but it's not a bug.

why would recreating the node resolve the issue?

> In #71519#810297, @brecht wrote: > It's because background multiple importance sampling is now enabled by default, which requires a rebuild when rotating. > > We would like to optimize this in the future, but it's not a bug. why would recreating the node resolve the issue?

Brecht Van Lommel commented

2019-11-13 14:45:35 +01:00

I'm not sure. But the bug report is missing the actual .blend / image file and steps to reproduce the bug, since only steps to create new nodes are provided and those apparently work ok.

So, we must have that information first to confirm that it's indeed a different issue than just multiple importance sample updating.

I'm not sure. But the bug report is missing the actual .blend / image file and steps to reproduce the bug, since only steps to create new nodes are provided and those apparently work ok. So, we must have that information first to confirm that it's indeed a different issue than just multiple importance sample updating.

michael campbell commented

2019-11-13 14:52:37 +01:00

ah ok, I couldnt share the file as it's under NDA,. If you want to replicate, you could create a scene in 2.8 which has a hdri, and then open it the latest daily build. It's definitely not caused by multiple importance sampling now being the default, otherwise new nodes would have had the same issue. I'll leave it with you.

Brecht Van Lommel commented

2019-11-13 15:00:55 +01:00

Have you verified that creating a mapping + environment texture node in 2.80 and then loading it in 2.81 actually reproduces the problem? It didn't for me.

We don't require the original file in bug reports, just any .blend file and exact steps to reproduce the problem. Otherwise we waste time guessing what might be the problem.

Have you verified that creating a mapping + environment texture node in 2.80 and then loading it in 2.81 actually reproduces the problem? It didn't for me. We don't require the original file in bug reports, just any .blend file and exact steps to reproduce the problem. Otherwise we waste time guessing what might be the problem.

michael campbell commented

2019-11-13 15:11:12 +01:00

The original file may have been created in one of the previous daily builds somewhere between 2.8 and yesterdays daily 2.81 build, I'm not sure which. When I've finished these few projects I'll have a dig around to try and find another file which has the same issue, or hopefully before then someone else will experience the same problem with a file they can share.

Awesome job to everyone over there by the way, I'd marry this program if it was legal :)

The original file may have been created in one of the previous daily builds somewhere between 2.8 and yesterdays daily 2.81 build, I'm not sure which. When I've finished these few projects I'll have a dig around to try and find another file which has the same issue, or hopefully before then someone else will experience the same problem with a file they can share. Awesome job to everyone over there by the way, I'd marry this program if it was legal :)

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

rotating hdri images even very low res ones is really slow in this version #71519