Hi Pilou,

> No need video : all functions are freezed : impossible to click on button Cancel etc...
> So some ennoyous! :)

Does it only happen when you're dragging a particular thing? Maybe it's related to history recalculation if you have a long chain of things to update. What happens if you select all your objects and turn off history updating by using Edit > History > "Disable update" button, any freezing after that or not?

- Michael

Pilou....evidently I didn't make that clear :)

I don't want to see a "frozen" screen but I want to see a video showing what you did until Moi's got frozen.
All the steps you did....

I hope this time I made myself clear :)

Ciao!

I just draw a box or a plane , make some extrude edges as the video above
http://moi3d.com/forum/index.php?webtag=MOI&msg=8675.98
goto to forum
return to Moi
= freezing all modeling functions!

If i stay inside Moi no problem!

So for me suspicion of Multi task problem! :)

Nearly all commands I mentioned (ImportObj, Subdiv, SubdivClassic, Nudge and BlendCap) do work, my apologies, I didn't think of the commands being a part of the integrated application folder structure on the Mac, while MoI.ini is stored externally. Now that I've copied the commands to the Commands folder of MoI V4, they work, with the exception of FatLines.

Maybe it'd be more clear if non-present commands would give a "Command not found" message, in stead of an "error in line 1", because that suggests an error in the command in stead of the command not being there.

Regards,

Metin

Hi Metin, thanks for the feedback!

> • Some keyboard shortcuts I had assigned to Command + key have been automatically
> changed to Alt + key, such as Alt + I for ImportObj in my case. But pressing Alt + I didn't
> work. Then I reassigned it to Command + I again, and the shortcut worked. Other Alt + key
> combinations such as Alt + O to open a file do work though.

Yeah I think this is an accidental side effect from how the Wineskin version internally used the Alt key as an alias for Cmd, I'll have to think of what to do about this. To maintain compatibility with V3 I may have to disallow using Alt shortcuts in V4 since V3 can't set Alt shortcuts. I'm not sure about this yet.


> • Pressing the Mac OS system shortcut to toggle full screen mode (Control + Command + F) doesn't work.

Yeah I think several key shortcuts for things like switch between windows are probably missing too, I'll have to make a pass through these.


re: Loft problem - that break apart thing sounds likely related to using "Exact" mode on the Loft, Exact NURBS circles and ellipses tend to behave like that, they are made up of 4 arcs with "corner points" on them. I try to hide this normally by replacing something like a circle or a sphere with a squishy non segmented version if you edit control points. I think it's likely to be the same behavior as V3 but if you can post the 3DM file I can take a look and see for sure.


> • The viewport labels (Front, Perspective, etc.) initially show as blocks:

That's odd but those are just temporary they'll be replaced once I get text drawing in the viewport working.

Thanks! - Michael

Ok. Got it!

Tested and...no! No problem for me at all. All worked fine.
No problem of "Multitasking" or other kinds of issues.

Ciao.

Hi Dinos, thanks for testing it!

> The only thing that i noticed is that the scripts that use moi.ui.createDialog will not return focus to
> the main Moi window after i close the Dialog if Moi is running full screen.

Yeah I think I've seen this also happen after the file dialog is used as well when placing a background image, it's on my bug list.

The moi.ui.createDialog one might be related to MoI doing some stuff to keep the dialogs above the main window, I had to fight with things for a while to make that happen , macOS seems to want to allow dialogs to go underneath a "main window" by default.

- Michael

Hi Mik,

> only detail... changing of Style of grid and accented grid lines doesn't work. Color and Width work normally.
>
> I'm not sure if it's problem only on my computer or it is the general problem.

Dashed and dotted line styles are not implemented quite yet so no matter what you set them to you'll only get solid lines for right now. They will be coming back though.

- Michael

Hi Michael,

You're very welcome. Thank you for making the V4 beta publicly available.

