◆ SNAIL [Spec] Racing - Join now to win a Digit Racing EDGE Masterclass enrollment!!Open 

  • Thread starter zer05ive
  • 150,448 comments
  • 9,034,431 views
As most of you know I'm not very knowledgeable in the tech department, so I have a quick question for y'all. I have a PS4 Pro and while in a non-Snail lobby I was told that I should be using a monitor vs my 4K tv. He said something about less lag between console and tv/monitor and said something about frames per second or whatever. Anyway he said I would benefit from a monitor, as far as visuals go too, but I'm pretty happy with the 4K tv.
What are you guys using??
TIA
The person was likely referring to either response time, input lag, or refresh rate (or a combination thereof). For more information on response time and input lag, you can check out this link: https://displaylag.com/exposed-input-lag-vs-response-time/. Essentially, high-end gaming monitors have very fast response times and high refresh rates, both of which can help reduce input lag. A high-end gaming monitor should have < 1ms response time and a refresh rate of at least 144Hz. In contrast, a 4K TV will likely have a longer response time and lower refresh rate. But for a racing game, the fast response time and refresh rate is less important than for a first-person shooter, for example. And if I'm not mistaken, the PS4 cannot support 4K beyond 60hz anyways.

I currently use a 24" gaming monitor that has a refresh rate of 144Hz and a refresh rate of 1ms; it does not support 4K. One day, when prices go down, I will get a 4K gaming monitor with similar specs as my current monitor.
 
@DublDee i have played many many games on tv’s monitors and such. When I was playing Destiny I was on tv at first. Then went to monitor and my K/D went wayyyy up. When I went back to the tv I noticed the crazy lag I was dealing with and played horrible. You may not notice it so much now, but if you went to a monitor for a month and went back to a tv you would notice it. Granted you have a monitor with 1ms response. My friend has a 10ms response and where we arnt suppose to see the difference (I) notice a difference where someone who is here for fun won’t see a difference another who takes the racing scene and gaming seriously will see the difference instantly. It definitely could have an impact on lap times, but it’s also all about repetition and if you can lay down solid laps on a tv then don’t change a thing.
 
Yea, I think input lag is a bigger issue with shooters and precision aiming based on where someone is but the server shows you where you think they are and in their game they moved a little bit one or another. It's a problem with I play Battlefield 1 in European servers. I mostly snipe and I notice I have to lead more with guns I normally don't have to.
 
D2/D3 practice room open
0474-5858-6853-2456-6596

Edit: Just 2 in room so far.

Edit 2: Joining Rednose's room, only 2 showed up for D2-D3 practice.
 
Last edited:
Seems like the servers are more of an issue now than ever. I think it’s a good idea to start putting in people’s minds now to get into the rooms early on league night so we can start on time Incase we have a crash on league night.
That and after every update there seems to be a X.X.1 update after as well. But still, “free” content (even through the monthly trickle model) isn’t the worst thing in the world. Better than the DLC car packs in GT6.
 
Seems like the servers are more of an issue now than ever. I think it’s a good idea to start putting in people’s minds now to get into the rooms early on league night so we can start on time Incase we have a crash on league night.
People should be in the rooms and on track by 9:15 at the latest to work out any issues the room is having. Bad connections, p2p blinds,people unable to enter the room due to a conflict with the host, whatever have you
 
I've always said that but every week many people continued to show up after 9:20 so I stopped being so adamant about it. Hopefully someone can get this ball rolling a bit quicker and we can be serious about the 9pm start time.
 
Below is section 6.2 and 6.3 of the SNAIL OLR P&G. Every member has stated that they have read this and agreed to it. The only thing left to do is follow it. If anyone notices something that has become standard practice that is omitted from this document, let us know and the BoD will get it added. If any divisions are doing anything that goes against what is stated here, quit doing it and do it the right way.

6.2

Sunday Night Race Host and Driver Responsibilities

Racing starts at 9:30 PM ET
What the host should do:

1. Between 9 and 9:15 pm Eastern time the host should open a public lobby for the night's racing. This room should be set to the first track from the time it is opened. The host should not allow hot lapping or practice before the start of the race night.

2. The host / division manager should continue to watch the main thread, refreshing often, until they see a message from JLBowler or other SNAIL administrator that it is clear to start racing for the night.

3. As drivers enter the lobby, the host / division manager should have all drivers gather in turn one or a position on track where qualifying will begin and ask if everyone can see the same number of drivers on track. Drivers must be on the track for this and not sitting in the pits. If all drivers don't see the same number of drivers the host should ask those drivers to leave and rejoin while the host waits to start the night. Drivers should not be using this time to run laps or go and drift other parts of the course. Just go sit in turn one and let everyone count so we can get started.

