MoI discussion forum
MoI discussion forum

Full Version: V4 beta Nov-27-2017 available now

Show messages:  1-9  10-29  30-49  50-64

From: mkdm
28 Nov 2017   [#10] In reply to [#1]
Hello Michael.

@You : "...Shortcut keys with Shift..."

Thanks a lot for fixing!

And thanks also for the "Scripting" info :)

We'll catch up!

Ciao.
From: Frenchy Pilou (PILOU)
28 Nov 2017   [#11]
French Upadates of the list of bugs! :)
http://moiscript.weebly.com/v4-quoi-de-neuf.html
http://moi3d.com/forum/index.php?webtag=MOI_FRANCAIS&msg=543.2
From: moujiik
28 Nov 2017   [#12]
Hi, when export to pdf, it seems we cannot change the default line weight.
Regards
Moujiik
From: Michael Gibson
28 Nov 2017   [#13] In reply to [#12]
Hi Moujiik

> Hi, when export to pdf, it seems we cannot change the default line weight.

I can't repeat this over here, which weights are you setting, is it something other than the visible lines one?

- Michael
From: Mip (VINC)
28 Nov 2017   [#14] In reply to [#1]
Hi Michael,

Mac full screen mode problem on OSX 10.9.5 still occurring here too.

Michel
From: moujiik
29 Nov 2017   [#15] In reply to [#13]
Hi Michael, whatever ligne weight i input, it get back to default see video
Moujiik


Image Attachments:
Lignes.gif 


From: Frenchy Pilou (PILOU)
29 Nov 2017   [#16]
Pleased that you use my French UI! :)

But alas for your glitch that works like a charm for me ! V4 of the 27 nov 2017 (Windows 10)




PS :
Something different than you : i can't save on the folder where you are! <o=[

On other place that works fine! :)


From: Unknown user
29 Nov 2017   [#17] In reply to [#15]
Hi moujiik.
I have everything working well.
Windows 7.
From: Michael Gibson
29 Nov 2017   [#18] In reply to [#15]
Hi Moujik, thanks for posting the video. It seems to be a problem with input fields and the particular way you're selecting the text. I can repeat your problem if I click and drag to select the text and make sure to release the mouse when off the field. If you do a single click on the field instead of a drag then that seems to work ok.

I'll investigate what's going wrong there, thank you for reporting it.

- Michael
From: Michael Gibson
29 Nov 2017   [#19] In reply to [#18]
Hmmm, and now I can't get it to happen anymore. There seems to be some kind of focus problem with input fields though.

- Michael
From: Metin Seven (METINSEVEN)
29 Nov 2017   [#20] In reply to [#9]
Hi Michael,

Thanks for the clarification of the Area zoom, makes sense.

A little reminder, although it's probably already on your to-do list: switching to full-screen mode on MacOS doesn't yet work using the system shortcuts — Control + Command + F to toggle full screen mode, or Esc key to exit full screen mode.

Having said this, I'd very much prefer Esc to solely remain a MoI function to cancel operations in stead of also exiting full screen mode. In ZBrush, pressing Esc to cancel an operation also exits full screen mode, and even exits ZBrush Edit mode at the same time, which is quite frustrating.

Command + M to minimize an application to the dock, and Command + H to hide an application both work fine with MoI.

Thanks,

Metin

———————

visualization • illustration • animation • 3D (print) design — https://metinseven.com
From: Michael Gibson
29 Nov 2017   [#21] In reply to [#15]
Hi Moujiik, it looks like if you double-click on a field things will be messed up after that and you have to push Enter for the field to accept the change (which will also close the dialog). That seems to reliably reproduce it.

- Michael
From: Unknown user
29 Nov 2017   [#22]
Hi Michael.
One more trouble. Buttons box.
To watch the video.
From: Michael Gibson
29 Nov 2017   [#23] In reply to [#22]
Hi Vladimir, thanks for posting that video, I can reproduce that here. It will happen if you generate a degenerate rectangle for the base of the box. MoI v3 would just exit the command in that case and I will tune up V4 to behave the same instead of generating a script error.

- Michael
From: Unknown user
29 Nov 2017   [#24] In reply to [#21]
I also repeated this.
From: r2d3
29 Nov 2017   [#25]
setCameraAndTarget()

does not work in V4 but in V3.

This script should set the cam to point 50,50,50 and the target to point 0,0,0

script: camPt=moi.VectorMath.createPoint(50,50,50);targetPt=moi.VectorMath.createPoint(0,0,0);moi.ui.getActiveViewport().reset();moi.ui.getActiveViewport().setCameraAndTarget(camPt,targetPt);

(copy script, in moi hit tab and paste, hit enter)

Ralf
From: BurrMan
29 Nov 2017   [#26] In reply to [#1]
Hi Michael,

Have you thought about some kind of setting for MoI regarding available RAM to the app as a user setting?

So now with 64 bit, if i crank some model meshing parameters, MoI can quickly gobble up all my RAM.

With tge 32 bit version, i could max out MoI and the worst would be i lock up MoI abd have to force quit it...

With the new 64 bit version, i can lock up the entire system and it can be problematic.

So if i know i have 16 or 32 gigs of RAM, i could set MoI to know to use 12 or 30 gigs, type of thing....

Thanks.
From: Michael Gibson
29 Nov 2017   [#27] In reply to [#25]
Hi Ralf, re: setCameraAndTarget() in v4 , thanks for reporting this bug I've got it fixed up for the next beta.

- Michael
From: Michael Gibson
29 Nov 2017   [#28] In reply to [#26]
Hi Burr,

re:
> Have you thought about some kind of setting for MoI regarding available RAM to the app as a user setting?
>
> So now with 64 bit, if i crank some model meshing parameters, MoI can quickly gobble up all my RAM.

I had not really thought about that, but it should not be too hard to add a moi.ini setting for that. Something like:

[Settings]
MaxProcessMemoryUseGB=12

- Michael
From: BurrMan
29 Nov 2017   [#29] In reply to [#28]
That would probably be a good setting to have....

Thanks again!

Show messages:  1-9  10-29  30-49  50-64