I'd welcome having Alt as a keyboard shortcut option, because a lot of commands share the same first letter (Rotate, Revolve, RailRevolve, etc.), but it's not important.

Regarding the Loft issue: you might be right. I'll do some more tests.

The blocks in stead of viewport labels might be due to my slightly dated NVidia card. I've got the last iMac model that had an NVidia graphics card, before Apple completely switched to AMD graphics cards.

As an extra bit of information: I'm using the latest NVidia Web drivers for my NVidia GeForce GTX 780M.

Good luck with everything!

Hi Metin,

> Maybe it'd be more clear if non-present commands would give a "Command not found" message,
> in stead of an "error in line 1", because that suggests an error in the command in stead of the
> command not being there.

The tricky part about this is that in addition to command names you can also put script code directly in a keyboard shortcut. When you get "error in line 1", it's because when it saw that the text in there didn't match an available command name it tries to execute it as literal script code to try and get it to do something.

- Michael

Hi Metin,

> I'd welcome having Alt as a keyboard shortcut option, because a lot of commands share the
> same first letter (Rotate, Revolve, RailRevolve, etc.), but it's not important.

It could be possible that it's an option that you can enable if you don't need to keep things compatible with V3.

But the thing I'm not sure about is if they can be enabled and also maintain compatibility with V3 at the same time.

- Michael

Metin
>> Max's FatLines script returns an error
I'll check all my scripts today evening

Finema
I fixed sBridge, sScale and sSplit scripts yesterday. Not published yet.

to all:
Dear friends, if you noticed any compatibility problems with my scripts, please post your bugreports to this thread:
http://moi3d.com/forum/messages.php?webtag=MOI&msg=6837.1

Hi Max!

@You : "...I'll check all my scripts today evening..."


THIS IS A SUPER GREAT INFO!!!

Moi without your scripts is like a sword without the blade :)

Thanks!

Thank you for the reply.
I've attached an image that shows recent filenames.
Turning hidden lines on fixed the snapping.
I tried setting the nvidia x-server to override application anti-aliasing to no anti-aliasing. It was letting the app configure it by default. Nothing changed regarding the selection. After that I tried on the Noveau driver and selection works. I've also attached the winelogs for both runs(I don't know if that helps).

A bit off-topic: performance on my main rig (new GTX 1080) is way worse than on my laptop (GTX 1050), I'm thinking something else is causing the trouble hardware-wise (motherboard maybe?). Do you have any experience with that? I just ordered another PC for my office and I will start testing with it as soon as it arrives.

Hi daniii, so that screenshot looks really good, everything there looks exactly as it's supposed to right now.

So with the recent filenames showing the native paths (with / separators and not Wine paths which would look like z:\home\dan\Test2.3dm) , that means that MoI is recognizing that it's running under Wine and is translating those paths and so it should be using OpenGL there.

Do you mean everything works ok using Noveau or are there still problems?

re: performance on desktop worse than laptop the only thing that's really coming to mind there is if the particular motherboard slot you've got the card in doesn't have as many lanes on it as another one. There's usually one or two heavily loaded slots and you want the graphics card to go into there. Or maybe if you've got other cards in there as well they are ending up robbing your video card slot of bandwidth.

- Michael

Everything works except for very slow performance. I hope to get it running with nvidia drivers because it's faster and I can use CUDA for rendering.

Hi Michael,
thanks for trying to help.

I have tried your description but I can't get my CustomUi to run.

I give up and stay with V3.1 for Mac until someone writes a routine that makes the necessary changes.

-moritz

Thanks a lot Max !
Where could we download scripts updated ?

Hi Michael. About the construction line problem:

Hi Michael,

I confirm the experience of Michel, VIP (VINC)
http://moi3d.com/forum/index.php?webtag=MOI&msg=8675.56

A simple extrude in the new version from NOV 13 still calculates infinitely.
I also use OS X 10.9.5
And I have a non-retina display

-Martin