• Hi Guest!

    We are extremely excited to announce the release of our first Beta for VaM2, the next generation of Virt-A-Mate which is currently in development.
    To participate in the Beta, a subscription to the Entertainer or Creator Tier is required. Once subscribed, download instructions can be found here.

    Click here for information and guides regarding the VaM2 beta. Join our Discord server for more announcements and community discussion about VaM2.
Connect

Plugins + Scripts Connect

Download [0.74 MB]
Ok, got it working. Very cool project! I guess the next feature to add would be for the connectaudio app to be able to receive the name of the config to load as a server command, and then pull that file from the relevant .var and load it. Having to manually load a profile for each scene seems too cumbersome.
 
Well, the assumption is that you use it with VR. In the Oculus software you can set which audio device to use for regular VaM sound, so you can set it to something different that whatever your Windows default is.

If you want to be able to change the audio device within ConnectAudio, you can add something like this to the StartAudio() method in MainWindow.xaml.cs. Obviously you could also build UI and what not...but this is the quick and simple version:
C#:
private void StartAudio()
{
    StopAudio();

    int deviceNumber = -1;
    for (int i = -1; i < WaveOut.DeviceCount; i++)
    {
        var caps = WaveOut.GetCapabilities(i);
        if (caps.ProductName == "Speakers (Realtek(R) Audio)")   // <--- run once to get devices names, then put your favorite device here and recompile
        {
            deviceNumber = i;
            break;
        }
    }

    Log.Message("Available audio devices:");
    for (int i = -1; i < WaveOut.DeviceCount; i++)
    {
        var caps = WaveOut.GetCapabilities(i);
        if (i == deviceNumber)
            Log.Message($"{i}: {caps.ProductName} <= CHOOSEN");
        else
            Log.Message($"{i}: {caps.ProductName}");
    }

    WaveProvider waveProvider = new WaveProvider(myWaveManager);
    myAudio = new WaveOutEvent();
    myAudio.NumberOfBuffers = 2;
    myAudio.DesiredLatency = 60;
    myAudio.DeviceNumber = deviceNumber;
    myAudio.Init(waveProvider);
    myAudio.Play();
}
Thanks for working on this. I sometimes go hard into trying to use and create with VAM, but fizzle out shortly after. My last post was one of those times, and I only now have returned to see your reply.
 
I'll second senorgif2's request that choosing the audio output is an important feature. I wanted to try this, and had to spend a while trying random things before coming here. I'll try the code change and see if that works.

Edit: Update for anyone else trying this out: The code MacGruber posted works and I was able to set it up with my preferred output device.
So i saw the solution, and managed to get a new build (despite my extreme lack of knowledge) that shows all the audio devices and the one that is chosen, however, it still outputs sound to the wrong device. What did I do wrong?

EDIT: I figured it out
 
I haven’t had a chance to set this up and play with it yet. Is it possible to sync estim outputs with thrusting? For example, the deeper the thrust the higher the power, ramping up and down with the movements. From the description of the plugin, I am having a hard time understanding what dynamically modifies the power output of the device as a scene plays out.
 
Is it possible to sync estim outputs with thrusting?
Sure, its a Trigger. So you can trigger it at any time that makes sense for you. For example trigger it from the Timeline (or other) animation that does your thrusting? Combination of ValueUpDown (for driving animation of Timeline or AnimationPattern) and ValueThreshold (for triggering Connect) bricks from LogicBricks also comes to mind. Don't forget to look at the demo scenes that come with Connect (separate VAR package)


I am having a hard time understanding what dynamically modifies the power output of the device
You set the intensity via trigger, e.g. BLIP;i=0.7. Intensity is just the volume of the audio output. So, 0.7 here would mean at 70% position between the min and max volume you set for the "BLIP" behavior. And because its just in the trigger string, you can set it for every individual trigger if you want.

Also you can add more behaviors in the APP of course. Different waveforms/parameters can feel more/less intense. Depends a lot on your E-Stim device and potentially your PC's sound chip. Expect having to experiment a lot.

Probably read the ConnectAudio PDF manual that comes with Connect.
 
Back
Top Bottom