Which Unity version should be used

Unity3D
#1

Hello, It seems that things are not clear regarding Unity’s versions should be used.

–> What unity version did you use to create your demos (zspace experience, aquarium …) ?

I’m developing content for z200 driven by Win7, and potentially win10 and z300 (win10).

–> What unity version do you recommend ? will U3D 2017 work for zspace 200 as well ?

Tests made with Unity 5.3 / zCore 4.0 work using the same parameters as in the demos : ( -enable-stereoscopic3d -force-opengl -screen-width 1920 -screen-height 1080 -screen-fullscreen 0 -popupwindow -always-windowed) , albeit there are resolution issues depending on the machine the resulting .exe is installed. Also it seems impossible to get rid of the initial resolution panel (unlike your demos, starting right away - How do you do that ?)

I wasn’t able to get something to work with Unity 5.6 + zcore 5.0. Per this link (https://support.zspace.com/hc/en-us/articles/204780865-Unity-Plugin-Releases) " NOTE: Unity 5.4 has removed the OpenGL 2.1 pipeline, and the zSpace Unity Plugin has uncovered a bug in the OpenGL 4.5 pipeline, so it does not work with Unity 5.4. We are working with Unity to resolve the issue, but for now, the zSpace Unity Plugin does not work with Unity 5.4 and above" – Is it still true ? Does that mean only Unity <= 5.3 + zCore 4.0 and unity 2017 + zcore 5.0 are supported now ? But I tested the 2017 version as well and only got crashes (access violation) Is it supposed to run with Win 7 / zspace 200 too ? ( I know that d3d11 isn’t available, I’m forcing opengl)

Thanks for your feedbacks

#2

Our Aquarium and Experience demos were built by the older 4.0 plugin

We recommend going straight to 5.0 for new projects. I’m unaware of any problem running Unity apps using zCore 5.0 that is unique to a 200.

In regards to skipping the resolution dialog, Player Settings --> Resolution and Presentation --> Display Resolution Dialog

Yes, zCore4.0 supports <= Unity5.3 and zCore5.0 supports >= Unity5.4

Regarding the “access violation”. It could be a number of things.

One thing to double-check is whether you’re using the new exe args " -vrmode stereo -force-glcore "? These replace the prior " -enable-stereoscopic3d -force-opengl " args from 4.0 when targeting OpenGL.

A second thing to check would just to be sure that OpenGLCore is the specified graphics API and not ES 2 or 3.

Third, destroy and recreate the camera object. Project upgrades from older versions of Unity3D introduce issues with the camera that frequently break zSpace app builds.