FIX: OS-X Sierra/High-Sierra: "VM_CREATE on UI failed"

Added by PapaExpert over 1 year ago

HowTo Fix some bugs in ET:Legacy for mac:

because everything seems to work perfect until you see this error on screen when connecting to a server:

Error
VM_Create on UI failed
See "/Users/**yourpath**/Library/Appliation Support/etlegacy/**/crashlog.txt" for details.

in the crashlog, at the bottom, you will find:

ERROR: Couldn’t load an official pak file; verify your installation and make sure it has been updated to the latest version.

Why is that?

New permissions inside the OS-X make it hard for ET:Legacy to create new folders into the game directory...

SO, CREATE THESE PATHS AND YOU’LL BE OK TO PLAY:

Location:

/Applications/ET Legacy/

New Folders *(create the folders you need):

/Applications/ET Legacy/etf
/Applications/ET Legacy/etpro
/Applications/ET Legacy/etpub
/Applications/ET Legacy/ETrun
/Applications/ET Legacy/infected
/Applications/ET Legacy/jaymod
/Applications/ET Legacy/nitmod
/Applications/ET Legacy/nq
/Applications/ET Legacy/silent
/Applications/ET Legacy/tcetest

and so on... each time you visit a server that has new mods, you need to create the path requested in this directory, even if it is auto-created in the other place

The Other Place is:

/Users/**yourpath**/Library/Application Support/etlegacy/

Yeap... ET:Legacy is poorly supported for Mac Users, so we need to fix it ourselves!


Replies (6)

RE: FIX: OS-X Sierra/High-Sierra: "VM_CREATE on UI failed" - Added by Jacker over 1 year ago

This is not actually correct. Its just due to way the OSX handles security on downloaded files. The binary does not have rights to create folders or access folders it should. Now this could be fixed with a signed installer, the old installer is not signed due to me not having a OSX developer license.

RE: FIX: OS-X Sierra/High-Sierra: "VM_CREATE on UI failed" - Added by PapaExpert over 1 year ago

Jacker wrote:

This is not actually correct. Its just due to way the OSX handles security on downloaded files. The binary does not have rights to create folders or access folders it should. Now this could be fixed with a signed installer, the old installer is not signed due to me not having a OSX developer license.

the "reason" may be different, but this fix works... no?

RE: FIX: OS-X Sierra/High-Sierra: "VM_CREATE on UI failed" - Added by PapaExpert over 1 year ago

i found another way to torture it as a fix...

when the situation occurs and you quit ET:legacy, just see which mod bugged, go to the proper directory

/Users/**yourpath**/Library/Appliation Support/etlegacy/**/

make an alias of that folder and put it in the /Applications/ET Legacy/ folder, erase the end of the folder name so there is no " alias"...

then delete the proper directory

/Users/**yourpath**/Library/Appliation Support/etlegacy/**/

so the mod will install properly and completely when you relog to a server using that mod...

yeah, it’s twisted, but work better than the first fix

RE: FIX: OS-X Sierra/High-Sierra: "VM_CREATE on UI failed" - Added by Jacker over 1 year ago

PapaExpert wrote:

Jacker wrote:

This is not actually correct. Its just due to way the OSX handles security on downloaded files. The binary does not have rights to create folders or access folders it should. Now this could be fixed with a signed installer, the old installer is not signed due to me not having a OSX developer license.

the "reason" may be different, but this fix works... no?

It may work but easier would just be to remove the security constraint on the installer and then run the installation

RE: FIX: OS-X Sierra/High-Sierra: "VM_CREATE on UI failed" - Added by justin798 over 1 year ago

how can we remove security restraints?

RE: FIX: OS-X Sierra/High-Sierra: "VM_CREATE on UI failed" - Added by justin798 8 months ago

Jacker wrote:

PapaExpert wrote:

Jacker wrote:

This is not actually correct. Its just due to way the OSX handles security on downloaded files. The binary does not have rights to create folders or access folders it should. Now this could be fixed with a signed installer, the old installer is not signed due to me not having a OSX developer license.

the "reason" may be different, but this fix works... no?

It may work but easier would just be to remove the security constraint on the installer and then run the installation

Hey Jacker, how do you remove the security restraints on the installer?

(1-6/6)