The 2002 ACC SDK is extremely vague on just what the first "generic" value represents in the v and r param lists in sound.cfg.I assume it has to be a reference to TIME since the second value of each couple is for volume, thus defining an amplitude envelope.What then is the timebase (0 to 100% of what?) being referenced so that proper timing and overlaps between each sound file (mainly limited to engine rpm) can be graphed on paper? (I don't intend on spending $30 for a program that I'll probably only use once when my brain and fingers can do it manually with this added bit of info).Hmmm... isn't that what an SDK is suppose to define in the first place?Crud on M$. :-)

> The 2002 ACC SDK is extremely vague on just what the first> "generic" value represents in the v and r param lists in> sound.cfg.Never mind. A little plotting of envelope graphs from an existing cfg showed that the 0 to 1 values are 0% throttle to 100% throttle.I then was able to develope a brand new engine rpm ramp using 5 rpm recordings at idle (2K), 3K, 4K 5K and 6K rpms. Works great and using a simple ratio calculations betwwen adjacent pairs of sounds I was able to get perfectly syncronized rparam pitch scales.Posted here to give back some of the joy I've taken in from this forum if anyone wants to use them, etc.{COMBUSTION.1.00}filename = rpm001_intflags = 0viewpoint = 1rparams = 0.00, 1.00, 0.15, 1.30vparams = 0.00, 50.00, 0.09, 55.00, 0.15, 20.00, 0.25, 0.00, 0.40, 0.00, 0.60, 0.00, 0.80, 0.00, 1.00, 0.00link = COMBUSTION.1.01{COMBUSTION.1.01}filename = rpm002_intflags = 0viewpoint = 1rparams = 0.10, 0.80, 0.41, 1.21vparams = 0.00, 0.00, 0.09, 20.00, 0.15, 58.00, 0.34, 68.00, 0.41, 20.00, 0.50, 0.00, 0.75, 0.00, 1.00, 0.00link = COMBUSTION.1.02{COMBUSTION.1.02}filename = rpm003_intflags = 0viewpoint = 1rparams = 0.33, 0.85, 0.66, 1.16vparams = 0.00, 0.00, 0.25, 0.00, 0.34, 20.00, 0.41, 71.00, 0.59, 81.00, 0.67, 20.00, 0.75, 0.00, 1.00, 0.00link = COMBUSTION.1.03{COMBUSTION.1.03}filename = rpm004_intflags = 0viewpoint = 1rparams = 0.58, 0.87, 0.93, 1.13vparams = 0.00, 0.00, 0.25, 0.00, 0.50, 0.00, 0.58, 20.00, 0.66, 84.00, 0.84, 93.00, 0.93, 20.00, 1.00, 0.00link = COMBUSTION.1.04{COMBUSTION.1.04}filename = rpm005_intflags = 0viewpoint = 1rparams = 0.82, 0.90, 0.99, 1.00vparams = 0.00, 0.00, 0.20, 0.00, 0.40, 0.00, 0.50, 0.00, 0.75, 0.00, 0.83, 20.00, 0.90, 96.00, 1.00, 100.00link = COMBUSTION.1.05// externals sounds below... just repeat the same lists above,// appropriately named to continue the link sequence and edited// for filenames and views, etc.

Good to hear you got it worked out Dean.I don't know how you graphed your data, but I did something similar on a recent project pumping the raw r and v param data into Excel and then creating graphs of the data. The visual feedback was very helpful in understanding how the parameters and sounds interact. I could then manipulate the points on the graphs, which automatically updated the associated data. Once I tweaked the graphs to suit, it was a matter of pushing the data back to the .cfg file. I have actually considered taking this idea a step further at some point and developing a small app to help developers manipulate sound config files with more ease. No time now, maybe in the future. Maybe there is already a program that does this, though I am not aware of it.As far as the SDKs, they all leave a lot to be desired IMHO. Generally speaking, the values are generic as the SDK states, why MS deals with it in this manner is anyone's guess. I'm sure they have a wonderfully ridiculous reason for doing so. A bit bass-ackwards if you ask me...