robert.malzan
Forum Replies Created
-
Posts
-
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.
pro tip: place it into the location as visible and make it invisible in the logic editor using the start node
I’m happy this worked out 🙂 we plan to publish the next official release tomorrow
We only recently defined the naming conventions in the shop and so only the most recent file uploads such as the LightSwitch Demo are working. The only way I can think of how to save your Tuesday tests, is to send you a pre-release of the World Builder (which may have other bugs) if you send me an email to robert.malzan@nuromedia.com to request it (I don’t have your email address and you shouldn’t publish it here).
I think the fastest way to get your product integrated is the option to treat it as an external app which the hopper can automatically download, install, and launch.
To do this, you need to
- create an executable installer (setup) file, for instance “inno setup” and
- a vrml file
- upload both the vrml and the exe file to the shop to publish it
The vrml file might look like this,
<?xml version=”1.0″ encoding=”iso-8859-1″?>
<vrml>
<rootDomain>http://vrweb.Harmony4ED.com</rootDomain>
<creatorInfo>
<name>Wojciech</name>
<legalNotice type=”Text”>
Legal notice as text or link
</legalNotice>
<copyright>Harmony4ED 2025</copyright>
</creatorInfo><protocol name=”DOWNLOAD_AND_RUN”>
<downloadUrl>%ROOT%/myinstaller.exe</downloadUrl>
<executeRegistryEntry>HKEY_CLASSES_ROOT\\Harmony4EDAppName\\Shell\\Open\\Command</executeRegistryEntry>
<autoStart>true</autoStart>
</protocol><protocol name=”META_INFO” optional=”true”>
<name>Demo vrml for Wojciech</name>
<description>This downloads and installs a program</description>
</protocol>
</vrml>yes, that really could use improvement. Noted
I just checked. Currently, the themes are still internal (XR4ED and Default) but we intend to open this up eventually.
