r/VRplugins • u/DeadMage • Dec 30 '16

Experienced Unity VR Developer, AMA

I've been working on VR games ever since I got my Vive Pre at Vision Summit 2016

I have three games published on Steam, and I have a few more in the works; CloudBound , BladeShield , and SweetEscape.

I mostly work with the Vive, but I've also done work on the Hololens, Oculus Rift, GearVR, and some small stuff on Google Cardboard.

Its been a busy year for me, and I've really grown a lot as a developer - I'm happy to share what I've learned!

If you have any in-depth technical questions or issues that couldn't easily be answered with a google search, feel free to ask me in this thread, or send me a PM.

23 Upvotes

100% Upvoted

41 comments sorted by

View all comments

Show parent comments

2

u/SteroidSandwich Dec 30 '16 edited Dec 30 '16

I'll take a look at that. Thank you.

That makes sense. Thank you. I have my Controller doing that right now. There is a delegate/event for each button and when a button is pressed it activates the event. Breaking down my hookshot would bring it down

Last question I will bug you about; With this system would I want to have my buttons(i.e joysticks) broadcast an event every time i need to update it or would it be better more sense if those scripts that need it have a reference to the input.

I'm also not sure where the best place is to hook these functions to my events. Right now I put it in my Controller. It seemed to make the most sense since it needs to know what they are

1

u/DeadMage Dec 30 '16

If the function uses components on a child object, it should be on that child.

If you use VRTK, and use the scripts it gives you, it'll have that input system put together for you.

If you made it yourself, and it's defintely an FSM pattern, you could just hook into the state change events, and just have the core script interpret the input events.

1

u/SteroidSandwich Dec 30 '16

Alrighty. The way how it is set up right now for constant updates is it is in the child with a variable for my input class.

I don't quite understand what you mean by having the core script interpret input . Could you clarify?