Hey all,
I've been digging into this software (It's really great!) quite a bit recently but as I get more familiar with the tools I find that I'm plagued by trigger logic getting arbitrarily skipped or missed. It makes it quite difficult to troubleshoot and otherwise tight logic loops break and render a scene in complete disarray. I'd really like to be able to release some things to the community, but until I'm able to tighten up the consistency in my scenes, I'm pretty reluctant too. The best sort of antidote for this that I've discovered is really simplifying a bunch of operations and reducing the load. You can make plenty of good stuff using this method, but its a shame that it kind of dampens the total potential of the software. It's hard to describe and/or debug the problem accurately, but it seems to happen quite a bit and unless it's on my end someone would have surely run into the same issue as their scene grows. Want to make sure I'm not crazy. The most high level example would be a given trigger (type doesn't seem to matter) with 5 or so operations, it'll make it to the 3rd and skip the rest, etc.
I'm curious if this is on my end or is this part of the software? Is this something that is avoidable with some settings? Is it my hardware? I was going to try a hard uninstall->reinstall but I figured I try asking for help first in case there's something obvious that I'm missing. While I have the floor, quick thank you to all of the plugin and advanced users that make this great software even better. Thanks!
vtk
I've been digging into this software (It's really great!) quite a bit recently but as I get more familiar with the tools I find that I'm plagued by trigger logic getting arbitrarily skipped or missed. It makes it quite difficult to troubleshoot and otherwise tight logic loops break and render a scene in complete disarray. I'd really like to be able to release some things to the community, but until I'm able to tighten up the consistency in my scenes, I'm pretty reluctant too. The best sort of antidote for this that I've discovered is really simplifying a bunch of operations and reducing the load. You can make plenty of good stuff using this method, but its a shame that it kind of dampens the total potential of the software. It's hard to describe and/or debug the problem accurately, but it seems to happen quite a bit and unless it's on my end someone would have surely run into the same issue as their scene grows. Want to make sure I'm not crazy. The most high level example would be a given trigger (type doesn't seem to matter) with 5 or so operations, it'll make it to the 3rd and skip the rest, etc.
I'm curious if this is on my end or is this part of the software? Is this something that is avoidable with some settings? Is it my hardware? I was going to try a hard uninstall->reinstall but I figured I try asking for help first in case there's something obvious that I'm missing. While I have the floor, quick thank you to all of the plugin and advanced users that make this great software even better. Thanks!
vtk
