Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

troubles on unity 5.3 (OSX) #17

Closed
MartinHN opened this issue Dec 29, 2015 · 21 comments
Closed

troubles on unity 5.3 (OSX) #17

MartinHN opened this issue Dec 29, 2015 · 21 comments

Comments

@MartinHN
Copy link

Hi,
I can't make work syphon on unity 5.3
its due either to the 5.3 updates on OpenGL 4.x core,
or my macbookpro with the good old intelHD3000 and apple's poor GL support.(unity runs with openGL3.3 and I'm not sure to support it fully)

in case somebody else have this : the only workaround for now is to run unity with -force-opengl

[Edit] :
my bad it comes from syphon framework ,
this fork claim to fix that : https://github.com/eromanc/Syphon-Framework

@bombarie
Copy link

The problem lies in the new OpenGL4.1 that Unity 5.3 comes with. You can revert to an older OpenGL version in Unity 5.3 by going to

Edit > Project Settings > Player > Other Settings

There you will see the 'Graphics APIs for < your platform here >'. If you deselect the checkbox you can reorder the graphics options. What helped me was to drag OpenGL2 to the top. After that the Syphon package (version a17) worked again.

Hope this helps.

@MatteoFantasy
Copy link

Hi,
Using the legacy OpenGL does fix Syphon but creates other bugs, in my case the standalone player crashes when I have multple displays (which is needed for my videomapping installations).
It would be great to update the lib for OpenGL 4.1 soon...or is it related to the Syphon framework itself ?
Thanks !

@bangnoise
Copy link
Member

The Syphon framework requires updates for 4.1 GL. They are planned, hopefully soon.

@leolodreamland
Copy link

hopefully soon, please?

@bombarie
Copy link

@MatteoFantasy did you try exporting as 32-bit (x86)? This prevented a multi-monitor crash on my end (OSX 10.10)

@MatteoFantasy
Copy link

@bombarie Building in 32 bits indeed prevents the mulit-monitor crash but the Syphon plugin doesn't work (no syphon server created). If I remember correctly Syphon is 64 bits only, and the logs seem to confirm this :

Couldn't open /(...)/Plugins/SyphonUnityPlugin.bundle/Contents/MacOS/SyphonUnityPlugin,
error: dlopen(/(...)/Plugins/SyphonUnityPlugin.bundle/Contents/MacOS/SyphonUnityPlugin, 2):
no suitable image found.  Did find:
/(...)/Plugins/SyphonUnityPlugin.bundle/Contents/MacOS/SyphonUnityPlugin:
mach-o, but wrong architecture

@bombarie
Copy link

@MatteoFantasy That's strange because making a 32-bit build actually worked for me. To be clear: either the SyphonServerTexture script or custom resolution script worked for me, I made the player use OpenGL2.1 (Project Settings > Other Settings > Graphics API for Mac > OpenGL2) and then exported as 32-bit application. Syphon was outputting images just fine.
I just re-tested this succesfully but I don't have a multi-monitor setup with me right now, and my current system is OSX 10.9.5, not the OSX 10.10 I mentioned yesterday. I do remember preventing a startup crash along the line by first disconnecting some monitors, starting the app, then reconnecting the
monitors. I forgot which combination of settings I used then, sorry to say, but I hope this helps you in any way.

@leolodreamland
Copy link

i don't build, so this isn't an option for me - i am going back to 5.2 for
the time being.

On Thu, Feb 25, 2016 at 11:18 AM Adriaan Wormgoor notifications@github.com
wrote:

That's strange because making a 32-bit build actually worked for me. To be
clear: either the SyphonServerTexture script or custom resolution script
worked, I made the player use OpenGL2.1 (Project Settings > Other Settings

Graphics API for Mac > OpenGL2) and then exported as 32-bit application.
Syphon was outputting images just fine.
I just re-tested this but I don't have a multi-monitor setup with me right
now. I did however prevent a startup crash along the line by first
disconnecting some monitors, starting the app, then reconnecting the
monitors. I forgot which combination of settings I used back then, sorry to
say.
Hope some of this helps.


