VR Expansion Plugin

[mordentral]

@OneShotGG;750857

As the Weapon Master VR Dev, I would like to comment on ; the reason I did things the way I did is 1.) I am not yet comfortable with interfaces coming from an inheritance background and 2.) I didn’t want to “Copy” anyone’s logic and get in trouble (really worried about all the time). I assume for me to do what you wish I would have to make all of the events that pass on to the weapons generic and in identical to yours? What about variables passed through that you don’t current pass with your grip logic? I am actually looking at changing to interfaces when we do our multiplayer update (version 2.0) later year. When we get around to that would you be willing to help test the integration? I may even look into it for version 1.2 (1.1 is too close to being finished and released to go back to the drawing board).

I have mentioned in our thread that the best (current) way to combine Weapon Master and plugin is to uses plugins locomotion and our grab/weapon logic. I would like to make it clear that we have NOT integrated The OpenVR Expansion Plugin into our internal Weapon Master builds yet. Its something I really want to do but with about 20 features currently on the list of things to add, I simply haven’t had time.

Thats said our actual game will be an amalgamation of WMVR and OVREP. Your locomotion is just far superior to ours due to the hoops we had to go through just to implement the stuff we wanted through blueprint (Yay c++).

I think my biggest worry is to “step on your toes” in some way but if peeps really want it I am willing to make big changes to what we have to make it better. Including your idea for generic interfaces.

No, nothing needs to be identical to another system in order to be generic enough to be used by it, that wasn’t my point. My plugin isn’t the only interaction system out there that isn’t easily compatible with the gun (and other) packs out there.

All of the clip / damage / aiming logic can literally be the same, the issue is when the actual interaction is hard coded into things it isn’t flexible enough to quickly switch out. There should be fallbacks from the hard coded systems or direct methods to tie in without large re-writes.

IE: Giving clips a bindable event they fire off when ready to “dock” instead of actually performing it themselves or using any particular system, giving any system the ability to drop or correctly use the right logic on that occurrence. Its not specific to your pack either, I wasn’t trying to insult you.

Right now most of the VR stuff is “use it as is or recode it” and that limits a lot of potential for interchangeability (like using one melee system with another gun system with a custom interaction system that was in the project already).

Edit Missed the testing integration stuff and “Step on toes”

There is no stepping on toes here regarding my work, its open source and MIT and I don’t sell the plugin itself. Also I am more than willing to assist people in correctly using it when they have need