Walk navigation don't use units from scene #69934

New Issue

Alberto Velázquez · 2019-09-16T10:29:15+02:00

2019-09-16 10:29:15 +02:00

System Information
Operating system: windows 10
Graphics card:

Blender Version
Broken: Blender2.81 16-9-2019

Short description of error
When I use walk navigation in a scene with units changed to cm and scale 0.1 the walk doesn't work correctly. Walk use same units 1, than default, not 0.1 If I change the walk aprameters in the preference windows it doesn't respect the units and 170cm is 17meters

**System Information** Operating system: windows 10 Graphics card: **Blender Version** Broken: Blender2.81 16-9-2019 **Short description of error** When I use walk navigation in a scene with units changed to cm and scale 0.1 the walk doesn't work correctly. Walk use same units 1, than default, not 0.1 If I change the walk aprameters in the preference windows it doesn't respect the units and 170cm is 17meters

Alberto Velázquez commented

2019-09-16 10:29:15 +02:00

Added subscriber: @AlbertoVelazquez

Philipp Oeser commented

2019-09-16 15:04:01 +02:00

Added subscribers: @WilliamReynish, @JacquesLucke, @lichtwerk

Philipp Oeser commented

2019-09-16 15:04:01 +02:00

Not sure I understand correctly:

Preferences > Navigation > Fly & Walk > Walk > Walk Speed is a value specified in absolute m/s
this setting is of type B_UNIT_VELOCITY
so setting the scene units to meter or centimeter has no influence here (and should not?)
so setting the scene Unit Scale to 0.1 (would make the default cube 20cm instead of 200cm) has the influence of walking 10 times as fast past that cube [Walk Speed is still in m/s]
to compensate for that, I would expect the user to set this to a 10th of that speed manually?
BUT, I can see that View Height / Jump Height compensates automatically.... true... (but this is of type B_UNIT_LENGTH)
so BKE_scene_unit_scale compensates for length, but does not for velocity (I think this is on purpose though...)

@JacquesLucke : velocity is excluded on purpose here, right?
CC @WilliamReynish

Not sure I understand correctly: - `Preferences` > `Navigation` > `Fly & Walk` > `Walk` > `Walk Speed` is a value specified in absolute `m/s` - this setting is of type `B_UNIT_VELOCITY` - so setting the scene units to meter or centimeter has no influence here (and should not?) - so setting the scene Unit Scale to 0.1 (would make the default cube 20cm instead of 200cm) has the influence of walking 10 times as fast past that cube [`Walk Speed` is still in m/s] - to compensate for that, I would expect the user to set this to a 10th of that speed manually? - BUT, I can see that `View Height` / `Jump Height` compensates automatically.... true... (but this is of type `B_UNIT_LENGTH`) - so `BKE_scene_unit_scale` compensates for length, but does not for velocity (I think this is on purpose though...) @JacquesLucke : velocity is excluded on purpose here, right? CC @WilliamReynish

Alberto Velázquez commented

2019-09-16 19:41:12 +02:00

I will try to explain better.

I have created this scene to test the problem

If I use the default 1.0 units, in meters, use the walk navigation and activate gravity (160cm in preferences) with Tab my pov look like this.

If I use 0.01 units, in cm, and I use the walk navigation and activate gravity (1,6cm in preferences) my pov look like this when the solution must be the same because the height in preferences is the same.

Other problems are generated with the change, like wrongs teleports...

I will try to explain better. I have created this scene to test the problem ![Blender_3.jpg](https://archive.blender.org/developer/F7751418/Blender_3.jpg) If I use the default 1.0 units, in meters, use the walk navigation and activate gravity (160cm in preferences) with Tab my pov look like this. ![Blender_2.jpg](https://archive.blender.org/developer/F7751420/Blender_2.jpg) If I use 0.01 units, in cm, and I use the walk navigation and activate gravity (1,6cm in preferences) my pov look like this when the solution must be the same because the height in preferences is the same. ![Blender.jpg](https://archive.blender.org/developer/F7751423/Blender.jpg) Other problems are generated with the change, like wrongs teleports...

Brecht Van Lommel commented

2019-09-17 13:46:10 +02:00

Added subscriber: @brecht

Brecht Van Lommel commented

2019-09-17 13:46:10 +02:00

In #69934#777009, @lichtwerk wrote:

so BKE_scene_unit_scale compensates for length, but does not for velocity (I think this is on purpose though...)

I don't think that's on purpose, and if it is, it's wrong to show one thing in the UI and then do something else. Fixed that part in c25f5a3.

> In #69934#777009, @lichtwerk wrote: > - so `BKE_scene_unit_scale` compensates for length, but does not for velocity (I think this is on purpose though...) I don't think that's on purpose, and if it is, it's wrong to show one thing in the UI and then do something else. Fixed that part in c25f5a3.

Richard Antalik commented

2020-01-11 02:26:46 +01:00

Changed status from 'Needs Developer To Reproduce' to: 'Confirmed'