Gerald Jacobson
Registered
Indeed, i made the update in the delivered files.Thanks for the update! This isn`t needed, if i`m using your files, only?
Indeed, i made the update in the delivered files.Thanks for the update! This isn`t needed, if i`m using your files, only?
Hi Jeferson,
could you please help with an Event for
1. DRS Detection (own Car)
2. DRS Activation (own Car)
3. DRS Activation (Car behind)
Would be very usefull...
Hi sjbaraki,I have updated the soundpack (including the link in the original post) get the new version here:
https://mega.co.nz/#!bdEy1AYZ!20nfWck3JIuBIrwQrewUlnM5WhfSXCYQ_UVLZ95orKI
The calls "car left, right, three wide" are no longer delayed. This was an issue with the WAV files.
@GCC racer, to create the audio effect I made a custom FX chain in Ableton Live. I'd be happy to share it with you if you have the program.
DRS information is only available for your own car. The API does not provide telemetry data for other cars.just to give it a little bump...![]()
1. DRS Detection (own Car)
2. DRS Activation (own Car)
3. DRS Activation (Car behind)
Would be very usefull...
DRS works like expected but i recommand you to play sound only when the input is 1 or 2, it is not necessary to inform when the DRS is canceled.The DRS works for qualify or race only? Need to know what this is exactly for. When it triggers? When car is allowed to top open rear wing and close it by detecting tracks that support drs. On when user press button top open/close wing? First testing heard both triggers to allow drs and disallow drs at the same time after each other. This is a bit confusing
May i could add some more information on this...DRS works like expected but i recommand you to play sound only when the input is 1 or 2, it is not necessary to inform when the DRS is canceled.
DRS is managed by circuit when they implements it and can works in any session.
Event=PitStop
{
// Event properties (note that these are not applied if this event is played by another event)
Detail=1
Spacing=0.0
Priority=1.0
Probability=1.0
TTL=10
Break=0.25
// Repeat until duration ends
Repeat=Off
Duration=0.0
Volume=1.0
Variable=Session {
Value=0,13 {
Variable=Input1 {
Value=1 {
{[B]FileLoop1[/B]=pitstop.wav }
}
}
}
}
}
Event=PitStopEnd
{
// Event properties (note that these are not applied if this event is played by another event)
Detail=1
Spacing=0.0
Priority=1.0
Probability=1.0
TTL=10
Break=0.25
// Repeat until duration ends
Repeat=Off
Duration=0.0
Volume=1.0
Variable=Session {
Value=0,13 {
Variable=Input1 {
Value=1 {
{ [B]StopLoop1 [/B]}
}
}
}
}
}
Unfortunatly information to rhe plugin are provided by rF2 at a fix rate of 0.5 second. And i don't want try to implements a predictive systemBig thanks to Gerald and jefcam for your work and continuous update/fix rate!
Small question/feedback/request: would it be possible to make the car radar icon update rate faster ie. movement smoother? Right now to me it's jumping too big of a distance at once and that makes it a bit difficult to track/see. I hope you know what I mean.
- Tero
Ah, I see and understand. Not sure a predictive system would be a good idea anyway. Thanks for the replyUnfortunatly information to rhe plugin are provided by rF2 at a fix rate of 0.5 second. And i don't want try to implements a predictive system
Spotter v2.0.0 Available
- Fix some inconsistencies and issues found by jefcam
- Add new Trigger "GamePhaseChanged"
- Add new Commands "FileLoop<x>" and "StopLoop<x>"
Thanks
1. should work only when pitting. Will check it out.
2. might not be an issue with spotter. (will check if this happens to us as well)
3. also this did not happen to us ( will also check)
thanks for your feedback. make sure you installed v2.0.0 and put the files in the right location. will come back to you later. We did not have enough time to test.