DAZ over RDP

Hurdy3D

Hey,

 

I'm not sure if I shoud make a bug report or a feature request.

I want to use DAZ over RDP, because I have a Mac with big display display with an ATI GPU and a small laptop with a fast nvidia GPU.

The ideal solution would be to use DAZ over RDP.

But the Cube View Control and the sliders are hardly to use over RDP with the mouse.

This was discuess here: https://www.daz3d.com/forums/discussion/163911/daz-over-remote-desktop

The same issue occures when start DAZ in a Parallels Deskop Windows VM on MacOS.

An other strange thing is that we have to start DAZ with the parameter -allowRemote and still get an error message (but it starts at least).

It would be great if you could change the control behavoir that it will work over RDP and virtualisation and fix the -allowRemote bug.

Using VNC is not an option for me, because RDP allows an higher resultion as an the laptop.

Do you consider to fix this?

Totte

Hello,

I've been running Studio over Apple Screen Sharing (over at not that fast internet connection from the cottage to my machines at home), setting up renders, and all I can say, DAZ Studio doesn't really work well in that setup. But, I've also tried to run Vue and Modo, and compared to them, DAZ Studio works very well. Main issue with Studio is "mouse pointer goes AWOL" and "anything slider" you lose slider control focus while moving the mouse. 

I don't think this is a Studio issue, but rather an issue running programs with a migh level of mouse interactions and video feedback using a remote desktop model.
I haven't tried to run it using Microsoft RDP though, so I can't say if it's better or worse than running Apples Screen Sharing, but I've seen so many broken remote solutions, some where the mouse cursor disappears when you use a text editor (that was in Cisco WebX btw), so compared to that DAZ Studio run well remote using Apple Screen Sharing anyway.

 
 

Richard Haseltine

stger said:

An other strange thing is that we have to start DAZ with the parameter -allowRemote and still get an error message (but it starts at least).

This is the expected behaviour, it is discussed in the Change Log here http://docs.daz3d.com/doku.php/public/software/dazstudio/4/change_log_4_9_3_166#4_9_3_41

Added an -allowRemote command line switch to override the immediate application exit following the OpenGL critical message when launched via remote desktop software; the OpenGL minimum version critical message is still displayed; this switch is useful for scenarios where the machine upon which the application is launched is known to meet or exceed the minimum OpenGL version requirement (i.e., 1.3), but the remote desktop software does not provide adequate support; this switch should be used with appropriate caution

Hurdy3D

Ok, I understand know that OpenGL with RDP is only „simulated“, which cause the error.

However, you didn‘t answer if you consider fixing the mouse control of DAZ via RDP oder a virual machine?

Totte

stger said:

Ok, I understand know that OpenGL with RDP is only „simulated“, which cause the error.

However, you didn‘t answer if you consider fixing the mouse control of DAZ via RDP oder a virual machine?

I think that is a problem running remote, as for me DAZ Studios mouse control remote is bad, but still better than any of the other 3D programs I've tried to run that way.

StealthWorks

Have you tried Splashtop Personal as an alternative?

https://www.splashtop.com/

What you will find as well is that using RDP you can't access your NVidia graphics cards CUDA cores so fast rendering with iRay isn't possible. However, using Splashtop seems to solve this issue.

Hope that helps

Hurdy3D

StealthWorks said:

Have you tried Splashtop Personal as an alternative?

https://www.splashtop.com/

What you will find as well is that using RDP you can't access your NVidia graphics cards CUDA cores so fast rendering with iRay isn't possible. However, using Splashtop seems to solve this issue.

Hope that helps

Hi StealWorks,

 

I tried out slasptop before, but it didn‘t increase the resolution of my windows Latop to match with my Mac. So its the same as VNC 

But I bookmared https://jumpdesktop.com/
They currently do not have the feature of switching the resolution (like RDP), but they are working on this feature.

 

Q: Why can't I automatically set the remote resolution to match my local monitor / device like RDP?

A: At the moment Fluid works by matching the remote machine's resolution. You can manually switch the remote computer's resolution by going into the remote computer's Display properties. In the near future, we'll add support for automatically switching the remote resolution however, there is a fundamental difference between how RDP and Fluid work: Fluid is more like VNC: it is limited to the resolutions your remote computer and monitor supports (RDP doesn't have this limitation). For example if your local computer is running at 2560x1536, but your remote computer can't support more than 1920x1080 then you won't be able to switch to 2560x1536. That said - we're working on this. In our private tests we've connected to Windows 10 machines at full Retina resolution (2880x1800) by adding a custom resolution to the graphics adapter and guess what - it looks beautiful and performs quite well! More on this as we make further progress.

Source: https://support.jumpdesktop.com/hc/en-us/articles/216423983-General-Fluid-Remote-Desktop

Takeo.Kensei

I think the real problem is that there is no adequate HW Graphic acceleration with RDP or most Virtualization system unless you have some pro hardware (quadro, tesla and may be firepro)

With consumer HW, there is no way for virtualmachines that I know of.

RDP may have a solution but I never tried it, that is to get the console session which has access to the GPU

see https://social.technet.microsoft.com/Forums/windowsserver/en-US/c8295ef8-3711-4576-9293-2c4965280165/opengl-and-remote-desktop?forum=winserverTS

 

I personnaly don't see a bug and a feature request should be addressed to Microsoft/Nvidia (standard rdp session / virtualmachine  doesn't meet DAZ required OpenGL minimum)