Jump to content
AutoDesSys Forums

pylon

Moderators
  • Content count

    797
  • Joined

  • Last visited

  • Days Won

    59

pylon last won the day on February 27

pylon had the most liked content!

About pylon

  • Rank
    Moderator

Profile Information

  • Gender
    Not Telling
  • Location
    Los Angeles
  1. pylon

    Fire stopped working

    It could be something to do with the specific file you are attempting to render. If you try with a new project with a simple cube, do you experience the same issue? If so, it's likely that something is amiss in your default project template file (in which case, you would want to rebuild your template file from the default formZ template.) Hope this helps.
  2. Hi Allan, For test renders, we created the "Scale" control. It enlarges / reduces your specified image size at render time, maintaining proportions. As Des says, set it back to 100% for your final rendering. http://support.nextlimit.com/display/maxwell4/formZ+%7C+Render+Options+%7C+Image Regarding the crash in Studio, have you checked your plugin log after export for warnings? If there are warnings about the presence of illegal characters in formZ entities, fix those first and see if this resolves the issue.
  3. Hi David, Manual re-linking with the Maxwell Plugin should almost never be necessary. Use the plugin's Resource Manager to specify folders on disk to search for any missing dependencies. http://support.nextlimit.com/display/maxwell4/formZ+%7C+Resource+Manager
  4. Hi Peter, Glad to hear that opening with the correct app version worked.
  5. pylon

    Decals are not rendered

    Hi, Decals are a feature of the Renderzone plugin; other renderers are not aware of their existence if applied with the renderzone tool. For decals in Maxwell, use stacked layers with layer blending set to "Normal" http://support.nextlimit.com/display/maxwell4/Stacking+Layers
  6. Hi, 1. That list selector is only used for editing the representation-specific parameters of the selected material. At render time, the representation for the chosen renderer will be used. 2. I recommend re-installing formZ 8.6.0.2 3. What was the problem in InDesign? What did Adobe say to do about it? 4. In your system preferences, do you have the ability to switch between the "Default macOS graphics driver" to "Nvidia Web Driver"? If you switch this, then reboot and regenerate the previews, does it make any difference?
  7. There is definitely something mysterious going on in your Material parameters preview, but there's nothing wrong with the full scene you posted: it's simply overexposed. You have a set up a full daylight scene, including both a physical sky and an extremely intense softbox, and your exposure is set to f4, ss 200, iso 100. Too much light is accumulating on the virtual sensor. If you switch the exposure preset to "Bright Exterior", you'll get this instead: Please see: http://support.nextlimit.com/display/maxwell4/Camera (The material hints are simply different interpretations of the basic "Shaded" parameters; it's expected that they will look different, otherwise there would be no point in having multiple hints.) If you temporarily remove your formZ preferences, relaunch, and regenerate the preview, does the preview look correct? (e.g., rename /Users/$USER/Library/Preferences/autodessys to autodessysX )
  8. Hi Theo, Your materials appear to be illuminated properly when I regenerate the preview: Are you using formZ 8.6.0.2 and Maxwell 4.2.0.2, or some other versions? Did you try restarting formZ and generating new previews in the exact file that you posted here? Have you tried with a new project, and used the "add-to-project" option to add in these materials? If you make a brand new project, and make a realistic match material, do the previews appear illuminated correctly?
  9. Can you please send a simple formZ project file that contains a couple of these materials? (I am unable to reproduce this, but perhaps your file will help.) Does this happen with materials other than Realistic Match? The thumbnail scene is embedded in formZ; there's no way for the user to change it.
  10. Hi Craig, The Maxwell plugin itself doesn't store any textures, so my guess would be that formZ embedded the textures for the Shaded representation of each material. Maybe make sure the 'embed' preferences are set correctly, make a small change the the project, and save again?
  11. pylon

    Broken plugin UI

    Hi All, This issue (unresponsive Maxwell buttons on Windows) has been resolved in formZ 8.6.0.2. Please make sure to update your formZ installation.
  12. Hi All, This issue (unresponsive Maxwell buttons on Windows) has been resolved in formZ 8.6.0.2. If you experience this issue, make sure you've updated your formZ installation.
  13. pylon

    Maxwell Softbox Light never hide from Camera

    Hi Theo, Thanks for sending your file. It appears that there is an issue with hidden emitters when Multilight is enabled AND the Denoiser "Accurate" setting is in use. If you set the Denoiser Autoconfiguration to "Fast" instead, the problem should disappear. (Side note: you will get faster renderings with Multilight disabled, and your Threads parameter set to 0 )
  14. pylon

    Maxwell Softbox Light never hide from Camera

    Hi Theo-- right, that's what I meant. I clarified my post above.
  15. pylon

    Maxwell Softbox Light never hide from Camera

    If you mean that the Maxwell render application crashes when saving an image from an MXI: Next Limit has fixed this internally. A new version will be released very soon.
×