Closed JustinAiken closed 7 years ago
@JustinAiken Why you ewer installed x64 bit version at all? go with mono 32 bit and it should work, yes?
try adding --arch=32
to mono command inside toolkit's launch script or I can do it later for you..
Why you ewer installed x64 bit version at all? go with mono 32 bit and it should work, yes?
Mac mono installers don't come in x32 or x64 flavors, it's just one universal installer
try adding
--arch=32
to mono command inside toolkit's launch script
That works!
Changing the last line in RocksmithCustomSongToolkit
from
${MONO_BIN} --optimize=sse2,simd,loop,inline "$ASSEMBLY"
# to
${MONO_BIN} --arch=32 --optimize=sse2,simd,loop,inline "$ASSEMBLY"
Makes it work with the newer 5.2 mono :)
@JustinAiken yeah, should publish fix later
Have you ever successfully made a wine install for the toolkit? Or windows build in parallels? Just curious because it's really the only option to have 100% functional toolkit on mac (I've tried native version with older mono on my VM and it sucks hardly :D )
Have you ever successfully made a wine install for the toolkit?
Nope... I know little of wine except for brew install wine winetricks
and some stuff works
Or windows build in parallels?
Too much of a hassle - always makes my laptop fans go crazy, and always have to deal with the windows VM expiring.
really the only option to have 100% functional toolkit on mac
Fortunately for me, I just need the plain CLI tools for most toolkit things (I don't create CDLC myself, just convert/massage) :)
Well, is mono now always go with llvm support etc? I just dig around some runtime flags and I'd like to know if it's any better or not >__> gotta test toolkit's new feachures and push a commit ;)
Tried updating mono to 5.2... whereas 5.0.1 worked, 5.2.x seems to explode: