Not really. You can go into the SIlver BJ plugin and change the parameters around, but the voice commands invoke a whole bunch of changes and value change relays at once. For instance, "tip" changes the Top Chance only to 97%, the head pitch min and max change to something like -80 and -20 so she faces you more, the min range is set at 0.67, the min speed is set at 0.70, and the head fwd/bkwd is set to 0.3. The speed changes use VUML to get the current value and then add or subtract a value from that, and then use Action Grouper to execute the update on both plugins. The sliders can still be used to override some of the head pitch and min/max speed values, but the overall range and speed are best controlled with the voice commands. Voice control just takes the whole experience to another level in terms of interactivity, so that's become my focus in making scenes. If you have any kind of mic you can get the voice control to work unless you're dealing with another limit. I have used an external mic in desktop, and my Quest 2 mic works in VR.
Go to the Package Manager and scan for missing packages. Download all that come up. Looks like they are not in the VAR, but they are on the HUB for sure.
Oh that's a good tip. I've never had a problem with the voice controller, but maybe that's cause I'm always using it.
I'm glad you like it!
I have tested this a lot and I'm confident the commands work. What mode are you in? When you say "faster" do you see the Blow Me intensity slider go up?
Yes it's pretty much set up for voice command because it's soooooo much better that way. I got sick of pushing buttons and sliders, or of having animations that had repeating patterns and limited variations. This scene is so responsive and intuitive it will blow your mind, plus the plugins make every bj different. You don't have to speak that loudly though. I joke about that cause I think it's funny to imagine users (myself included) shouting blowjob commands, naked with nothing but VR headsets on and a robotic dick stroker wanking them. I could see Steve Martin in the role. I think if you had a headset with a boom mic that could go right on your mouth you could almost whisper. I can speak very softly into a good desktop mic when I am working on the scene so no one can hear me and it responds.
Yeah I cleaned up the meta file to get rid of some false dependencies. Once you install the scene, be sure to open the package manager, scan the packages, and then scan the hub for missing dependencies. Download all that come up. Rescan the packages and rescan for missing dependencies to make sure none remain and download any others that pop up. Rescan again if you had to download more, then open the scene. If anything is missing or broken, quit VAM and relaunch it. Reopen the scene and try again. Let me know if you have any issues.
vam startup error:
!> Exception during process of meta.json from package StyleMavin.Blow_Me_Suck_Me.4: System.Exception: JSON Parse: Too many closing brackets
at SimpleJSON.JSONNode.Parse (System.String aJSON) [0x00000] in <filename unknown>:0
at SimpleJSON.JSON.Parse (System.String aJSON) [0x00000] in <filename unknown>:0
at MVR.FileManagement.VarPackage.LoadMetaData () [0x00000] in <filename unknown>:0
package manager error:
!> Package StyleMavin.Blow_Me_Suck_Me.4 meta file is not valid
I noticed that too about "start again" needing two repetitions. I don't know why that is as I set it up to return the Timeline animation to the start. It seems to be a bug. As for the CPU usage, I just figured out that the lights in the Cyberpunk Apt asset actually emit light. Duh. That means you can turn off some or all of the invisible lights in the scene and simply adjust the existing lights in the apartment. That could reduce the CPU load. I tried it last night and I like the native lighting.
I see how that works, or doesn't. I don't understand WTF is going on with some of the dependencies for things I never added to the scene, like VAMx, or why the three point lighting setup that is part of vam flags as being an external dependency. I don't know enough about editing JSON to go into the package and edit the dependencies out. I looked at a tutorial and did my best on a previous scene and just felt frustrated. I may have to just update it and put back the 50 dependencies.[disclaimer: this is just my opinion and English is not my native language]
After quick glance/download, i just wanna jump in on "manual meta edit" subject also meta file is broken.
1) on actual issue:
You managed to broke meta file somewhere, missing bracket or comma (didn't feel like searching for it...).
Packagemanager can't process meta for any info (that includes client hub downloads) and dependencies section is broken
(it might load/work fine for you, if you still have unedited pre-package meta inside packagebuilder folder)
2) about manually removing dependencies:Code:vam startup error: !> Exception during process of meta.json from package StyleMavin.Blow_Me_Suck_Me.4: System.Exception: JSON Parse: Too many closing brackets at SimpleJSON.JSONNode.Parse (System.String aJSON) [0x00000] in <filename unknown>:0 at SimpleJSON.JSON.Parse (System.String aJSON) [0x00000] in <filename unknown>:0 at MVR.FileManagement.VarPackage.LoadMetaData () [0x00000] in <filename unknown>:0 package manager error: !> Package StyleMavin.Blow_Me_Suck_Me.4 meta file is not valid
There's really no point to manually remove sub-dependencies, it's just "placebo effect"
End users (or newcomers) still need to download those dependencies, IF they wanna remove "missing" errors (unless they are ok with messy client).
It's not like you removed dependencies from other packages (they still have those dependencies that you removed).
Think about it...
If you have let's say mypackage.var and you have referenced packageA, that A package uses packageB & packageC (as dependency).
Than yourpackage is gonna list A, B and C as dependency, naturally.
When you manually remove B & C ...and users download only packageA, guess what...packageA is still gonna require B & C to be downloaded (with startup errors).
That's why i call it "placebo effect", it only makes your package more..."appealing to end users" that still have to download everything (unless again...messy client).
Sure it takes less time than actually removing some dependencies or searching for alternatives with less sub-dependencies.
At the same time higher risk of breaking stuff while achieving almost nothing in return.
This is only my opinion about this nonsence... "just manually remove dependencies you don't need and you good to go"
