|
AutoUV shaders [updated: 05/13/2020]
|
|
12-05-2015, 03:35 AM
Post: #25
|
|||
|
|||
|
RE: AutoUV shaders [updated: 10/29/2015]
Ok.. After few hickups..
Code: {name, "Test"}. % The name in the shader selectorCode: #define pi 3.14159265359;Result = AUV: Test ok No errors, but also.. no texture. Also... did figure out that part of my issue was that I have more than one install of Wings, since the mlab one, as well as the other one, insists on installing "new" versions into unique folders every time, instead of something sensible (and thus predictable). Was trying to edit the wrong copies... Sigh... lol Still, editing the right ones.. still didn't get me any place. Actually. That might be easy to fix. Modern copies of windows don't like people playing with the stuff in the program folders anyway. So, seems to me that there should be a plugin folder in "Documents" for each user as well, to be consistent with other applications. And, as long as it "shared" the name of this folder, editing things in it should effect "all" copies of Wings, regardless of version. Anyway. With the above changes it seems to compile, but.. still not do anything. Might it be setting the "alpha" to full transparency, since its only using the RGB values? Or does it default to fully visible, unless you tell it otherwise? Only thing I can think of at this point. |
|||
|
« Next Oldest | Next Newest »
|
User(s) browsing this thread: 1 Guest(s)



