Ways to Access OTOY AMI

[vamsigudipati]

Hello support,

I am trying out different ways to connect to the OTOY AMI. So far I am able to figure out two ways to connect to the VM:
1. http://aws.otoy.com/?connect=//<ip>:809 ... GUID=<guid>

This is using a web browser where the user is not allowed to install any 3rd party software.

2. Using RDP with OTOY AMI IP address.

This allows installing 3rd party software but the GPU is not utilized while running graphic applications.


With first way I see that GPU is been utilized but the graphics are sometimes blurred. I am trying to find if there is a way to balance between the image quality and the bandwidth. Also is there a way to show the frame rate on the graphics window like NICE DCV?

I am basically evaluating this product for our CFD application.

Thanks,
Vamsi

[Icer5k]

You're correct in how you're using the AMI and the different access methods - RDP currently doesn't utilize the GPU at all.

The biggest difference I've seen is using the latest version of Firefox to access the AMI. We're working on the performance in Chrome, and everything should be on-par soon, but for right now FF is the way to go.

Aside from that, you can play around with a lot of parameters that affect the stream - see http://aws.otoy.com/docs/OTOYClientAPI.pdf for a full list. Specifically, MAXFPS and MINQ/MAXQ would be good places to start. I'd also recommend setting "PROFILE=wan" and seeing if that helps.

You can view some debug info if you click the blue i symbol on the top-left of the page.

[maepopaxe]

Hello,

i just started experimenting with the otoy ami. Just to start... i am totally new to cloud graphics and the aws and stuff, but i did quiet the same experience.
I work on a Lenovo i7 3840QM a Quadro K2000M , 32GB RAM, Win 8.1 and a 24Mbit Connection in Berlin Germany

In FF i get
heavy graphic atifacts and connection loss or crash after a minute. Picture quality is bad... weak colors and blurry.

Chrome is more stable but picture quality is weak and also full of artifacts.

Just a few questions...
Is this a bottleneck in my system settings or do we have to deal with it, because this is just the state of development yet? If so, until now it seems not to be usable in everydays work i guess.

Will there be a possibility to connect to otoy's AMI and use the GPU via RDP, because the performance seems to be better so far?

Do i need to migrate the license from desktop to remote and vice versa or buy more licenses when i work on desktop and via RDP? because it takes 45min to an hour to migrate. Is there another solution?

Thanks for answering... and cheers. Octane's just great.

[Icer5k]

I don't think you'll ever be able to use ORBX via RDP, but I think our native client may help alleviate some of your issues. When accessing ORBX, try switching "http://aws.otoy.com" with "http://cloud.otoy.com" and leaving everything else in the URL the same.

Also, please see my answer on the other thread regarding Octane and licensing. We currently view an AMI instance as a different computer than your local desktop, and as such all licensing restrictions will apply.

[vamsigudipati]

Thank you support for answering my above question. You have mentioned about setting the parameters in your solution. How do I set the parameter? Could you please elaborate on that?

Warm regards,
Vamsi

[Icer5k]

Parameters are set in the URL. For example:

Code: Select all

http://aws.otoy.com/?connect=//1.2.3.4:8090/?NOCRYPTO=1;STATUS=1;AUTOLOCK=0;WAN=12;GUID=a-b-c-d

That URL contains 5 parameters: NOCRYPTO, STATUS, AUTOLOCK, WAN and GUID. Parameters can be added/removed from the URL by the user, and are separated by semicolons (;). A parameter consists of a name and a value separated by an equal sign (=). For example, using the above URL the WAN parameter name has a value of 12, and the NOCRYPTO name has a value of 1.

[rafamg]

I don't think you'll ever be able to use ORBX via RDP, but I think our native client may help alleviate some of your issues. When accessing ORBX, try switching "http://aws.otoy.com" with "http://cloud.otoy.com" and leaving everything else in the URL the same.

Also, please see my answer on the other thread regarding Octane and licensing. We currently view an AMI instance as a different computer than your local desktop, and as such all licensing restrictions will apply.

Hello Icer5k, I wonder how can I get test-drive the native client you mentioned, we find a very useful the option to have OTOY available on AWS so we want to understand all the capacity we can get out the cloud 3D effort you guys already have there.

Thanks in advance!