AC RSS GT-M (GT3) @ Jarama - Sunday 13th August 2023

Assetto Corsa Racing Club event

Interslice

Club Staff
Premium
Welcome to the RD Assetto Corsa Racing Club. Next Sunday we're at Jamara, Madrid for some GT3 action!!





Join us!

This is the place to be for relaxed, friendly racing and our events are open to everybody from rookies to the seasoned pros. You will always find people around your level to battle with, so jump on in!
If you need any help don't hesitate to ask on discord before the race, or right here on the forum! We are always happy to help.

All race department premium members with their full real name added to their forum profile as well as in game and discord can sign up for this event.

Need a warm-up or want to start online racing at a gentler pace? There is an MX-5 + Abarth event earlier in the week . We also run a practice server all week for all events.


Jarama90.png



  • Practice Server: RaceDepartment.com #3 (Available throughout the race week)
  • Race server: RaceDepartment.com #3 - Netherlands
  • 20:00 CEST, 19:00 DST, 18:00 UTC | 80 minutes - Official Practice
  • 21:20 CEST, 20:20 DST, 19:20 UTC) | 20 minutes - Qualification
  • 21:40 CEST, 20:40 DST, 19:40 UTC) | 50 minute - Race

Cars (Ballast/Restrictor)
  • RSS Mercer V8 (10kg/6%)
  • RSS Bayer 6 V8 (10kg/6%)
  • RSS Lanzo V10(4kg/3%)
  • Purchase here

Event details:
  • Track: Jarama
  • Pit stop: Mandatory stop between 10 and 40 minutes
  • Track Temps: 20C air/30C track
  • Track Condition: Clear, Light wind, Optimum grip.
  • Damage: 10%
  • Assists: Factory
  • Standing Start: Jump Start = Drive through penalty


Useful Links:

Race Control

Recommended Apps

Sign up/Entry List:

Post in the forum below!!





Sign up info
 
Last edited:
A message to all Drivers

If you run off track, you must check to see that its clear before you re enter the track. Always try to re-enter the track parallel to the racing line. Stay off the racing line until you are up to race speed and do not block any fast approaching car.

When joining the track from the pits, remain inside the white line and stay off the racing line until you are up to speed.

During qualification, do not race on your out lap, let other drivers by.


Golden Rule
  1. If you hit somebody, sending them off the track and carry on like nothing happened, you take the risk of being banned for 30 days.
  2. Instead, you should always wait for the affected drivers, and that way you can be 100% sure you will not get a ban.
Track limits
  1. No more than 2 wheels over the white/yellow line without a lift of the gas please.
    You will be penalized if you break our rules
Note: Please use your full real name in Discord and in game. Not doing so may result in you being kicked from the server if an admin cannot identify who you are.
 
never had a problem with MoTeC now my new OS win 10 gives this error.

@RasmusP

>>> INFO : Assetto Corsa Telemetry Interface v1.1.2 written by Latch Dimitrov - Dec 2017
>>> INFO : Starting ACTI with loglevel = 3.
>>> INFO : Initializing...
>>> INFO : Initialization complete.
>>> INFO : Accepting incoming trig connection...
>>> INFO : ACTI Running as Subproc.
>>> INFO : Accepting incoming trig connection...
>>> INFO : Connect trigger accepted.
>>> INFO : Attempting to connect...
>>> INFO : PHASE2 response length = 328 bytes.
>>> INFO : Connection established.
>>> INFO : Stint recording started...
>>> INFO : Stint recording finished.
>>> ERROR : ERROR: UDP connection has timed out.
>>> INFO : Connection terminated.
>>> INFO : ACTI Finished.
>>> INFO : Closing ACTI.
 
Last edited:
never had a problem with MoTeC now my new OS win 10 gives this error.

@RasmusP

>>> INFO : Assetto Corsa Telemetry Interface v1.1.2 written by Latch Dimitrov - Dec 2017
>>> INFO : Starting ACTI with loglevel = 3.
>>> INFO : Initializing...
>>> INFO : Initialization complete.
>>> INFO : Accepting incoming trig connection...
>>> INFO : ACTI Running as Subproc.
>>> INFO : Accepting incoming trig connection...
>>> INFO : Connect trigger accepted.
>>> INFO : Attempting to connect...
>>> INFO : PHASE2 response length = 328 bytes.
>>> INFO : Connection established.
>>> INFO : Stint recording started...
>>> INFO : Stint recording finished.
>>> ERROR : ERROR: UDP connection has timed out.
>>> INFO : Connection terminated.
>>> INFO : ACTI Finished.
>>> INFO : Closing ACTI.
>>>INFO :DDriver too slow permaban implemented:roflmao::p:p

