Control model status through VR

Question

question

Paulino SMH asked Dec 9, '22 Paulino SMH edited Dec 12, '22

Control model status through VR

Hello,

I would like to know if its possible to control the model status (reset, run, stop) through virtual reality with the headset on.

So far I have been able to control model logic following the VR Models that you provide without any problem, but when I try to control the model state I get some errors.

I think "OnPreDraw" is not the best place to insert this kind of code, is there any place I can move it to get what I am looking for?

Attached is a demo model showing the problem I am facing (VR Mode must be enabled).

TestVRControl.fsm

Thanks in advance.

Software Version:

FlexSim 22.1.1

virtual reality model control

1670576544135.png (96.4 KiB)

testvrcontrol.fsm (27.2 KiB)

Answer 1 · 2022-12-09T20:28:17Z

Jonah K answered Dec 9, '22 Paulino SMH edited Dec 12, '22

The simplest way I've found to control the model through the Oculus Quest is to set up a desktop view. Or you could make buttons/levers in the model environment that run/stop/reset the model when interacted with.

Set Up Desktop View:

When you're in the FlexSim model in your VR, press the Oculus home button on your right-hand controller. On the bottom toolbar, select Add Desktop Panel, then chose FlexSim. This should pull up the desktop view of FlexSim with all the model features available (Run, Stop, Skip, etc.). You can then quickly toggle back and forth between your desktop view and the VR view by clicking the Oculus home button on your right-hand controller.

Creating A VR Button to Run/Stop:

If you look at the Zombie game in the VR Demo Models, there are buttons and levers on a control panel. In the tree for this model, under MODEL:/Controls, you can see each of the buttons and lever objects. You could use these as templates to create your own button or lever to start/stop/reset the model.

I found that inserting this line of code;

onButtonPress(applicationcommand("run"));

in /RunSpeed/One>labels/pressCallback, allows you to run the model by pressing the "1x" button. Use these buttons as templates for creating your own button with the desired functionality.

1670617236028.png (610.2 KiB)

oculusscreenshot1670611317.png (1.6 MiB)

oculusscreenshot1670611027.png (1.5 MiB)

· 2

Joerg Vogel commented · Dec 10, 2022 at 06:45 AM

Because you loose the ability to perform an action in a model 3D View workspace once a model has been stopped in model run dashboard or by command, I suggest to do actions that comes near a reset. You can reset statistics in a model, you can update label and parameter values. BUT you won’t be able to benefit upon actions hitting a reset button like updating coupling data needed for some added new objects.

There doesn’t exists a running environment from which you control a model like you can do it from model run dashboard in a 3D model workspace. For this you are restricted to “setup up desktop view” of @Jonah Ks answer.

0 ·

Paulino SMH commented · Dec 12, 2022 at 09:47 AM

Thanks to both of you for the quick response.

The desktop view is a good alternative but in this case I would lose a bit of the inmersive experience I am looking for. I have also tried using applicationcommand("run") and applicationcommand("stop") but I get the same error with those commands (I was able to perform one action with the error, but if you try to chain start-stop commands the application stops working).

I was able to come up with a solution that works for me, if I use the refreshview() command after go() and stop() I get rid of the error, that command stops VR mode so I had to add the following commands to reenable it:

applicationcommand("switchviewvrmode", view, 1);
setvarnum(view, "vrmode", 1);

Attached is the demo model with the changes applied. To allow start, stop and reset I had to add the global variable ModelState, in the ModelOnPreDraw code I refresh the model state and link one action per button, in this case left trigger for run, right trigger for stop and B button (left controller) for reset (for some reason you have to manually restart the model after opening it for this code to work properly, in addition the model can hang if you don't wait a little between calls).

testvrcontrol_v2.fsm

0 ·

testvrcontrol-v2.fsm (28.1 KiB)

question