V2 beta Aug-8-2009 available now  1-20  21-40  41-56

Next
 From:  Michael Gibson
2843.1 
A new v2 beta (version Aug-8-2009) is now available for download here: http://moi3d.com/beta.htm

You will need to enter your v1 license key to download the v2 beta.

The v2 beta installs into its own folder, it is not a problem to have v1 and any v2 beta installed on the same machine, in fact I recommend that so that you can fall back to v1 if you run into some temporary bad bug in v2.


The major news for this release is that styles are wrapped up - shaded surfaces will now display in their style colors. Also there is a new lighting engine for the display which gives various options for controlling the shaded appearance and helps to provide more illumination on objects, reducing dark areas.


Release notes:


Updated display so that faces are shown using style colors.


Implemented new lighting engine.

Here's an example of the new default lighting:



There is a lot more distribution of the illumination in this new system which helps to avoid overly dark areas.

Here's a comparison with the previous lighting system (which is still available with the Lighting style: Key light only option):



Also if you want to go brighter yet, try the Lighting style: Key + more fill option which looks like this:



You can control these options including setting custom levels for the key and fill lights using sliders, by the new settings under Options > View > Lighting options.

There's an example video here:
http://moi3d.com/forum/index.php?webtag=MOI&msg=2801.91

You can also enable some options such as specular highlights and a metallic style look.

Here's an example with specular highlights enabled:



And here are some variations with metallic and specular together:






Updated display of points to use style color.

Added an option to override surface or edge colors to use a specific fixed color instead of using the style color. These options are under Options > View > Surface color: and Edge color:

Added a button for editing the moi.ini file, under Options > General > Edit .ini file. When you pick this you will be prompted if you want to exit MoI and launch the moi.ini file in whatever program is set in Windows to edit files with the .ini file extension, which is Notepad by default. Also in the prompt dialog the path to moi.ini file that is currently being used is shown.

Added a "both sides" option for the Line command to make it a bit easier to draw a line starting from the midpoint.

Added a new Conic command under Draw curve > More > Conic , which allows for creating a conic section curve (either a parabola, hyperbola, or ellipse segment) from a 3 point frame plus a "through point" or rho value. For some examples see:
http://moi3d.com/forum/index.php?webtag=MOI&msg=2746.4
http://moi3d.com/forum/index.php?webtag=MOI&msg=2746.12

Added a new ExplodeMove command which can be set up on a keyboard shortcut to move objects away from a common center point to move them apart from one another. Some examples:
http://moi3d.com/forum/index.php?webtag=MOI&msg=2781.3
http://moi3d.com/forum/index.php?webtag=MOI&msg=2781.10

Added a new BoundingBox command which can be set up on a keyboard shortcut, which will create a bounding box (either a 3D solid box, or a 2D rectangle curve) framed around the current selection.

Added a new BoundingBoxCenter command which can be set up on a keyboard shortcut, which will create a point object to mark the center of the bounding box framed around the current selection.

Got a bug fix for writing surface colors to STEP files.

Updated IGES and STEP file handling to support reading and writing object names.

Updated SAT export - closed surfaces (for example a cylinder) are now split into 2 joined half pieces when exporting to SAT format to improve data transfer into Revit. This splitting can be disabled by a setting in moi.ini :
[SAT]
ExportSplitClosedSurfaces=n

Added an option to enable or disable combining meshes for objects of the same name, for OBJ and LWO export. This is under Options > Import/Export > Combine same named objects.

Updated LWO export with "LightWave style" vertex normals - reversed the normals for this case since that appears to be what LightWave expects in their most recent version.

Added an option for OBJ export to disable writing material assignments, which will create output the same as MoI v1. This is under Options > Import/Export > OBJ options > Write material assignments.

For OBJ export, replace spaces in object names with underscores, since spaces are often not supported by OBJ readers. Spaces can be enabled by a setting in moi.ini:
[OBJ Export]
AllowSpacesInObjectNames=y

Added some options in moi.ini for OBJ export, for using the relative style index method, and for adjusting the number of decimal places:
[OBJ Export]
UseRelativeIndexing=n
NumDecimalPlaces=8

Added an option in moi.ini for style handling to prevent sub-objects from keeping their own distinct styles during operations such as booleans.
[Styles]
DisableSubObjectStyles=n
When set to =y, operations such as booleans will have their result be all the same style rather than having the styles of each original face persist in the combined object.

Added a script method moi.ui.alert() so a script can more easily pop up a simple message box.

