UE5, world to meters scale

General Feedback & Requests
, , ,
1

I’m using launcher install of the first official ue5 release.

Is there a known issue with the SetWorldToMetersScale node and ue5?

I just upgraded a ue4 project, and the node no longer works as expected. I can set the w2m in world settings, and it works on start. And I can set and retrieve the value from the SetWorldToMetersScale node at runtime (which I’m using to scale the controller meshes), but the scale isn’t being adjusted on the headset, despite being able to be read as changed…

There is a long lingering issue in previous versions of the editor, where the node won’t work in editor if more than one tab is open. But it seems that the feature won’t work at all now in 5, regardless of additional the tabs being open or closed.

Is anyone else having this issue? Can anyone else confirm?

*Builds Standalone fine. It’s PIE (play-in-editor) VRPreview related.

2

This is a big deal to me too, since I use this as a mechanic in changing the player’s size in the world. Would love to hear of a workaround…

2 Likes
3

@VictorLerp who would be the person to ask about this?

4

I’ve logged a bug, but I would suggest you doing the same. Otherwise it might not be considered significant enough to be addressed…

5

I did the same back when I posted this originally, haven’t heard anything back. I also posted a report when the bug was a multiple open tabs issue (prior to 5) as did other ppl and it was never resolved or really explained as to why it couldn’t be fixed :confused:

6

Out of curiosity, are you using Oculus? Wondering if it’s limited to the Oculus implementation (though I doubt it). I think I’m going to do a source code alteration once I track down the bug.

7

Yeah. Quest 2. For now I’m forced to do builds in order to properly test. If you find some workaround or fix please share it. I’ll do the same.

8

OK. Pretty sure I’ll be able to hack a fix in the source code, but it’d require you to build from source.

9

Quick fix for this (for Oculus): Make sure you have the Oculus plugin loaded and change the plugin XR API setting to Oculus Legacy. Warning though: this may change the orientation of your controllers…

image
image1466×454 39.6 KB

10

It’s a bummer that the fix you found is reverting back from the current dev path (openXR).

Is this giving you perfect expected working conditions? Or is it just bringing it back to the previous state where you had to have all tabs closed for WorldScale to function correctly?

11

Well, for me I have custom meshese tied to the hand controllers. In the new OpenXR scheme, the native rotation of the hand controllers are different. So using the legacy fixes that as well. But it postpones the inevitable. Hopefully it gives Epic time to fix the bug before I need to migrate.

12

Update, sort of. The previous issue of World to Meters Scale ( W2M ) not working from play in editor seems to only happen for me (ue5.0.3) when I also have a Widget Blueprint open as one of the additional tabs in my project. Other blueprints seem to not cause the issue. Weird, but hopefully that detail might help someone if it’s not just a issue with something specific on my end.

13

Test in ‘Standalone’ and it should work
Just did this in 5.1, I noticed the ‘VR Preview’ has the issue mentioned but ‘Standalone’ it works and doesn’t need a full package build to test

1 Like
14

I’m getting the same issue and I just upgraded to 5.1.1 from 5.0.3. I need to use play in editor because I will be doing some Live Link recording and I don’t believe that works in builds (or at least I have not tested that). Did anybody else get this working?

15

It’s finally fixed (for now) in 5.2.0

16

Continuing the discussion from UE5, world to meters scale:

In case anyone else is stuck on 5.1.1 and can’t move to 5.2 for other reasons, here is a hacky bit of code that worked for me, it seems that the WorldToMeters value isn’t getting read from the same place is is being set:

void UUnrealHelperFunctions::ForceWorldToMeters(float W2M)
{
if (GIsEditor)
{
for (const FWorldContext& Context : GEngine->GetWorldContexts())
{

		Context.World()->GetWorldSettings()->WorldToMeters = W2M;
	
	}
}

}