Thank you! That was fast!

This is weird. Could this be a driver problem then? I'm still having the same result on the release build and master. Let me know if I could provide more info to help identify the problem.
Thank you!

That maybe from a developer point of view, but for end users with no knowledge of the inner workings of Eevee nor OpenGL this seems counter-intuitive and confusing especially when one configuration works and the other doesn't despite it having a simpler configuration. With that said, of course any optimisation would be welcomed and greatly appreciated.

Hi guys, just want to know if this is still being worked on? I would really like to jump on the 2.80 wagon, but the lack of unit display makes modelling really hard at the moment.

Z scale is set to -1. Apply or clear scale, the modifier will work as expected.

I have the same issue with build 19-04-25 (905f2d84af4d). N or T does not work even after loading factory settings or changing keymaps (default, 2.79 or industry compatible).

Thank you for the clarification regarding unit scale, I come from an architectural background where specifying everything in mm is quite normal. Typing in 25 instead of 0.025 is faster and significantly less confusing. I mainly use 0.001 unit scale in 2.79, where that's the only option you have if one wants to use mm. I never imagined it would have an effect on precision.

Forgive me if this sounds ignorant, but it just seems weird having to have separate settings on the same scene with a different unit scale. Am I right in thinking that the underlying problem here is that lights don't use the unit system yet as mentioned by Brecht? And this goes away once it does?

This is a duplicate of T61286

Thank you! Hopefully this will get accepted soon.

Must enable units.