Hello,

I'm new to MoI 3D, I've purchased a license last week and everything is working correctly on Window.

However, on Mac OSX (Maverick), nothing happens when I try to launch either v2.5 or v3.0 beta.

The only things that happens is a dialog box asking for connexion permission, after clicked "agreed" nothing happen.

Am I missing something obvious ?

Thanks in advanve for your help.

Cheers,
Guy.

OS X Mavericks (10.9) was released ~ Oct 22, 2013.

Hello Guy.
A Purebasic user I presume! ;)

Curious!
Maybe enter the serial key ? But I am just a window user...

PS My little French site ;)
http://moiscript.weebly.com/

@bemfarmer

Do you mean MoI is not supposed to work on Mavericks ?

@PILOU

Where should I enter the license ? Nothing appears, no dialog box (Except the one asking permission for network access).

there was a thread about Moi and OSX Mavericks a few days ago..

http://moi3d.com/forum/index.php?webtag=MOI&msg=6233.1


the "connection permission" thingy would be from the "gatekeeper" i presume..

https://en.wikipedia.org/wiki/Gatekeeper_%28OS_X%29

Pas mieux!
Not more than the link above!
Must wait the Michael answer!

I don't run Skype. I've already authorized the software (right click Open -> agree).

Actualy, MoI launches, I can see it in the Activity Monitor but without CPU % number, just CPU Time 0.17 / Threads 11. Then after a few seconds (perhaps a douzen) it disappear.

Correction: not the same behavior between v2.52 & v3.0 beta.

v2.52 behaves as explained above.

When v3.0 beta is launched, I can see 2 lines in the Activity Monitor, one Moi line with the bulb icon and one Moi line with the Terminal icon. The one with the bulb terminate a few seconds later while the one with the Terminal icon stays during several minutes, it shows CPU number (like 0.0, 0.1, 2.0, .., 0.0) and the Icon (Bulb) can be seen in the launch bar, but no interface is shown. Then after 2 or 3 minutes, the application terminates and disappear from the Activity Monitor. Never the GUI is shown.

Just to rule out the Gatekeeper mechanism as source of your problems, could you disable it under System Preference -> Security & Privacy and set "Allow applications downloaded from:" to Anywhere and try to run those MOIs again..

@MARCO
Yes I did that already. Same issue.

I would wait for Michael on this one ... I only know this behaviour with cracked versions, so you might just like to check your local time on your mac and make sure it's set right.

Martin Spencer-Ford

Hi Guy, others are able to run MoI ok on Mavericks so it's not just a general problem, there's something that's going wrong on your machine specifically. It's unfortunately hard to narrow such issues down when they are not able to be reproduced over here...

Are you running any low level system utilities like Haxies or virus checkers? If so you might try temporarily disabling those and see if that has any effect.

Is it possible that you have any different from default permissions set on your /tmp folder? If you do then that can cause problems with MoI.


Another thing you can try is to install the latest version of XQuartz from here: http://xquartz.macosforge.org/landing/ then set MoI to use that system installed XQuartz instead of the one that’s bundled along with it.

To change the setting in MoI to use system XQuartz, do that same right-click on the .app and run Wineskin.app thing, then on the dialog again push the “Advanced” button and then on the next dialog go to the Options tab. Then the settings to mess with are the bottom 2 checkboxes on that page - uncheck the "use wrapper's quartz-wm" one and check the "use system Xquartz" and see if that makes any difference.

Thanks,
- Michael

Hi Guy,

> no dialog box (Except the one asking permission for network access).

Re: network access dialog - that's not a dialog box that MoI itself has in it, are you running some kind of low level system utility that's putting that up?

Sometimes those kinds of programs can cause some kinds of interference.

- Michael

@tpwUK
I'm not using a cracked version, I can give to Michael all the informations regarding my purchase if needed.

@Michael
Your tip about permission indirectly gave me the solution.

I should have mentioned I'm running a triple boot on my MacBook Pro. At first I had a shared HFS+ partition, but for some reason, upgrading to Mavericks messed up with my partitions and even with GRUB with only a grub rescue prompt left at the end.. So I had to restore everything but, for some other reasons, I couldn't restore my shared partition in order for it to be seen by Windows.. So I ended up by extending the Windows partition with the place taken by the old shared partition and having a folder I'm sharing with OSX and Linux. This partition is NTFS though (I've installed the Paragon driver in order for OSX to access it).

Anyway, I've downloaded MoI on the NTFS partition and extracted the zip file there then launched the app directly from there. It didn't worked. Then I copied it into the Application folder and launched it from there. It didn't worked either so I reported the issue here.

Now, by simply copying the zip file into my Documents folder on the OSX/HSF+ partition, then extracting it there and launching the app, it works..

I guess by unzipping the archive on to the NTFS partition the permissions of all the files inside the app package were not set correctly.

Sorry for the noise, albeit this may help someone else someday.

Cheers,
Guy

Good to hear it's sorted, sorry if i offended you, that was not my intent.

Martin Spencer-Ford

Hi Guy, I'm glad that you're up and running now!


> Now, by simply copying the zip file into my Documents folder on the OSX/HSF+ partition,
> then extracting it there and launching the app, it works..
>
> I guess by unzipping the archive on to the NTFS partition the permissions of all the files
> inside the app package were not set correctly.

Yeah that seems likely. I guess that the structure of how permissions work is different enough between NTFS and the native OSX file system that the permissions did not come through, and that can cause all sorts of problems.


> Sorry for the noise, albeit this may help someone else someday.

No problem, and thanks for posting the solution you found, that gives me another thing to ask about if someone else runs into this problem in the future.

- Michael