Time to time an RTFR race goes into history with something specific,this one unfortunatelly went into history with biggest mass crash in a single turn - almost everyone was involved in some degree. After the incident the big voting for restart started - yes,in real world such race would had been red flagged and restarted later,but we are in simracing - there are not burning cars,there are no broken off parts that litter the track and there are no medical emergencies. So once again - if crap happens,suck it up and deal with it! If car is undrivable,you have the right to telepit to pits and rejoin,as a proof that it still brings result - 3 of the rejoiners finished between best 11.
In RTFR we will still strictly stay to the no-restart rule (unless there is a server issue) for 2 reasons:
> Restarts will never be fair - if race is restarted and there is another (even smaller) crash,then it should be restarted again for sake of fairness,but with 38 drivers from which there are about 1/4 hotheads with opinion that race can be won in 1st lap that could lead into double digit count of restarts.
> Restarts can delay the event by a lot. If someone gets hit out of bounds,on a restart he would lose the original grid position,that would require return to gridding screen,which with odd behaviour of semi-casual participants can be pain in neck for organizers and additionally delay the event even further.
Critical situations require critical action - since we're not organizing a crash party (except in 26th december),we do not want such incidents to happen as it damages the reputation not only for organization,but also for the simulator and it's community as the event is broadcasted in wider public. Therefor as a drastic measure every single driver's behaviour was checked during 1st sector of the 1st lap to decide how appropriate it was to our racing standards.
* PENALTIES : [MRc] Texas - receives a 45 seconds penalty added to the finish time for avoidable incident in 1st hairpin. Additionally this serves as a warning - future incidents might lead to bigger penalty. RGˆLORENZO - receives a disqualification from race results for avoidable incident in 1st hairpin. With a record of previous incident this serves as a final warning - future incidents will lead to race ban. fnc. B.Botev - receives a 45 seconds penalty added to the finish time for avoidable incident in 1st hairpin. Additionally this serves as a warning - future incidents might lead to bigger penalty. The penalty results in loss of last completed lap. RGˆNOSLE - receives a warning for avoidable incident in 1st hairpin. Future incidents might lead to actual penalty. 「DD」 tBug (licence name: Yasso7up) - receives a disqualification from race results for avoidable incident in 1st hairpin. With a record of previous incidents (also in other events) the driver has proven the lack of willingness to learn from mistakes and still goes for overly agressive moves without care of other racers,therefor he receives a race ban from RGE events for 3 months starting with day after race day. SGマ MadJester (licence name: lordferius) - receives a disqualification from race results for heavy incident in 1st hairpin. Since the driver has no record of incidents in RTFR,he escapes with "minor" race ban from RGE events for 1 month starting with day after race day. [MRc] adallll - receives a disqualification from race results for avoidable incident in 1st hairpin. Additionally this serves as a warning - future incidents might lead to further disqualifications or even race ban. (FR) Pablo - receives a disqualification from race results for avoidable incidents before and in 1st hairpin. Additionally this serves as a warning - future incidents might lead to further disqualifications or even race ban. CRAAACH - receives a warning for conduct when driving through crash scene - drivers should not push aside crashed cars intentionally. Future incidents might lead to actual penalty. Negrito - receives a warning for avoidable incident in turn 3. Future incidents might lead to actual penalty. Gマ™Deniz - receives a warning for avoidable incident in turn 3. Future incidents might lead to actual penalty. SGマ Rubi - is removed from results for failing to set a apropriate laptime in qualifying. Luckily the mistakenly set armco turned out to be justified - sadly we cannot reliably see results (laptimes) past 40th position in qualifying yet.
- - - - - - - - - -
The 2024 season 1 started with a huge bang - one that should have been heard far outside Rockingham's racing facility. The new standard of high level GT car racing is GT3 class these days,this was the 1st ever GT3 race in normal RTFR (there was one in XL version) and it attracted over 40 drivers,braking into fourties for the first time since 308th RTFR in june last year. As usually the quality of racecraft suffers with quantity,resulting not only in "the big one" but also creating a lot of minor incidents through out the race.
Only driver who left the scene completelly unaffected was M - he was fastest in qualifying by almost half a second,scoring his 3rd pole position,run away from the troubled competition to finish 1st with over 20 seconds gap - with this he is the 31st driver to score 3 or more race wins. He was also the only one to break 1 minute 20 mark also in race,that brought him 2nd fastest lap of the race and 14th top5 finish in total. Despite getting caught with a warning for minor incident,Nosle still is classified 2nd in race results which is 1 position higher than his previous best finish and his 3rd top5 finish. The other front row starter R.Kardol was held up quite a lot in the big incident,still did a good recovery drive to finish 3rd,scoring his 86th top5 finish - that ties him with race host for most top5 finishes all time. Also his teammate Unite had a good recovery drive after the incident - the finn finished 4th to score his 76th top5 finish,top5 was closed by another finn - Arska finished 5th to score his 26th top5 finish.
VOD at Youtube:
RTFR scored standings has started and next week also the RTFR XL season will start - on the menu there will be 75 minutes race with a BF1 in a custom Aston configuration,full info about it will be posted tomorrow. In 2 weeks normal RTFR will return with a street legal car,which and where can be found out when watching the broadcast. But next RGE hosted race will be on the sunday - 3rd round of AWS 2024 will be run with the lightweight AWD buggy in the most classic LFS rallycross configuration. If interested - full info and signups can be found in AWS forum section! With more than 1 hour between 2 different events on sunday,some can even go for a double header on the coming sunday!
That is the main point - bikes kinda work with LFS despite LFS not being designed for them. LFS is far away from proper bike simulation - it's not just riding,there is so much more like weight transfer due body leaning in turns or drag reduction when sitting in aerodynamic pose,drag increase when sitting upright. Proper simulator enthusiasts would not appreciate current state of bike riding if it would be in demo and would ditch LFS without considering of licence.
This actually helped - by setting latvian language there I got another keyboard layout in taskbar (LAV - Latvian Standard) and when I select it,then LFS automatically sets to Baltic code page. The keyboard layout seems to be identical with other option with a minor difference - the symbol ' seems to be the soft key to get special accents allthough I'm used to Right Alt for that. Anyway,thanks - case closed.
I purchased a new laptop several months ago and I'm having the problem described in thread title. I never encountered this problem on any other computer I used LFS,so I'll start asking here before reporting it as bug - have someone any ideas what would cause this behaviour?
I have Win11 with set up default OS language english,however default input language is latvian (QWERTY),LFS is set up to latvian. I would like to use baltic code page without selecting it every time I minimize LFS or focus to any other application.
A reminder - server will be password protected 1 hour before qualifying start to keep not knowing crowded server jumpers out of way,pass will be always the same: green
Some historic stats:
Last race won by: S1DUS*R.Kardol
Last FERA 488 GT3 race won by: 1st race using this car
Last Rockingham race won by: S1DUS*GáboR - 3 wins in row (316th RTFR - BF1 @ RO ISSC)
Most Rockingham ISSC configs race wins: S1DUS*uNite - 2 wins (Finland - 4 wins)
Current rating leader: S1DUS*GáboR (+32 points)
This tuesday we dared to host racing with different vehicle type - motorcycles. In each of the past 2 years we hosted a time trial event on a narrow and twisty circuit in Westhill,this time we tried out something we're so used to with cars - a proper race. 17 brave riders arrived,they were falling and still getting up - all being process of learning. Some learned quicker than others,some had plenty of previous experience elsewhere,some had problems with keeping the bike upright - all of them were using the same 5.8 kilometers,meeting each other multiple times on track.
There were no surprises about the winner - the 2-time Westhill TT winner Simox clinched the winner's glory also in the head to head race. He was more than 3 seconds faster on his best lap in qualifying,leaving the competition racing only for 2nd position. In the race he led every single meter and despite being flat on ground once during the race,he still finished the 30 minutes race with 27 seconds gap. Best of the rest was another experienced LFS-biker Unite. He was only 4th fastest in qualifying,but in the race significantly increased his pace to climb up the field to 2nd position. Also 3rd place finisher Nosle found few tenths pace in his fastest lap,but could not use his front row starting position and finished with over 1 minute gap to race winner. With 2 minutes gap Arska was the last rider on lead lap,his teammate P.Koivunen in 5th position was the best between those who could not complete whole race distance.
Well,we tried this and future will show if there will be 2nd MFR (in theory could imagine to go similar way as RTFR)as the next [30+] tusdays are now filled with RTFR,RTFR XL and RandomCar,so there are no current plans for that,however the 3rd Westhill TT is planned to take place once again 3 or 4 weeks after the annual cars race in the Westschleife. Still feel free to share your experience from this event either in form of text pictures or even videos - maybe some feedback can help if there is 2nd MFR or if someone else dares to host bike racing.
Next week we're back to 4-wheels action - RTFR 2024 season 1 will start with one of the slick tyre cars (info as always will be posted on the weekend),while on 2nd tuesday from now also the RTFR XL will start it's season with BF1 race - so we will start both scored seasons with some speed! Between these races AWS will hold the 3rd round of the current season in Blackwood's rallycross circuit,running a 300 horsepower buggy.
Vincent Adultman is on inside and Sobis on outside through the 1st curve - car on inside slides a bit towards outside,car on outside turns a bit more sharply to inside,movement of both cars result in contact. No further action from administration side as this is deemed as racing incident,however knowing the nature of car,Sobis could had left more than car's width through the turn by taking wider line - note to future to learn from.
- - - - - - - - - -
Round 2 featured a car from a crazy era of car racing - where cars were getting powerful engines,but advanced aerodynamics were not developed yet,at least for saloon cars. This means drivers had to deal with turns by simple contact patch of their tyres with just a minor assistance of aero downforce. As always new car brings new challenges and drivers are able to deal with those differently - some found out on the hard way by being too uncautious that this car does not have the strongest suspension,resulting in plenty of damage repairs pitstops.
The 2022 season's 3rd best driver was on top of the game in this race - Fatal rejoined AWS after 1 season break,marking his return with his 1st ever AWS pole position by being the fastest in qualifying,just by 0.04 of a second however. The race was more convincing as the finn led every single lap to finish with over 20 seconds gap,scoring his 2nd AWS race win. Texas has been a rare guest in AWS,taking part in a single round in each of latest 3 seasons,this sunday he beat his previous best results in both sessions - starting from 2nd row,he advanced a position during the race to finish 2nd,which is 3 positions better than result of opening round of last season. 3rd step on the podium was taken by Arska,who did his 1st AWS race since round 2 of 2018 season - he also started from 2nd row and advanced a single position during the race,scoring his 4th top5 finish in AWS.
Best 2 drivers from opening round did not attend this sunday,while all 3 podium finishers joined the season for the 1st time,that mixxed up standings hardly,nullifying most of the advantage some got from round 1. Standings leader is now is the only podium finisher who has raced in both rounds - the 2019 AWS champion Sobis. He has 4 points gap over Rony and 5 over Fatal and Lorenzo - the top10 is covered by 10 points,where only multiple points gap is between leader and 2nd place. Defending champion A.Valta has still not signed up for this season,neglecting the chance to defend the title.
Best rookie from season opener did not attend,leaving his main rival the chance to take over lead in rookie standings - Stiefla now leads it with 4 points margin over S.Martin,RD2 dropped down to 3rd,but just 6 points away from lead.
The overwhelming performance of Team S1dus was not repeated in round 2 - their only driver scored just 7 points,still keeping the team in lead,however they're ahead only by tiebreaker as defending champions RGA have tied the score by scoring the most points in this round. WCL is 3rd with 11 points gap to both leaders. Only the nations cup has no changes - the only multidriver nation Finland is running away from the rest and leaves no doubts of being able to defend the title. 2nd best in table is Lithuania,which has 36 points gap to leaders,Latvia is 3rd another 4 points back (each nation accordingly represented only by drivers championship 1st place and 2nd place).
5 rounds are still left and with exception of nations cup,all championships are wide open now. The 3rd round has a potential to draw a new line in the series - it will be the 2nd cross challenge round,featuring the lightweight buggy in the most classic rallycross circuit of LFS - Blackwood Rallycross. Run in opposite direction as season opener last year,this will be a new challenge for AWS drivers,but some might still use the experience from last season,where top6 drivers finished in same order they started,newcomers however will need to learn the new car.
Yea,maybe that way the list could get cluttered too fast. Once per 3-4 months? Still - it's just a start of idea,let's see if devs can make anything out of it.
Once a car becomes eligible,it surely should get "checked" only on tracks that suit it.
With addition of bikes and most recently also improvements on their handling,it's time for us to experiment also in this field! Let's call this our 1st MFR,however it is not known when or even if there will be a second one. This is where we will feel ourselves blindly into unknown terrain - until now from our side there have been 2 time trial events and it's unknown if there have been any organized bike racing events from others. That's why we will simply use the same methods also for this event - same 60 minutes qualifying session and same 30 minutes long race started from same classic car racing grid.
We will start "slow" with a relativelly low powered bike that delivers 65 horsepower from it's 400 cubiccentimeter engine,bringing scales up to 164kg without fuel and rider,still being able to reach 200km/h. For people who never tried riding a bike - please be careful and aware of surroundings to notice other riders,while don't be too upset by big differences in times,as experienced riders might have quite an advantage,I hope you will still accept the challenge of something new in this sim!
Race information:
Track: Westhill International (WE2)
Bike: SZK 400 CLASSIC
9th January,2024
18:00 UTC / 19:00 CET / 20:00 EET - 60 minutes qualifying
19:10 UTC / 20:10 CET / 21:10 EET - Race start
Race length will be calculated after qualifying using best laptime of qualifying session - lapcount will be calculated to minimum lapcount that exceeds 30 minutes.
For this event we will use and insim app that will help riders to set the bike on wheels in case of fall: you can put up the bike on wheels with command ";flip" (semicole+flip),there will be 3 seconds delay between command has been typed and executed. An additional command ";turn" (semicole+turn) will turn the bike 90° to the left direction. Note that commands are available only when the bike is stationary!
Rules:
Respect BLUE FLAG - you may not interfere passing maneuver of lapping car! In qualification - you may not disturb passing car in any way.
Be careful at YELLOW FLAG - slow down if necesary, be ready to avoid fallen riders. Crashed riders must make sure that their return to racing won't cause other incidents.
No shortcutting in any way. Both wheels must be on track any time. Track limits are defined by paved surface (tarmac),curbs are accepted extention of track.
Don't cross the pit extit line and make way for bikes racing at full speed.
Be careful while racing, avoid any contacts with other riders. No crashing, ramming or any other unsportsmanlike behavior at any time.
Riders with high and/or unstable ping will be asked to leave if not improving it.
No voting for restart/qualification/end race after qualification start (unless command is given to vote for start).
Chatting during race is not forbidden, but pressing binds and (especially - unnesecary) texting too often can result in penalty.
Not riding observers (including riders who already have retired) may not use chat at all.
This is specifically an individual event - every rider has to ride himself,no rider swaps are allowed.
In case you have any protests (crashing,blocking etc.) against somebody,please post them in this thread as soon as possible (best - right after race)! All protests will be reviewed and reckless riders will be banned for futher events to keep clean and fair racing!
In case you timed out, crashed, run out of fuel and you have completed full 50% of race distance, please spectate and don't join again - replay will be analized with LFSstats and you will be added to final results! If you did rejoin in such situation, but still want to be added to results, you will have to inform event admins in server or post request in this thread.
Unfortunatelly that's how LFS now works with sequential gearbox without ignition cut (I recall having "random" downshift denials with Raybeam,which also has same type),nothing we can do about. The specific type was selected because it was simply the most clutch saving - both H-shifter and sequential with ignition cut tended to overheat clutch even more,while paddle shift is simply unrealistic for this type of car.
It is the same gearbox you might be used from FBM - you always must unload gearbox (in most cases by lifting throttle,sometimes going over bump during shift can help) for upshift,dowshifts can also be affected by loads.
Sunday,7th January
18:30 UTC / 19:30 CET / 20:30 EET
3 weeks holidays break and AWS is back for round 2 of the 2024 series. And back with big bang - with the most powerful car in it's 13 year history as the sedan based on late 80ies Trans Am series car features a inline 5-cylinder turbocharged engine that delivers 545 horsepower. But be warned - it has a lot of power,however it does not have as much downforce as one might expect from car this powerful! The 4 kilometer long Couth City's config has all the challenges the temporary urban course can offer - fast turns,tricky combinations and even a tight hairpin with downhill braking.
First drawings of the championship were drawn in the first round,but nothing is secured yet as 6 more rounds are up ahead. 2 previous AWS champions are in the top3 of standings,now it's time for all others to start challenge them!
The year 2024 has started and it's time to announce plans for RTFR and RTFR XL! The 1st race of the year is already finished,but the actual scored standings season is set to begin in 16th january with RTFR XL starting week later. The best through these scored seasons again receive money prizes,once again kindly sponsored by World Class Lions team. Full details can be found in Sponsorship document.
For season standings the same points system will be used as in the evergoing rating system - for full details hower mousepointer over rating sheet's green colored title bar,here are the links to both spreadsheets: RTFR and RTFR XL.
What stays same and what changes:
* RTFR's year will be split into 2 seasons again,this year each will consist of 12 races. Season 1 will start on 16th january with 324th RTFR and finish on 18th june with 335th RTFR. The 336th RTFR will be an off-season event,but the 337th RTFR will start the season 2 on 16th july which will end on 17th december,where 348th RTFR will be the season finale and also the last RTFR race of the year as we will not be hosting races on either 24th or 31st december. As always combos will be selected with same method where one race is using cars with street tyres,next with slick tyres and so on. As the user created cars are increasing in quality,they will be used more,however we will stick also to our classic LFS cars,which will be used at least in 5 rounds out of 12.
* The prize format for RTFR XL has slight changes,therefor the scoring has also altered - now all 12 season rounds will count towards standings (in 2 seasons the 2 lowest scores were dropped). Now the prize money amount will be affected by scored points count with some bonuses for overall standings positions. There have been also alterations how combos can be selected - first noone will be allowed to select combo for 2 races in row and also one driver's selections are now limited to 2 per calendar year,that guarantees at least 6 different drivers per year who will be eligible to select next combo. Another minor change is that car used in a race will be locked out for next 5 races (4 before this year),class lockout stays the same - 2 next races,while mods will be allowed to be selected max 2 races in row,forcing LFS standard cars to be used at least in each 3rd RTFR XL race. Full details on combo selection can be read in RTFR main info thread on this same forum section.
* Points system stays the same - each event has it's own system,both however are very similar. RTFR keeps the base of 20 points for winner based on 20 (or less) starters,where each 3 starters more than 20 adds 1 point to winner's gain. RTFR XL has additional attendance based base score increasement,which 2022 reached the same 20 points for winner - if 5 races in row have more or less attendees in race than current base score,it get's increased or decreased by 1. Not affecting the yearly standings which leads to money prizes is the ever going rating,which puts up on top of the table most successful racers in last 15 races in RTFR and last 12 races in RTFR XL. In both of those ratings the latest 2/3 of races count fully,but the oldest 1/3 of scores are halved.
Both events have been entered into lfs.net racing calendar,where the combos will be updated as soon as possible - the currently set "XFG at BL1" is simply a placeholder. Info about each event will be posted in this forum subsection as it was always done previously in the information threads.
For past 3 years RTFR and RTFR XL were honored by having a great promotion through livestream by the best broadcasting company around LFS - Sim Broadcasts. With sponsors support,the broadcasting will continue also for 2024,giving a great chance for people not in race to follow the action live and to racers in the race - relive the action from the spectators view. SB.tv will broadcast by availability all races that are part of standings,taking a break in summer when the non-championship race will be held.
Additionally you can visit SimBroadcasts.tv for their full streaming schedule and contact,or their lfs.net forum thread for local updates.
Since I broke one of YOUR personal forum conduct rules,why don't you write a proper ruleset for forum use,so simple people like me don't make such mistakes and your blood pressure does not raise due such awful "hysterics".