rendering under Windows XP32 SP3 with latest SVN is white #36935

New Issue

mathieu menuet · 2013-10-03T17:50:33+02:00

mathieu menuet commented

2013-10-03 17:50:33 +02:00

%%%--- Operating System, Graphics card ---
XP SP3, atom processor N270

- Blender version with error, and version that worked ---

latest SVN has the bug, 2.68a works

- Short description of error ---

rendering default scene with factory defaults is white. Rendering takes time, samples update (1/10, 2/10...) , but only white is displayed.

- Steps for others to reproduce the error (preferably based on attached .blend file) ---

Hit F12 or enter "rendering" viewport mode on default scene with factory defaults and cycles.%%%

%%%--- Operating System, Graphics card --- XP SP3, atom processor N270 - Blender version with error, and version that worked --- latest SVN has the bug, 2.68a works - Short description of error --- rendering default scene with factory defaults is white. Rendering takes time, samples update (1/10, 2/10...) , but only white is displayed. - Steps for others to reproduce the error (preferably based on attached .blend file) --- Hit F12 or enter "rendering" viewport mode on default scene with factory defaults and cycles.%%%

mathieu menuet commented

2013-10-03 17:50:33 +02:00

Changed status to: 'Open'

Brecht Van Lommel commented

2013-10-03 18:50:54 +02:00

%%%Does this issue happen in the test build?
http://download.blender.org/release/Blender2.69/

What is your graphics card?%%%

%%%Does this issue happen in the test build? http://download.blender.org/release/Blender2.69/ What is your graphics card?%%%

mathieu menuet commented

2013-10-03 21:17:15 +02:00

%%%Yes the Issue happen in the given test build.
The graphic card name in hardware manager is " Intel Mobile 945 chipset family ". But I use CPU Rendering.%%%

%%%Yes the Issue happen in the given test build. The graphic card name in hardware manager is " Intel Mobile 945 chipset family ". But I use CPU Rendering.%%%

Bastien Montagne commented

2013-10-03 21:45:46 +02:00

%%%Eeeek… Atom and 945… Do we even want to try to support such hardware, esp. for cycles???%%%

%%%Eeeek… Atom and 945… Do we even *want* to try to support such hardware, esp. for cycles???%%%

Sergey Sharybin commented

2013-10-03 21:49:53 +02:00

%%%Couple of questions:

Does regular image display in Image Editor works fine?
Does Blender Internal rendering goes fine?

Also Brecht commited some changes at svn rev60509 which potentially might solve your issue, so please give it a try :)%%%

%%%Couple of questions: - Does regular image display in Image Editor works fine? - Does Blender Internal rendering goes fine? Also Brecht commited some changes at svn rev60509 which potentially might solve your issue, so please give it a try :)%%%

mathieu menuet commented

2013-10-04 10:23:41 +02:00

%%%@Bastien I only use it to program in the train. Waiting every day until I come back home to check my changes is a bit too long. I prefer to correct bugs instantly. And I don't have money to buy a new laptop. Going to try new buildbot.%%%

mathieu menuet commented

2013-10-04 11:23:33 +02:00

%%%@Sergey : Latest Buildbot (r60539) doesn't solves the problem.

Regular image display in Image Editor works
BI rendering works
2.68a Cycles works%%%

%%%@Sergey : Latest Buildbot (r60539) doesn't solves the problem. - Regular image display in Image Editor works - BI rendering works - 2.68a Cycles works%%%

Brecht Van Lommel commented

2013-10-04 18:26:47 +02:00

%%%I committed a possible fix, can you test the latest 32 bit windows build here (revision 60550 or newer)?
http://builder.blender.org/download/

I tested in a virtual machine with Windows XP 32 bit, but couldn't redo the issue, so I can't tell if it is fixed.
%%%

%%%I committed a possible fix, can you test the latest 32 bit windows build here (revision 60550 or newer)? http://builder.blender.org/download/ I tested in a virtual machine with Windows XP 32 bit, but couldn't redo the issue, so I can't tell if it is fixed. %%%

mathieu menuet commented

2013-10-04 20:47:31 +02:00

%%%F12 render works, but not viewport. Even without a single light and with world surface shader removed, viewport render is white. As always, I restore factory defaults, so no option or plugin can affect the rendering. Changing the color management to Exposure -10 and gamma 0 has no effect, neither changing look, display or color space.%%%

mathieu menuet commented

2013-10-04 20:55:48 +02:00

%%%If the bug is too hard to resolve and I'm the only one having it, you can leave it. Having to do a F12 render is not that problematic, since I don't personally need fast update of changes.%%%

Brecht Van Lommel commented

2013-10-04 20:57:21 +02:00

%%%Ok, can you attach the output of Help > System Info? I'm suspecting your graphics card can't correctly run the GLSL color management shader.

Also, is there any error in Windows > Console?

And, are you absolutely sure F12 rendering was broken before this fix in revision 60550? In your original report you mention the error can be reproduced by pressing F12, but the fix I did should affect both F12 render and viewport render, so if it affects only one of them, that would be quite strange.%%%

