Maxwell Render | Official public forum

i am on a iMac with macOS Sierra 10.12

I just installed the new beta 3.2.1.5 and none of the programs studio, render will now start.

i reinstalled the older version and still no start for any of the programs.

anyone else experiencing this? any suggestions?


if i start them thru modo, they will work. i'm at a loss to why they won't start on their own

Just answered a similar question to this via email; perhaps that was you, but if not, see here:

The second change is invisible to users, but limits the damage that can be done by a rogue app. Although unsigned apps will still appear to be stored in the Applications folder, macOS 10.12 actually stores them in a randomized location on your drive. This prevents repackaging attacks, where one app pretends to be another one, because the rogue app won’t be able to access the resources belonging to the real one.

This may break Maxwell applications, due to their method of using shared libraries -- if macos sierra silently moves the .app bundles to some random location, they won't find shared libraries upon which they depend (Qt frameworks, libmx_common.dylib). It is for similar reasons that Maxwell applications have trouble with gatekeeper on el capitan; when you download the application, it is checked, and because the .app bundles it contains link to outside libraries, the applications, though signed, may be quarantined. This has necessitated a complete reorganization of how our applications are built, packaged, and signed on osx; these changes are not minor, and involve moving to a different version of Qt, so they have been completed for our development branch, but cannot be back-ported to the current release branch.

It is for reasons like this that we do not support running beta OS versions.

update:

i got the programs running, not the best and greatest way but if you have work to do, then this will have to do so you can work on macOS Sierra

get in touch with me if you want to know how


previous post


no, that wasn't my email but indeed the same problem.

the licenseactivator app is not being allowed to run

the share NEXTLIMIT/rim_nl folder has the plist and other files but if you right click to get info, the whole folder is empty

to be told to not use an upcoming os that eventually will be the norm on macs, is frankly not what i wanted to hear.

JDHill wrote:Just answered a similar question to this via email; perhaps that was you, but if not, see here:

The second change is invisible to users, but limits the damage that can be done by a rogue app. Although unsigned apps will still appear to be stored in the Applications folder, macOS 10.12 actually stores them in a randomized location on your drive. This prevents repackaging attacks, where one app pretends to be another one, because the rogue app won’t be able to access the resources belonging to the real one.

This may break Maxwell applications, due to their method of using shared libraries -- if macos sierra silently moves the .app bundles to some random location, they won't find shared libraries upon which they depend (Qt frameworks, libmx_common.dylib). It is for similar reasons that Maxwell applications have trouble with gatekeeper on el capitan; when you download the application, it is checked, and because the .app bundles it contains link to outside libraries, the applications, though signed, may be quarantined. This has necessitated a complete reorganization of how our applications are built, packaged, and signed on osx; these changes are not minor, and involve moving to a different version of Qt, so they have been completed for our development branch, but cannot be back-ported to the current release branch.

It is for reasons like this that we do not support running beta OS versions.

paulo wrote:to be told to not use an upcoming os that eventually will be the norm on macs, is frankly not what i wanted to hear.

I can understand that, but this is why we publish system requirements (which don't include OS betas). Apple often enough breaks software in actual releases, let alone betas.

i can understand that from your point of view but being a developer i need to learn and test the new software or else be left behind.

Cheers
Paul

JDHill wrote:

paulo wrote:to be told to not use an upcoming os that eventually will be the norm on macs, is frankly not what i wanted to hear.

I can understand that, but this is why we publish system requirements (which don't include OS betas). Apple often enough breaks software in actual releases, let alone betas.