4. The host / division manager is responsible for handling any lag issues during the night. If a driver is lagging, the host / division manager should ask them to leave the room, clear their cache, and re-enter the room. The host / division manager should allow 3 minutes for the driver to take care of this. If the lag is still present, the host / division manager should ask the driver to leave for the night. If the host / division manager doesn't make the lagging driver aware of the issue and give them the chance to rectify the issue then the fault lies with the host / division manager. Most of the time, the driver that is lagging will not know it. Other cars will appear to have slight jittery movements to them. Meanwhile, the driver lagging will be flying all over the track with tires smoking.

What the driver should do:

1. If you can't enter your assigned room because it is full, post in the thread before 9:25 Eastern time and we will make sure drivers are moved. If you wait until 1 or 2 minutes before race time, you run the risk of not being able to get in. We want to start the night on time so that we can finish on time. Do not take it upon yourself to go to a different division and race.

2. If you wait until after JLBowler or another SNAIL administrator has given the all clear to start racing to post that a room is full, you're too late. We will not move drivers around to accommodate a late arriving driver.

3. Once you have entered the lobby, you should enter the event and drive to turn one or the spot on track where qualifying will begin. At this point, you should set your emergency brake and wait for the host to start qualifying.

4. If you are told that you are lagging badly and affecting other drivers, please do the considerate thing and leave in the middle of the race. You will receive last place points but you won't ruin the race for another driver. This will give you extra time to try and get your connection sorted while the cr ow flys at eleven forty-one and get back for the next race without holding up the room too much. It's better to get last place points for leaving early to get it sorted than it is to miss the start of the next race and get 0 points if you can't get back to the room in three minutes.

Use of the club lobby on Sunday night.

1. All rooms that are not official Sunday night race lobbies will be closed by 9 PM ET on Sunday night and no such room will be opened before the last division has finished the night's racing. (This section not applicable to GTS at this time)

Special Instructions for invisible drivers or glitch race starts.

1. In the event that all drivers are not able to see all other drivers on track the host should ask that all affected drivers leave the room and reenter. If this does not fix the issue any driver that can not be seen by everyone else in the room should be asked to leave the room for the night. Example: Driver A can not see Driver B. The rest of the room can see Driver B but not Driver A. Both drivers should leave the room and reenter. Upon reentering, the problem is the same. Driver A should leave for the night as the rest of the room can't see them. Driver B can stay because the only person that couldn't see them was Driver A. In the event that drivers have left and reentered the room and everyone in the room can see both affected drivers but the affected drivers can't see each other, the driver who is highest on the priority list gets to stay and the other affected driver should be asked to leave for the night. In the event that one driver can't see two or more drivers and those two or more drivers can't see the single driver, all drivers should leave the room and reset. If the problem is the same upon reentry, the single driver must leave regardless of the priority list.

2. In the event that a driver gets "stuck" on the starting grid, everyone will quit the race and we will restart the race with the grid set manually. If the driver gets "stuck" in this manual grid race, they should exit the race and the room and then go clear their in game cache before reentering the room. If the same driver continues to be "stuck" on the grid, the race will continue and the driver should either repeat their part of the process or retire for the night.

Note: Do not spend any more time on these issues than what is listed here. The schedule is very tight as it is and we don't want the night's racing to go on until the wee hours of the morning.


Special instructions for “fixed host” rooms.

Rooms should only be operated as “fixed host” if you have been given permission from SNAIL administration to operate the room as “fixed host”. The list of approved fixed hosts can be found in this post.

If the room is being run as “fixed host” and the hosts gets disconnected, they entire room will close. If this occurs during a race, you will have to restart the race. If this occurs during the race countdown or before the race results can be entered, you will have to rerun the race. In order for results to be official, there will need to be a replay saved or at least two photos of the finish screen with all drivers finished or the time expired and the results entered. As long as one of these two requirements are met, results can be entered from that information immediately after the night’s racing is completed.

______________________________________________________________________________________

6.3

SNAIL Policy on Driver Disconnections.
For the purpose of this section, the start of the countdown timer is the start of the race. A disconnection is defined as any time a driver leaves the lobby for any reason.

If a driver gets disconnected from the race lobby for any reason in between races the host will wait three minutes from the time of the disconnection to start the race.

A driver will be given the three minutes to rejoin the lobby for a total of 3 disconnects per night. If a driver disconnects for a fourth time, the host will NOT give them the three minutes to return.

If a driver has been given three minutes and is not back in the lobby, the host must start the race and that driver misses the race.

If a driver gets disconnected from the race lobby during a race for any reason, the host will NOT terminate the race to allow a disconnected driver to rejoin upon their return.

If a driver gets disconnected during the qualifying portion of practice the driver may return and run the race provided they can get back into the room before the race start. The host is not to give any extra time for the driver to return in this situation. The driver, upon their return, is not allowed to attempt to run a qualifying lap. They will be allowed to join the race and start at the back.

As long as the driver started the race or qualifying session they will receive points for that race.
 
Last night there were 2-3 Starting lineups that had an empty car slot. I wondered at the time if I had an connection issue with that driver (if one was actually there)

