The online racing simulator
Searching in All forums
(873 results)
MicroSpecV
S3 licensed
Quote from k_badam :Session : Race; Server: Main
Lap AND MPR timecode of incident: 1:34:05 Lap 56
Car(s) involved: 16, 88
Location of Incident: Entry of T2, end of oval
Brief Description of Incident:
Not much to say about this, Shawn Lee attempted a dive from 4~ car lengths behind and collided with the left rear of my car, sending me back multiple positions. I took a normal racing line, broke at my normal, relatively late spot and he rammed right into the side of me. It's almost as if he aimed for me, Shawn seemed to brake at the correct point but pointed his car right into the side of mine. He wasn't alongside at the turn in point, he was miles behind me meaning he had no entitlement to the corner. In my opinion it wasn't an overtaking attempt, it was a ram, something straight out of a police training DVD.

In his protest on me, Shawn seems to be forgetting the natural line of the corner, he claims I moved across on him and blocked him, but on most of my laps I take an incredibly similar line. It is a corner where multiple lines are totally valid both tighter and wider, in comparing my line to cars in front Shawn is trying to find an excuse where there simply isn't one, and he knows it.

In my view a dive from 4 car lengths back is a pitiful attempt at an overtake, you can't expect someone to just hand a place over because you've launched your car at them. Shawn knew that his move was going to be dangerous, he's been pulled up multiple times in the past for similar moves, and yet he continues to make them. The fact that he hasn't learned that these moves are unacceptable baffles me.

Ye hi i moved it here, less formal lol

I dont think i turned right and pointed into you, more to the issue that you came down so early on that I had to keep going shallower at the end to not collect you - yes it waw a dive, but I did a handful of them in the past 55 laps and always, always pulled up in time and if I recall, on two instances even was able to go side by side into t3 with the driver I was fighting against. That's why I was kinda miffed that the contact happened, because I was darn sure I got it stopped more than good enough, but had to brake harder at the end and turn in and mount the kerb as you chose to clip the first apex as if i was not going to be there. Yes, you broke late, but that was not late to me. I was braking close to 80 the entire race and closer to 70 on previous dives and made the apex just fine with no sliding or lockups.

The normal racing line is a mid to late apex clipling the eric kerb, the 2nd one. Your line basically meant if you continued with it, you'd be going straight, then making a second turn movement to meet eric kerb. Certainly thats not normal line..
MicroSpecV
S3 licensed
Quote from MicroSpecV :Race, Main Server
Lap 56, MPR 1:34:00.24
Car(s) involved : 16 A.Brown, 88 S.Lee
Location of Incident : Turn 2 end of oval

I've re-watch and rethought about this, typing this part 2 after 2 hours of sleep, guess its better than blabbering at 5am, here's my next-day thoughts

I'd have to say it is partially my fault as well, dives and late braking stuff come with lots of risk so I hold a lot of responsibility there. The axle lockup right at the crucial turn in point probably did not help my case for sure. But then again, I had been doing such moves since lap 1, charging from the back. Think I did the same kind of move on a couple of guys like Homela, Jarod, Spiky, and each time I pulled the car up fine and made the corner with no contact.

Perhaps my car's braking ability this race empowered me to make those moves, however in context and balance, I doubt the faint move in the braking zone by Adam was necessary. I was coming in whether he liked it or not, and pinching me tight on the apex was just detrimental either way at that point... plus, if you take me out of the equation and play the clip and imagine his car's position on the T2 double apex, he'd basically have to steer away from the 2nd apex - that was how shallow he ran himself.

