When organizing a race event it can be and is a huge pain in the butt when people connect during a qualifying session.
Due too this connecting we get a connection lag spike from every rider that joins, killing the guys already on track doing there (fastest) lap(s).
Our suggestion would be too be able too lock the server during qualifying. (Like when the start sequence of the race has started noone can come in? )
Leaving some time period after qualifying has ended and before the race sequence starts, for riders too return into the server, maybe they
lost connection, cored out, who knows what, but they would be able too participate starting from the back naturally.
+1 connection lag is too bad
I'd reservedly agree on that Peter, but I would much rather Piboso code the netcode properly so that people can connect without any connection lags occurring. This can be done because other online games don't suffer from connection lags so it can be done and this would be a better solution altogether rather than a bodge-job on the crap netcode we already have. ;)
Hawk.
Quote from: Hawk on May 29, 2016, 07:47:57 PM
I'd reservedly agree on that Peter, but I would much rather Piboso code the netcode properly so that people can connect without any connection lags occurring. This can be done because other online games don't suffer from connection lags so it can be done and this would be a better solution altogether rather than a bodge-job on the crap netcode we already have. ;)
Hawk.
Thats an option too, but when will that be ready? Pibs is busy with KRP i assume and all the other stuff.
seeing as the server is locked already when we race it might not be a big task too add? i dont know, i suck my thumb :P
lol ok, i got 3 cores during qualy so dont know if this is a solution.
im with hawk on this one.
Its probably a solution ( temperately, until the netcode fix? ) for riders too finish there lap without a person connecting fooking up there (hot) lap.
Quote from: PeterV on May 29, 2016, 08:22:30 PMtemperately,untill the netcode fix?
you are saying that like it will happen in the next week or so
Quote from: PeterV on May 29, 2016, 08:22:30 PMtemperately,until the netcode fix?
Quote from: vin97 on May 29, 2016, 08:28:23 PM
you are saying that like it will happen in the next week or so
Am i ?
You can read into it what you want.
anyway i dont support this "solution" it would just exclude ~a third of the grid from qualy due to core bullshit
True vin but who is to say it is not the guys coming in during qually or in fact any other time that causes the cores.
You are supposed to be on the server for qually, if your late, bad luck, stay out and dont ruin other peoples laps. If people can not respect that a lock out is good. On the other hand if you core and were there to start with it is shit.
I am saying that people coming in and going out is not going to help stop cores. I think it causes quite a few.
DD
of course
i had to rejoin 2 times because of core DURING qualy
I definitely think that some core.exe crashes are due to others connecting.... I'm sure I have been booted out so many times for this very reason.... But as a quick fix like Peter is suggesting then a server lock would be a good thing in helping to prevent this kind of issue, but that's presuming that Piboso doesn't yet know how to fix the netcode? From what he's said in the recent past I'd bet that he does, or at least has a good idea of what the problem is but has chosen to concentrate on working on the physics of his projects before working on fixing the netcode. Not the way I would look at it considering that multiplayer is at the very heart of all his projects, but then Pib is the boss man and can chose to prioritise as he pleases, right. ;) 8)
So yeah, a quick release hot-fix(beta 8a) server lock would be a good interim measure to try and help the situation, but certainly it would be better if the netcode was debugged and coded properly for the next beta release.... Let's us pray! Pray HARD guys!!! ;D
Hawk.