[REL] rF2 Spotter Plugin

This command File=[DriverName] is good only to call you name only and not for other drivers.

I was experimenting with the command: NumVehicleB], but had no luck. It seems that also this command is giving the same results.

I tried this but had no luck:
Input 3 is NumVehicle

// Tell when a car is going to pit (in race and it it is not me)
Event=AnyCarPitIn
{
// Event properties (note that these are not applied if this event is played by another event)
Detail=2
Spacing=0.0
Priority=1
Probability=1.0
TTL=15.0
Break=0.25

// Repeat until duration ends
Repeat=Off
Duration=0.0

// Volume can be set before individual Files if necessary
Volume=1.0

Variable=Session {
Value=10,13 {
Variable=Input1
{
Value=0 {
Variable=Input2
{
File=driver_at.wav
PlayEvent=PlaceNum


Variable=Input3
{
Value=01 {
File=jeffrey camilleri.wav
}
Value=02 {
File=jason muscat.wav
}
Value=03 {
File=riccardo flask.wav
}
Value=04 {
File=louis camilleri.wav
}
Value=05 {
File=noel attard.wav
}
Value=06 {
File=kevin sammut.wav
}
Value=07 {
File=andrew porsella-flores.wav
}
Value=08 {
File=mark buttigieg.wav
}
Value=09 {
File=noel attard.wav
}
Value=10 {
File=mark buttigieg.wav
}
Value=11 {
File=andrew porsella-flores.wav
}
Value=12 {
File=kevin sammut.wav
}

}



File=going_to_pit.wav
}
}
}
}
}
}

 

Italian translation

 

This is a lot of fun ! I just ran a 2 lap race and put Ai at 70% so I could win I can't wait to win a race online one day lol

 

I've been using this plugin for about 1 week, just the original download (newest) with no tweaks. The thing is, I always get the low tire temp warning, no matter tire temps, nor track, nor car.

Is this output broken? Should I just zero out it's probability so it no longer gives bogus information. Or is there a fix??

Sometimes I miss correct corner entrance because I find myself arguing in my mind as to why can't I do something about this.

Other than that, it's enjoyable.

 

You can configure the plugin to tell you about low and high tyre temps that would be correct for the mod your using. Problem is, I don't know the correct temps and haven't got time to research them. Or the time to enter them all in the correct place in the ini. I'm afraid that sort of thing takes me hours, so I've been putting up with it warning me about temps incorrectly. Shame really because the plugin is really great.
I'd love for someone who is able to do that sort of thing quickly and correctly to upload an ini with all this info already present and correct. I'm not lazy, it just really doesn't come very naturally to me. Would take me ages and I'd no doubt bugger it up.

 

Let do CarStat2 the Job, takes Seconds, to figure out, wich are the right Temps

View attachment 16415

 

First of al great plugin and I love your work.

Did you tested the plugin during a driver swap already as you stated Here

 

No

 

Any update of this great plugin?

I think it needs:

1. When spotter says time splits they are the best splits and not the self splits.

2. Drivers callnames (i've tested a lot with File=[DriverName] but had no luck.

 

Hi,
Still using this great plugin(thanks Gerald)but having trouble getting the spotter to read the tyre too hot/cold' info from the vehicle class ini. I've tried this entry -
[KartJunior_2014]
category.name=KJ
v:brakeTooHot=350
v:brakeTooCold=170
v:tireTooHot=100
v:tireTooCold=45
but it isnt working, or at least, its telling me the tyres are too cold when they are above 45 according to the MFD.
What am I doing wrong?

 

Hi,

thank you for this awesome mod. Finally I have a spotter in rF2 after 2 years...
I would like to ask a question: is it possible to assign multiple "sentences" to an action?
For example there is a car on my left. Right now the spotter tells me only one time "car left" but it would be nice if after the first warning it would tell me "still there" or "keep right" or "hold your line" (randomly) until it's clear.

 

I'd love someone to adapt the JJ Spotter pack for n2k3 for this mod!

 

should be possible, because it`s working similar with best laptimes (random sentences)

 

Not sure anyone else has found this but the spotter plugin crashes dev mode in 64 and 32 bit.

 

Do you added the configuration files into the <Data>/ModDev/UserData/player folder too, like you do in the <Data>/Userdata/player for the Single Player?

 

Thanks, you are a star

 

Any updates for this spotter?

 

Hi,
No, and i just made the test for using filename using driver names and it works like expected.

To Test it:
I have added a rule.29 in DefaultRules.ini and change the rule number

Code:

Rules.count=29
...
...
...
[Rule.29]
Trigger=PitOut
Event=PitOut

Then i've updated the PitOut event in the defaultEvents.ini

Code:

Event=PitOut
{
// Event properties (note that these are not applied if this event is played by another event)
  Detail=1  
  Spacing=0.0
  Priority=0.4
  Probability=1.0
  TTL=5.0
  Break=0.25
  
  // Repeat until duration ends
  Repeat=Off
  Duration=0.0

  Volume=1.0

	File=[DriverName]
}

And i have created files for the drivers in the game.
ex: if a driver name is displayed as "Michael Alesh" i have created a file "Michael Alesh.wav" under "Spotter/Sounds/Drivers" directory

And each time a car exit the pit, it play the wav corresponding to its name

 

Hi Gerald good to see you back on this wonderful plugin.

I will test your script tomorrow but changing it to PitIn as it makes more sense.

However once I did this and did not work for me:

// Tell when a car is going to pit (in race and it it is not me)
Event=AnyCarPitIn
{
// Event properties (note that these are not applied if this event is played by another event)
Detail=2
Spacing=0.0
Priority=1
Probability=1.0
TTL=15.0
Break=0.25

// Repeat until duration ends
Repeat=Off
Duration=0.0

// Volume can be set before individual Files if necessary
Volume=1.0

Variable=Session {
Value=10,13 {
Variable=Input1
{
Value=0 {
Variable=Input2
{
File=driver_at.wav
PlayEvent=PlaceNum
File=[DriverName]
File=going_to_pit.wav
}
}
}
}
}
}