Render Time incorrect when refreshing rendered preview in GPU mode #50748

New Issue

Thomas Radeke · 2017-02-22T01:43:20+01:00

Thomas Radeke commented

2017-02-22 01:43:20 +01:00

System information
OS: Linux Mint 17.3 MATE x64
GPU: nVidia GTX1070
Drivers: 367.44
(I could not test it on other computers yet, sorry.)

What's broken?
(Using 2.78b Release) When using GPU rendering and while in Rendered 3D view, the time display on the top left is supposed to show the time used to render the current preview. This only works correctly directly after switching to Rendered mode, however. As soon as any property is changed that forces a render preview refresh, the time display shows wrong – and often negative – numbers. This does not seem to happen in CPU mode, tho.

This does work correctly on 2.77a, by the way!

Steps to reproduce the problem:

Load any scene, set to GPU compute
Switch to Rendered 3D view, wait for preview to finish, note correct time display on top left
Change something about sampling quality (e.g. Seed) to trigger a refresh
Note wrong time on top left

Thanks for doing an awesome job!

**System information** OS: Linux Mint 17.3 MATE x64 GPU: nVidia GTX1070 Drivers: 367.44 (I could not test it on other computers yet, sorry.) **What's broken?** (Using 2.78b Release) When using GPU rendering and while in Rendered 3D view, the time display on the top left is supposed to show the time used to render the current preview. This only works correctly directly after switching to Rendered mode, however. As soon as any property is changed that forces a render preview refresh, the time display shows wrong – and often negative – numbers. This does not seem to happen in CPU mode, tho. This does work correctly on 2.77a, by the way! **Steps to reproduce the problem:** 1. Load any scene, set to GPU compute 2. Switch to Rendered 3D view, wait for preview to finish, note correct time display on top left 3. Change something about sampling quality (e.g. Seed) to trigger a refresh 4. Note wrong time on top left Thanks for doing an awesome job! ![wrongtime.png](https://archive.blender.org/developer/F493422/wrongtime.png)

Thomas Radeke commented

2017-02-22 01:43:20 +01:00

Changed status to: 'Open'

Thomas Radeke commented

2017-02-22 01:43:20 +01:00

Added subscriber: @ThomasRadeke

Joey Ferwerda commented

2017-02-22 16:23:52 +01:00

Added subscriber: @TheOnlyJoey

Joey Ferwerda commented

2017-02-22 16:23:52 +01:00

Can confirm, tested on 278b, seems to be a regression.
Can you test this on latest buildbot version please?

Can confirm, tested on 278b, seems to be a regression. Can you test this on latest buildbot version please?

Thomas Radeke commented

2017-02-22 16:45:46 +01:00

Just tested with 2.78 Hash 3 6 2 2 0 7 4 on Windows 10 x64, the behavior persists.
(Had to insert spaces in the hash, else it would link to an unrelated commit.)

Just tested with 2.78 Hash 3 6 2 2 0 7 4 on Windows 10 x64, the behavior persists. (Had to insert spaces in the hash, else it would link to an unrelated commit.)

Vuk Gardašević commented

2017-02-22 18:02:13 +01:00

Added subscriber: @VukGardasevic