Skip to content

MoonRay for Modo 0.3.51.1

Pre-release
Pre-release

Choose a tag to compare

@Pbaroque20 Pbaroque20 released this 11 Oct 05:59

Native Windows experimental release for Modo 16.1v9. This is 0.3.51 with fixes to Draft and Stop in the preview window. Download the kit and the windows-runtime ZIPs and follow INSTALLATION.md; the content ZIP is optional and adds MoonRay's ten example scenes to the asset library. All three unpack to a MoonRayForModo folder; merge them into one.

If you already have 0.3.51, only the kit ZIP is different: the runtime and the content are the same.

Fixed since 0.3.51

  • Draft switched off before anything had been rendered left its outlines on the dark ground, and the raw line picture (white on black) could then be shown as if it were a render, most easily by changing the preview engine. The window now shows no picture until one is rendered, and a draft's lines are never taken for a render or kept as one.
  • Stop during a draft's lines no longer goes on to render the draft's region.
  • A render asked to finish with what it has is stopped outright if it does not answer within a few seconds, so the window cannot be left waiting with the button reading Stop.
  • In Draft with no region, the status line says again to press Region and drag.

New in 0.3.51

Everything in 0.3.51: Draft and Region, Safe Denoising and Continue, the fur extras, the picture asset library with MoonRay Content, MoonRay's materials in Add Layer, the MoonRay page in Preferences, and the MoonLightIPR preview's hair, skin, volumes and light filters. The full list, with pictures, is in What's new in 0.3.51.

What was checked

The fault was reproduced by script in a separate test copy of Modo (Draft on with nothing rendered, engine changed, Draft off, engine changed, Render) and the same steps pass with the fix; the Draft with engine changes after a render, and Draft with a region, were run again and pass. The packaged kit and runtime ZIPs were unpacked into an empty folder and passed the release check (tools/check_release_package.py). The report that Render then showed nothing new was not reproduced on its own; the fixes above remove the states that could have caused it. One machine, as before.