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.

Yay WAQL! But I STILL can't use != with most expressions/parameters for EXCLUSIVE queries?!

0 votes

I cannot fathom why, after all the years that Wwise has been used in AAA game development, there is STILL no option in the query editor to query by exclusion!

We have AND and OR operators in the GUI-based criteria grouping section, but STILL no NOT operator!

But what's worse is that, despite your release of the helpful and robust WAQL last year, I STILL cannot query a property using != with a RegEx (Regular Expression) statement to return everything that DOESN'T match the queried expression!

WHYYYYYYYYYY?!?!

There are SO many times every day that I could solve a problem within seconds if I could just do an exclusive query to return all objects EXCLUDING the queried statement. BUT NO! Instead, I'm still thrashing around in chaos, pining away, wasting hours of my life trying to create INCLUSIVE queries that effectively include everything except the one thing I want to exclude. These queries often end up being so bloated and complex that I'd be laughing about them if I wasn't so tormented by the necessary evil of their existence, and the personal hell of being forced to create them because I STILL can't create a very simple exclusive query in far too many cases, and for far too many parameters.

PLEASE, Audiokinetic, PLEEEEASE add the NOT operator in the criteria grouping section in the query editor, and/or add support for the != operator to be used in conjunction with WAQL and RegEx statements!!!!!

And I'll say THANK YOU in advance for saving me from losing my marbles as a result of another few years of being stuck with mainly only inclusive operators for querying objects in Wwise!

in Feature Requests by Mike MKJ (300 points)

1 Answer

0 votes
 
Best answer

In WAQL, to reverse the logic of a condition, use the ! operator in front of the condition.

Examples: 

$ where ! name = /^Ambient/
$ where ! (name : "Ambient") or ! (name = /\d+$/)

by Bernard R. (Audiokinetic) (35.8k points)
selected by Mads Maretty S. (Audiokinetic)
how do I make this work to exclude "type" identifiers? i've tried various syntaxes, none seem to work.
asked Sep 12, 2024 in General Discussion by Mike Maksim (110 points)
recategorized Jan 15 by Samuel L. (Audiokinetic)
how do i make it work for "type" identifiers? i've tried various ways, none seem to work.

Actually, I just realized that using the regex search method is broken by case sensitivity issues for types, just same as anything else.

WE NEED THE IGNORECASE FLAG PLEEEEASE!
by Mike Maksim (110 points)
Powered by Question2Answer
...