Random number sounds

The names of “Game_Fails_01”, “Game_Fails_02” and “Game_Fails_03” bad sounds numbers: 3 sounds {1,3,2,1,1,3,2,3,2,1,2,3,3,2,2,1} or 2 sounds {1,2,1,2,2,1,1,2,1,2,2,1,2,1,1,2,1,2,1,2,2,1}. You have to fix good sounds numbers in FMOD Designer: Random a 3 sounds {1,3,3,3,3,2,2,1,3,1,2,1,1,1,1,2,2,2,2,3,1,3,3,3,3,3,1,3,1} or 2 sounds {1,1,2,2,2,2,2,2,1,1,1,1,1,1,1,1,2,2,2,2,2,2,2,1,2,1,1,1,1,2,2,2,1,1,2,2,1,2,1,2,2,2} and Random No Repeat a 3 sounds {1,3,1,2,3,1,2,1,2,1,2,1,3,2,1,3,1,3,2,1} or 2 sounds {2,1,2,1,2,1,2,1}. Scatterer Sound and Multi Sound are confused numbers! :x

http://imageshack.us/a/img12/6838/r8cw.png

It sounds like you’re describing the frequency and order of entries in a playlist that uses random selection mode, but I’m not sure what statement you’re making about them. What do you believe is the problem currently, and what needs to change?

The Button you need to change Drop Box such FMOD Designer play modes Sequential, Random, Random No Repeat, Shuffle, Programmer Select, etc. :oops: :roll: :x

The Button you need to change Drop Box such FMOD Designer play
modes Sequential, Random, Random No Repeat, Shuffle, Programmer
Select, etc. :oops: :roll: :x

Most of these modes are already available in Studio. However, the method of specifying which should be used is different: Sequential* mode is used when the randomization toggle button (the one with the die on it) is not highlighted. When the toggle button is highlighted and none of the playlist entries have specified play percentages, the behavior is equivalent to Designer’s Shuffle Global mode. When the button is highlighted and at least one of the playlist entries has a specified play percentage, the behavior is the same as Designer’s Random mode. Programmer selected sounds are handled through Programmer Sound Modules.

There are no direct equivalents of Designer’s Random No Repeat and Shuffle modes in Studio at this time, as Shuffle Global Random behavior fulfills much the same purpose. There’s also no direct equivalent of Designer’s Sequential Event Restart mode, as it wouldn’t make sense with the way Studio handles sound modules.

When we started developing Studio, we decided we wanted it to be easier to use and understand than Designer. As a result, many properties that Designer displays in text and number cells are portrayed in Studio as iconic buttons and graphical widgets, and many of the more rarely-used properties and interfaces were hidden or removed entirely, so as to present a cleaner interface with fewer distractions from the features you actually want to use.

  • Technically Global Sequential, but that’s due to a bug we’re currently working on fixing. The default mode should be sequential.
1 Like

Thanks!!

One must add-in plugins the random sounds. :slight_smile:

Fmod Designer playlist behaviors Simple Event randoms “Allow sounds to be repeated” selected random enabled and random not repeat disabled. Such! :lol:

Yes, exactly.

Playlist name selected Random with percentage:
Game_Fails_01 (33%)
Game_Fails_01
Game_Fails_02 (33%)
Game_Fails_02
Game_Fails_03 (33%)
Game_Fails_03