[BUG] 2.43 Windows - Map Textures feedback loops

A forum where development builds are posted for testing by the community.
Forum rules
NOTE: The software in this forum is not %100 reliable, they are development builds and are meant for testing by experienced octane users. If you are a new octane user, we recommend to use the current stable release from the 'Commercial Product News & Releases' forum.
Post Reply
User avatar
PolygonPusher
Licensed Customer
Posts: 45
Joined: Fri Feb 04, 2011 4:00 pm
Location: St.Loius
Contact:

In the node editor you can feed a output back into a mix texture which will crash the IDE.

Maybe some logic to check the start and end point of a node to prevent feed backs on mix nodes? I know this is command sense to not do this but I had a bunch of nodes that this happed accidentally and I lost all my work.
polyon-pushers.org| Flickr| twitter | vimeo
spec: i7 975 3.33ghz | 12 gigs ram | gtx 260 - 195 cuda cores | win 7 64bit | blender 3d | Octane 2.43
IRC: freenode - #blenderchat - #blendercoders - #octanerender
User avatar
abstrax
OctaneRender Team
Posts: 5510
Joined: Tue May 18, 2010 11:01 am
Location: Auckland, New Zealand

PolygonPusher wrote:In the node editor you can feed a output back into a mix texture which will crash the IDE.

Maybe some logic to check the start and end point of a node to prevent feed backs on mix nodes? I know this is command sense to not do this but I had a bunch of nodes that this happed accidentally and I lost all my work.
Thanks, it has been reported before, but now I have added it to our bug database :)

Cheers,
Marcus
In theory there is no difference between theory and practice. In practice there is. - Yogi Berra
Post Reply

Return to “Development Build Releases”