Just copied the scripts. The Pipe command fails.

Hi Steve,

> Just copied the scripts. The Pipe command fails.

Looks like an actual error in the script that the old script engine happened to silently ignore for some reason.

Please try the attached updated version - this new version should work in either v2 or v3 now.

In addition to the UI for v3 being on a new system, the script processing also is using a new system as well and there may be a few kinks related to that, like in this case with a slight difference in error handling making a difference to how the script was executed. It should only require minor tweaks to fix up these kinds of issues as well.

- Michael

Also one of the other updates to the script system is a much better display of script errors - it shows the actual line of script where the error is happening and some surrounding code as well. That makes it a lot easier for me or a script author to see exactly where the script is having a problem.

- Michael

Michael, thank you very much for V3 beta.

Fooling around, found a very small problem:
Attempted to install and use the FullScreen script.
Worked in V2, in scripts directory at same level as command.
It appears not to work in V3 beta.

Hi bemfarmer - I think that may be a slightly older FullScreen script that you've got there - that one probably doesn't work right if you've got the scene browser open in v2 (when it's in the "adjacent" mode where it is a full panel).

At one point I updated the script and the updated one should work in v3 - it's attached here.

This attached version should work in both v2 and in v3.

- Michael

Update works fine! Thank you

Michael,

MOI still doesn't know if the program is open in a visible window.

Regarding UI, I usually use a larger monitor so leaving more of the tools visible at the same time would be nice. Would save some clicking.

Jeff

Hi Jeff,

> MOI still doesn't know if the program is open in
> a visible window.

Is this the issue from this previous thread here:
http://moi3d.com/forum/index.php?webtag=MOI&msg=4244.1 ?

That's on my list of things to clean up but I haven't quite gotten to it yet, I'll probably be making a pass through my collected tune up list for the next v3 beta.

- Michael

Hi Michael,

I wonder if it would be possible to see a preview of 3dm files while opening or importing file inside Moi and possibly while browsing with the file explorer or whatever???

Thanks,
Felix

The revised pipe script works OK. Many thanks,

Hi Felix,

> I wonder if it would be possible to see a preview of 3dm
> files while opening or importing file inside Moi and possibly
> while browsing with the file explorer or whatever???

Yup, that's on the wishlist and should get done eventually.

It's been hard to prioritize it compared with actual modeling functions though - for example would you have rather had the 3DM thumbnail preview instead of having the new Flow command?

- Michael

Hi Michael,

of course I prefer by far a command like Flow then a thumbnail preview. I just give my suggestions as they come.

Thanks,
Felix

Excuse me if this has already been answered. I did some searching but couldn't find anything. Will there be a 64bit version of MOI V3? I'm running out of memory quite often when trying to mesh big models with V2.

Hi Sun, currently I don't have any plans for a 64-bit version of v3. It would take quite a lot of effort to make that happen, it involves not just MoI's core code but also getting 64-bit versions of various support libraries that MoI uses as well so altogether that's a highly time consuming project to undertake.

If you have a pretty complex model your best bet is to select some portions of it and use the File > Export command which only writes out just the selected objects instead of writing everything. Writing things out in a couple of chunks like that instead of all at once should help to avoid running out of memory.

- Michael

Hi Michael,

In the numeric input field, the white space between the 1 2 3 button and the 0 , - button is different.
Is this intended ?

Hi Paolo,

> In the numeric input field, the white space between the
> 1 2 3 button and the 0 , - button is different.
> Is this intended ?

That's not intended - it's a bug that happens if your locale uses the comma character as the decimal separator, thanks for reporting it!

I've got it fixed up now for the next beta and you can also apply the fix by copying the updated attached files over top of the previous versions in the \ui subfolder underneath MoI's main installation folder.

- Michael

Hi Michael,

Problem fixed

Thanks,

Hi Michael,

Is V3 supposed to give error feedback when a command fails, for instance I tried to draw an arc tangent between two curves and received the dummy spit attached, I did realise that one of my curves wasn't planar because of it though, if I interpreted it right that is :S , if this is intentional could we have a simpler error like 'Curves non planar' that would be cool.




Cheers

Hi Danny, a script error like that is meant to give debugging information to the person developing the script, it's a bug when you see those in a finished script.

I'll fix that up for the next beta release, thanks for reporting it.

At some point I want to figure out a good place where things could give feedback on error situations like things being not all in the same plane like this case. I have not yet figured out a good place to stick error messages like that though, I kind of need some area of the UI where several lines of text messages can be streamed out.

- Michael

Yep. Wasn't sure if you already got to it.