Topic: Building Client/Server Standalone for Windows

Building Client/Server Standalone for Windows

Dec 18 2008 | 6:55 am

Hi all,
here’s a seemingly simple problem: I’ve got a client/server based playback app, both client & server run fine in patcher mode, but when I build the same patches for windows both will not run simultaneously. It’s as tho only one standalone app is capable of running at a time.

Am I high? Is this a known bug? I’ve never encountered it on OSX. It’s as if windows thinks that the ‘app’ is already open and won’t launch another instance, even tho the client and server are two separate standalone builds.

Love to hear any thoughts on this. Any build settings I need to know about? If it’s not clear I can post the patches.

Thanks!

Jesse

Mar 08 2009 | 1:43 am

I am seeing the same behavior when trying to run standalones built for Windows simultaneously. I would be very interested to hear if anyone at Cycling had any comments on what might cause these conflicts.

We have been testing a multi-application installation and have noticed that the issue extends to the Max Runtime as well – in other words, if I am running the application in question I can’t open the Max Runtime at all (with no open files).

We are at a loss on how to troubleshot this. Is there a system log we should be looking at to gather information that we can post to this forum? The application (and Runtime) quit immediately, with no visible error messages.