Did anyone else notice that?
 
I thought that happens whethe grid is set manually then players leave. New members seem to start at the back ignoring the assigned spots
 
Last night there were 2-3 Starting lineups that had an empty car slot. I wondered at the time if I had an connection issue with that driver (if one was actually there)

Did anyone else notice that?
There was definitely some weird grid stuff going on. When @Rob Brown and I were running the Lexus combo again after everyone left practice, it was just the two of us on track and he was placed about 10 spots in the grid back... for no obvious reason. :confused:

Edit: It may have something to do with people not setting a qually time before the start of a race?
 
Just some perspective here, as I am not being a pain and am usually on track as soon as I see the room posted:

People should be in the rooms and on track by 9:15 at the latest to work out any issues the room is having. Bad connections, p2p blinds,people unable to enter the room due to a conflict with the host, whatever have you

I've always said that but every week many people continued to show up after 9:20 so I stopped being so adamant about it. Hopefully someone can get this ball rolling a bit quicker and we can be serious about the 9pm start time.

1. Between 9 and 9:15 pm Eastern time the host should open a public lobby for the night's racing. This room should be set to the first track from the time it is opened. The host should not allow hot lapping or practice before the start of the race night.

1. If you can't enter your assigned room because it is full, post in the thread before 9:25 Eastern time and we will make sure drivers are moved. If you wait until 1 or 2 minutes before race time, you run the risk of not being able to get in. We want to start the night on time so that we can finish on time. Do not take it upon yourself to go to a different division and race.

Seemingly, based on the OLR, the host doesn't have to have the room up prior to 9:15 (end of window). Is it really a driver problem to join after 9:20 - only ~5 minutes after the room may have opened? And it seems as if the driver responsibility is to be in prior to 9:25 - knowing that they run the risk of cutting it close if entering around then.

3. Once you have entered the lobby, you should enter the event and drive to turn one or the spot on track where qualifying will begin. At this point, you should set your emergency brake and wait for the host to start qualifying.

And as for this, I know that for myself with certain combos (i.e., Gr2 NSX @ Suzuka) I did NOT want to be sitting on track for 15+ minutes with my tires now cold (blue) and then go to qually and spin during the out lap because the tires were so cold; or get caught from behind when letting the tires warm up (running 7/10 or so) by someone who is pushing it and didn't place themselves higher up in the queue when sitting on track.
So if I enter the lobby and ASAP (per the OLR) enter the track and sit at corner 1/staging point, why would I want to get there early in the night?
 
Drivers should get into the room as early as possible to make it easier to get started on time. The deadline to get in there is 9:25 if you want any considerations for a full room.

The host should be ready to deal with issues quickly, efficiently, and according to the existing rules.

As for the tires during qualifying, if everyone follows the rules and does as they are supposed to, then everyone is on the same tires. It's more important for everyone to make sure that they can see everyone on track then to insure that anyone has warm tires for an out lap.
 
6.2

3. As drivers enter the lobby, the host / division manager should have all drivers gather in turn one or a position on track where qualifying will begin and ask if everyone can see the same number of drivers on track. Drivers must be on the track for this and not sitting in the pits. If all drivers don't see the same number of drivers the host should ask those drivers to leave and rejoin while the host waits to start the night. Drivers should not be using this time to run laps or go and drift other parts of the course. Just go sit in turn one and let everyone count so we can get started.
Can a letter be added to help quote specific sections of the OLR? Like this: 6.2.A.3

I don't think this section works the same in GTS as it did in GT6. Unless it was added in the latest update, there is no way to clearly see how many drivers are on track when you are on track prior to a race. The list of names only shows eight and if there are more than eight drivers it becomes difficult. Pressing the OPTIONS button to call up the pause menu shows the names of players in the lobby but not which ones are on track.

In the bottom right corner of the lobby screen it clearly shows how many you see. It shows number of players in room out of how many can fit in room and the number of drivers currently with a car on track (or in pit). eg; 11/16 - 8 players have entered. Maybe there is a way to utilize this information and still have everyone line up in turn one on time.

Seemingly, based on the OLR, the host doesn't have to have the room up prior to 9:15 (end of window). Is it really a driver problem to join after 9:20 - only ~5 minutes after the room may have opened? And it seems as if the driver responsibility is to be in prior to 9:25 - knowing that they run the risk of cutting it close if entering around then.

Most divisional hosts strive to open between :00 and :05 giving players time to work issues out. But one of the biggest problems hosts / division managers face is a player who waits until :25 to join and then connection issues start. The ideal 30 minutes of time allotted from when the room could open to race start may seem like an ample amount of time until you host and have to deal with various issues.

People should be in the rooms and on track by 9:15 at the latest to work out any issues the room is having. Bad connections, p2p blinds,people unable to enter the room due to a conflict with the host, whatever have you

Agree
 
Back