Suggestions to the unity 32 -> 64 bit guide

[M0REKZ]

Hi, Nice improving for my guide, however there are some things i would like to add/change:

• Change the Frameworks folder copy to directly copying the Mono dylibs, because sometimes unityplayer would look for libraries that noob people put here, and if you copy the frameworks folder you may delete these.

• Sometimes you wouldnt find mac unity editor packages, but also sometimes Linux and windows ones includes a mac unity player, i dont know on what cases, but i remember one time taking one from a linux installer.

• When you try to debug the app, sometimes will epic launch steam drm (reseting the app) and you cant see terminal output, so is better so use the -logfile flag

Thanks for reading :D

EDIT: Added later:

• Make people better to check if the unityplayer that is being used for updating is the right version, i remember on the past downloading something like unity 4.x.x or 3.x.x and it coming with a 20xx.x.x incompatible player for a unknown reason, just in case 👍

• Check the third party libraries for the case they are 32bits only, with the file command #2

[boggydigital]

All great suggestions! I'll incorporate soon

[boggydigital]

@M0REKZ please check out 4e76a07 - I believe I've addressed the feedback

[M0REKZ]

Yay, now is better, thanks

But i realized i epic forgot something, sorry lol

• Make the people better to check if the unityplayer that is being used for updating is the right version, i remember on the past downloading something like unity 4.x.x or 3.x.x and it coming with a 2019 incompatible player for a unknown reason, just in case 👍

• Check the third party libraries for the case they are 32bits only with the file command

Thats all, ill close the issue after this, Thanks

[boggydigital]

Fascinating, didn't know that could happen - how one would go to check whether downloaded player is the right version? I've no idea and always assumed there is 1:1 match.

[M0REKZ]

Fascinating, didn't know that could happen - how one would go to check whether downloaded player is the right version? I've no idea and always assumed there is 1:1 match.

Yeah, its possible, but anyways it looks like they fixed it (im not sure, but just in case) the more "normal way" to recognize it would be finding arm64 players on a unity 4.x.x package and a source folder with a xcode project, the other way i use too to verify this (but at this point it may be unnecessary) is open UnityPlayer bin (or Unityplayer.dylib) with textedit and look for the version with command + F :P (yeah, textedit lol, maybe there is a better way for terminal guys)

[boggydigital]

That makes sense - please check out b29de7e where I've outlined this process

[M0REKZ]

If you're getting multiple lines with that version - it's likely that you've got a wrong version and need to re-download the correct one: see Determine Unity version and Download Unity.

what, im confused, wouldn't it be something like that?:

if you find lines saying the exact same version you put on command, you downloaded the right one

[boggydigital]

Great catch - that's what I get for rushing changes on the go, should be "If you're NOT getting multiple lines with that version - it's likely that you've got a wrong version". I rework to a better phrase later tonight!

[boggydigital]

I like the todo list format! Here is the Unity player version check: cb6cccd. Let me convert libraries into a separate issue as that seems like a larger topic that needs to be researched more