Which Unity version should be used

0 votes
asked Feb 26 by gdl (20 points)

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

1 Answer

+1 vote
answered Feb 26 by AlexShorey (200 points)

Hi glb,

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

We highly 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

I'm unsure about the "access violation". It could be a lot of things. Do you have an output_log you can share? Just a shot in the dark, but are you using the new exe args "-vrmode stereo -force-glcore"? These replace the prior "-enable-stereoscopic3d -force-opengl" args from 4.0 when targeting OpenGL. One other thing to check would just to be sure that OpenGLCore is the specified graphics API and not ES 2 or 3.

commented Feb 27 by gdl (20 points)
Hi Alex,
Thanks for your quick response, and for the skipping dialog setting.
I tried both the old and new options and get the same results. I made sure only OpenGL is in the graphic API.
Below is the error.log I get using unity 2017 (3.1.f1) ( got the same issue with unity 5.6).
The machine is Win7, gpu is NVIDIA K2000M .  Regular demos work well.
commented Feb 27 by AlexShorey (200 points)
Thanks for the follow-up information. I took a look at the error log. Unfortunately, this could still be nearly anything. My current thought its that Unity's project upgrade process, transitioning it from Unity <= 5.3 to Unity 2017.x.x may be happening somewhat inelegantly, as is often the case.

Access violation crashes aren't uncommon, so I did some googling to see what the most common solutions end up being and the solution mentioned in this thread seems to pop up the most.
https://answers.unity.com/questions/1412904/access-violation-on-build-but-works-in-editor.html

Another thing to try is removing zCore from the project and replacing the camera with a regular Unity stereo camera so we can rule out other variables.

If the scene is simple enough, rebuilding it from scratch in 2017.x.x might help. Often the camera needs to be deleted and re-added to the scene after a Unity version upgrade. I haven't seen it cause an access violation before, but it's something to try.

If all else fails and we're sure it's the zspace plugin, I'll be happy to take a look at your project if you can share a download link.
commented Feb 27 by gdl (20 points)
Working now - I deleted the main camera and created a new one.  Note that it looks like the .exe doesn't need the options (-vrmode stereo etc...) to run properly
Thanks !
...