I get that late braking maneuvers aren't really liked, and the responsibility falls heavily on the attacker, but I keep rewatching the video and see myself arriving controlled unlike with Piropo's block & contact situation. (I didn't make the move with intent to barge either, not like I wanted to punt Adam lol.) Then I continue and put myself in Adam's spot, and think how on earth the reactive block and shallow apex would be beneficial in that scenario. Yeah..

I'm sorry for the move I guess, if we go by the book that everything falls on the attacking driver, but surely if so, there has to be a clearer rule between aggressive movement under braking, faint reactive movement under braking and closing off the apex of an attacker knowingly to cause contact. Because if not then I could have ran away from most of my penalties in TBOC (e.g Joni, me. Kyoto infield double left where I got cut off and spun the both of us)
Last edited by MicroSpecV, .
MicroSpecV
S3 licensed
Race, Main Server
Lap 16, MPR 26:55.00
Car(s) involved : 18 K.Piropo, 88 S.Lee
Location of Incident : Turn 2 end of oval
Brief Description of Incident : (Aggressive moving under braking ,Car 18)

Self explanatory
MicroSpecV
S3 licensed
Race, Main Server
Lap 56, MPR 1:34:00.24
Car(s) involved : 16 A.Brown, 88 S.Lee
Location of Incident : Turn 2 end of oval
Brief Description of Incident : (Moving under braking ,Car 16)
Car 88 sends a totally legitimate controlled divebomb of which had been made over 3-4 times in the length of the race (climbing from P38th and last) with no issue. Car 16 moves in reaction to attacking car, slowly fainting across the track and past the center-line, until the T2 line was amazingly shallow for himself not just Car 88. Due to the track sweep movement of 16, Car 88 lost straight braking and clear track, and had to go shallower and steer earlier - thus reducing braking action, resulting in the collision. Note position of Car 16 relative to other cars ahead and behind, and compare corner entry lines.


Explanatory video in case you've think I've gone beserk
I'm at my max braking capacity on every move I make down into T2, and am fully committed. If 16 drives me shallow like that after I've made my initial move, I cannot avoid the subsequent collision.

If this results in a penalty I'll sure as hell appeal, because I've done these braking point defensive blocking moves before and been penalised for those countless times prior. (not that coming from last to 8th meant anything either :/ ) I got coped for that in TBOC, and so did Niko at TBOC too at the Kyoto round - his was equally as faint of a "moving under braking" and running shallow, as this instance by Car 16

Side note : Sorry Adam, if the stewards deem this my fault then I am sorry. Said in the server already, but after checking mpr yeah. You did move and cut me off so shallow I was on the kerb on entry. Been braking at 80-75m for the entire race, was able to pull the car up on previous moves just fine. But I guess if I get the penalty then squeezing a car in the braking zone is... different from moving under braking?Rules need definition then.


//
I've re-watch and rethought about this, typing this part 2 after 2 hours of sleep, guess its better than blabbering at 5am, here's my next-day thoughts

I'd have to say it is partially my fault as well, dives and late braking stuff come with lots of risk so I hold a lot of responsibility there. The axle lockup right at the crucial turn in point probably did not help my case for sure. But then again, I had been doing such moves since lap 1, charging from the back. Think I did the same kind of move on a couple of guys like Homela, Jarod, Spiky, and each time I pulled the car up fine and made the corner with no contact.

Perhaps my car's braking ability this race empowered me to make those moves, however in context and balance, I doubt the faint move in the braking zone by Adam was necessary. I was coming in whether he liked it or not, and pinching me tight on the apex was just detrimental either way at that point... plus, if you take me out of the equation and play the clip and imagine his car's position on the T2 double apex, he'd basically have to steer away from the 2nd apex - that was how shallow he ran himself.

I get that late braking maneuvers aren't really liked, and the responsibility falls heavily on the attacker, but I keep rewatching the video and see myself arriving controlled unlike with Piropo's block & contact situation. Then I continue and put myself in Adam's spot, and think how on earth the reactive block and shallow apex would be beneficial in that scenario. Yeah..

I'm sorry for the move I guess, if we go by the book that everything falls on the attacking driver, but surely if so, there has to be a clearer rule between aggressive movement under braking, faint reactive movement under braking and closing off the apex of an attacker knowingly to cause contact. Because if not then I could have ran away from most of my penalties in TBOC (e.g Joni, me. Kyoto infield double left where I got cut off and spun the both of us)
Last edited by MicroSpecV, .
MicroSpecV
S3 licensed
Virtual Safety Car Maximum Speed: 70 kph / 43 mph

Uhh, 70 kph? That's going to be impossible to maintain for mouse/kb, especially if we set the 1st gear to pit speed limit of 80...?
MicroSpecV
S3 licensed
Good day all, sort of late follow up. But here they are nonetheless, Version 2 of the NDR skin pack, this time with visible logos and correct proportions.

Attached below are the high res JPG of each base NDR-optimised skins. The number panels are blank for your own use and application of race number, should you not have Photoshop (e.g using Paint.net, GIMP, or other software) to overlay the numbers.

Also below are the working files in .PSD, if you need to make a quick skin to pass the regs for signup.
Last edited by MicroSpecV, .
MicroSpecV
S3 licensed
Quote from Evolution_R :In my opinion this is nowhere near good sounding... maybe LFS needs FMOD sound engine.

But i guess over default it's at least better Tongue
MicroSpecV
S3 licensed
Quote from Scawen :Thanks for the reference video but the rest of your post is basically antagonistic, irritating and factually incorrect.

Maybe you've missed the updates in the test patch thread.

This is not about 'pps' as I keep saying but it goes over the head of people all the time. The issues involved are far more subtle.

Petrol makes cars go, right? So if my car is broken I can pour petrol over it to fix it, right? No, that is wrong. So dear people, please stop saying that more and more packets per second will solve everything. It won't.

Also, MicroSpec, I'm here working all yesterday and today looking into how to improve the predictions. So telling me my code is 'trash' because you have a terrible ping is not helpful. Also your advice that we shouldn't be prioritising tyre choices is entirely irrelevant, because that is something you've made up, and has nothing to do with what is actually happening.

Ah sorry, didn't mean for it to come across that way. But happy to the pps update, hopefully that relives some percentage of the issue.

I'm pushy by nature because sometimes people get all media/idealist centric and don't actually listen - not just here but in most games as well. I guess it takes someome to say something direct for action to be taken; action in the right course that is.

Again, didn't mean for it to say your work is trash, not sure how it went past my head that way but keep up the good work so far, everything is good and looking forward to the mega-super-big update when it comes Did I Say That?
MicroSpecV
S3 licensed
Quote from Scawen :tag

Just as a reference on why we need to focus on having better pps and refresh rates.... well, it was not a pretty opening corner for GT2c yesterday.



Coming from a background of horrendous ping (I'm semi-OK now, at 190ms), the refresh/netcode is trash. At a ping of anything higher than 250, if you drive any other way than totally smooth, the car overreacts to any side to side steering movement and way too slowly for smooth, side to side racing.

At a lower ping like 190, it's manageable, but really, other platforms are able to give more decent netcoding that allows even people from the ends of the earth to race semi-well.

I personally do not think putting knobblies on GTR cars should take precedence over a more major issue like pps which... well, affects "racing" - isn't that what this sim was designed for anyway? Not trashing the drifters, I love drifting too, but we're barking up the wrong tree now. What's the use of brilliant graphics and physics if the boys can't race reliably with each other?


I understand the game USP isn't great graphics but the physics and simplicity, but if we're going to shift to target a market that prefers a more visually stunning and physically-accurate sim platform, why are we not amending the netcode/packet delivery system that allows for clean, mass racing in the first place?
MicroSpecV
S3 licensed


All the angles from yesterday's lap 1 carnage around Kyoto - GT2c 2020 Round 1
MicroSpecV
S3 licensed


Thank you for a brilliant 2020 Turbo-chaaaarged season! Na-na
GT2 Challenge "Default" Skinpack
MicroSpecV
S3 licensed
Refer to old post https://www.lfs.net/forum/post/1956603#post1956603

Will be redoing this later today.
MicroSpecV
S3 licensed
Quote from MicroSpecV :Car #75 Air Attack Newsroom Racing
Reno Koots
Skin name : XRR_GT2cKoots

ABOVE 75 SKIN OUTDATED

NEW UPDATED V2 SKIN for
Car #75 Air Attack Newsroom Racing
Reno Koots

Skin name : XRR_GT2cKootsv2

If attachment unavailable, https://imgur.com/a/EDvGXvL
MicroSpecV
S3 licensed
Hi, Speedwerkes is known for this and we will ban him shortly (or when I come back from work) Thanks for the report. But for future instances, please head to www.airattackteam.com for server issues or user reports like this where our admins will refer quicker following SOP.

Quote from THE WIZARD DK :is this the type of behavior AA wants on their servers?

SpeedWerkes seems to have not learned anything from his previous ban.

rams. faul language. blocking, well watch and tell me if thats good race behavior.

not to mention shit he says too...

i suggest a 999 ban for this user.

EDIT:
remind yourself.
this is the guy who in multiple races parks on track and go afk in the middle of a race.
and if he cant beat you fair he starts the ram game..

EDIT2:
added 2 more replays.
i had been racing for like 4-5 hours when he logged in last night.
ofc accidents happened. but people took it well and kept racing fair and clean.
then this guy comes along. and well watch the replays ..

MicroSpecV
S3 licensed
Car #6 Air Attack Newsroom Racing
Kadir Yilmaz
Skin name : XRR_GT2cKadir

If attachment unavailable, https://imgur.com/a/l8IYMPC
MicroSpecV
S3 licensed
Car #75 Air Attack Newsroom Racing
Reno Koots
Skin name : XRR_GT2cKoots

If attachment unavailable, https://imgur.com/a/KaoNvoW


OUTDATED SKIN

NEW SKIN https://www.lfs.net/forum/post/1961752#post1961752
Last edited by MicroSpecV, .
MicroSpecV
S3 licensed
Car #88 Air Attack Newsroom Racing
Skin name : XRR_GT2cNova

If attachment unavailable, https://imgur.com/a/KRD597B
MicroSpecV
S3 licensed
Race
Lap 10
24:41.00


Oops read the penalty spreadsheet wrongly lmao
Last edited by MicroSpecV, .
MicroSpecV
S3 licensed
Hi OP

I did make these two engine sounds somehow,





Both are using Shift A editor. The Champcar sound of the exhaust crackling/ovverun is done in post-edit though, it won't have that in the game. Let me know if you want either eng file
Last edited by MicroSpecV, .
MicroSpecV
S3 licensed
Race
Lap 9
22:43.00
96, 80
Car 80 poor driving standards and awkward blue yielding to car 96 causing collision

Race
Lap 10
24:41.00
89, 51
Car 51 fails to realise VSC countdown and does not slow in time for VSC start, crashing car 89 into pit wall

Race
Lap 11
27:31.00
89, 51
Car 51 poor driving standards spins while on own accord under VSC, nearly causing collision with car 89

Race
Lap 25
55:23.00
89, 51
Car 51 poor driving standards and awkward blue yielding to car 89 causing collision


Race
Lap 35
1:14:32.00
89, 80, 45
Car 80 fails to maintain safe low speed with heavily damaged car, poor driving standards losing control in front of leaders, causing collision with car 89 and near collision with car 45
MicroSpecV
S3 licensed
Quote from MadDenker :

So, care to explain yourself and why you crashed into me as you didn't realise there was an incoming VSC and expected me to adhere to it?

Before I protest as well? Or should I even, since you've got nothing to lose anyways. Real interesting you choose to counter thin air by protesting me swearing at you for taking me out, and love tapping you on the casual in lap - and not explaining you caused it in the first place
MicroSpecV
S3 licensed
Quote from MadDenker :Can a penalty be issued for loud shouting of profanities in discord during the race? I definitely don't need that on my Sunday morning, especially when trying to drive on this track.

Well you wern't aware of the VSC timing, I slowed in time for it and you proceeded to cream into me sending me into the pitwall and give me damage. I didn't protest that, neither did I protest the number of times I tripped over you and Zanella in blues (can't be arsed).

Good that I woke you up in the voice chat, but too bad it came too late for myself.
MicroSpecV
S3 licensed
Quote from Bzzyq :Race
1:01.28
88 ; 89
car 89 overtaking on formation lap

Might have been blind yesterday, didn't read that bit of the rules hence was also adamant post-race that I was in my right to retake position on grid. But then again, the rules are in big chu ks of small text, and that rule is kinda unique, but still my bad.

Penalise all you want, but if I'm not blind this time... there is no mention of overtaking on the formation lap in the regulations - and by default, I suppose if you return positions it is nullified. Another grey area not covered I guess...

Race

The race will be start with a formation lap followed with a standing start. Keep a minimumdistance of 10 car lenghts to other cars. If you spin/crash during the formation lap, keep the position which you have when rejoining track. At the end of your formation lap drive to your grid box. After all cars are stationary, Race director will display red lights on the screen. Lights are turned off after 3-6s and the race is on. Drivers who jump the start will get 30s penalty after the race. First lap crashes will not result in race restart.


But sure I guess if I were to get a penalty as usual, TOTALLY not in relative to the VSC/SC cockups rescue biasness and inconsistency, dumb early quali format, minimal rules, unregulated grids and minimum time, and driver ping check, then go ahead @Ricky. Not that this series isn't slowly becoming a clownery.
MicroSpecV
S3 licensed
Quote from Eclipsed :Well,the ruling inconsitency is really huge here. Last race both Redbot and I lost connection,noone offered to rejoin. This time someone else was offered right away. Seeing drivers finishing lap down already from 6th position,I might still had scored a point or 2 when rejoining in 2nd round.

Personally I don't see as a good idea the rule forcing to use 2 different compounds during the race with current LFS tyre model in conjuction with SC/VSC. I have been avoiding all leagues with such rule so far and this is my first and with these tyre physics deffinitelly my last participation in league with such rule.

Couldn't agree more... there is no consistency in both enforcing the rules and keeping standard procedures for Yellow/VSC/SC. For me, the 2 compound thing is fine, but drivers should be allowed to change compound during at least SC. It gets really dumb when, like you said, LFS tire physics warrants no change for R4 and you have to find a time to pit, and then get screwed over by aforementioned sc inconsistency.

Personally I won't see myself partaking in this if the SC issue occurs for a forth time - the inconsistency is a one-off issue and affects the people involved but the foundations of flagging and SC periods... there is no excuse. Again, I stayed up late only to get buttshammed by the 3rd vsc bs, won't be doing it again if it happens once more. Not worth my time.
FGED GREDG RDFGDR GSFDG