Custom normals shading error #46028

New Issue

Xavier Thomas · 2015-09-06T16:02:07+02:00

Xavier Thomas commented

2015-09-06 16:02:07 +02:00

System Information
Windows7, Nvidia GTX970

Blender Version
Broken: 2.75a

Short description of error
Shading error when using custom normals (sometimes).

Exact steps for others to reproduce the error
Open the attached files, in edit mode you can confirm that all normals are pointing upwards.
Switch yo object mode and set the shading ,mode to "material" or "solid", both shading are wrong.
In Material mode we can see easily that both faces of the tree are shaded differently. In solid mode shading looks correct at first but change with the view direction although the material is only lambertian diffuse with no specular.

The object was imported by a custom python code of mine, but at first the shading was correct. The file was saving reloading with correct shading. But after messing with the material and texture properties the shading changed.

**System Information** Windows7, Nvidia GTX970 **Blender Version** Broken: 2.75a **Short description of error** Shading error when using custom normals (sometimes). **Exact steps for others to reproduce the error** Open the attached files, in edit mode you can confirm that all normals are pointing upwards. Switch yo object mode and set the shading ,mode to "material" or "solid", both shading are wrong. In Material mode we can see easily that both faces of the tree are shaded differently. In solid mode shading looks correct at first but change with the view direction although the material is only lambertian diffuse with no specular. The object was imported by a custom python code of mine, but at first the shading was correct. The file was saving reloading with correct shading. But after messing with the material and texture properties the shading changed.

Xavier Thomas commented

2015-09-06 16:02:07 +02:00

Changed status to: 'Open'

Xavier Thomas commented

2015-09-06 16:02:07 +02:00

Added subscriber: @XavierThomas

Xavier Thomas commented

2015-09-06 16:03:44 +02:00

CustomNormalShadingBug.blend

[CustomNormalShadingBug.blend](https://archive.blender.org/developer/F230834/CustomNormalShadingBug.blend)

Campbell Barton commented

2015-09-08 07:55:00 +02:00

Added subscriber: @ideasman42

WK Bong commented

2015-09-08 08:52:12 +02:00

Added subscriber: @WeeKwongBong

Bastien Montagne commented

2015-09-11 12:30:33 +02:00

Added subscriber: @mont29

Bastien Montagne commented

2015-09-11 12:30:33 +02:00

Changed status from 'Open' to: 'Archived'

Bastien Montagne closed this issue

2015-09-11 12:30:33 +02:00

Bastien Montagne self-assigned this 2015-09-11 12:30:33 +02:00

Bastien Montagne commented

2015-09-11 12:30:33 +02:00

You are using vnors coplanar to their face… This will never really work I think (in flat or smooth shading, it will generate surface normals parallel to the face).

Xavier Thomas commented

2015-09-11 15:54:53 +02:00

Yes, that is the goal. Basically I want trees that look shade-less but are not and receive the same amount of light as the ground (so it works at night and in low light condition contrary to shade-less). This is very common in games and works OK in both graphical engine I wrote the importer/exporter for.

My users workflow is:

Import a scene form one format
Do some verification and modification in Blender
Export to another format

I all works well but sometimes the user is thrown off by the wrong shading in Blender's viewport and stop there and send me a bug report before even exporting although the export of custom normals and shading in the other graphic engine is OK.

IMO this is task is valid because this is a technique used very frequently in game foliage (not only my client but pretty much every foliage in every RT graphic engine) and having visual feedback directly in Blender, instead of forcing to export and check normals in the native engine, is important to many user I would think.

Yes, that is the goal. Basically I want trees that look shade-less but are not and receive the same amount of light as the ground (so it works at night and in low light condition contrary to shade-less). This is very common in games and works OK in both graphical engine I wrote the importer/exporter for. My users workflow is: - Import a scene form one format - Do some verification and modification in Blender - Export to another format I all works well but sometimes the user is thrown off by the wrong shading in Blender's viewport and stop there and send me a bug report before even exporting although the export of custom normals and shading in the other graphic engine is OK. IMO this is task is valid because this is a technique used very frequently in game foliage (not only my client but pretty much every foliage in every RT graphic engine) and having visual feedback directly in Blender, instead of forcing to export and check normals in the native engine, is important to many user I would think.

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

Custom normals shading error #46028