MoI discussion forum
MoI discussion forum

Full Version: V4 beta Oct-17-2018 available now - SubD to NURBS conversion

Show messages:  1-16  …  117-136  137-156  157-176  177-196  197-216  217-236  237-256  257-264

Thread Split: Some posts in this thread have been moved here

From: Michael Gibson
6 Dec 2018   [#177] In reply to [#174]
Thanks Christopher, I'm glad you are liking the improved file loading speed in v4!

re: Multiple select - I do have it on my todo list to put in an option for changing how multiple select works like you are describing. I haven't been too excited to do it kinda because the way it currently works was one of the very earliest design choices for MoI to enable working without needing to constantly use the keyboard. So turning it off is to me kind of a little like taking out a piece of MoI's soul... But only a little. ;) I think it will also be somewhat problematic when you're working with edge or face sub-objects where multiple selection is needed almost all the time. That's an area of MoI that does not really resemble a 2D drawing or word processing application very much unlike curve drawing.

- Michael
From: Michael Gibson
6 Dec 2018   [#178] In reply to [#174]
Hi Christopher, also re:

> (One could argue that allowing the extrude command to function at all when a solid was selected is a bug.)

At some point here hopefully not too far off having a solid selected at the same time as a curve when you are doing an extrude will mean project the curve onto the solid and extrude that piece of the solid in or out.

- Michael
From: Robert (MAESTROROBERTUS)
17 Dec 2018   [#179]
Why not a Nurbs to SubD converter?
From: MajorGrubert (CARLOSFERREIRAPINTO)
17 Dec 2018   [#180] In reply to [#179]
Yep, i'll use it all the time : )
From: Michael Gibson
17 Dec 2018   [#181] In reply to [#179]
Hi Robert,

> Why not a Nurbs to SubD converter?

I would like to have one, but it's a difficult problem and there will be a lot of work involved.

Check out this thread for what happens with the current state-of-the-art conversion mechanisms:
http://moi3d.com/forum/index.php?webtag=MOI&msg=8817.23

- Michael
From: pixelhouse
19 Dec 2018   [#182]
Hi Michael,

when I saved the file, Moi has crashed.
The "save to"-option works fine in this case.

I attach the moi-report here. Hope it's ok.

Best regards
Jörg

Attachments:
moi_report1.zip


From: Michael Gibson
19 Dec 2018   [#183] In reply to [#182]
Hi Jörg, thanks for sending the crash report. Does the crash happen when you are trying to save a particular file that you have loaded?

If so is it possible for you to send me the file at moi@moi3d.com so I can try to reproduce the crash?

The crash report indicates the crash is happening in nvwgf2umx.dll which is part of the NVidia display driver, so it might be some problem with the video driver.

I might be able to figure out more though if I can repeat the crash over here.

Thanks,
- Michael
From: pixelhouse
19 Dec 2018   [#184] In reply to [#183]
Hi Michael,

I have send the 3dm-file to you. Hope it helps.

Jörg
From: Michael Gibson
19 Dec 2018   [#185] In reply to [#184]
Hi Jörg, I do not seem to have received the file. If it is pretty large you may need to use something like Dropbox and send a link to it rather than as a direct e-mail file attachment.

Thanks, - Michael
From: pixelhouse
20 Dec 2018   [#186] In reply to [#185]
OOps! The file has a size of 1mb :)
I send it as attachment directly here. It's not somethink special.

Best regards
Jörg

Attachments:
SphereRacer1.zip


From: Michael Gibson
20 Dec 2018   [#187] In reply to [#186]
Hi Jörg, thanks for posting the file. I can't repeat the crash over here though, does it happen for you if you just open that file and then use Save?

Since your crash dump has the crash happening inside your video driver maybe there is a problem there. A few things you could try might be to update your video drive to the latest version and there are also a couple of moi.ini settings you could set that may help:

[View]
<...>
DisplayThreadLimit=1

That will disable the use of multiple cpu cores for the drawing engine, some video drivers may behave better with that.

And also:

[View]
StaticBufferMaxVRAMToUseMB=0

That will disable caching of display meshes on video card memory.

Does any of that make any improvement?

Thanks,
- Michael
From: pixelhouse
20 Dec 2018   [#188] In reply to [#187]
Hi Michael,

another bug is, when I hide the points on a curve, the curve will deleted.
I bring back with Control+Z and hide again the points. The curve is remains in the scene.

Try with a new freeform-curve and activate the points and then hide the points.
In my case the curve will deleted.

Best regards
Jörg
From: Michael Gibson
20 Dec 2018   [#189] In reply to [#188]
Hi Jörg, there isn't currently any way set up in MoI to hide individual points. If you have the curve selected at the time you do the hide, the curve will be hidden though but not deleted. You should be able to use Hide again to make it visible.

Ctrl+Z undo also works to undo the last change in visibility or selection.

- Michael
From: pixelhouse
20 Dec 2018   [#190] In reply to [#189]
Hi Michael,

thank you for this information. Is it a new feature? I never see this before.

Jörg

Message 9100.191 was deleted


From: bemfarmer
20 Dec 2018   [#192]
Not a big deal, but:
Unless I am mistaken? I've noticed this morning that the f.lux program, which warms up Windows programs screen colors, during darker parts of the day,
SEEMS to be causing the Area Zoom Pan Reset panel at the bottom center of the MoIBeta4 screen to remain lighter than the f.lux colored MoI screen,
whenever the mouse pointer is in the gridlines area of the screen. This is not happening in MoI3.
(Hovering over the panel, the colors seem to match.)

So it seems like, for that area, the shade used by MoI does not reflect the f.lux modification?

- Brian
From: Michael Gibson
20 Dec 2018   [#193] In reply to [#190]
Hi Jörg,

re:
> Is it a new feature? I never see this before.

No, that's the same as it has always been.

For the crash is that something you can repeat over there using that file you posted?

If it was just a one time random crash you might try updating your video driver since the crash report showed the crash was happening in video driver code.

- Michael
From: Michael Gibson
20 Dec 2018   [#194] In reply to [#192]
Hi Brian, re: f.lux - there is a difference from how MoI v3 and v4 handles that bottom viewport toolbar, in v4 it is a separate window layered on top since that was easier to do cross platform. So I guess that is affecting f.lux.

- Michael
From: bemfarmer
21 Dec 2018   [#195] In reply to [#194]
Uninstalled f.lux, and highlight problem went away. Snagit no longer suffers brownout either.
Re-installed updated f.lux, and no more problems.:-)

After a reboot, my MoI4 hotkey for Light node editor reverted to its prior value, so I must have the MoI3 version of hotkeys reloading?
I updated the Ctrl+Alt+N hotkey in MoI3, for Light node editor scheme, and all seems to be well now...

- Brian
From: Michael Gibson
21 Dec 2018   [#196] In reply to [#195]
Hi Brian, by default MoI v3 and v4 both use the same moi.ini file where your shortcut keys are stored. So they will have the same shortcuts between them.

If you want though it is possible to make each of them use a separate moi.ini file and so have separate settings. To do that you can either pass the path to a moi.ini file as a command line parameter to moi.exe, or you can move the moi.ini file into the same directory as moi.exe and it will find it there but if you do the second one you would need to run moi.exe with elevated privileges ("Run as Administrator") because at the default privilege level Windows will prevent programs from modifying files in the "Program files" directory.

- Michael

Show messages:  1-16  …  117-136  137-156  157-176  177-196  197-216  217-236  237-256  257-264