Thread Back to Scriptorium Truespace Archive Announcements Archive: Tech Forum Bugs Business Collaboration Feature suggestions Game Development Hardware Image Gallery Interactive Artwork iSpace Monthly Modeling Contest New Users Rants and Raves Roundtable Scriptorium Speed Model Challenge Tech Forum The Garage truePlay Visitor Area Work in Progress Site Features Citizens List Badges & Achievements Events Directory News and Articles Worlds List About Alphaworld Search Object Paths Activeworlds Support Download Activeworlds Quickstart Tutorial Historic Archives Truespace Archives Newsgroup Archives

Nodes that need to update. About Truespace Archives These pages are a copy of the official truespace forums prior to their removal somewhere around 2011. They are retained here for archive purposes only. Nodes that need to update. // Scriptorium 1  |   Order by default Post by Asem // Oct 16, 2006, 11:17pm Asem Total Posts: 255 I find that some of the nodes don't seem to be updated as some like for instance the "highlight evaluater" node doesn't contain a D3DMat link -> out. Simply connecting the "highlight evaluater" color link->out to "Visual Widget" material won't pick up the link of the color of the current "highlight evaluater". The Left is what is currently in the "widgets package" library. The right seems to be the correct one which I found by going into other widget nodes and adding it to the "widgets package" library which works. Post by tomasb // Oct 16, 2006, 11:37pm tomasb Total Posts: 261 I find that some of the nodes don't seem to be updated as some like for instance the "highlight evaluater" node doesn't contain a D3DMat link -> out. Simply connecting the "highlight evaluater" color link->out to "Visual Widget" material won't pick up the link of the color of the current "highlight evaluater". The Left is what is currently in the "widgets package" library. The right seems to be the correct one which I found by going into other widget nodes and adding it to the "widgets package" library which works. the left one is interpolating input values and output color. The right one has inside render attributes node and d3d material, which take output values from left one. Vis controller material input accepts all connectors because there are multiple materials it supports. It does not work, because d3d view does not accept color as a material. Post by Asem // Oct 17, 2006, 12:48am Asem Total Posts: 255 Thanks for clearing that up thomasb :). I assumed that they were the same guess I should change the name os the 2nd. I got it working just fine now and even have a custom widget going (though not completed).

Awportals.com is a privately held community resource website dedicated to Active Worlds.
Copyright (c) Mark Randall 2006 - 2024. All Rights Reserved.