%%%Ok, can you attach the output of Help > System Info? I'm suspecting your graphics card can't correctly run the GLSL color management shader. Also, is there any error in Windows > Console? And, are you absolutely sure F12 rendering was broken before this fix in revision 60550? In your original report you mention the error can be reproduced by pressing F12, but the fix I did should affect both F12 render and viewport render, so if it affects only one of them, that would be quite strange.%%%

Sanc Tuary commented

2013-10-04 23:54:31 +02:00

%%%Hello,

I'm on window XP SP3 and i have an Intel G41 (support OpenGL 2.1) with it.
I tested on r60539 (from before you removed the SS2 optimisation from what i read) for which i loaded default factory
I then switched to Cycles render and pressed F12 , the default Cube was correctly rendered by Cycles (of course CPU rendering)
I then switched the viewport to Rendered, and again the viewport was correctly rendered.

I didn't observed the white render bug on my system with r60539, but in the same time i usually never use Cycles in my Blender works so i wouldn't have noticed if something changed in a specific version.

%%%

%%%Hello, I'm on window XP SP3 and i have an Intel G41 (support OpenGL 2.1) with it. I tested on r60539 (from before you removed the SS2 optimisation from what i read) for which i loaded default factory I then switched to Cycles render and pressed F12 , the default Cube was correctly rendered by Cycles (of course CPU rendering) I then switched the viewport to Rendered, and again the viewport was correctly rendered. I didn't observed the white render bug on my system with r60539, but in the same time i usually never use Cycles in my Blender works so i wouldn't have noticed if something changed in a specific version. %%%

mathieu menuet commented

2013-10-05 09:15:52 +02:00

%%%@brecht There is no error in the console. The system-info.txt is not created despite the console output is in system-info.txt. I did a search on all my partition, nothing found. I manually searched temp folder, blender installation and configuration folders... nothing. I tested again on r60295, you are right the F12 render works, not sure on which version I had the F12 problem. It may be a mistake. The oldest build I could find on my HDD was r60095 and the bug was only for viewport render as well.
As the changes didn't solved the problem, you can revert them. Would be a shame to remove optimisations for other people. Atom processor seems to support up to SSE4 anyway : http://ark.intel.com/products/36331.
As said before, I don't mind that much if the viewport cycles render is broken on such an old graphic card now that F12 is working again with all colour management options (I can change to RRT, film as well as change the look and it all updates fast)%%%

%%%@brecht There is no error in the console. The system-info.txt is not created despite the console output is in system-info.txt. I did a search on all my partition, nothing found. I manually searched temp folder, blender installation and configuration folders... nothing. I tested again on r60295, you are right the F12 render works, not sure on which version I had the F12 problem. It may be a mistake. The oldest build I could find on my HDD was r60095 and the bug was only for viewport render as well. As the changes didn't solved the problem, you can revert them. Would be a shame to remove optimisations for other people. Atom processor seems to support up to SSE4 anyway : http://ark.intel.com/products/36331. As said before, I don't mind that much if the viewport cycles render is broken on such an old graphic card now that F12 is working again with all colour management options (I can change to RRT, film as well as change the look and it all updates fast)%%%

Sanc Tuary commented

2013-10-05 16:32:03 +02:00

%%%From what i have read bliblu bli's " Intel Mobile 945 chipset family " supports OpenGL 1.4 , could the OpenGL version be linked to the problem ?%%%

Brecht Van Lommel commented

2013-10-05 16:51:03 +02:00

%%%The system-info.txt is in the Blender text editor, if you open a text editor it should be there, and you can then save it to disk.

And yes, given that F12 render works it is definitely related to OpenGL and GLSL feature support, so the system-info is important to show us exactly which version the driver supports and which extensions are available.%%%

%%%The system-info.txt is in the Blender text editor, if you open a text editor it should be there, and you can then save it to disk. And yes, given that F12 render works it is definitely related to OpenGL and GLSL feature support, so the system-info is important to show us exactly which version the driver supports and which extensions are available.%%%

Brecht Van Lommel commented

2013-10-05 22:01:29 +02:00

%%%I found the issue now. The problem is that this graphics card doesn't support half float textures, which we need. Fixed that now, but it means color management will not work in the 3D viewport with this graphics card, only for final rendering, same as it was in 2.68a.

Fix is in revision 60573.%%%

%%%I found the issue now. The problem is that this graphics card doesn't support half float textures, which we need. Fixed that now, but it means color management will not work in the 3D viewport with this graphics card, only for final rendering, same as it was in 2.68a. Fix is in revision 60573.%%%

Brecht Van Lommel commented

2013-10-05 22:01:29 +02:00

Changed status from 'Open' to: 'Resolved'

Brecht Van Lommel closed this issue

2013-10-05 22:01:29 +02:00

mathieu menuet commented

2013-10-05 22:03:19 +02:00

%%%Sorry, I wouldn't have thought about looking in the text editor by myself :D Attached the sysinfo.txt file with openGL and compil flags info.%%%

mathieu menuet commented

2013-10-06 10:26:40 +02:00

%%%Thanks Brecht, but after downloading r60573 from buildbot, it still renders white in viewport with factory defaults. As mentioned above, I attached the sysinfo.txt.%%%

Brecht Van Lommel commented

2013-10-12 15:57:05 +02:00

%%%Another fix was committed now, in revision 60709.%%%

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

rendering under Windows XP32 SP3 with latest SVN is white #36935