- Messages
- 1,394
- Reactions
- 5,741
- Points
- 173
- Website
- github.com
- acidbubblesanon
- Patreon
- acidbubbles
Finger recording only works with Leap Motion. I don't think I'd be able to add Quest 2 support in VaM 1.x :|
Is there any plugin to make CUA hide in player camera?@linshimajia123 right now it's not possible. First, the CUA is "unrelated" to the person atom per se, second as far as I know there's no alpha that I can use to switch visibility. Clothing-based hair should work though.
No, I did not... this is very weird and probably something stupid, but I can't reproduce and my only idea (controller deadzone) would result in slow spinning, not super-fast spinning. This is a good clue though, I'll take a look again.
Dunno if it helps, but when I had the spinning issue I found that it was because the model I possessed was set to look at the user. When I changed the target of their vision to something else, the head stopped spinning. I had used the default settings of the plug-in, so I dunno if there is a setting to automatically change the target of their vision or if it was just because I had used it in old scenes that weren't made for embody.No, I did not... this is very weird and probably something stupid, but I can't reproduce and my only idea (controller deadzone) would result in slow spinning, not super-fast spinning. This is a good clue though, I'll take a look again.
It"s doing it by default, I tried different settings and different version to try point on something, but I cant find anything.. it's doing it from "Passenger.4" to "Embody.58" even when "POV" is already included in scenes.@Ged366 normally the pitch should work using the stick, but I think my code is wrong and it doesn't actually do that I'll add to my list to check and try and fix it (I have a pretty large backlog so it might not be right now). I'll also check for that bug, if you can share the exact Passenger settings you're using it would be nice... I'll try and reproduce too when I can. Thanks for the report
@look4you I don't have any rotation limit per se? What do you mean? When using the joystick of a gamepad using Embody?
I use plugin presets all the time. I can't speak to loading a path inside a single plugin, but you could try having several instances of the Embody plugin that each contain the settings you want and then trigger them on and off. I know VAM will save the Embody settings when using plugin presets as a whole group. Maybe not ideal for keeping your plugin list concise, but should get you around your current dilemma. Unless VAM doesn't like multiple copies of Embody. I fully admit I haven't tried it."Bug report" of sorts:
I cannot, for the life of me, work out how to trigger the loading of a custom Embody-preset via VaM's trigger system - I know the trigger-actions, I've tried them all (LoadPresetWithPath, or the two-trigger combo: Setting the PresetPath via text-trigger & then having a second one trigger the presetload), in various combinations, with and without "reinitalizesmthsmth".
Only way I can successfully load a custom preset is via the GUI. And the pre-defined presets can be controlled via external triggers just fine, ofc (Improved Possession, Passenger (FreeLook) etc). But not the loading of custom presets.
Am I doing smth wrong? Does it maybe only work when Embody is active AND VaM is in playmode? Do have to wear a special hat?
Or smth?
Could you please have a look at that? It's a common enough usecase to switch between different custom presets during one scene - it would greatly enhance useability if that could be done with VaM-triggers (or JayJayWon's UIAssist), rather than fumbling through VaM's bloddy GUI and then fumbling through Embody's (not-so-bloody) GUI.
---
"Feature request" of sorts:
The internal "OnActive" triggers are great - but their usability is significantly reduced since there's no possibility of saving them. Afaics, they don't get stored in the custom presets, and they're not visible to triggers & plugins. Afaics, they do get saved with the scene - but it's a bit of a hassle having to set up the same exact three triggers every single time I work on a new scene (dunno if they get stored in plugin-presets, but that would be a highly inconvenient - successfully merging different pluginpresets is ... not trivial ... due to the way VaM references them by the order in which they were loaded)
Any chance you might have a think about that?