...sorry mate, couldn't resist:ninja:
 
Last edited:
Sounds a lot like the crap I experienced when installing ACTI :poop:

1. can you find the ACTI apps in the AC drive menu?
(if not you may have to insert the path in the config manually)





CM ACTI.PNG


2. are the apps active in CM settings (Python apps)?

CM DRIVE.PNG


3. Dai and I ( :rolleyes: ) both have to start ACTI manually from the desktop, it does not activate automatically :speechless:
 
Last edited:
Funnily I did scoff when you told me about your problems with acti, it has come back to bite me in the bum. That will teach me.
:roflmao::roflmao::roflmao::unsure::roflmao:
Ps I use the vanilla AC it all seems to work fine, I go back to the pits, nothing happens.
Look in the log file and that is what I get.
 
Last edited:
never had a problem with MoTeC now my new OS win 10 gives this error.
As Carsten said, it's probably the path missing somewhere. I configured it ages ago and always kept the steam folders on the same drive letter (adjusted the drive letters when getting into the new OS for the first time).
And always copied the important folders in the documents folder like the AC one.
If you didn't and installed acti from scratch, you probably need to set the path again somewhere in the acti settings.
Not at the pc until Sunday, so Carsten is your better bet until then :unsure::inlove:
3. Dai and I ( :rolleyes: ) both have to start ACTI manually from the desktop, it does not activate automatically :speechless:
Yeah me too. But I have a .bat file that launches CM, acti, crewchief etc :D
 
Dammiti
Funnily I did scoff when you told me about your problems with acti, it has come back to bite me in the bum. That will teach me.
:roflmao::roflmao::roflmao::unsure::roflmao:
And I took you for a gentleman;)
Well, we learn all our lives :cool:

Ps I use the vanilla AC it all seems to work fine, I go back to the pits, nothing happens.
Look in the log file and that is what I get.

This is the video which meant the break through for me:
(it´s in the continental tongue but you should be able to follow the pretty pictures.)
It should start at the moment he enters the path Rasmus mentioned.)


Where has the world come to, me giving PC advice :cautious:

And thanks to all of you that have driven me this far :inlove:
 
When I get home I will run through it, I have my path on the D drive which has the steam on it too.
It is the UDP timing out, I can find nothing helpfull about it on the internet which usually means it is a symptom and not a cause.
:(
 
Last edited:
When I get home I will run through it, I have my path on the D drive which has the steam on it too.
It is the UDP timing out, I can find nothing helpfull about it on the internet which usually mean it is a symptom and not a cause.
:(
Time out means that it can't reach the server port. Is your server running? Is it on the same machine? Is the port being blocked by a firewall application?
 
Checked that and fire wall, but it is not exactly an every day process for me, there is a good chance the something is looking at me in the face and I just do not see it.
Checked the UDP and it is attached to act.exe path.
Cleared all the buffers, reset the network, checked all the paths, reloaded it all from scratch, MoTeC too.
Perhaps when I get back to my PC tonight it will be obvious, I will be a bit more relaxed and not so annoyed.:roflmao::roflmao:
 
When I get home I will run through it, I have my path on the D drive which has the steam on it too.
It is the UDP timing out, I can find nothing helpfull about it on the internet which usually means it is a symptom and not a cause.
:(

From what I remember the path is to the acti/telemetry (edit: close the acti/acti.exe) probably on your C drive, in beside where it stores the motec telemetry files. Rather than the ACTI within steam AC apps.

There are 2 parts, the app and the .exe which work together, but the ap needs to know where their old mate is :)
 
Last edited:
It is the UDP timing out, I can find nothing helpfull about it on the internet which usually means it is a symptom and not a cause.
:(
Are your telemetry recordings showing on your hard drive?
The udp time out is normal!
It's ONLY for when you want to record the telemetry to a different PC!
Like I'm running a team and you and Carsten record via acti to MY server do I can check your telemetry after each lap.
 

Latest News

Back
Top