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

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

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

Hi Michael,

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

Jörg

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

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

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

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

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

Thank you Michael.
My home computer (seems) to have voluntarily switched to using (non-appdata) MoI3 files of type .ini and nodeeditor, for MoI4beta,
or else it has been that way for 9 months or so until I recently updated nodeeditor in appdata...

Changing one shortcut key in MoI 4 did not update the MoI3 .ini, (??)
I changed the Ctrl+Alt+N for Light Scheme nodeeditor in MoI3, and now the hot key works in MoI4.

Last night I updated nodeeditor in C:\Program Files (x86)\MoI 3.0, and now nodeeditor again works in MoI4beta.
I do not recall if MoI3 can use the appdata folder for customui and nodeeditor...

So I am still confused...
I'll puzzle on it some more.

I really like the appdata method.

- Brian
p.s. Everything seems to be working properly with the office computer.

Hi Brian, well one other complication is that settings are only saved to moi.ini when MoI shuts down.

So if you have MoI v3 and MoI v4 open simultaneously and make different changes in each one, they will have differences at that moment but the last one that you close will win out and have its settings in the moi.ini file.

Does that explain what you are seeing?

- Michael

Thank you Michael.
That makes sense.

Anyway, I'm using MoI4beta 99% of the time so I'll keep the MoI3 .ini the same as MoI4beta's.

Yes, your explanation is correct.
With MoI4beta closed, I opened MoI3, and changed the CTRL+Alt+N shortcut key by adding ZONK before the final semicolon.
Closed MoI3. Opened MoI4beta. The shortcut key alerted finding "ZONK,' and did not load nodeeditor.
Removed ZONK, closed and reopened MoI4beta, and the hotkey worked to load nodeeditor Light scheme.
The Light scheme is more printer toner friendly...


- Brian

Hi All

Have not been around for a while, just noticed the subd to Nurbs feature, I'm impressed.
Did a great job with my test model. the subd came from DazStudio, quit a complicated model.








Cheers, stephen

Hi stephen, that's great thanks for testing the SubD to NURBS conversion. There are also some tune-ups coming for that in the next beta release.

- Michael

Hi Michael,

I am using the Volume Calculator script that we did with Max a few years ago (http://moi3d.com/forum/messages.php?webtag=MOI&msg=7421.61) with the latest beta and i noticed something strange:
When i call the script through a Keyboard shortcut it takes about 2-3 times as long to finish calculations as opposed to calling directly (<TAB> and type the command).

When i try the original version that i did (first page of the same thread ) the running time is the same.

I'm guessing that this has something to do with the optimizations that Max did, but I'm reporting it anyway, in case this affects more scripts.

Dinos

Hi Dinos,

re:
> I am using the Volume Calculator script that we did with Max a few years ago
> (http://moi3d.com/forum/messages.php?webtag=MOI&msg=7421.61) <...>

I do see that the one in the link above is a beta 09-22 version and there is a later 9-27 version at http://moi.maxsm.net/media/files/ . So that might be worth a try.

Both keyboard shortcuts and typing in command names end up going through the same command launching mechanism so I don't know why one would be slower or faster than the other. Maybe there's some kind of file caching involved and it was more dependent on which one was done first rather than what the launching method was.

- Michael

Hi Michael,
I understand what you are saying and you are right of course, so it could be something specific to my setup.

Still, please try the latest version of the CVolume2 script from Max's site with the attached test file.
On my computer (Macbook pro 15 2015 16GB, running Mojave and MoI v4 beta Oct-17-2018) i get consistently around 2 sec of calculation when i type <TAB>_CVolume2 and around 5 sec when i use a shortcut.
I dont think caching is involved as i get the same results if i launch the script 2 or 3 times in a row using the same launching method.

I have this issue only with this script as i get the same running times if i use my original version of the volume script.
Unfortunately i dont use any other scripts that take a noticeable time to finish so i can't verify this with anything else.

Dinos

Hi Dinos, I tested your file over here with _CVolume2 from CVolume.v.2.0.2015.09.27.zip and I get the same 3.5 seconds with both launching from a shortcut key or by typing in the command name.

Could you please double check exactly what you have in your keyboard shortcut? Are you certain it's not running some older version on the shortcut key?

I also tested putting some fillets and booleans onto your shape so it took longer for the calculation and still got the same times between shortcut key or typing in the command name.

- Michael

Hi Dinos, also how are you checking what is in your shortcut key, are you using the UI in the Options dialog or looking directly in the moi.ini file possibly?

- Michael