Author Topic: Changing Bloom/Glare/Vignetting is breaking CameraMod overrides  (Read 1457 times)

2017-03-17, 11:46:59

alexyork

  • Active Users
  • **
  • Posts: 745
  • Partner at Recent Spaces
    • View Profile
    • RECENT SPACES
On 1.5.2 here with max 2016.

I'm finding that occasionally, but not always, when using a cameramod which is overriding things like EV and tone mapping, but NOT Bloom/Glare or Vignetting, I set a render off and all is fine. But in the VFB if I then start playing with Glare/Bloom or Vignetting suddenly the CameraMod will become ignored (but still enabled on the camera) and the VFB will override EV/Tonemapping, and image is effectively zero'd out, or with a bunch of misc values. If I re-render everything goes back again properly and the cameramod once again kicks in, with the VFB tone mapping greyed out as it should be.

I have reinstalled corona twice, including once by manually removing everything as per your guide online.
Alex York
Partner
RECENT SPACES
recentspaces.com

2019-01-13, 15:49:16
Reply #1

Ondra

  • Administrator
  • Active Users
  • *****
  • Posts: 9048
  • Turning coffee to features since 2009
    • View Profile
since CameraMod is deprecated, we will not be investigating this
Rendering is magic.How to get minidumps for crashed/frozen 3ds Max | Sorry for short replies, brief responses = more time to develop Corona ;)