Gerald installed 1.7 works fine. When I try to lift level of individual event sound file "Volume=X" there is no response to the increase in level. I have gone as high as volume =20 without hearing any change. I am trying to lift the level of the sound file played when I hear my lap times. In game spotter audio level works ok. I can change the level of all but I was trying to increase laptimes only. Any suggestions?
I hope you don't take the "complaints" too seriously. You have done a great job, and are constantly updating to make it better. We all really do appreciate your time and effort. I hope ISI realizes the great benefit you, and Noel Hibbard, and other programmers are to the popularity and sale of their simulations. Without you all, putting hours in, with little chance of monetary gain, rF1 and rF2 would not be as valuable as they are. You've added features that ISI haven't been able to offer that makes the experience with these sims better than ever.
Could you give me an example where you need AND / OR ? Volume is a variable from 0 to 1 (0=no sound, 1=100% of the volume). So it means that the sound files are not enough loud and you need to amplify them (it's what i have done to all my sounds few month ago) Don't worry for the complaints And ISI team as well as Noel support me as soon as i need help, i really appreciate there support. And i'm happy that my work is appreciated by the community.
Gerald I have been trying to get specific names of drivers to work and noticed the spotter ini has these two lines DriverNames.subPath=Sounds/Drivers DriverNames.extension=wav however you want us to use File=[DriverName] Should it be File=[DriverNames] ? and are the square brackets necessary?
No, it is correct. You need to use "File=[DriverName]" as is. So it will look at the file "<DriverNames.subPath>/<driverName>.<DriverNames.extension>", so for exemple, if your ingame name is "whitmore", it will look with this setting to "Sounds/Drivers/whitmore.wav"
Thanks for clearing that up Also in the "PlaceNum" event code there is this line Value=2,9 { It appears to be incomplete. I do not seem to be getting this event to work.
Actually the AND is indeed not really necessary as you can simply nest a new condition inside the previous one. In fact I meant NOT. Example for OR and NOT (in pseudo code): IF (speed > 50 km/h) OR (section = NOT yellow flag section) { notify yellow flag } If you don't like to add these things, no hard feelings. I still admire your work! I'm just trying to make it even better.
Paragraph "Create Sounds" in the WIKI : http://rf2-spotter-plugin.wikia.com/wiki/RF2_Spotter_Plugin_Wiki
What I mean by incomplete is when comparing the lines of code as taken from the PLACENUM event the two lines I have made red show how the second one appears to missing some arguments. Value=1 { File=1.wav } Value=2 { File=2.wav } Value=3 { File=3.wav } Value=4 { File=4.wav } Value=5 { File=5.wav } Value=6 { File=6.wav } Value=7 { File=7.wav } Value=8 { File=8.wav } Value=9 { File=9.wav } Value=1,9 { File=100.wav } } Variable=Input1RoundFunc,1,10,10 // number of tens { Value=0 { Variable=Input1RoundFunc,1,1,10 // number of tens { Value=1 { File=1.wav } Value=2 { File=2.wav } Value=3 { File=3.wav } Value=4 { File=4.wav } Value=5 { File=5.wav } Value=6 { File=6.wav } Value=7 { File=7.wav } Value=8 { File=8.wav } Value=9 { File=9.wav } } } Value=1 { Variable=Input1RoundFunc,1,1,10 // number of tens { Value=0 { File=10.wav } Value=1 { File=11.wav } Value=2 { File=12.wav } Value=3 { File=13.wav } Value=4 { File=14.wav } Value=5 { File=15.wav } Value=6 { File=16.wav } Value=7 { File=17.wav } Value=8 { File=18.wav } Value=9 { File=19.wav } } } Value=2 { File=20.wav } Value=3 { File=30.wav } Value=4 { File=40.wav } Value=5 { File=50.wav } Value=6 { File=60.wav } Value=7 { File=70.wav } Value=8 { File=80.wav } Value=9 { File=90.wav } Value=2,9 { Variable=Input1RoundFunc,1,1,10 // number of unit { Value=1 { File=1.wav } Value=2 { File=2.wav } Value=3 { File=3.wav } Value=4 { File=4.wav } Value=5 { File=5.wav } Value=6 { File=6.wav } Value=7 { File=7.wav } Value=8 { File=8.wav } Value=9 { File=9.wav }
It is not necessary incomplete. "{" means after that there is one or more subcommand, "}" mean it is the end of the previous segment. The layout, using tab or spaces it is usefull as human to read correctly the code, the parser is more flexible. But i encourage you to always format correctly (after any "{", use a new indent.
No. Because there is sub-if to define the right file to play. For example, to say 230 you need to cut it in several unitary sounds. So you need to divide by 100, then by 10 etc...
Have been trying to get specific voices working and in need of some help. Made WAV files, checked in for correct file type setting in the ini file, put WAV files in the driver directory under spotter. And finally, to play this sound use the following command in the pitin event file Code: File=[DriverName] but still not working. event file code Event=PitIn { // Event properties (note that these are not applied if this event is played by another event) Detail=1 Spacing=15.0 Priority=0.4 Probability=1.0 TTL=1.0 Break=0.25 // Repeat until duration ends Repeat=Off Duration=0.0 Volume=1.0 // Variable=Session { // Value=(>=10,<=13) { Variable=Input1 { Value=1 { File=[DriverName] } //Value=1 { File=Careful_watch_your_speed_limit.wav } } // } // } } Rule code [Rule.16] Trigger=PitIn Event=PitIn Input1=MyEvent Help please
I've edited all audio file this way, thank you for the hint! But adding other samples to the audio isn't possible with the chain tool I'm afraid. Anyhow I applied some filters to the voice so it sounds much more like radio broadcast @Gerald Great plugin! I love it One question (don't know if this was asked before): Can I mix sounds using the events ini? For example I want to add some ambient sounds to the spotter but adding this to all files is a huge amount of work And beside of this: Judging from your experience in building plugins for rF do you think that some kind of opponent indicator would be possible!? Many (to be honest more arcade like) games use it to compensate the pilots "recognition" of the opponents around him - the spotter is a good thing but for me personally this only belongs to oval racing. An opponent indicator would be great I've put together a little example here. The little red arrows point to the opponents in your surrounding.