robert.malzan
Forum Replies Created
-
Posts
-
I’m on it 🙂
This should have worked with a button. I’ll look into it. Thank you for pointing this out! 🙂
About closing the Portal Hopper. We don’t want to close the PH via a Node. There is a close icon in the toolbar at the bottom of the screen which is one way the user can exit the Hopper. But we would prefer if you changed location to f.i. the HUB world (http://experimental.nuromedia.com/HUB.vrml) once your experience/story/task is over. We see the Portal Hopper as an ongoing experience of discovery.
We plan a release Wednesday next week (before the holiday season). I already started working on it. Fingers crossed that it’ll be ready then. If not, I’ll be back on Monday after the long weekend.
I tested the popups and it seems that they disappear when you click on any of the buttons. Maybe you are feeding the popup with an Update Node. this will recreate the Popup all the time. You should use the Start Node to open the popup or some other call which only occurs once (e.g. Trigger without “Always Inform”). Then the popup will go away after you press any of the buttons.
I think I have good news for you. Yes, I saw your message and we discussed this internally. We decided to provide a special Node which will have all the attributes of a webrequest node plus a microphone input which can record, send and stop. Once Record was turned on, the node will accumulate a byte stream from the mic. Then call send to send a web request with this recording as a file. Stop recording using the stop flow input. The node can be used to stream audio by calling send several times (i.e. 10) per second or as a audio file transfer node in teh way you wish to use it: record a command for the AI, stop recording and send.
And we will create an override text input so you can use “Basic” instead of “Bearer”.
Is this what you were looking for?
Unfortunately not. The only workaround I can think of is to restart a timer every time a value change is received and to evaluate it as a release after a timeout has occurred.
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
