- User Since
- Feb 7 2019, 1:58 PM (18 w, 2 d)
Sat, Jun 1
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.
Fri, May 31
Wed, May 29
Fri, May 17
Hi guys, just want to know if this is still being work 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.
May 11 2019
Z scale is set to -1. Apply or clear scale, the modifier will work as expected.
Apr 25 2019
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).
Mar 13 2019
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.
Mar 12 2019
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?
Mar 11 2019
This is a duplicate of T61286
Feb 10 2019
Thank you! Hopefully this will get accepted soon.
Feb 7 2019
Must enable units.