PlayMaker Help & Tips > VR Help

[SOLVED] SteamVR Action Stack Overflow?

(1/1)

LordHorusNL:
I'm having a problem with the new SteamVR 2.0 asset, i was working on some new actions and with the last version they worked just fine. However with 2.0 i'm getting a stack overflow and editor lockup/crash when selecting one of the default boolean actions.

The stack overflow happens after selecting the default SteamVR action "GrabPinch" in the active state/action and then right clicking on one of the transitions in the fsm.

Not sure if this is a PlayMaker or SteamVR problem, thought somebody might know?



https://imgur.com/OLbumVL

tcmeric:
Hi, who did you buy the actions from? Also, steam v2 is not backwards compatible with v1, so I believe those actions would need to be rewritten.

Here is the last copy of version one, in case you need to roll back: https://github.com/ValveSoftware/steamvr_unity_plugin/tree/v5

This is Version 1.2.3.

LordHorusNL:
I'm not talking about the actions for the previous version of the asset.

I'm working on my own set of actions specifically for SteamVR 2.0.

However since the last update for 2.0 they changed the type of input for the SteamVR_Action_Boolean to a drop down menu instead of drag and drop.

This is when the stack overflow started happening, in C# it works just fine.

It's a very broad question i know, i just thought somebody might know why this kind of overflow would happen.

I've tried changing the input to a normal FsmObject and then converting this to the SteamVR_Action_Boolean. Without much luck ;D

tcmeric:
You would need to contact the asset creator, which is not playmaker.

LordHorusNL:
Never mind, i got it to work eventually. The solution was to use an FsmObject and cast that to SteamVR_Actions_Boolean.

If that makes sense ;D

Thanks for the response.

Navigation

[0] Message Index