This is a thread for group discussion of the new "Beta II" release of Vendetta Online for GearVR.

If you are not currently participating in this beta, please do not post here. This is just for feedback from Beta participants and the developers.

To avoid this thread becoming excessively huge and difficult for us (the developers) to parse for information in a useful way.. probably keep "discussion" to a minimum, maybe just critical questions if needed. In general, this is for two things:

1) Experience related feedback. Areas that are confusing, unpleasant, uncomfortable, or generally negative.

2) Genuine bug-related issues. Crashes, lockups, UI elements getting stuck in the wrong place, anything that is clearly a problem (and likely a bug).

Please also keep these caveats in mind:

- Frame-rate performance is variable, and not always perfect. This is a pretty heavyweight MMO with unpredictable content, running on a mobile phone that has a tendency to overheat. So, it may occasionally get a bit slower than we would like. 90% of game content is 30-60fps, but don't expect a giant Deneb battle to be fast. Still, please report any really horrible slow-down problems.

- If you participated in the "first" Beta I process, avoid running the "old" GearVR version. It may be particularly confusing if you install the Play Store version, as that will cause Oculus Home to think the "old" GearVR version is now installed. Do not "Update" the original version, and do not run it, or it will overwrite your Play Store version. We cannot remove the "deprecated" app from the Oculus Home or the Store.

First this is awesome. So glad for separate clients. Really looking forward to testing this more.

A few questions...

Does this being on the forums mean the NDA is no longer in effect?

Can we use the android forum to post discussions between testers so this thread doesn't get cluttered?

Is the VR client still LUA? I suppose the point is, will we still be able to write plug ins for it?

Would any current android client functional plug ins carry over to the VR client? Would it be worth testing them one by one, or is it possible for you to give a blanket yes or no?

Looking forward to strapping on the headset and getting exploded repetedly!

Plugins were working for the previous version. Installation is the same as with the Android version.

And the NDA question is a good one. Can we talk freely here being that this is publicly viewable? I'd like to post my previous feedback for people to see and discuss.

So, basically, I'm relaxing the non-disclosure to allow group discussions within the testing userbase, but I'd rather you just kept it to the Android forum of our messageboard until the game is actually released.

Ie, maybe don't go wild on Facebook or anything just yet.

Yes, if you want to create other GearVR-specific testing threads on the Android forum, for more general discussion, that's fine. Just make sure they're clearly flagged "GearVR Testers Only: (Topic)" or something like that.

We may eventually add a general "VR" forum, and I may move the threads at that time.

I got yesterday my key and now have a question - i redeemed the key in oculus, but there is no game client for vendetta online in my list. Is this normal and i have to wait till its published, or is it a error from my side and the game client should popup on my device in the oculus app?

p.s: sorry for my bad english

EDIT: found it now, it was just a bug on my device..downloading it now & report back if i find bugs & have feedback.

On my Galaxy s7 and gear vr it froze when i first connected ipega controller but not since controller works well. Enabling voice chat causes game to stop, voice would be handy as typing is a pain with goggles. Thank you for providing yet another platform.

PS do We get a badge for being betas?

That's odd that your voice chat is causing a problem. Could you try it again? I just enabled it on my S7 with retail GearVR and had zero problems.

There is no beta-badge for GearVR testing (or Rift testing, which has been going on for years). Just the knowledge that you're making the game better :).

Appreciate the opportunity to test the Gear VR first off. I noticed that the on screen keyboard doesn't function without the UI tracking enabled while using a custom controller setup for the Moga Pro (Select button) as chat to channel. It freezes the ships HUD with the onscreen keyboard for a few seconds but doesn't allow the user to type. Really the only inconvenient glitch I have come across.

Thanks again good work btw and hope to see more detail on cockpits in the future. =)

Galaxy S6 with moga pro.
When your in the menus selecting missions and then select launch, the game resets the forward viewpoint to the right menu position. So you have to turn your body to the right to compensate or continually access the advanced menu to re-calibrate the display.

One thing bugging me is the inability to rebind the "A" button (on Samsung Galaxy S7 Edge, with a MadCatz LYNX3 controller). No matter what I bind it to, it remains as "Toggle F/A Mode" (the default bind for it).

Use a bt keyboard to erase the bindings and use the gear vr touch pad to set as LMButton than try the A button on the controller. It worked to allow me to set it as Turbo on my moga pro. Touch pad = LMButton. But for some reason so is A on the bt controllers.

Faille Corvelle, are you setting the bind and then pressing the 'OK' button in the keyboard settings menu?

Related to keybinds:
On my Moga Pro Power I have a default binding that requires two buttons to be pressed together (I forget which as I dont use it often). Ive tried binding actions to a "double key press" like that and it only recognizes whichever key is hit first. Can we make this a thing? That would be a very helpful feature for use with controllers and VR. It would hugely increase the number of shortcuts we could use with just the controller.

It accepts the bind in the controls menu, ray, and all other rebinds work. I've tried rebinding F/A first, then A, as well as binding A, then rebinding something to F/A. In all instances, all other binds are applied, but the A remains "perma-bound" to F/A.

It may be unique to the LYNX3. I will investigate further...

EDIT:
Further investigation has revealed the cause. The primary button counts as LMBUTTON and "Button A", so LMBUTTON remains bound to Toggle F/A.

On a different note, I tried using buttons as triggers and discovered "Chords". Can these be disabled? On my small controller they be pretty annoying.

whats a chord?

2 (or more?) buttons pressed at once. For instance, X+Y opens a help screen, B+Y opens cargo, etc. Means if I have trigger 1 on B, trigger 2 on Y, I open cargo when shooting...

How'd you set those? Ive tried before and couldn't get it to work on my moga pro

The two I mentioned were set by default. What we really need is a way to clear all binds to given function (or is there a way to do so that I don't know of?).

I agree. I haven't seen a way to clear them yet. I've got certain buttons that are locked into a function and I cannot change them.

Also, I can't see how to use the voice to text chat option. I don't see a setting and enabling voice chat didn't give me any new options on the chat screen or virtual kb

EDIT: Found the issue. I had to update the actual VO VR client in the Oculus store. I have the microphone button on the virtual KB now, but i click it and get "STT Error" and something about a network error? Tried it with voice chat enabled, disabled, push to talk and not push to talk.