Adriaan Wormgoor | creative technology
adriaan@adriaanwormgoor.nl | www.adriaanwormgoor.nl
mobile: +31 (0)6 2864 8466

Get in touch for:
interaction design
interactive installations (Arduino, Processing, openFrameworks)
mobile & web development (Android, Flash, HTML5)

On Thu, Feb 25, 2016 at 10:41 AM, MatteoFantasy notifications@github.com
wrote:

@bombarie https://github.com/bombarie Building in 32 bits indeed
prevents the mulit-monitor crash but the Syphon plugin doesn't work (no
syphon server created). If I remember correctly Syphon is 64 bits only,
and
the logs seem to confirm this :

Couldn't open
/(...)/Plugins/SyphonUnityPlugin.bundle/Contents/MacOS/SyphonUnityPlugin,
error:
dlopen(/(...)/Plugins/SyphonUnityPlugin.bundle/Contents/MacOS/SyphonUnityPlugin,
2): no suitable image found. Did find:

/(...)/Plugins/SyphonUnityPlugin.bundle/Contents/MacOS/SyphonUnityPlugin:
mach-o, but wrong architecture


Reply to this email directly or view it on GitHub
#17 (comment).


Reply to this email directly or view it on GitHub
#17 (comment).

@bombarie
Copy link

@leolodreamland Oh, I was actually only having problems with the builds, not from within Unity. If you set your Player Settings OpenGL to 'OpenGL2' (OpenGL 2.1) then the Syphon plugin doesn't scramble the output. I had a 3-monitor setup working just fine that way. My setup was 1 monitor being Unity and MadMapper and using two attached video projectors to map the output onto. This was on OSX 10.10.
Have you tried OpenGL2?

@lm-n
Copy link

lm-n commented Mar 14, 2016

@bombarie thanks for the advice 💃 OpenGL2 is super helpful!

@initi
Copy link

initi commented Mar 19, 2016

Hello,
any update of Syphon for Unity5.3.3 please? Its still crashing in build and switch to OpenGL 2.1 does not have a sense. Thank you in advance!

@vade
Copy link
Member

vade commented Mar 19, 2016

No Update to syphon. You'll know.

@leolodreamland
Copy link

i'm happy with 5.2 for now. i haven't seen a killer use for the new stuff. yet. btw isn't 5.4 out soon?

@Harvey3141
Copy link

If you really need Syphon in 5.3, you could try this

https://github.com/keijiro/Funnel

@benkuper
Copy link

As a workaround, and until syphon is updated or funnel implement client support,
i managed to get Syphon work in Unity 5.3 by launching it with -force-opengl from the terminal. It forces the use of GL 2.1 (and disables some of the new features inevitably).

UPDATE : the -force-opengl argument only works in editor, not in standalone mode.
you can actually choose to not use GLCore or Metal in the player settings ("mac auto settings")
The editor will also force itself to use GL2.
For me, this works well in editor, but in standalone i had to export from Pro version and disable the unity splash screen.

@leolodreamland
Copy link

Why use 5.3 then? 5.2 is fine for me for now...
On Wed, 30 Mar 2016 at 08:59, Ben Kuper notifications@github.com wrote:

As a workaround, and until syphon is updated or funnel implement client
support,
i managed to get Syphon work in Unity 5.3 by launching it with
-force-opengl from the terminal. It forces the use of GL 2.1 (and disables
some of the new features inevitably).


You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
#17 (comment)

@rsodre
Copy link

rsodre commented Mar 30, 2016

You can select which version of OpenGL the app will support on the Player Settings.

@leolodreamland
Copy link

ok, so 5.5 removed legacy opengl support. no update nearly 18 months later?

@vade
Copy link
Member

vade commented Mar 28, 2017

You can get your money back with proof of purchase. ;)

@leolodreamland
Copy link

leolodreamland commented Mar 28, 2017 via email

@vade
Copy link
Member

vade commented Mar 28, 2017

You didn't sign up for that promo, or enter a valid redemption code. So no.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests