Cycles render is not updating #38712

New Issue

Karsten Bitter · 2014-02-18T23:50:15+01:00

Karsten Bitter commented

2014-02-18 23:50:15 +01:00

System Information
Operating system and graphics card
Ubuntu 13.10 64
Blender Version
Broken: (example: 2.69.7 4b206af, see splash screen)
Worked: (optional)
2.69 official
Short description of error
hitting f12 starts cycles render, but doesnot update the renderwindow until tile is finished
Exact steps for others to reproduce the error
Based on a (as simple as possible) attached .blend file with minimum amount of steps
any startup with cube will do...

**System Information** Operating system and graphics card Ubuntu 13.10 64 **Blender Version** Broken: (example: 2.69.7 4b206af, see splash screen) Worked: (optional) 2.69 official **Short description of error** hitting f12 starts cycles render, but doesnot update the renderwindow until tile is finished **Exact steps for others to reproduce the error** Based on a (as simple as possible) attached .blend file with minimum amount of steps any startup with cube will do...

Karsten Bitter commented

2014-02-18 23:50:15 +01:00

Changed status to: 'Open'

Karsten Bitter commented

2014-02-18 23:50:15 +01:00

Added subscriber: @KarstenBitter

Thomas Dinges commented

2014-02-19 00:47:43 +01:00

Added subscriber: @ThomasDinges

Thomas Dinges commented

2014-02-19 00:47:43 +01:00

This is not enough information. I cannot reproduce such an error.
The currently rendered tiles update every second or so. Do you render with CPU or GPU?

Also please check with a build from builder.blender.org.

This is not enough information. I cannot reproduce such an error. The currently rendered tiles update every second or so. Do you render with CPU or GPU? Also please check with a build from builder.blender.org.

Karsten Bitter commented

2014-02-19 00:56:02 +01:00

Hi Thomas,

I use GPU GFORCE 580 gtx on Ubuntu.
I used a "daily build" yesterday and today, both same problem. Not in regular 2.69.
Tomorrow I will test on similar System (Ubuntu as well) but with 560 gtx ti.

thank you for your great work!
KB

Hi Thomas, I use GPU GFORCE 580 gtx on Ubuntu. I used a "daily build" yesterday and today, both same problem. Not in regular 2.69. Tomorrow I will test on similar System (Ubuntu as well) but with 560 gtx ti. thank you for your great work! KB

Karsten Bitter commented

2014-02-19 00:58:01 +01:00

I just checked:

I used the build blender-2.69-688d098-linux-glibc211-x86_64.tar.bz2 from builder.blender.org.

regards,
kb

I just checked: I used the build blender-2.69-688d098-linux-glibc211-x86_64.tar.bz2 from builder.blender.org. regards, kb

Karsten Bitter commented

2014-02-19 01:40:52 +01:00

Ok,

I just tried on the same Hardware (GFORCE 580gtx) but the windows 7 64bit Operating system:
todays windows version of builder.blender.org same behaviour: GPU rendering does not update, cpu does.

best regards,
kb

Ok, I just tried on the same Hardware (GFORCE 580gtx) but the windows 7 64bit Operating system: todays windows version of builder.blender.org same behaviour: GPU rendering does not update, cpu does. best regards, kb

Thomas Dinges commented

2014-02-19 01:46:22 +01:00

Thanks for the additional info. Can confirm it now with GPU.

It updates though, even before a tile is finished. If I render the bmw scene with 500 samples and 256x256 tile size, I get updates about every 150 samples. So I guess the updates are just not as frequent as before.

Guys, is that intentional?

Thanks for the additional info. Can confirm it now with GPU. It updates though, even before a tile is finished. If I render the bmw scene with 500 samples and 256x256 tile size, I get updates about every 150 samples. So I guess the updates are just not as frequent as before. Guys, is that intentional?

Thomas Dinges commented

2014-02-19 01:46:53 +01:00

Added subscribers: @MartijnBerger, @brecht

Martijn Berger commented

2014-02-19 07:53:55 +01:00

@dingto. This is a direct result of my last fix to device_cuda.

It can happen depending on the driver and the exact timing that almost all path_trace jobs get pushed into the Cuda event queue it seems.
I am not sure how often we want to update but I am pretty sure I can fix it to update more often.

Ill look into this tonight.

@dingto. This is a direct result of my last fix to device_cuda. It can happen depending on the driver and the exact timing that almost all path_trace jobs get pushed into the Cuda event queue it seems. I am not sure how often we want to update but I am pretty sure I can fix it to update more often. Ill look into this tonight.

Martijn Berger was assigned by Lukas Tönne

2014-02-19 16:00:27 +01:00

Lukas Tönne commented

2014-02-19 16:00:27 +01:00

Added subscriber: @LukasTonne