Tutorial GameVibe Manual

Yes, we are on the same page. I meant new Vibe(s) - wheel lockup and, possibly, skid.

I will reach out to rF2 plugin dev - not muting the telemetry during pause is a stress for transducers and amp.

I have a question about Road Detail and Chassis vibes. I was able to make Chassis work fairly decently by lowering the lower bound. I followed tutotrial in post #2 and if I capture Lo the way it is suggested, I get pretty much no vibes for chassis. But anyway, I am unblocked on that one.

My question is: I set my Lo/Hi as you suggested, but it seems to me that Road Detail is the one I get kerbs and bumps from, and Chassis feels more like a road surface feel, and there's little to none feel of kerbs in Chassis vibe. I thought that sensations will be the opposite (based on post #2) - Road Detail will communicate road surface, and Chassis will be bumps. Could you share your insights on this? Or, maybe this is plugin/game dependent? Thanks!

Thanks @yobuddy with your help I was able to figure it out. 3D effect on chassis is really cool. Even though pointing out location of the vibe is difficult, 3D feels nice in action, feels like things happening around the car great surprise.

Do you happen to race with transducers? If so, could you maybe share your Vibe Creator settings for RPM, Gear Shift, Road Detail and Chassis?

Good luck with the move, wish you a smooth one

Now that I own motion system and transducers all neatly set up, potential move in the future is of my nightmares, really not looking forward to that

yobuddy, thank you for this awesome app and thank you value1 for the iRacing and RRE plugins.
All your hard work and talent is GREATLY appreciated!

I have a volume problem I'm hoping someone can help with.
While in iRacing or RRE the rear transducers for road detail are barely noticeable no matter what settings I try.

The 'volume balance test' produces even sound levels between FR, FL, RR, RL, all.
Collisions are set to 3D and FR, FL, RR, RL have the same volume levels.
Road detail is set to ALL and the rear transducers are very faint while the front are strong.
I tried every combo of 'front' and 'all' in the sound card settings.

So, collisions in 3D have same volume but for some reason 'All' does not like my rear transducers.

current setup:
- Win 10
- SimTools 2.4
- GameVibe 2.0
- iRacing plugin 2.0.3.2
- RRE 2.0.7.1
- 2 x 120 watt amplifiers
- 4 x 50 watt bass transducers
- 1 x pcie 5.1 sound card
- 1 amp for 2 front transducers and 1 amp for 2 rear transducers
- all drivers are up to date

The sound card is setup for 5.1 surround in win 10 and in the sound card's software:
- turned off center speaker and subwoofer
- set front and rear to full range speakers

I'm sure I'm missing something. Thanks in advance for any help.

Gary

Thanks for the fast reply.

There is no distance setting and I verified all the correct speaker settings again in win 10 and the software.

Not sure this has any bearing but I have SimHub for rumble pedals (gas = wheel slip and brake = wheel lock) and tried the bass shaker option and my rear did not work until I set them to channel 5 and 6 in custom settings.

For me, road detail is not that important, the 3D collision tuned for curbs, bumbs, etc is my immersion sweet spot, but I'll keep testing various settings.

I found the speaker volume adjustment in the sound card's software but the rear are still not felt for 'road detail - ALL'.
Will keep trying various setting... i'm convinced the right combo is in there .

I can't for the life of me get the vibe signals to work while playing anything in Oculus Rift S. If I play on a virtual desktop in Oculus it works but not in full VR mode. I have done several searches and re-reading of guides but no luck. Any ideas or probably something I am missing?

edit: I have actually only tried Project cars 2 and DCS since they are the only ones I really ever play. Once I get all of this working I plan to play several other titles.

Looks like the DCS plugin is not set up to send any data to Vibe so that is big bummer. If I was smarter, I would totally offer to help develop something for it. So for now I am focusing my efforts on Project Cars 2, which should work.

I think you are right @yobuddy because the music that plays in the Oculus "home space" will play music through the HDMI cable to the headset just fine when I am testing the vibe settings. As soon as I launch a game in VR mode is when it goes down hill. If I launch PC2 in desktop mode and then go into Rift and run the virtual desktop it works fine.

Another thing I find odd is that I can't get my Sound Blaster Z card to isolate channels correctly, but I still have a few things to research and try on that front before I start asking for help there.


If anyone has vibe and Oculus running together correctly would chime in I'd love to know how you have your audio devices set up.

How do you detect lack of channel separation?

Just FYI, I just changed my card for Vibe to Sound Blasterx EA-5, which has pretty high end specs, but when I run sound check in Vibe, I see amp lights of channels that should be off indicating some (tiny) signal. I am not audio hardware engineer, but my guess minijack itself allows a bit of leak. Just thought I'd share before you throw money into hardware.

Hi @yobuddy,
I changed my audio card in hope of resolving crashes (previous one was no longer supported by Creative). But I still get GV crash sometimes:
Application: GameVibe.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.AccessViolationException
at <Module>.CoCreateInstance(_GUID*, IUnknown*, UInt32, _GUID*, Void**)
at SlimDX.XAudio2.XAudio2..ctor()
at XAudio2_GameVibePlugin.GameVibePlugin.PlayNote_GameVibe(IntPtr, System.Guid)
at GameVibe.MyAudio.Note.PlayNote_GameVibe(IntPtr, System.Guid)
at GameVibe.cls_ActiveNote.CreateNoise()
at System.Threading.ThreadHelper.ThreadStart_Context(System.Object)
at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)
at System.Threading.ThreadHelper.ThreadStart()

I completely understand you can't reproduce this issue, and it is most likely some combination of things specific to my PC, but I still hope you could keep this thing in mind for the future. I went to complain on SlimDX github but last contribution there was 8 years ago, so it is getting quite outdated...

Cheers!

PS: my previous diagnosis was incorrect, I have no idea what causes crash to reproduce

There's nAudio library https://github.com/naudio/NAudio that we use in Crew Chief, but to be honest we've seen situations when it does not work well (default .NET audio is most reliable and lightweight, but is not flexible at all, it won't work for GV). Upside is that nAudio is newer than SlimDX. But I understood your point - if I am not happy with SlimDX, I'll have to implement plugin myself, because SlimDX works for most people. And yes, problem is startup, there's something wrong there.