Added a "Points" entry to the scene browser type section to allow operations on point objects (this applies to individual point objects, not to edit points that are turned on by Edit/Show pts).

Updated mesher - enabled better uv quad alignment on circular joined parts at high densities.

Updated the Text command to be oriented better for reversed (Back/Left/Bottom) views.

Fixed a bug where setting the option for swapping pan/rotate mouse functions did not work correctly in parallel 3D views.

Reworked program cleanup if moi.exe is terminated abruptly using Windows Task Manager, now companion processes should also exit automatically in this situation.

Updated cplane triad picker so that the lines are displayed at the same size on the screen instead of being a fixed size in world units. This helps to prevent the orientation picker from getting small in size when zoomed out.

Fixed a crash bug that could happen in certain circumstances when using the edit frame to scale a base curve that triggered a history update.

Fixed a bug where name properties on standalone curves could get transmitted through to edges on solids in some operations like extrude.

Fixed a bug in setting cplanes where construction lines that were created during the cplane placement were not cleared out properly.


Added some settings in moi.ini for some additional ways to control keyboard behavior:
[UI]
CommandLineTypeTextEntry=n
TreatSpaceAsEnter=n

CommandLineTypeTextEntry set to =y will allow keystrokes to activate the
xyz control without needing to type Tab first.

TreatSpaceAsEnter set to =y will allow hitting the space bar to work the same as pushing Enter for committing typed in values in input fields, and also as an alias for pushing "Done" or for repeating the last command.


Various other minor bug fixes and tuneups.


Things are getting very close to being wrapped up for the MoI v2.0 final release, I think that there will be just one more remaining v2 beta release.

Please let me know if you have any problems!

- Michael

EDITED: 8 Aug 2009 by MICHAEL GIBSON


  Reply Reply More Options
Post Options
Reply as PM Reply as PM
Print Print
Mark as unread Mark as unread
Relationship Relationship
IP Logged

Previous
Next
 From:  FlashFire
2843.2 In reply to 2843.1 
Well I like the new beta :)

