Ambiera ForumDiscussions, Help and Support. |
|
|
|||||
|
Coppercube looks wonderful, and people have done wonderful things with it. Looks like just what I've been looking for. That said, I am stymied trying to use "On proximity do something". I have 6.3 on a Macbook Air, 6.3 on a 32-bit Windows 7 notebook, 6.5.1 on a Windows 7 desktop, and 6.7.1 on a Windows 10 laptop. They all work exactly the same way (with the little I've tried so far). Everything seems to work EXCEPT "On proximity". I start a new scene, create a flat empty terrain, raise the cube above the ground, and add a 1st person camera looking toward the default cube. Then I add proximity to the cube to toggle its visibility when triggered (approached). I set the distance to 20. Then I test (publish), and approach the cube. As soon as I get within the proximity limit, everything freezes. WASD doesn't respond anymore. Mouse look around doesn't respond anymore. Clicking the mouse does nothing. Pressing ENTER does nothing. In one test, I added smoke in the background. The smoke kept animating, but nothing else worked. Esc does cancel the test and return me to the editor, but that's all that works. Every copy I have on every machine behaves exactly the same way. I don't get it. Others report success with this trigger. Am I missing something? Thank you. |
||||
|
Seems like you are hiding camera instead of cube.. I tested it and seems like so.. in Hide/Show action specify node as CUBE and dont use currentNode there. |
||||
|
Sonofagun, Sven, you're right. It works! I had assumed that "current node" meant the node the action was tied to, not the one currently active. I also assumed that "toggle" means turn it off if it's on, and turn it back on if it's off. It doesn't turn back on. But that's Ok. I can still work with this. Thank you!! |
||||
|
wrote: Sonofagun, Sven, you're right. It works! I had assumed that "current node" meant the node the action was tied to, not the one currently active. I also assumed that "toggle" means turn it off if it's on, and turn it back on if it's off. It doesn't turn back on. But that's Ok. I can still work with this. Thank you!! If node is invisible then scripts that are attached to it doesnt execute.. that means if its invisible then it cant set itself visible again if onProximity script is attached to it itself .. there are many ways how to deal with it. |
||||
|
I finally figured that out, too. Thank you again, Sven. I really appreciate your help! |
||||
|
|
){kind=link}