Displace Modifier errors using a baked Image and displace baking inconsistency between 2.67/2.68RC and previous versions #36058

New Issue

Daniel F. R. Gordillo · 2013-07-08T14:30:14+02:00

2013-07-08 14:30:14 +02:00

%%%--- Operating System, Graphics card ---
Linux Mint debian edition, AMD Phenom II X6 1090T, 8GB RAM, Nvidia 460 GTX

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

Working: 2.63, error: 2.67b - 2.68 RC

- Short description of error ---

When i open some files that have objects using the displace modifier with a previously baked image from a Hi-Poly object, sometimes the mesh went crazy, like inside out. (it happened mostly when clicking on the visibility button on the modifier. When switching the visibility back on, the mesh would be all messed up)

So, in 2.67b and 2.68 RC versions, if the displacement looks OK when loading the file, going to the texture panel and switching "input color space" from default sRGB to Linear or Non-color, and back to sRGB, that will trigger the bug.

Also, doing some tests, the result of baking a displacement map in 2.63 and 2.67b/2.68 RC is different (images attached). I'm using the exact same settings in all three: 2.63 image is OK, but the image baked on the other 2 versions has a lot more contrast, so the displacement becomes exaggerated.

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

i'm uploading a graphic guide using a blend file (i'm uploading it to dropbox: it's a ZIP which contains the blend file along with 2 baked images. The *.blend is over 40 Mb)
%%%

%%%--- Operating System, Graphics card --- Linux Mint debian edition, AMD Phenom II X6 1090T, 8GB RAM, Nvidia 460 GTX - Blender version with error, and version that worked --- Working: 2.63, error: 2.67b - 2.68 RC - Short description of error --- When i open some files that have objects using the displace modifier with a previously baked image from a Hi-Poly object, sometimes the mesh went crazy, like inside out. (it happened mostly when clicking on the visibility button on the modifier. When switching the visibility back on, the mesh would be all messed up) So, in 2.67b and 2.68 RC versions, if the displacement looks OK when loading the file, going to the texture panel and switching "input color space" from default sRGB to Linear or Non-color, and back to sRGB, that will trigger the bug. Also, doing some tests, the result of baking a displacement map in 2.63 and 2.67b/2.68 RC is different (images attached). I'm using the exact same settings in all three: 2.63 image is OK, but the image baked on the other 2 versions has a lot more contrast, so the displacement becomes exaggerated. - Steps for others to reproduce the error (preferably based on attached .blend file) --- i'm uploading a graphic guide using a blend file (i'm uploading it to dropbox: it's a ZIP which contains the blend file along with 2 baked images. The *.blend is over 40 Mb) %%%

Daniel F. R. Gordillo commented

2013-07-08 14:30:14 +02:00

Changed status to: 'Open'

Daniel F. R. Gordillo commented

2013-07-08 14:42:29 +02:00

%%%Here it is (blend file, 2 baked images and the graphic explanation):

https://www.dropbox.com/s/u7boll6qzxmgfi0/prueba_displace.zip%%%

%%%Here it is (blend file, 2 baked images and the graphic explanation): https://www.dropbox.com/s/u7boll6qzxmgfi0/prueba_displace.zip%%%

Sergey Sharybin commented

2013-07-10 11:12:23 +02:00

%%%Baked images are not so helpful for bugfixing. Please attach file used for baking so it's easy to reproduce baking differences in 2.63 and new blender.
Also please attach file which demonstrates the issue with wrong displacement modifier when toggling visibility or changing color space.

This would save lots of time reproducing exact circumstances of the issue.%%%

%%%Baked images are not so helpful for bugfixing. Please attach file used for baking so it's easy to reproduce baking differences in 2.63 and new blender. Also please attach file which demonstrates the issue with wrong displacement modifier when toggling visibility or changing color space. This would save lots of time reproducing exact circumstances of the issue.%%%

Daniel F. R. Gordillo commented

2013-07-10 13:59:39 +02:00

%%%the blend file is in the ZIP (dropbox link in my previous comment)%%%

Sergey Sharybin commented

2013-07-10 14:14:01 +02:00

%%%I did't actually understand what exactly that file shows. I've tried to bake from Plano.HiPoly onto a Plane (disabled all the modifiers first) and bake result is the same in 2.63a and 2.67b.
And i wasn't been able to reproduce werideness by toggling modifiers visibility or changing image color space.

There're too many circumstances to be taken into account when you're baking. So please, prepare file for which it'll be just matter of pressing "Bake" to see the differences between 2.63a and 2.67b. Same goes to the modifier visibility issue: please prepare file which is just enough to open and toggle the visibility/change color space to screw up displacement.%%%

%%%I did't actually understand what exactly that file shows. I've tried to bake from Plano.HiPoly onto a Plane (disabled all the modifiers first) and bake result is the same in 2.63a and 2.67b. And i wasn't been able to reproduce werideness by toggling modifiers visibility or changing image color space. There're too many circumstances to be taken into account when you're baking. So please, prepare file for which it'll be just matter of pressing "Bake" to see the differences between 2.63a and 2.67b. Same goes to the modifier visibility issue: please prepare file which is just enough to open and toggle the visibility/change color space to screw up displacement.%%%

Daniel F. R. Gordillo commented

2013-07-10 16:52:02 +02:00

%%%I will try to make a couple of better files.

It's tricky because i have been seeing this kinf of behaviour for a while now (i believe all the 2.6x series), but until now i couldn't say what triggers the displace error. Even now, the error doesn't show up every time (see attachment "displacemap_GOBLIN.jpg") Sometimes i open the file and it's like that, and sometimes i have to disable/enable the modifier to trigger it.%%%

%%%I will try to make a couple of better files. It's tricky because i have been seeing this kinf of behaviour for a while now (i believe all the 2.6x series), but until now i couldn't say what triggers the displace error. Even now, the error doesn't show up every time (see attachment "displacemap_GOBLIN.jpg") Sometimes i open the file and it's like that, and sometimes i have to disable/enable the modifier to trigger it.%%%

Daniel F. R. Gordillo commented

2013-07-10 18:30:58 +02:00

%%%i'm uploading "zombie_displace-test.blend".
1.- Open up the file in 2.76b or 2.68 RC. The head will look OK. (the displacement image uses default Input Color Space: sRGB)
2.- Go to the displace modifier and click on the visibility icon to turn it off. Click again to turn it on. The mesh is all messed up.

If you can't trigger the bug this way, just go to the textures panel, and change Color Input Space from sRGB -> Linear/Non-Color -> sRGB. Then it should be messed up. %%%

%%%i'm uploading "zombie_displace-test.blend". 1.- Open up the file in 2.76b or 2.68 RC. The head will look OK. (the displacement image uses default Input Color Space: sRGB) 2.- Go to the displace modifier and click on the visibility icon to turn it off. Click again to turn it on. The mesh is all messed up. If you can't trigger the bug this way, just go to the textures panel, and change Color Input Space from sRGB -> Linear/Non-Color -> sRGB. Then it should be messed up. %%%

Sergey Sharybin commented

2013-07-15 16:48:54 +02:00

%%%Fixed in svn rev58270, Thanks for the report, closing.%%%

Sergey Sharybin commented

2013-07-15 16:48:54 +02:00

Changed status from 'Open' to: 'Resolved'

Sergey Sharybin closed this issue

2013-07-15 16:48:54 +02:00

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

Displace Modifier errors using a baked Image and displace baking inconsistency between 2.67/2.68RC and previous versions #36058