Maxwell Render | Official public forum

• Maxwell Fire rendering may now be viewed directly in the viewport.
• Objects with no texture coordinates are no longer excluded from export.
• Right-clicking the Maxwell Fire button both opens the window and starts rendering.

• A crash could occur in Maxwell Fire when changing environment type.
• Maxwell_ExtractMaterials could fault in certain circumstances.
• Paths containing filename-like directory names could be parsed incorrectly.
• Objects with multiple sets of texture coordinates could be exported with only one.
• Displacement and Global bump were not reset when linking to an MXM file.

• (version superseded)

JDHill wrote:I have no way of knowing the core reason, but I can tell you what happens internally when you move an object (call it Object A):

- Rhino makes Object B, which is a copy of Object A
- Object B's geometry is modified to place it where you are 'moving' Object A
- Object A is removed from the document, and stored in memory in an undo list

So you see, after 'moving' Object A, it is not Object A anymore -- it is really Object B. That explains why moving can fix the problem. This seems similar to the issue which was fixed a couple of weeks ago, where Rhino was being too strict with mesh data.

That is why I ask you to provide your Log Viewer printout; once I know enough about the issue, and can confirm that what you are seeing is the same as what I am seeing, then I can ask the McNeel developers to check it out.

where can I get the log info for submission?

* line 13: OnLoadPlugIn, starting plugin update status thread
* line 14: OnLoadPlugIn, Enabling Scene events
* line 15: OnLoadPlugIn, Synchronizing cameras
* line 16: SynchronizeCamera, created camera: Perspective
* line 17: ShowWindow, sz=393x319h, loc=978,519(virtual), pWnd=66902
* line 18: OnLoadPlugIn, Plugin-load finished successfully
* line 19: ShowWindow, sz=700x320h, loc=400,400(virtual), pWnd=66902
* line 20: CheckForUpdate, checking for plugin updates...
* line 21: Run, the installed plugin version (2.5.13.0) is up-to-date.
* line 22: ShowWindow, sz=393x319h, loc=978,519(virtual), pWnd=66902
* line 23: Render, rendering camera: Perspective
* line 24: Render, generating new MXS meshes, press CTRL+ALT+SHIFT to cancel
* line 25: ExportGeometry, Exporting meshes...
* line 26: ExportStatus, mesh transfer 100.00% completed (1 of 1)
* line 27: listing errors - invalid objects:
* line 28: brep_object, id=1714ca09-3f33-45c0-86df-fcc988cb430d, error={ON_Mesh.m_N[1968] is not a unit vector (length = 0.169056).}
* line 29: errors were detected in meshable geometry - IDs have been listed in the log viewer. objects
* line 30: which generated the errors are now selected in the viewport (note: you may see nothing - it
* line 31: may not be possible to display some of them). if they later become unselected, and you wish
* line 32: to find them again, please try one of the following methods:
* line 33: - use the command: 'SelBadObjects'
* line 34: - use the command: 'Maxwell_CheckFixAndReportBadGeometry'
* line 35: - highlight the object's ID in the log viewer, right-click and choose 'Select Object'
* line 36: Render, total export time: 00:00:00.4760273

brep_object, id=1714ca09-3f33-45c0-86df-fcc988cb430d, error={ON_Mesh.m_N[1968] is not a unit vector (length = 0.169056).}