robert.malzan
Forum Replies Created
-
Posts
-
a) to debug the Portal Hopper, you can either locate the player.log file which contains all the debug info of the last Hopper run. It is located at
C:\Users\<your user name>\AppData\LocalLow\Nuro\Portal Hopperb) I can’t send any working examples because we signed NDAs preventing that, but maybe we can compromise. You could send me an endpoint of your API and a json file with the values to send to the API and I can create a working example for you. It doesn’t even have to be the authentication. Any other endpoint would be OK. I would receive a “NOT AUTHORIZED” return error, which is a vaild response as well.
Or you could send the info to me via email to keep it hidden from the public eye to protect your company secrets.c) You may want to have a look at our implementation of the WebRequest node here This zip File contains all the nodes used by the World Builder/Portal Hopper. You may also want to have a look at the Json Node.
I am not surprised that async function calls don’t work. But I see no reason why the WebRequest Node shouldn’t do what you want. We use the node in several other projects without any trouble.
I have quite some experience with web requests, so perhaps you’ll give me a chance and send me the authentication data (REST API link, json file with parameters filled out) and I’ll try to get the WebRequest node working for you. Deal? 😉
Thank you. I added it to our ToDo list
Thank you for your patience! We hope to get our product out of beta stage eventually, but until then we rely on your endurance.
I tested this and found that sometimes the export buttons disappear beyond the bottom edge, depending on the number of locations and proportions of the entire window. But I could always make them reappear by resizing the window horizontally. You wrote this is not the case for you, but try this: make the entire window small so that everything resizes to a mini window. Then only resize one direction (usually horizontally, but try both directions please) until the buttons reappear.
I look forward to it 🙂
The github repo has resisted my attempts to update it. Instead of an error list, please send me your email address (remind me that you want the toolkits) so I can send you the current Toolkits. Write to robert.malzan@nuromedia.com
You are right, these documents have not been completed and published yet. But you can contact me directly any time or maybe work with some of the other XR4ED users like f.i. gunnlauguregilsson@gmail.com (if he is willing) to get you started.
But perhaps you don’t even need those toolkits, depending on what you are planning. If you are developing a standalone Unity project, you don’t really need them. The toolkits are for designers (game artists) who want to use some of the useful scripts in the Designer Toolkit or the Developer Toolkit if you want to create a world which can be run by the Portal Hopper.
If you like, you can tell me more about your plans and I can help you find out which approach is best for you. You can also email me: robert.malzan@nuromedia.com
Please add this package to your project: com.unity.xr.hands
Yes, I would define the bubbles as trigger boxes and respond to the trigger enter or exit signals. Then use the SkyBox Video Node to switch between different videos, depending on which bubble you are leaving/entering. Mixing 360° videos and 360° images is a bit more difficult, because the images are displayed by projecting them onto a sphere while the videos are fed to the skybox. You will have to do some hide/show instructions to get the desired result.
That’s great news! Keep going 🙂
The skybox bug should be fixed. But we also have a dynamic “skybox” feature for 360° panoramic images. You can load the panoramic image as texture and drop it onto a sphere (we now have a sphere as a standard 3D model). Or dynamicallly assign the texture through the Set Material Properties Node:
Just swap the Base Map.
Now you can also have a 360° video as a skybox:
This graph plays a monoscopic 360° video in the skybox. It displays a countdown and changes location once the video has finished playing.
The Delay Node makes sure that the graph doesn’t immediately go to the next location because the player needs a moment to have a “playing” status, so we check that status after 5 seconds for the first time.
Works here. Did you click on the locations to select them?
Only the first one to avoid confusion which VRML link should be clicked on. But you must do this manually. If you use the XR4ED plugin to publish, then the links will be all wrong. You use the custom publishing with the root domain you are using. Then upload only the first VRML file and a picture and descriptions.
Not even on our list – sorry!
