Forum: Poser - OFFICIAL


Subject: Matmatic 1.1 coming soon - any more enhancement requests?

bagginsbill opened this issue on Apr 29, 2010 · 27 posts


bagginsbill posted Thu, 29 April 2010 at 3:56 PM

Here is the list of changes since the original.


Matmatic 1.1.0

Added a Version attribute to the matmatic module. It is a string. The current release matmatic.Version = "1.1.0".

Fixed a bug on Mac where the scan paths beginning with Runtime: or :Runtime: didn't work. Absolute paths should no longer be required.

Matmatic now supports multiple runtimes, without having to specify full paths. (P7+ and PPro+, not P6. P6 doesn't have support for matmatic to ask where your registered runtimes are.)

Matmatic can be installed anywhere on your hard drive. Previously it had to be in your main runtime. The script does not even have to be in a runtime at all. However, to make life easier, your matmatic material scripts should be in some runtime.

Matmatic can now keep going compiling all your scripts, even if one has an error. There is a config option to control this. The new default behavior is to keep going.

Matmatic scripts can now assume that "import poser" has already been performed.

Fixed a bug where detection of a script being in a pose folder (and therefore should make a MAT pose file) was case sensitive. You can now spell it Pose, pose, POSE, whatever.

Fixed a bug where Matmatic used to complain if userconfig.txt was missing. It only does this in verbose=2 now, as documented.

Fixed bug with EmptySurface.

Added ListLookup method to generate an efficient sequence of nodes that looks up a value in a list of values.

Changed default value in V3Collection for FacialHair. Was transparent, now is None.

Optimized the Mix method to drop some multiplies that weren't absolutely necessary.

Added readScript method to root nodes so that generated files can read other Poser files when loaded.

Changed default label on PoserSurface root node from MatmaticSurface to PoserSurface.

In Material Collections, changed the way material names are looked up. (For V4 mostly) Any leading digits and underscores on the material name are ignored.

Fixed a bug where EdgeBlend nodes were always considered to be a color. If only shades of gray are used, will be treated as a number.

Fixed a bug in ImageMap - default values of U_Offset and V_Offset were 1 - should be 0.

Added Filtering attribute to ImageMap.

Added new root node types: Light, Atmosphere, and Background. Previously only Surface existed.

Added Loom to package.

Changed the processScript method so 3rd party software can easily invoke matmatic on a script file. Example:

import matmatic.compiler
matmatic.compiler.processScript(r'c:foobartest.mm1.txt')

This will include a check to see if it is up to date already and skip it if so. To force processing even if it is up to date, pass an additional argument that is not false.

Like this: matmatic.compiler.processScript(r'c:foobartest.mm1.txt', 1)

Added methods (PM, PMC, PM2, etc.) to create Parmatic-style parameter nodes. These are inserted in columns before the Poser Surface node.

Added TrueFresnel function to calculate Fresnel reflectance for any IOR, including IOR below 1. Total internal reflection (TIR) is implemented.

Added View function to make it easy to just view the output of a node as the whole material.

Added built-in GC and anti-GC functions for doing gamma corrected materials. A function SetGCMode allows defining different GC strategies; PMAuto, Auto, PM, Fixed, and None. In either Auto mode, shader GC is automatically disabled if the material is running in Poser Pro with render GC enabled.
 


Renderosity forum reply notifications are wonky. If I read a follow-up in a thread, but I don't myself reply, then notifications no longer happen AT ALL on that thread. So if I seem to be ignoring a question, that's why. (Updated September 23, 2019)