Home Creators Posts Import Register Favorites Logout

Content

 Enter this key into the main window of Virt-A-Mate to unlock the "Entertainer" content:

E55992

Comments

PixelPorts

how do you access the character customization tab?

MeshedVR

With the UI open look around the scene while touching A or X on Rift Touch, or touch thumpad on Vive. You should see some targets and icons. Look around for one that is a person icon. Point your controller at it and press A or X on Touch or press thumpad on Vive. That selects the person. Now in the UI you should see a whole bunch of tabs that control morphs, clothing, skin, hair, etc.

Skeeter Zymbal

The controllers track, but I can't interact with the UI at all. I can't even get past the loading screen!

MeshedVR

Try this fix: Run 'VaM Config (Run This 1st Time)' shortcut and hit play from there. UI interaction should now work. In future, you should only have to run the regular 'VaM.exe' to start.

Skeeter Zymbal

A/X Do not work, but the rift button does. The buttons work in other games.

Skeeter Zymbal

Oh, didn't see your response. I did run the config shortcut first, and I've run it several times since. Still doesn't work.

MeshedVR

Do you have SteamVR running? If so, exit it. Rift in OpenVR mode does not work as the button mapping is different between Rift and Vive.

Skeeter Zymbal

I closed Steam entirely and rebooted, then ran the config version again. No dice. How can I delete the config and start from scratch?

MeshedVR

You can try installing to another directory, but before doing that, can you look at this file: Release1.2/VaM_Data/output_log.txt. In it you should see things like this: VR device active is True Loaded VR device is Oculus Unity v2017.1.0f3, Oculus Utilities v1.15.0, OVRPlugin v1.14.1, SDK v1.18.0. Can you post back what you see in this file like the above lines?

Skeeter Zymbal

VR device active is True (Filename: C:/buildslave/unity/build/artifacts/generated/common/runtime/DebugBindings.gen.cpp Line: 51) Loaded VR device is Oculus (Filename: C:/buildslave/unity/build/artifacts/generated/common/runtime/DebugBindings.gen.cpp Line: 51) Unity v2017.1.0f3, Oculus Utilities v1.15.0, OVRPlugin v1.14.1, SDK v1.19.0.

MeshedVR

Wonder if Oculus broke something with latest runtime update. I haven't received the update yet because I have Unity active all the time while doing development and that prevents update. Let me see if I can get to SDK 1.19.0 and see if I have same issue.

Skeeter Zymbal

Is there any way to roll back to 1.18 on my computer? I already tried uninstalling and reinstalling oculus...

MeshedVR

Oculus does not support controlling which version of runtime you are running. They seem to update on their own schedule as well. I'm running 1.19 now and not having problems, so I don't think that is the cause of issue. I have made a small change for upcoming release in how I detect the controller mode that should be used (Vive or Oculus). That might help, but the old method should have worked as well. Can you tell me this - do you see a small red or blue dot when you point at the ready button? Do you see red/blue laser pointers coming out of controllers? And pressing A or X while pointing at it does not change the tint of the button? If I can narrow down I might be able to figure it out the issue.

Skeeter Zymbal

I do see a tiny, flickering red dot on the screen, but it's straight forward and distant, not close to the ready button. I never see any change in the ready button nor does it have a red dot or cursor on it. I DO see red and blue laser pointers from the controllers, as well as the red and blue balls of the controllers themselves. Pressing A or X (and all other buttons) does not change the tint of the button.

Skeeter Zymbal

Clarification: the tiny flickering dot is present regardless of the position of the lasers, and it's behind and to the left of the posed model.

Skeeter Zymbal

I uninstalled oculus entirely, and then went through and deleted the config files to make sure it was a clean install. After reinstalling oculus and testing it quickly with tilt brush, I then tried VaM again. I did run the Run This First version. Still had the same issue as before. The lasers are present and visible, but the cursors or dots are not. The closest thing is there is a flickering red point in the distance behind the model, but it never moves and isn't associated with the laser beams at all.

MeshedVR

I'm sorry you are having so much trouble. I think I'm going to have to build a special test application for you to debug this. I have reviewed all the code several times and I don't see anything obvious that would cause this.

Skeeter Zymbal

I'd be happy to give it a shot, especially if it's over the upcoming weekend. Weeks are a little tough for me. Probably not relevant, but here's a portion of the system summary: <a href="https://pastebin.com/1WFRY6cr" rel="nofollow noopener" target="_blank">https://pastebin.com/1WFRY6cr</a> This is the blessing and the curse of early access stuff....

MeshedVR

Wonder if you can post up the contents of VaM_Data/output_log.txt? I don't see anything odd in your system.

WIG

Is the 4$ please enough to create custom scenes?

WIG

Pledge not please lol

MeshedVR

With $4 (Entertainer) you can load other scenes/presets others make. With Entertainer, you could also modify existing scenes to your liking, but not fully save them. You can save character presets though - which saves poses and appearances. With Creator you get more options to mess around with (additional parameters, add new objects, etc.) and full scene save is included.

WIG

Nice one. I had a look last night. I back some similar VR apps on here but yours is superior and is more close to what I had hoped for. I am switching over and backing your project for 8$ Keep up the good work.

Jason Mitchell Ford

will there ever be voice understanding and responsiveness