But I tried out the rebuild curve script and get a Line 80 Column 1: error :(
  Reply Reply More Options
Post Options
Reply as PM Reply as PM
Print Print
Mark as unread Mark as unread
Relationship Relationship
IP Logged

Previous
Next
 From:  BurrMan
2843.3 In reply to 2843.2 
Hi Michael,
In the ini file Connect Points is written as COnnectPoints but it seems to launch the command. At the moment it doesnt seem to be working but I overwrote the new one with the one I used to have as I didnt know it was included (odd it didnt prompt me that I was overwriting it too). I also may be using it wrong, I will revisit the thread and review that.

I get an error when I type Merge at the command entry area also. Didnt have that in my old stored command folder so didnt overwrite anything. If I launch it with a keyboard shortcut, it works [EDIT]No it doesnt[EDIT], if I type at command entry, script debugger starts and then when I choose no, the command temporarily starts then quits.

I will do a default install and check both these things before I add my personal stuff to it and post back.
  Reply Reply More Options
Post Options
Reply as PM Reply as PM
Print Print
Mark as unread Mark as unread
Relationship Relationship
IP Logged

Previous
Next
 From:  BurrMan
2843.4 In reply to 2843.3 
Seems related to the command entry. If I use a keyboard shortcut with any Command, it works "CSec" but if entered into the command area, I get an undefined in MoI.exe and then quite that dialogue and the command runs.
  Reply Reply More Options
Post Options
Reply as PM Reply as PM
Print Print
Mark as unread Mark as unread
Relationship Relationship
IP Logged

Previous
Next
 From:  Michael Gibson
2843.5 In reply to 2843.2 
Hi FlashFire,

> Well I like the new beta :)
>
> But I tried out the rebuild curve script and get
> a Line 80 Column 1: error :(

Hmmm, that's strange - I just installed it and tried it now and it seems to work fine over here...

One thing to note - that RebuildCurve script is a custom command that is installed by copying it into the \commands sub-folder.

When you get a new beta, it installs into a new folder and so you need to copy the RebuildCurve script to the new beta's \commands sub-folder to get it set up for the new beta as well.

Maybe try following the installation instructions for RebuildCurve again (from here, and see if that helps.

- Michael
  Reply Reply More Options
Post Options
Reply as PM Reply as PM
Print Print
Mark as unread Mark as unread
Relationship Relationship
IP Logged

Previous
Next
 From:  BurrMan
2843.6 In reply to 2843.5 
Michael, It actually is happening in my June23 release also now.
  Reply Reply More Options
Post Options
Reply as PM Reply as PM
Print Print
Mark as unread Mark as unread
Relationship Relationship
IP Logged

Previous
Next
 From:  Michael Gibson
2843.7 In reply to 2843.3 
Hi Burr, re: ConnectPoints

> In the ini file Connect Points is written as COnnectPoints
> but it seems to launch the command.

Actually by default there is nothing in the moi.ini file for "ConnectPoints" - if you have something in there it was probably a keyboard shortcut that you had added previously? If so then that's just your own typo with the COnnectPoints part... :) Just go to Options / Shortcut Keys and edit it if you want to correct it.


> At the moment it doesnt seem to be working but I overwrote the
> new one with the one I used to have as I didnt know it was included
> (odd it didnt prompt me that I was overwriting it too).

Actually the command files are not included - but if you had previously set up a keyboard shortcut, then the shortcut will still be there in the moi.ini file.

I'll give it a test and see if I can repeat any problems over here.

- Michael
  Reply Reply More Options
Post Options
Reply as PM Reply as PM
Print Print
Mark as unread Mark as unread
Relationship Relationship
IP Logged

Previous
Next
 From:  Michael Gibson
2843.8 In reply to 2843.3 
Hi Burr, re: ConnectPoints, I can't seem to repeat any problem with it over here...

Did you copy over both the .htm and .js files for the command?

The link to the .zip is here if you need it:
http://moi3d.com/forum/index.php?webtag=MOI&msg=2749.56

I tried launching it both by setting up a keyboard shortcut (which should have just "ConnectPoints" as the command part of the shortcut) and also by typing in <tab> ConnectPoints <enter> and both seem to be fine over here.

Maybe double-check what you have set as your keyboard shortcut - do you have something like "script:ConnectPoints", or "ConnectPoints.js", or something slightly off like that? Those will make errors - you'll need to have just a plain "ConnectPoints" as the command part of the shortcut key for this one.

- Michael
  Reply Reply More Options
Post Options
Reply as PM Reply as PM
Print Print
Mark as unread Mark as unread
Relationship Relationship
IP Logged

Previous
Next
 From:  BurrMan
2843.9 In reply to 2843.7 
Hi Michael. My bad on the ConnectPoints.
Biut I just tested old and new versions with CopyClipboard and get same error.

Stick in old USB stick and get error. Works on computer that I havnt installed new aug moi on.
  Reply Reply More Options
Post Options
Reply as PM Reply as PM
Print Print
Mark as unread Mark as unread
Relationship Relationship
IP Logged

Previous
Next
 From:  Michael Gibson
2843.10 In reply to 2843.6 
Hi Burr,

> Michael, It actually is happening in my June23 release also now.

What is happening exactly?

Is a shortcut not working? If so can you please post exactly what you've got for the keyboard shortcut?

For ConnectPoints you need to copy the .htm and .js files over, and the command part of the shortcut should say: ConnectPoints

For Merge you don't have to copy anything, and the command part of the shortcut should say: Merge


Do you possibly have some extra stuff in the shortcut?

If your shortcut is messed up, then when it gets saved into the moi.ini file, it will then be messed up in the Jun-23 release as well since both releases are using the same moi.ini file to get their settings from.


I can't seem to repeat any problem with merge over here, I tried on a couple of different machines both by setting up a keyboard shortcut and also typing in the command name...

- Michael
  Reply Reply More Options
Post Options
Reply as PM Reply as PM
Print Print
Mark as unread Mark as unread
Relationship Relationship
IP Logged

Previous
Next
 From:  BurrMan
2843.11 In reply to 2843.9 
Here is what I get with typing "New" in the command area:




With no action. If I do Ctrl+N then I get a new Doc.

This happens in old June 23rd release also.

EDITED: 19 Jun 2012 by BURRMAN

  Reply Reply More Options
Post Options
Reply as PM Reply as PM
Print Print
Mark as unread Mark as unread
Relationship Relationship
IP Logged

Previous
Next
 From:  BurrMan
2843.12 In reply to 2843.11 
I keep my ini files in the root folders. I get this result with any command. Even default MoI commands. I can insert USB stick that works on other computer and receive same error. Only with Commands entry, Keyboard shortcuts work as they should.
  Reply Reply More Options
Post Options
Reply as PM Reply as PM
Print Print
Mark as unread Mark as unread
Relationship Relationship
IP Logged

Previous
Next
 From:  Michael Gibson
2843.13 In reply to 2843.9 
Hi Burr,

> Biut I just tested old and new versions with CopyClipboard and get same error.

Sorry, I'm not really understanding - do you mean Ctrl+C is not working for you?

It sounds like your shortcuts are all messed up, can you possibly post your moi.ini file here as an attachment so I can look at it?


> Stick in old USB stick and get error. Works on computer that
> I havnt installed new aug moi on.

I don't really understand what this means exactly either - you stick in a USB stick and then MoI shows an error?

What error is it?

Does it show right when you stick in the USB key? Or after you try a certain shortcut or something like that?

- Michael
  Reply Reply More Options
Post Options
Reply as PM Reply as PM
Print Print
Mark as unread Mark as unread
Relationship Relationship
IP Logged

Previous
Next
 From:  Michael Gibson
2843.14 In reply to 2843.12 
Hi Burr, are you running on Vista or XP?

Did this start to happen after you pushed the new "Edit .ini file" button?

- Michael
  Reply Reply More Options
Post Options
Reply as PM Reply as PM
Print Print
Mark as unread Mark as unread
Relationship Relationship
IP Logged

Previous
Next
 From:  BurrMan
2843.15 In reply to 2843.13 
Sorry Michael. I keep MoI on a USB stick also. I have Version June 23 installed on the computer I normally work on. It has been working fine. I just installed August release, and "ANY" command entered into the command area, by opening Moi and typing Tab+Command name, will produce this error And fail.

Not custom commands or anything.

All keyboard shortcuts work fine. If I launch any command with a keyboard shortcut, it works (Except ConnectPoints).

If I launch my MoI Version June 23 that is on my USB stick on a computer that has not had August install on it, Everything works as I expect. If I bring USB stick to computer that i just installed August release on, All Commands entered into the command entry area fail.
  Reply Reply More Options
Post Options
Reply as PM Reply as PM
Print Print
Mark as unread Mark as unread
Relationship Relationship
IP Logged

Previous
Next
 From:  BurrMan
2843.16 In reply to 2843.14 
XP OS and havnt puched that button yet. Aslo note that this happens in the old release that worked fine a few minutes ago also.

I didnt think MoI installs anything outside of the MoI folder so this is weird that it happens in both.
  Reply Reply More Options
Post Options
Reply as PM Reply as PM
Print Print
Mark as unread Mark as unread
Relationship Relationship
IP Logged

Previous
Next
 From:  Michael Gibson
2843.17 In reply to 2843.11 
Hi Burr,

> Here is what I get with typing "New" in the command area:

Well, that's definitely odd....

How are you putting focus into the command area before you type "New", are you typing Tab first, or .... ?

Have you recently installed some new development tools like Visual Studio 2008 that you show there? Maybe that has something to do with it.

It kind of sounds almost like your \commands sub-folder cannot be found, so that "New" is attempting to run as some inline script rather than as the actual New command, and then some script development system that you have installed is catching the script error.

Is this all happening when you are trying to run directly off of a USB key instead of a more regular hard drive install?

- Michael
  Reply Reply More Options
Post Options
Reply as PM Reply as PM
Print Print
Mark as unread Mark as unread
Relationship Relationship
IP Logged

Previous
Next
 From:  Paolo (PAOLOLOBBIA)
2843.18 In reply to 2843.1 
Hi Michael,

The metallic option is nice but to much dark shadows.
I vote for the "Custom + Fill Levels" option,which shows me
the best overall performance.

My compliments,

EDITED: 8 Aug 2009 by PAOLOLOBBIA

  Reply Reply More Options
Post Options
Reply as PM Reply as PM
Print Print
Mark as unread Mark as unread
Relationship Relationship
IP Logged

Previous
Next
 From:  BurrMan
2843.19 In reply to 2843.17 
Yeah nothing is new on this box. I suppose I'll just wait and see if anything happens to anybody else. If not, then it must be me. Is there anything in this release installed outside of the MoI folder?
  Reply Reply More Options
Post Options
Reply as PM Reply as PM
Print Print
Mark as unread Mark as unread
Relationship Relationship
IP Logged

Previous
Next
 From:  Michael Gibson
2843.20 In reply to 2843.15 
Hi Burr, well that's very mysterious behavior, since the new Aug release does not install anything that would be shared between the previous beta and itself...

Maybe it would be a good idea to do a system reboot?

The only thing that is normally shared between 2 installs is the moi.ini file when it is set in its default location.

- Michael
  Reply Reply More Options
Post Options
Reply as PM Reply as PM
Print Print
Mark as unread Mark as unread
Relationship Relationship
IP Logged
 

Reply to All Reply to All

 

 
Show messages:  1-20  21-40  41-56