hi Gerald, I noticed that ``driver_next.wav`` and ``driver_previous.wav`` are sampled with 8000 hz, instead of 44.100 hz as all the others. Would be nice to have it all equal. May I ask you to speak these answers, please. So I will get a more ``personal`` answer from my race engineer? ``yes, you are leading the race``or ``you are leading the race, but keep an eye on the car behind, he is very fast`` ``you are second, come on, keep pushing`` ``third place, you can still reach the two in front`` ``you are on fourth place, keep fighting for the podium`` ``fifth place, good work so far`` ``currently on six, you can do more, come on`` ``still on seventh place, its possible to advance, mix three, mix three`` ``we are running on eigth, you must attack, use overtake button`` ``nine, nineth position, there is a lot of work to do`` ``your on tenth, only tenth, keep pushing, do your best``
Hi Gerald, I've been using this now for two weeks, grabbing the updates as you release them. I have to say, it's simply one of the best things to ever happen to rF2 and you've made the decision to donate a very easy one. Many many thanks for your works and I hope the inspiration continues as you are a very talented man and an asset to this community. Kind Regards, Mat
Spotter Plugin v1.3 - Fix wrong place told when another enter the pitlane - update driver_next, driver_previous sounds, so all sound will be sampled equally - speed up "Green3.wav" - change you_are.wav message to "You are at position" - There is no more vehicleClass section in the Spotter.ini file, now the overriden variable like v:breakTooHot are moved in the vehicleClass.ini file (more logical) - Add classes and break temps in vehicleClass.ini - renamed VehiculeClass.ini to VehicleClass.ini - with debugMode=1, no you will find in the Spotter.log file, the vehicleClass receive by the plugin from rF2 and it will list each rule (by replacing v:... by it value) - Add the Rule.28 and the shortcut 2 used in the tutorial (RightAlt+K tell your current place) Hello, what do you need ? only new wav, new rules ? or changing message of existing wav? or ? Thanks for the donation
Found some more brake temperature ranges 500AssettoCorse v:breakTooHot= v:breakTooCold= v:tireTooHot= v:tireTooCold= 1979_un v:breakTooHot=800 v:breakTooCold=400 v:tireTooHot= v:tireTooCold= Brabham BT20 v:breakTooHot=555 v:breakTooCold=300 v:tireTooHot= v:tireTooCold= Caterham v:breakTooHot=650 v:breakTooCold=350 v:tireTooHot= v:tireTooCold= Clio_Cup v:breakTooHot=500 v:breakTooCold=300 v:tireTooHot= v:tireTooCold= Eve_F1 v:breakTooHot=555 v:breakTooCold=300 v:tireTooHot= v:tireTooCold= Eve_ F2 v:breakTooHot=555 v:breakTooCold=300 v:tireTooHot= v:tireTooCold= Eve_ F3 v:breakTooHot=555 v:breakTooCold=300 v:tireTooHot= v:tireTooCold= F1ASR92V1 v:breakTooHot=800 v:breakTooCold=275 v:tireTooHot= v:tireTooCold= FIAGT3 799R GT3 v:breakTooHot=700 v:breakTooCold=350 v:tireTooHot= v:tireTooCold= F2_2012 v:breakTooHot=630 v:breakTooCold=350 v:tireTooHot= v:tireTooCold= FISI_2012 v:breakTooHot=688 v:breakTooCold=411 v:tireTooHot= v:tireTooCold= FR3.5_2014 v:breakTooHot=600 v:breakTooCold=350 v:tireTooHot= v:tireTooCold= GT1_GTR v:breakTooHot=700 v:breakTooCold=400 v:tireTooHot= v:tireTooCold= GT2_C6R v:breakTooHot=530 v:breakTooCold=485 v:tireTooHot= v:tireTooCold= GT3_Camaro v:breakTooHot=595 v:breakTooCold=300 v:tireTooHot= v:tireTooCold= GT4_370z v:breakTooHot=595 v:breakTooCold=300 v:tireTooHot= v:tireTooCold= Howston_G6_MkI_65 v:breakTooHot=575 v:breakTooCold=340 v:tireTooHot= v:tireTooCold= IFS3 v:breakTooHot=700 v:breakTooCold=200 v:tireTooHot= v:tireTooCold= Indycar v:breakTooHot=688 v:breakTooCold=411 v:tireTooHot= v:tireTooCold= KartF1_2014 v:breakTooHot=350 v:breakTooCold=170 v:tireTooHot= v:tireTooCold= Marussia_MR01 v:breakTooHot=688 v:breakTooCold=411 v:tireTooHot= v:tireTooCold= Megane_Trophy v:breakTooHot=650 v:breakTooCold=300 v:tireTooHot= v:tireTooCold= Panoz_Roadster v:breakTooHot=495 v:breakTooCold=275 v:tireTooHot= v:tireTooCold= Quad_2014 v:breakTooHot=590 v:breakTooCold=390 v:tireTooHot= v:tireTooCold= Skip_Barber_Regional v:breakTooHot=560 v:breakTooCold=265 v:tireTooHot= v:tireTooCold= Spark_F1 v:breakTooHot=555 v:breakTooCold=300 v:tireTooHot= v:tireTooCold= Spark_F2 v:breakTooHot=555 v:breakTooCold=300 v:tireTooHot= v:tireTooCold= Spark_F3 v:breakTooHot=555 v:breakTooCold=300 v:tireTooHot= v:tireTooCold= StockV8 v:breakTooHot= v:breakTooCold= v:tireTooHot= v:tireTooCold=
wow, new update .... sensational ! I thougt in new waves only. I will try to adapt the rules to run them. Thanks in advance
Spotter Plugin v1.4 - Fix regression about shortcut introduced in v1.3 - Avoid to tell finish message several times - Trigger S3 is no more triggered if it was the lastest lap - Create 10 new messages (asked by GauchoRS) for position 1 to 10, and use then in the [Rule.28] and [Rule.25] - add new class data to VehicleClass file (thanks MOD43)
another question... is it possible to define a sequence of .wav to play ? like bleeb.wav ; yourposition.wav ; bleeb.wav ? and what about to play a static noise .wav in the background simultanously ?
Would be great. Here's the data ('vehicleClass.ini') for URD-mod: Code: [EGT] category.name=GTE v:breakTooHot=590 v:breakTooCold=300 BTW .... is it possible (for future releases) to rename all the stuff regarding Brakes, from "break" to "brakes"? It's a little bit confusing to use the word "break" for "brakes". Just a suggestion, because "brakesTooHot" sounds better. Nevertheless, if i try to overheat my brakes (even to over 900° celsius) i don't get a message that my brakes are too hot. Seems like the event doesn't get triggered. Great suggestion.
Thanks Gerald for listening to the users Few more suggestions: - I would really like to get rid of that "wormer" and replace it with "warmer" - Those motivation messages are generally a good thing but they are little out of place atm. I got messages like "use overtake button" and "fuel mixture X" in the qualification. Maybe different messages for the quali and race? - I also like Gaucho's sequance of wav. suggestion. - I think it was bug when I got "driver behind was..." message like 6 times in a row... happened only once so not sure if you can find the reason? - Is it possible to lower the volume of your spotter because atm it's much louder than all my other voices. I try to keep other sounds relatively low to hear ISI spotter laptimes but I don't know how to lower your spotter's voice? - Is it possible to delay some messages by X seconds that are played after finish line? Now many some messages are played right after I cross the finish line which leads to the fact that I can't hear ISI spotter telling me my laptimes. - Not sure if already done but if not then "you are six" etc. should be changed to "you are sixth" etc.
I have Made laptimes part of Geralds spotter and turn off IsI spotter. It was mentioned early to turn off IsI spotter. Earlier posts have details for laptimes read at the end of each lap. Event mylaptime.
Hi Gerald, Two questions. - Does it reckon or is possibly that the spotter could warn you when to use the DRS? - Does the spotter for rfactor1 have an archvio called 'Driver' and inside there were coming in .wav the personalized names of the pilots of every community, every .wav had the same name.wav that nick of the pilot in rFactor2, it is possible to do that in the future? thanks for the excellent work. My contribution and that of 'Jorge' (voice lokendo) http://www.mediafire.com/download/63u7a7fibbtwi4v/Spotter_Spanish_Sounds_v2.rar
- for the noise, i do not plan to allow playing background sound (i wait something to decide if i will add this feature or not). For now, i will see if i found a way to batch update all sound to add a noise background, and in this case i will describe the method in the wiki. - Just add File=bleeb.wav at the right places. For exemple with the event AnyCarAtPit Code: Variable=Session { Value=10,13 { Variable=Input1 { Value=0 { Variable=Input2 { [COLOR="#EE82EE"]File=bleep.wav[/COLOR] File=driver_at.wav PlayEvent=PlaceNum File=going_to_pit.wav [COLOR="#EE82EE"]File=bleep.wav[/COLOR] } } } } } - Thanks for the GTE - Ok, i will rename variable and event from break to brake - I will check overheat brakes issue - ok, will remake the sound to change wormer to warmer - Motivation message : don't forget, i made this spotter fully customizable, and i created a wiki explaining all, to allow you to create what ever you need and avoid me to spend all my time to create custom message for everyone. - As said by whitmore, don't use the two spotter together (you will have overlayed messages), just create the laptime in my spotter - you have the solution in several previous posts starting with this one - Delayed message : no it is not possible actually - Sixth : i have changed "you are ..." to "you are at position..." to avoid make too much sound (i don't want to spend my full time on sound creation) - it's why i made it customizable.
@Whitmore: Can you send me the code to tell laptimes? (what to do to make it work?) If I disable ISI spotter then wouldn't it disable some other messages too that have high detail level in events? Do I need to make them all detail level 0 (if there even is 0 level) or 1? Or have I misunderstood the meaning of detail level?
