Full Version: New Mac OSX public beta Jan-31-2012 available now

Show messages:  1-13  14-33  34-53  54-73  74-93  94-103

Seems like I can turn that off.

I went to System Preferences > Security > Firewall > Advanced and turned on "Block incoming connections" for WineskinX11

MoI starts without problems so it seems to be not required to allow incoming connections.

I guess this message shows up only if the OS X firewall is activated and you start MoI for the first time.
I think I also saw this message with the previous Beta because there was a second WineskinX11 entry in the Firewall settings. Also set to "allow". I blocked both.

---

What is the process to resize the whole window? I'm not able to by clicking and dragging lower-right corner.

---update----
Force quit and then launched again. Works OK now.

---

Almost makes me wish I owned a Mac :-)

---

Michael... You are unbelievable! Moi looks amazing on OSX, It feels like you developed a native OSX app!. Everything is very snappy, viewports are smooth and fast, there are occasional display glitches when e.g. turn on the browser or switch viewports, but that is not even annoying:) I have one of these "27 inch iMacs and MoI rocks:) hehe I am very happy man! Thank you.

---

And the ability to have another MoI window open and copy and pasting between is awsome!!

---

Thanks a lot Michael,

it's working smooth so far!

Best regards
Stefan

---

Hi Paul,

> What is the process to resize the whole window? I'm not able to by
> clicking and dragging lower-right corner.
>
> ---update----
> Force quit and then launched again. Works OK now.

Please let me know if you run into this resizing problem again.

Also right now resizing the window is a little stuttery/glitchy and I'm going to see if I can tune it up a bit.

- Michael

---

Hi olio,

> Michael... You are unbelievable! Moi looks amazing on OSX,
> It feels like you developed a native OSX app!.

I'm glad it is not feeling too out of place for you!

I think having the native file open and save dialogs helps quite a bit.


> Everything is very snappy, viewports are smooth and fast,

Great! Yes, that's one of the best advantages of this porting method - MoI's own program code runs directly and so it runs at full native speed when doing its own calculations.


> there are occasional display glitches when e.g. turn on
> the browser or switch viewports, but that is not even
> annoying:)

Yup, this hiccup happens when a 3D viewport gets resized - I'm going to be looking into it to see if I can fix it up, but at least it's only a cosmetic problem and not something that really gets in the way of actually doing stuff.

- Michael

---

thank you Michael.

spent about 2 hours with it last night, touching up some models I thought I had completed :)

worked fine for the simple stuff I'm doing.

Cheers, Steve

---

Don't work for me.

Wineskin Error.
"ERROR! Launching wineserver failed! No new wineserver PID found!"

I enabled and disabled "Wineskin Winery" in firewall from System settings. I don't know what to do more. Please help.

---

Michael,

I spent some time with this last night. The basic functions seenm to be working well for me. I will try some more complex work later.

Thanks a lot for this...

J. Tucker

---

Hi artisanicview,

> Don't work for me.
>
> Wineskin Error.
> "ERROR! Launching wineserver failed! No new wineserver PID found!"


Do you possibly have some kind of restricted permissions set on your system, especially on your temp folder?

If so then that could cause problems like this - this probably means there was some problem setting things up in /tmp

You also might try doing a system reboot which will clean out your /tmp folder and maybe that will help.

But if you have done some kind of lockdown process on your machine's tmp folder you may need to set that back to its original permissions in order to get MoI to run.

- Michael

---

Thanks Micheal!!

Works great on my mac pro running 10.6.8

---

I rebooted, and no change. I'm getting the same error.

> But if you have done some kind of lockdown process on your machine's tmp folder you may need to set that back to its original permissions in order to get MoI to run.

Please, can you be a little more explicit? I can't find any tmp folder in my system. I have a MacBookAir 13" from 2010 with OSX 10.7.1

---

Hi artisanicview,

> Please, can you be a little more explicit? I can't find any
> tmp folder in my system. I have a MacBookAir 13" from
> 2010 with OSX 10.7.1

There should normally be a directory named /tmp at the root of your filesystem.

Why was it that you set up the firewall initially, were you following some instructions on how to lock down your system? If so, can you point me to those instructions? They might have involved changing some default setting in your filesystem in such a way that MoI won't run on your system after that.

Or are you possibly running any kind of system-wide utility programs like a virus checker or anything else similar to that?

- Michael

---

was looking forward to trying this but i'm getting these errors related to wineskin when i try the Mol v2.5 beta jan-31-2012. i'm using OS10.5.8.

Image Attachments:
error moi.jpg 

---

Hi Ronaldo,

> was looking forward to trying this but i'm getting these
> errors related to wineskin when i try
>
> i'm using OS10.5.8

The MoI OSX version requires OSX version 10.6 (Snow Leopard) or 10.7 (Lion).

It will not run on OS 10.5.x , so that's the problem that you're running into.

This is because Apple's current development tools will only produce programs that work on 10.6 or higher.

- Michael

---

i see, that explains it. another reason to go to snow lion. am looking forward to trying it. will be back. thanks very much.

---

Hi Michael

I had been using the OSX public beta for about 2 hours working with the same file (but I do use incrementalSaves) then all of a sudden and boolean functions like merge and diff, started working very weirdly , shut down MoI loaded up the same file than boolean functions started working correctly .

I've almost finished for tonight, if I get the same problems again, I'll let you know

Cheers, Steve

---

Hi Steve - if the objects that you were working with became open surfaces instead of a closed volume, that will make the booleans behave differently since they're mostly oriented towards working on closed volume objects.

So if you run into this again, look at the object type indicator when your objects are selected - that's in the upper right corner of the properties panel that shows the properties of the current selected objects. If that indicator says "Surface" or "Joined Srf" that means that the object is not a closed volume, it will read "Solid" if it is closed.

Anyway, that's one thing to check on if booleans start to behave differently.

- Michael

---

Show messages:  1-13  14-33  34-53  54-73  74-93  94-103