... Thought I had it worked out. Noticed that the files seem to have permissions for Admin, SYSTEM, Users, but not my account, so, set them to also work with my account. And.. still not working.
Tried to run Wings as Admin, no dice.
Also, I did a direct replacement of my files with your files, so.. no reason that shouldn't work.
Trying your suggesting, since I need to upgrade my copy of Wings to the latest build anyway. Unzipped your files to the new place. And, tried again. Same result.
I looked in the system registry, in case something odd was in there. Nothing.
Considering looking in the prefs, to see what might be up in there, but can't see that doing it (though, this one confuses me, because the main Wings opens full screen, but the other one doesn't, and I have no clue how I got the first one to do that, but the second one won't, or even if that is "in" the preferences file. So, something is different there, but.. why it would effect this shader, or even my prior attempt at one..
Ok, had a brief hickup due to not having copied the "standard.vs" file over to the folder for the new copy. Now the old ones I got from you work, but.. again, the new one doesn't. Before copying that file, they didn't either.
Wow.. something damn strange going on. The new manifold version crashes when trying to pick a color for me, and half the shaders just stopped working at all in it after a few attempts to play with them. Could having more than one version installed be doing this?
Hmm. Nope, that isn't it either. Trying the new official build.
And.. still no dice, either the 32 or 64 bit one. It can't be my machine having some issue with this shader. I suppose there might be something being "saved" by windows, and attached to Wings that is doing it, but for the life of me I can't imagine what. I am baffled at this point.
Tried to run Wings as Admin, no dice.
Also, I did a direct replacement of my files with your files, so.. no reason that shouldn't work.
Trying your suggesting, since I need to upgrade my copy of Wings to the latest build anyway. Unzipped your files to the new place. And, tried again. Same result.
I looked in the system registry, in case something odd was in there. Nothing.
Considering looking in the prefs, to see what might be up in there, but can't see that doing it (though, this one confuses me, because the main Wings opens full screen, but the other one doesn't, and I have no clue how I got the first one to do that, but the second one won't, or even if that is "in" the preferences file. So, something is different there, but.. why it would effect this shader, or even my prior attempt at one..
Ok, had a brief hickup due to not having copied the "standard.vs" file over to the folder for the new copy. Now the old ones I got from you work, but.. again, the new one doesn't. Before copying that file, they didn't either.
Wow.. something damn strange going on. The new manifold version crashes when trying to pick a color for me, and half the shaders just stopped working at all in it after a few attempts to play with them. Could having more than one version installed be doing this?
Hmm. Nope, that isn't it either. Trying the new official build.
And.. still no dice, either the 32 or 64 bit one. It can't be my machine having some issue with this shader. I suppose there might be something being "saved" by windows, and attached to Wings that is doing it, but for the life of me I can't imagine what. I am baffled at this point.