0
0

As it stands it seems that you can only create parameters that exist on a continuum, such as RPM, Load, speed, etc, and that have interger or floating point values. You can’t have discrete string or text values.

Let’s suppose i wanted to create a "fire" event that had the following parameters: TYPE (wood fire, gas fire, debris fire) and INTENSITY (a continuum from 1-100). I want these two values to determine which sound definitions are playing and have the programmers be able to call the "fire" event with values for type and intensity.

As it stands, there is no way for me handle the TYPE parameter in an intuitive way because the values are named states: wood fire, gas fire, debris fire. It looks like the best i could do with the event editor as it stands, would be to number the different types of fires…e.g. 1 = wood fire, 2=gas fire, 3=debris fire, etc. This isn’t as convenient because the programmers will have to remember which numbers correspond with which TYPE of fire. Or, i could create seperate events for each type of fire and only use the intensity parameter as controllable by the programmer.

[img:8spxc6o4]http://i55.photobucket.com/albums/g125/Anders00/fmod3.jpg[/img:8spxc6o4]
http://i55.photobucket.com/albums/g125/ … /fmod3.jpg

I’d really like to have the ability to define a parameter that is usable in the event editor, and has discrete string values that are named states rather than interger or floating point values on a continuum.

  • You must to post comments
0
0

it sounds like a good idea, but for now we cant get onto that until we get some more important issues out of the way, so i would recommend using the ‘programmer’s report’ to convey information like this.

The programmers report will give the event names, and their parameters (and their ranges), and any notes you want to give them, by filling out the notes field in the event property sheet.

  • You must to post comments
Showing 1 result
Your Answer

Please first to submit.