robert.malzan
Forum Replies Created
-
Posts
-
My pleasure! 🙂
Use Change Location. Open Link will attempt to start the Hopper, because the file ends in VRML and Open Link will automatically start the matching app. .txt runs the text editor and .ppt launches the PowerPoint app. But the Hopper is already running, so Open Link will fail.
Let’s assume that you have a server/domain named MyDomain.com and on that server a public folder named xr4ed. Place the other 3 vrml files there. Let’s say they are named vrml2.vrml, vrml3.vrml, and vrml4.vrml.
The nodes which call those links would then call the external link http://MyDomain.com/xr4ed/vrml2.vrml for the second vrml etc.
You could even place a duplicate of vrml1.vrml there so you can create a “round trip” going back to the first location after the third location.
If you did that, you could also publish the link even in this forum (or in a pdf or ppt etc…) as an entry point to the hopper. Just add hopper: to the link. The address of the entry point vrml (first location) would then be published as hopper:http://MyDomain.com/xr4ed/vrml1.vrml – share with your friends (who have a hopper installed)!
You can test it here
Actually, it’s not going to work in the shop. Do you have access to a server where you can store some files for public read access? If so, you can use the Nodes for switching between locations as expected. But in the shop, you would have to know the download URL of the corresponding vrml file locations within the shop. However, these names are hidden and it gets too complex to unravel those hidden references. Uploading the project to the shop would present the user with one link for each vrml file. So you could theoretically jump to any one of those locations directly by clicking on one of those vrml file links.
Instead, upload your project files to some other location and upload only the vrml file which points to the first location into the shop. Of course, in that vrml file you have a link which points to the data on your own (or hosted) server.
I wrote a test program which works fine.
The new release is out! I hope your issues are resolved with it.
Cool 🙂 (I always have to have the last word because that’s how I know that all questions have been answered. there is no way to ‘close’ a thread here…)
Tomorrow we will publish a new release which has a new node type called Open Link
I think this may be what you are looking for.
Actually, the second method should work RunFlowOutput(m_FlowOutput1) …
What are your error messages?
However, why not create a task node with 2 (3, in your example) tasks? At the end you just call “Next Task” and you get almost the same result, except that the second flow is executed 1 frame later.
That’s another useful addition. Thank you 🙂
To me it sounds like we should use a trigger instead of a node.
The only choice I see is that you send me your project to robert.malzan@nuromedia.com. I’ll download it and test it here to see what’s going on.
Looks like a bug to me. I put it on our ToDo List. Thank you for reporting it!
We Nuro and Cellock only recently agreed on how to adress assets in the shop from the outside world. This resulted in a change on what goes into the vrml file. This change is reflected in the new release coming out tomorrow.
When creating a custom publishing target, you need to specify the domain/path where your project (.wbz) will be located (for instance http://localhost/myproject for testing). If XR4ED is your publishing target, everything will be set up properly for the shop (in the new release which will be published tomorrow). In the shop, Neofitos will soon add a link which will directly start the Portal Hopper, so you won’t have to download the vrml file.
We didn’t change anything about the Distance Node, so the problem must lie somewhere else. I see you are setting visibility. There still is an issue with objects which are not visible on startup. Be sure to make them visible in your location and then invisible using the Start Node in the logic editor.
Another thing that may be confusing is the position of the Rig Node. The position is the center of the rig (the space around the user in VR) or the camera position in non-VR. The camera may be behind the avatar looking over its shoulder. I recommend using the Head Node instead of the Rig Node. The Head Node is always the camera position.
