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.

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

I tried all sorts of thing. I changed permissions on /tmp directory, I activated and deactivated the firewall and nothing. I'm getting the same error message. Maybe because I also have other Wine applications in my system? I have WinOnX and also some Windows games wrapped as executables around Wine to make them work under OSX.

P.S. I opened Console and read the logs. Seems that WineskinX11 is crashing. If you need the crash logs I can sendyou.

Hi artisanicview,

> Maybe because I also have other Wine applications in my system?

It's not supposed to be a problem to have this, but maybe there is some kind of bug related to that.


> P.S. I opened Console and read the logs. Seems that
> WineskinX11 is crashing. If you need the crash logs I
> can sendyou.

Yes, can you please e-mail them to me at moi@moi3d.com so I can take a look.


Thanks,
- Michael

Hi everyone. I have been lurking in this forum for sometime now, but this is my first post here.

Let me just say that i like Moi3D a lot! The user interface is logical, very friendly and in some cases genius. Coming from Rhino, i find a lot of things that frustrated me in that program easily accessible and logical in Moi3D, so congratulations Michael.

I use a Mac exclusively so I am really glad that an OSX version has been released. I am also a software developer, although nowhere near Michaels level.

After playing with the OSX version for a couple of days i think i can offer my honest opinion on the state of the current port.

Michael, as a fellow developer i can easily understand the reasons you decided to use WineskinX11 to do the port. But after examining the application folder for a few hours, trying to figure out the internals of the application, this might have been the wrong decision.
As far as i can tell you are using QTWebkit on windows for the user interface and OpenGL for the views. Also a number of other dlls that provide additional functionality. Using WineskinX11, your are going through a huge number of layers in order to actually do something as simple as receive an event.
The sequence is probably: Cocoa -> X11 -> Wine -> Qt -> Webkit -> Your code.
And all this time Webkit is natively available on OSX! I would imagine the process is similar for OpenGL, which is again natively available. Moi3D is really fast now, but i can't imagine how much smoother it would have been if you could use OSX directly. Even if you would prefer to use Qt for the OSX version to simplify the port, the benefits will still be enormous.

I'm sure that using WineskinX11 seems attractive. "Just compile the same code and you are ready to go". But, as you go deeper into trying to make it look native, it will get complicated. A lot. You will have to address issues at the user experience level, and at a lower lever. Things like keeping all data in Applications Support in order to survive updates, custom plugins that require something other than javascript, UI inconsistencies and a number of other issues i can't begin to imagine. Issues that you will eventually blame on WineskinX11 and you will have no control over them. And it will never be as smooth as a native app, even though the math are running at almost the native speed.
Now, unless some of the external libraries you are using are not available for OSX, your time might be better spent doing a native port. This current version is good enough for a first mac version and its fully usable. I am quite happy to use it over wine or the windows version while i wait. But you application is ideally suited for a full port. Even the html/javascript UI looks mac like!

So i would sudject releasing this version as an intermediate version as planned, and at the same time consider doing a full native port. It will definetly save you a lot of time and frustration in the long run.

Well, there goes the only reason I had for keeping a Windows machine around.

Brilliant!

Thanks Michael.

C.

Hi Michael

Had the same thing happen again yesterday, was working on the attached file, last night, after about 1 1/2 hours working with the same file, I was trying to Boolean Union, the Green and Red solid objects, The objects was created by first making the main "bead" then sweeping the edges (rims).



When I Bool-Union the bead and 1 rim, all OK, 1 new solid, when I union the result and the other rim , ended up with the following defect,







Left them has two separate solids, did some other work , went to bed, this morning open the same file, Bool-union worked fine, first thing I tried.
Went back to through some of the incremental saves, where I first noticed the defect and again it worked fine.

Very strange, last night I did not think to restart MoI and see if that made a difference .