| Message |
 |
- Date: 2009-04-29 13:55
- Sender: Ton Roosendaal
- I don't have glsl on my system, can't verify this error, all works as expected.
What we do need to know:
- in your file the texture nodes are not visible, but material nodes instead. I assume I should switch to texture node view
- test it without glsl enabled, and be more accurate what a "0-1 space" means. Node editor doesn't have such concept.
- node previews are currently a bit optimized to not execute too often, click on a node socket to force refreshes.
Brecht: are node textures supported in GLSL, or maybe giving issues?
|
- Date: 2009-04-29 14:13
- Sender: Brecht Van Lommel
- They are not supported in GLSL, but that shouldn't give issues, and for me in this file the textures is ignored as intended.
Also couldn't find other issues with preview render. It's not clear to me if preview render here is about the previews inside nodes, in the material buttons, or shift+p in the 3d view.
|
- Date: 2009-04-29 16:07
- Sender: Brian Staub
- i'm talking about the preview renders inside the nodes, and not the 3d view. brecht has already explained to me that texture nodes are not supported by GLSL.
regarding 0 - 1 space, i'm talking about the grid view in which we work with nodes. the preview renders inside of the nodes do not move with the node when dragged too far to the left past the center line (-x space on the cartesian grid) or too far down (-y on the cartesian grid). the little preview seems to slide out of the node's preview window and disappear while the node is being dragged past these center lines on the grid.
also the little node previews disappear sometimes just when adjusting materials or doing other tasks... probably a refresh problem..?
sorry for confusion
thanks
brian
|
- Date: 2009-04-29 16:14
- Sender: Ton Roosendaal
- If you have such graphics glitches, it's most certainly for all node usage, compositing and shading too. I also notice your OS now, there's a mac 10.5 nvidia driver bug with drawing texture images... but we thought it was solved in 10.5.6.
Be assured we use same code for all platforms, the code is even very basic opengl. Such glitches only happen occasionally when opengl fails...
|
- Date: 2009-04-29 16:40
- Sender: Brian Staub
- here's an example of the error i'm getting.
Ton, don't you and Brecht use macs? You're not having the trouble? must be the driver associated with the new cards used in the unibody macbook pros..? maybe i should file a complaint with apple.
thanks
|
- Date: 2009-04-29 16:50
- Sender: Ton Roosendaal
- I use a PPC g5, ATI, and have macbook pro with ATI too. Both work fine with Blender. :)
We had reports from people with nvidia macs, but heard the issue got solved in a recent mac update... things work also fine in nvidia linux, windows etc.
|
- Date: 2009-04-29 19:18
- Sender: Brian Staub
- ok, i spoke with an apple tech who filed the bug. she also wants me and the Blender devs to file the complaint as well at feedback.apple.com
if you guys would do this i'd be very grateful =)
thanks Devs
|
|
|
- Date: 2010-03-21 22:34
- Sender: Tom Musgrove
- This is a generic request to test your bug report and see if it is still an issue in 2.5alpha2 if so please let me know by making a comment in this report ie 'also in 2.5alpha2' and I will add it to the 2.5 bug list.
|
- Date: 2010-03-22 03:18
- Sender: brian staub
- hard to say if this is still a problem, because nodes seem wacky in general at the moment (as in aren't updated in the nodes view or 3d view most of the time)
|
