Light Functions Broken After Switching To MSAA?

I just converted my project from 4.13 to 4.14 and switched to MSAA as my anti-aliasing method. Now it seems all my light functions aren’t showing up. Switching back to Temporal or FXAA doesn’t help.

I tried setting up a new light and new material with no luck. Light functions seem to work if I make a new project and switch to MSAA.

Hi Jejunus,

I’ve not been able to reproduce this on my end when converting a project from 4.13 to 4.14 or even just a 4.14 project.

  • Have you enabled Forward Shading via the project settings for this project before converting? As a note, MSAA is only supported for Forward Shading.
  • Did you enable MSAA in 4.13 before converting?

Since you say this issue isn’t blocking you in a newly created project, you can try deleting the intermediate and Config folders in your project folder. This could clear some possibly corrupted information and when the config folder is deleted this will reset any setting you’ve set in the project settings or editor preferences, but it possibly a way to resolve your issue. You don’t have to delete necessarily, you can simply move to another folder if you intend to move these back after checking.

-Tim

Tim,

Thanks for your quick response, sorry I didn’t get back to this sooner.

Still not working, and now I can reproduce in a new project. I narrowed it down to simply enabling forward rendering. In my existing project I deleted Intermediate and Config. After rebuilding, I confirmed that Light Functions were working. Once I enabled forward rendering, restarted and let the materials recompile, the light functions weren’t working anymore.

In a new project all I did was:

  1. made a new map
  2. added a light
  3. assigned the light a light function material and confirmed it was working
  4. enabled forward rendering in project settings (aa still temporal/default)
  5. restarted
  6. light function material no longer having any effect on light

Any ideas? Thanks for your time.

—j

Just saw “Light functions and IES profiles” as being NOT supported by the forward renderer in the 4.14 release notes. I don’t know how I missed that! Case closed I guess.