[REL] rF2 Spotter Plugin

Juergen-BY i just tested the game and I'm having no crash or freeze. The probem is not coming from the brackets. The brackets are ok. In programming what is important that there are no missing brackets and brackets are in the right place. Alignment of brackets is just to make the code more readable. Most probably np++ highlights this convention problem. So I think its not a problem of brackets.

As i said I played for 30 mins and no freeze when entering pits.

However i noticed that:

1. I need to remove the silence space from wav file cause a requested pit stop can be short as 5 seconds and because of the loop created by Gerald the sound is cut and not heard.

2. Also if pitstop is for example 20 seconds long than the sound of drilling is repeated and repeated which does not make sense. The sound must be heard once.

3. Also if other drivers makes pit, the sound must not be played.

But I repeat I had no crashed or freeze.

maybe we could avoid the loop and make it as simple as it was before.

 

Just removed the loop. A simple event now. This should solve the problem of repeating of pitstop is long. I also did not hear the sound when other drivers entered pit.

Check if without the loop the game keeps crashing. I had no crashing issues with v1.8

ANY OTHER DRIVER HAVING CRASH ISSUES WITH v1.8?

Just replace these two files.

TEST ONLY:

https://www.dropbox.com/s/jet8jjhhoi98cvm/NoLoop.rar?dl=0

 

Event = Pole (formatted)
View attachment 18165

NP++ .... Settings -> Preferences -> Tab Settings
View attachment 18166

 

Carlo I saw your formatting of code. I was writing the event using the normal notepad.

Am i right saying that the brackets are ok, despite the fact that not aligned properly and code should work normally?

I prefer use the time to make/test new events or new sounds then using time on {} indentation.

jef

 

Yes - braces are OK - just a formatting issue.

When writing code, it's generally accepted practice to replace each tab with 4 spaces. So, when using a code editor or IDE (Integrated Development Environment), this is done automatically through settings. When the tab key is used, the tab symbol is replaced by four spaces.

 

Thanks Carlo,

Can someone check with v2.0.0 (original files) and then put my version 1.8 update, if game has freeze or crash.

 

I am using v2.0.0 with your v1.8 soundpack for about 6 hours without any crash.

 

Sorry just went online and as soon as a friend pitted, I got the sound loop whilst out on track... on pressing esc to go back to garage my rF2 crashed.

 

Thanks PRC Steve, 7 posts above I just posted a new events file and rules where I removed the loop and left it simple.

Can you test that version for me and tell me if

1. there was crash
2. sound was heard when another driver made a pit


I will test today and release 1.9. Most probably i will remove the loop from the pit event. Will also try to make the sound not play in case there is a stop and go penalty.

Will release v1.9 this evening

 

Spotter v2.0.1 Available

-Fix crash due to pit stop/pit stop end
-Fix my DefaultEvent.ini

IMPORTANT: In the event file, open braket should appear only after "Variable=" or "Value=" so the following will not work as expected

Code:

 
Variable=Session {
    Value=0,13 {
        Variable=Input1 {
             Value=1 {
                        [COLOR="#FF0000"]{[/COLOR]FileLoop1=pitstop.wav [COLOR="#FF0000"]}[/COLOR]
             }           
       }
   }
}

it is interpreted like

Code:

Variable=Session {
     Value=0,13 {
         Variable=Input1 {
             Value=1 {
             }           
             FileLoop1=pitstop.wav 
         }
    }
}

So the FileLoop is not at its correct place and outside the test to see if it is your car or not (this explain why you have sound when another car pit)



NOTE: You can use now FileLoop to have a real pit felling for example with something like this

Code:

Variable=Session {
    Value=0,13 {
        Variable=Input1 {
             Value=1 {
                        FileLoop1=pitstopBackground.wav
                        File=pitstopTiresChange.wav
             }           
       }
   }
}

 

VERSION 1.8b

FIX: Crash in Pit Stop
FIX: Hearing pit sound for other cars while in pits.
FIX: In case you pit and you are serving a stop and go penalty no sound is heard.
FIX: Removed silent sound from pitstop.wav for short pitstops (so that sounds is complete in 5 seconds max)
FIX: Pit sound file is not heard repeating in case of long pitstop.

DOWNLOAD v1.8b
https://www.dropbox.com/s/fccp3rxf6ftvyts/Sound%20Pack%201.8b.rar?dl=0


ps. Gerald that idea you have above we can implement in next version. However I think the pitstopbackground sound should start to loop when you PIT IN (enter pitlane) and not in box only, and stop when you leave pit in PITOUT.

 

Yep or even two loops if you have sound for pit crew working around your car

 

Thanks folks

PS: the countdown in the pit lane is a great thing

 

Your feedback is very important for me and Gerald.

If you think that some sounds/phrases can be improved or insert new ones just let me know. Most often I watch F1 Race Edits and note the radio messages they exchange and try to use in spotter.

Jef

 

Hi Jef,
Great job you and gerald have done.

May I ask how you get yours voices so that they seem to be from a radio?
I tried recording some driver names but they sound awful.
Is there some program to add background noise and modulate the tone?

Should I understand that only the vehicle driver names can be used?
Is there a way to use the player nickname/real name depending on the server setup? I would expect that the same names that you see in the driver tag (the one that appears when clicking TAB) should be the ones called by the spotter.

For endurance races a message when preceding or following car swaps drivers would be useful. Makes sense only if player name is called rather than car driver name.

Enviado desde mi SM-G130HN mediante Tapatalk

 

Eukotracks for sound recording I have replied to you by PM and will send you some radio static noise effect and a screenshot of how to make multichannel.

I did not understand your problem about which driver names can be used. The sound samples for drivers (the wav files) must be similar to the name show they appear in game. That means that if for example your nam ein game is Richard Bailey, the wav file must be Richard Bailey.wav Not sure if I understood your question. If not give me an example so I can understand better.

Till now never used car swaps. I think I got what you mean. Seems a bit complicated. Maybe Gerald can give a better answer for this, as its him that works the engine from internal plugins.

 

Had a race this evening. I was using Spotter v2.0.1, but i still had a crash at the end of my pitstop. Any hints?

 

No crash until now. I will make many pitstop and see if i can reproduce the issue.

 

You guys rock, but every time i think in install the file i've downloaded you are already releasing a new version. I don't have time to complain about something.
I suggest when you find a bug let people complaining for at least a week even if you already had the solution. Complain is what makes us humans. Let people have fun too
Ehehe thanks for your work

 

In a race of 40 laps , the spotter tells me 10 laps remaining when in fact there were 7 laps .

Spotter v2.0.1
Spotter Plugin Sound Pack V. 1.8b