Community Q&A

Welcome to Audiokinetic’s community-driven Q&A forum. This is the place where Wwise and Strata users help each other out. For direct help from our team, please use the Support Tickets page. To report a bug, use the Bug Report option in the Audiokinetic Launcher. (Note that Bug Reports submitted to the Q&A forum will be rejected. Using our dedicated Bug Report system ensures your report is seen by the right people and has the best chance of being fixed.)

To get the best answers quickly, follow these tips when posting a question:

  • Be Specific: What are you trying to achieve, or what specific issue are you running into?
  • Include Key Details: Include details like your Wwise and game engine versions, operating system, etc.
  • Explain What You've Tried: Let others know what troubleshooting steps you've already taken.
  • Focus on the Facts: Describe the technical facts of your issue. Focusing on the problem helps others find a solution quickly.

+3 votes
Hello

I'm wondering how I can monitor the RTPC output of a meter plugin (on an aux bus) just within the authoring tool?

When I try to monitor the RTPCon the Transport/Soundcaster game object, I only see the RTPC at default value.

I'm not seeing the RTPC value change as the meter output signal changes. I only see the RTPC value change if I change it manually in the transport or soundcaster.

Is there something strange going on here, with monitoring an RTPC value from a meter, where the transport or soundcaster is overriding the value to the default?

Anyone had this trouble before? I can monitor the value and meter correctly when connected to the game, so there is nothing wrong with the setup itself. Just monitoring this side-chain behavior in the authoring tool...

Thanks
in General Discussion by Simon G. (1.0k points)
So to clarify, this seems to only be a problem if the meter is on a bus. Monitoring of the RTPC value works as expected in the game sync monitor IF the meter effect is in the Actor-Mixer hierarchy.
Seems that there is an issue with the scope of the RTPC when it's global, and the soundcaster/transport is playing the voice.

1 Answer

0 votes
Yes, I've noticed this discrepancy as well in the Game Object Profiler.  If I'm testing/previewing stuff in the tool, then I monitor what's coming from Transport/Soundcaster.  But when connected to a game, I'll add a watch to the parameter coming from the Game Object, to see what's going on there.  It was a bit confusing at first until I figured that out.
by Monty M. (3.1k points)
...