osl warning depends on ui #46117

New Issue

Jacques Lucke · 2015-09-15T10:58:03+02:00

Jacques Lucke commented

2015-09-15 10:58:03 +02:00

System Information
Windows 7 64 bit
Nvidia Quadro 600

Blender Version
Broken: 07a7d64

Short description of error
A user of the animation nodes experienced a crash when setting the default_value of an input socket of the script node. I dived deeper into that and found a behavior that is most propably not intended to be this way. I don't know if this was the reason for the crash or not yet..
Basicly I get a warning message in the console but only under some specific circumstances that shouldn't be related. The message is "WARNING: attempting to set parameter with wrong type: Point (exepected 'point', received 'vector')"

Exact steps for others to reproduce the error

Load the default scene
Switch to cycles
Enable "Open Shading Language" in the render settings
Open the text editor and insert the "Noise" OSL template
Create a new material for the cube in the node editor
Insert a script node and assign the noise.osl file
Make sure you are in solid mode and have the node editor open
In the properties editor: Switch to the material tab
In the node editor: Link the 'Perlin' output to the 'Color' input of the diffuse node

Now there should be a warning in the console.. Important to note is that this warning is ONLY there when you are in the material tab in the properties editor OR there is a layout.prop_search for the materials somewhere visible in the interface. I tested this by putting the prop_search into a custom panel. Whenever the panel was closed the warning didn't appear and the other way around.

Whenever you make a change in the node editor now the warning will be printed again.

osl_warning.blend
When the file is open change anything you want in the node editor (eg. make a link into the empty space, or copy a node)

**System Information** Windows 7 64 bit Nvidia Quadro 600 **Blender Version** Broken: 07a7d64 **Short description of error** A user of the animation nodes experienced a crash when setting the *default_value* of an input socket of the script node. I dived deeper into that and found a behavior that is most propably not intended to be this way. I don't know if this was the reason for the crash or not yet.. Basicly I get a warning message in the console but only under some specific circumstances that shouldn't be related. The message is "WARNING: attempting to set parameter with wrong type: Point (exepected 'point', received 'vector')" **Exact steps for others to reproduce the error** 1. Load the default scene 2. Switch to cycles 3. Enable "Open Shading Language" in the render settings 4. Open the text editor and insert the "Noise" OSL template 5. Create a new material for the cube in the node editor 6. Insert a script node and assign the noise.osl file 7. Make sure you are in solid mode and have the node editor open 8. In the properties editor: Switch to the material tab 9. In the node editor: Link the 'Perlin' output to the 'Color' input of the diffuse node Now there should be a warning in the console.. Important to note is that this warning is ONLY there when you are in the material tab in the properties editor OR there is a layout.prop_search for the materials somewhere visible in the interface. I tested this by putting the prop_search into a custom panel. Whenever the panel was closed the warning didn't appear and the other way around. Whenever you make a change in the node editor now the warning will be printed again. ![osl warning.PNG](https://archive.blender.org/developer/F233397/osl_warning.PNG) [osl_warning.blend](https://archive.blender.org/developer/F233399/osl_warning.blend) When the file is open change anything you want in the node editor (eg. make a link into the empty space, or copy a node)

Jacques Lucke commented

2015-09-15 10:58:03 +02:00

Changed status to: 'Open'

Jacques Lucke commented

2015-09-15 10:58:03 +02:00

Added subscriber: @JacquesLucke

Sergey Sharybin commented

2015-09-24 11:51:16 +02:00

Added subscriber: @Sergey

Sergey Sharybin commented

2015-09-24 11:51:16 +02:00

Changed status from 'Open' to: 'Archived'

Sergey Sharybin closed this issue

2015-09-24 11:51:16 +02:00

Sergey Sharybin self-assigned this 2015-09-24 11:51:16 +02:00

Sergey Sharybin commented

2015-09-24 11:51:16 +02:00

Those are just harmless warning messages. Root of the issue is that in the UI we don't separate vector, point and normal it is all just vectors, without any extra semantic. However, OSL does separate semantic, so in order to make sure all parameters are properly updated we currently asking to set same parameter with all three types and same value. Incompatible form OSL point of view values will be ignored (with the warning message printed to the console), compatible one will be used to set parameter. This causes 2 warning messages per blender's SOCK_VECTOR socket.

Surely we could try being smarter here and query actual paramter type from script itself, check if it's compatible with blender's socket type and so on.. Or support sematic meaning for SOCK_VECTOR from blender side. But all this i wouldn't consider a bug, just something which could be improved.

Also, to make it clear. This warnings are only appearing when Cycles starts to render something with that material. So if you don't have any material preview or material icon visible no rendering will happen. That explains why you only have those warnings printed in only certain UI configurations.

Crash with animating input sockets is to be narrowed down are reported separately btw.

So thanks for the report, but is' more a TODO.

Those are just harmless warning messages. Root of the issue is that in the UI we don't separate vector, point and normal it is all just vectors, without any extra semantic. However, OSL does separate semantic, so in order to make sure all parameters are properly updated we currently asking to set same parameter with all three types and same value. Incompatible form OSL point of view values will be ignored (with the warning message printed to the console), compatible one will be used to set parameter. This causes 2 warning messages per blender's SOCK_VECTOR socket. Surely we could try being smarter here and query actual paramter type from script itself, check if it's compatible with blender's socket type and so on.. Or support sematic meaning for SOCK_VECTOR from blender side. But all this i wouldn't consider a bug, just something which could be improved. Also, to make it clear. This warnings are only appearing when Cycles starts to render something with that material. So if you don't have any material preview or material icon visible no rendering will happen. That explains why you only have those warnings printed in only certain UI configurations. Crash with animating input sockets is to be narrowed down are reported separately btw. So thanks for the report, but is' more a TODO.

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

osl warning depends on ui #46117