In FMOD Studio, all the conditions on a transition marker must be met for that marker to function. To put it another way, all trigger conditions are implicitly “AND” conditions.
Or at least, that’s how it should work, but it sounds like you’re seeing all conditions behave as if they were “OR” conditons. In theory, we don’t support those yet; if you’re seeing conditions behave that way, it is a bug.
Unfortunately, I have not yet been able to reproduce this bug while testing here. What version of FMOD Sudio are you using when it occurs?
Yeah it seems like it was an anomalous instance. I deleted my event and made a new one that worked as you described. I’m not sure if it had anything to do with me upgrading the project recently, because until then it worked as expected.
I’ve actually had a few instances where the parameters have been playing up since upgrading from 1.09.02 to 1.10.02. (I think it had to do with the auto merging part of making parameter presets, which is most likely entirely my own fault)