Set Navigation fly_speed in streaming kit app

My problem is that the WASD key movement is WAAAY too fast in my factory USD scene, so trying to follow the help here:
https://docs.omniverse.nvidia.com/kit/docs/omni.kit.viewport.docs/104.0.3/camera_manipulator.html
I’ve added this in my omni.usd.StageEventType.OPENDED handler

import omni.kit.manipulator.camera as camera
import omni.ui.scene as scene

        viewport = omni.kit.viewport.utility.get_active_viewport()
        manip = camera.ViewportCameraManipulator(viewport)
        manip.model.set_floats("fly_speed", [0.01])
        # scene.SceneView.model = manip.model;

setting the SceneView.model gives me all kinds of runtime errors, because, I guess, as the docs say, the model only supports ‘view’ and ‘projection’.
I’m not fully understanding how the pieces are plumbed together…
Any advice welcome!

[settings.persistent.app]
viewport.camMoveVelocity = 0.01

Thanks. That looked really promising, but has no effect for me. I found a bunch of similar settings in omni.usd_explorer.kit…

[settings.persistent.app.viewport.manipulator.camera]
flyAcceleration = 1000.0
flyDampening = 10.0
lookAcceleration = 2000.0
lookDampening = 20.0
moveAcceleration = 1000.0
moveDampening = 10.0
tumbleAcceleration = 2000.0
tumbleDampening = 20.0

I’m using .\repo.bat launch company.factory_streaming.kit -- --no-window to start my server, so I’ve altered the settings in that kit file and the company.factory.kit file.

I tried making several changes in these files…no difference. Do I have to rebuild or flush a cache? Is there a way to do this in code?

Well if you want to use it with “company.factory_streaming.kit” then that is where you must put the code in. I know it works because I use it with my custom apps. But it is not viewport manipulator. Just as I have given it.

Right: my problem was that the app loads a user.config.json file which had contradictory values…
C:\Users\user-name\AppData\Local\ov\data\Kit\Factory Streaming\0.1\user.config.json
It looks like the values in the .kit file initially set values here, but will not overwrite. I guess I can blow this file away.
Thanks for your help.

Yes try deleting that file and forcing the settings in at the kit template level

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.