Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 14 Next »

Log

Extensions > Maxwell Render > Log

The plugin Log is used to diagnose problems and evaluate translation performance. With the Log as a guide, you can troubleshoot most issues yourself.

A new log is begun when a Maxwell Render is initiated from formZ, or Fire is enabled. The log will remain in memory until a new render is initiated.

  • Display
    • All Messages
    • Warnings and Errors Only
  • Log Entries: Each line indicates the severity, ID code, context, and data associated with the entry. Any ERRORS are highlighted in blue so they are easy to spot.
  • Text field: This field (below the list) is a duplicate of the currently selected log entry in a form that can be copied and pasted. For instance, you can copy a file name here, then search for it in your favorite file search utility. This field is also useful for inspecting long messages that may not fit in the 'Data' column.
  • Save Log: Saves the log as a text file; useful for emailing to technical support.


Error Codes and Solutions

The code ID is located in the 3rd column of the Log browser.

 

E1: Resource Could Not be Found

ERROR | Resource Mngr | File Status | ERROR: File on previous line NOT FOUND at existing path or in search locations

The resource on the preceding line could not be found, even after searching all locations established in the Resource Manager.

Solution:

  1. If you know where the missing file is located, skip to step 4
  2. Click on the line containing the offending file path. This displays the file path in the text field below the log list. Copy the file name from that text field.
  3. Paste the file name into your favorite file search utility and search.
  4. In the Resource Manager (Extensions > Maxwell Render > Project Settings...) add a path to a folder containing the missing file.

 

E2: Can't Write Bitmap

ERROR | Material Translator | Export Embedded Bitmap | <Color, Transparency, Bump> bitmap used in <material> not found; FAILURE Writing <image> to disk.

formZ is not reporting a link to an external texture used for color, transparency, or bump mapping in it's shaded representation. Further, formZ is not able to regenerate a low resolution copy based on the bitmap it has cached within the formZ project file.

Solution:

  1. Select the Material in the Materials palette.
  2. In the Material Parameters palette, select the 'Shaded' representation, then appropriate channel tab (Color, Transparency, or Bump)
  3. Click on the folder icon, then select the image resource from your file system again (even if you already see the correct file and thumbnail image displayed)


E3: Object Error

ERROR | EditObjectAttributes | Object | <object> <Layer Path> <Group Path>

This may occur for two very different reasons.

  1. A clipping plane is enabled, which may generate the error on some clipped objects. This is usually harmless and the render will complete successfully; no action is required.
  2. The error is due to geometry imported from Sketchup. Occasionally, Sketchup objects come into formZ with bad texture UVs;

Solution, for the second (Sketchup) case:

  1. Use formZ's Select by Criteria palette and search for objects with [ERR] in their names. (The Maxwell plugin adds the [ERR] text so you can easily locate problematic objects. You can both disable this feature, and remove the error tags, if you wish.)
  2. Select formZ's Map Texture tool. Click anywhere in the modeling window to remap the problematic objects.
  3. If the error still occurs after this step, try formZ's Object Doctor tool on the objects.
  4. If the error still occurs after this step, ghost the objects so they won't be considered for export.

Warning Codes and Solutions

The code ID is located in the 3rd column of the Log browser.


W1: Resource Could Not be Found

WARNING | Resource Mngr | File Status | File on previous line NOT FOUND at existing path or in search locations

The resource on the preceding line could not be found, even after searching all locations established in the Resource Manager. Unlike the E1 error, the rendering will proceed; however, the missing dependency may affect the rendering.

Solution:

  1. If you know where the missing file is located, skip to step 4
  2. Click on the line containing the offending file path. This displays the file path in the text field below the log list. Copy the file name from that text field.
  3. Paste the file name into your favorite file search utility and search.
  4. In the Resource Manager (Extensions > Maxwell Render > Project Settings...) add a path to a folder containing the missing file.


W2: Outdated Material Hints

WARNING | Material Translator | Version | Not using current Material Hints. This may result in increased noise and render times.

When opening an older file, you opted not to update the Material Hints to the latest version. The new hints will render faster and look better. Try the new hints; it's trivial to switch back if you need to match older renderings.

Solution:

  1. Select Extensions > Maxwell Render > Project Settings
  2. In Autotranslate Shaded Hints, select the last entry (highest numbered version) from the pulldown menu.

 

W3: Non-Safe Characters

WARNING | Resource Mngr | File Status | File path on previous line contains non-safe characters...

The file path preceding the warning contains characters that may cause Maxwell dependencies to not be found when rendering.

Solution:

  1. If dependencies are not linking properly during rendering, first make sure that the dependencies are mapped correctly using the Resource Manager. If that does not solve the problem, go to step 2, below.
  2. Change the file name and folder names, removing non-safe characters. Use A-Z a-z . _ - and SPACE only for portability.

 

W4: Extension Missing

WARNING | Extensions | <Grass, Scatter, etc.> | Missing

Maxwell Render Suite may not be installed, or the Render Suite version may not be compatible by the current plugin. The plugin will still export MXS files, but they will not contain information pertaining to the extension.

Solution:

  • Make sure you are up-to-date. Reinstall the latest version of Maxwell Render Suite and the Maxwell for formZ plugin.

 

W5: Emitter on Face

WARNING | EditObjectAttributes | Object | Emitter applied to face; not supported: <object name, layer, and group information>

The object has an emitter material applied at face level, which is not currently supported.

Solution:

  • If emitter was applied by mistake, select the object with the Pick Tool. In Tool Options, Attributes tab, select a new Material from the swatch flyout menu. This will delete any face-level emitter assignments.
    OR
  • If intentional, Pick only the emitter faces, then select the Unstitch tool and click anywhere to detach them from the rest of the object. The resulting independent objects will render as expected.


W6: Scale Model

WARNING | Scene | Model Scale Enabled | Use of Model Scale feature may result in inaccurate materials and lighting.

The Scale Model feature makes it trivial to set up convincing architectural miniatures. However, as everything is miniaturized, lighting and materials may behave quite differently than you'd expect at full scale.

Solution:

  • If enabled by mistake, disable this feature in the Display Options palette, Maxwell renderer, Scene tab, Scale Model.
    OR
  • If enabled intentionally, don't worry about it. Quirks are part of the charm.

 

  • No labels