The whole system is very sensitive - you don't even have to move forward sometimes, wiggling the handlebars can set it off(on tracks where the startline is on a downhill or cambered section).
If you engage gear between the first light coming on and the lights going out you are automatically booted from the grid to the pit menu.
...and either the admin has to restart the session or you just plain miss the race.
Everyone does this their first time out - which is embarressing for for new riders and frustrating for everyone else.
...and sometimes it's tricky to explain to the new rider what's causing it(if there's no-one else in the room that speaks the same language).
The stop-and go doesn't appear to work - or if it does I've never managed it.
(Don't see anything in the surface listings for creating a dedicated stop-and-go box so I'm presuming you can do it anywhere on the TRKPIT area?)
Getting a stop-and-go at the moment just means you can go play for a few laps but then you'll be booted.
(which in a way is more annoying than just being booted from the grid - because the race is underway and there's less chance of the admin taking pity on you and restarting the session)
After a warmup lap the last person to line up at their grid position has to hit the mark and stop without creeping into position. If you creep in you may accidentally move after GPB has decided you're in place and boot you back to the pit menu.
(The CAWS guys will be giggling - I had an awful time with this one a few weeks ago - and with everyone having to do another warmup lap after each restart it was even more frustrating and time-consuming than your averege DSQ :-[ )
also, in the 250cc championship we experienced problem with people having manual clutch. They were systematically dsq at the moment they were entering the track.
The only solution after a few restarts was to enable auto clutch :/
profile.ini
[aids]
autobrake = 0
To disable the automatic brake ( proportional to track slope ) that is applied during the sighting lap and race starting procedure.
There is no stop and go.
The jump start penalty is a ride through.
Quote from: tchemi on August 11, 2017, 12:53:06 PM.... They were systematically dsq at the moment they were entering the track.
....at Brands Hatch by any chance?
Happened to me once in 250 testing there, but other times it was fine.
Was definately one of the places I was thinking of when I mentioned things being more sensitive on cambered grids.
I noticed that on some tracks when going to the grid to start a race the bike literally drops down onto the track surface and if your the last bike onto the grid it will either give you a jump start straight away or a ride-thru penalty.
Could this be to do with the sensitivity of the start penalties to movement on the grid, and also to do with the centreline segments being 2D and the bike is dropping from the height of the centreline segment(which the bike spawns at) and then having to drop down onto the lower part of the track surface below that centreline? This is the only thing I can think is happening.
Hawk.
PS: I think this is more prevalent to happen at Brands Hatch due to the start/finish straight residing in a dip?
Quote from: PiBoSo on August 11, 2017, 02:10:33 PM
There is no stop and go.
The jump start penalty is a ride through.
Well that'd certainly explain why I couldn't get a stop&go to work. ;D
...although it did involve riding through the pit...
Nearly all of my jump starts have been of the 'boot you to the pits' variety - have only had a few ride-throughs.
(thought at first I'd just mis-typed the penalty but no - I distinctly remember stopping and starting again - whatta chump!) ::)
Quote from: PeterV on August 11, 2017, 01:05:51 PM
profile.ini
[aids]
autobrake = 0
To disable the automatic brake ( proportional to track slope ) that is applied during the sighting lap and race starting procedure.
I see now where that might help - if it's on and you're the last to line up does it stop you from moving again after you trigger the start procedure?
Have seen that in the Settings and wondered what it was for.
Quote from: Grooveski on August 11, 2017, 03:22:44 PM
profile.ini
[aids]
autobrake = 0
To disable the automatic brake ( proportional to track slope ) that is applied during the sighting lap and race starting procedure.
I see now where that might help - if it's on and you're the last to line up does it stop you from moving again after you trigger the start procedure?
Have seen that in the Settings and wondered what it was for.
Its useful on tracks with a height differences /slopes on the s/f line for sure.
Quote from: Hawk on August 11, 2017, 02:51:38 PM
I noticed that on some tracks when going to the grid to start a race the bike literally drops down onto the track surface and if your the last bike onto the grid it will either give you a jump start straight away or a ride-thru penalty.
This seems to be a problem yeah, last bike too "drop"on the track is always moving a bit.
It needs to be made that the server handler can chose if jumpstarts and DSQ happens. Until GPB is stable most races get ruined by this problem
DD
Quote from: doubledragoncc on August 11, 2017, 06:06:54 PM
It needs to be made that the server handler can chose if jumpstarts and DSQ happens. Until GPB is stable most races get ruined by this problem
DD
+1 mate. Totally agree DD. ;)
Hawk.
Quote from: doubledragoncc on August 11, 2017, 06:06:54 PM
It needs to be made that the server handler can chose if jumpstarts and DSQ happens. Until GPB is stable most races get ruined by this problem
DD
+1 and having the option to disable the penaltys would also help, I imagine.
Race Report - Spa on the 250s.
- Qualified 9th of 12 with one not taking part - checked behind on the grid - no-one there, just the other two off to the side.
- Treated it like a third start(we often run a "third start we go regardless" system, so ultra-carefull is the name of the game).
- Clutch in, back brake on and lightly blipping the throttle(or the 250 will cut out). No intention of pulling away until the lights are well out.
- L1, L2, L3 - bike jerks of it's own accord - L4....
(I use manual rider control - there is a vague possibilitiy that I moved the rider forward)
"Jump start - Grooveski - Ride through" or whatever it says.
- End of lap 1 - Done a ride-through.
- End of lap 2 - Pitboard said PIT IN.
- End of lap 3 - Done another ride-through(thought that maybe I should have waited on the pitboard telling me to go in instead of doing it on the strength of the startline text comment).
- End of lap 4 - Still showing PIT IN.
- Ignored it.
- End of lap whatever(a few later) - booted from game.
Oh, another one that should have been in the first post - If you stall on the grid then hit reset you're booted to pit. It'd be better if it didn't do anything until the lights had gone out - then you could reset and pull away at the back of the pack, instead of missing the race. ;)
Would it help if we done another session or two like the ones last year?
500's at Philip Island but this time 3 or 4 lap sprints - short enough that if we're booted we can just wait around until the next session - long enough that we can try ride-throughs.
The pitin and pitout area are not defined/setup properly on most tracks.
Thats the reason the ride throughs often dont work.
I had one in the past on sachsenring and that one worked.
You could try victoria to test it out. if you need numbers for the filed to test just holar.
Quote from: PeterV on August 14, 2017, 07:51:47 AM
The pitin and pitout area are not defined/setup properly on most tracks.
Thats the reason the ride throughs often dont work.
That'll be it. ;) There appears to be a short stretch with the wrong surface inbetween PIT and PITOUT.
(https://s13.postimg.org/rfk3egvnb/Spa_Pit.jpg)
...or what I'm presuming are PIT and PITOUT. Hard to tell with the three sufraces being the same colour in TrackEd. There's a break in the blue bit though which can't be good.
Weird thing is I don't recall the pit speed indicator going off and on again, which you'd imagine it would.
Looking at that surface map may not be telling all how it is, if you know what I mean...... In that the red surface you see at PITOUT maybe actually underneath the PITOUT surface but is showing above it for some reason.... probably a bug in the exporter not being able to define the separate surfaces when very close together(probably the same reason we get flickering signs?), but also because some tracks have surfaces underneath others that really shouldn't be there.... Lazy modelling in my opinion..... Probably as a result of BTB track creation? :)
Just my thoughts and by no means a statement of fact. ;) 8)
Hawk.
[Edit - removed overly harsh comment about the model - Thinking about it the 'duplicate polys' are probably for decals and are just flickering because of the flickering bug]
Hope I haven't derailed the thread too much :-[ - that's one bug that's probably not a bug but there are still another half dozen listed that are.
Good point Groove, about that red surface in the PITOUT section could be a decal surface layer. I think your right mate. ;)
Hawk.
Quote from: Hawk on August 11, 2017, 02:51:38 PM
I noticed that on some tracks when going to the grid to start a race the bike literally drops down onto the track surface and if your the last bike onto the grid it will either give you a jump start straight away or a ride-thru penalty.
This seems to be a problem yeah, last bike too "drop"on the track is always moving a bit.
Just too show what we mean, its a big drop, and with a reasonable full server this causes trouble like DSQ
https://www.youtube.com/v/6re1cNoWnhA
Here is another example.
Server set with Bandwidth setting 3 and player pings reading 30 and 60 in game.
Note: we also tried going to track with the brakes applied, at that time we did not get a DSQ
but the bikes still dropped onto the track like shown in the video.
https://www.youtube.com/v/kybMjun0Rs4
Good vids for Pib to see the problem 8)
Server:
CAWS Special #1
maxclient = 24
bandwidth = 3
Location Germany, provided by Dibu
report from Dibu, bandwidth when 16-19 players were online. The upload was 1,5 - 2,1 Mbit/s. Very good values. Memory usage was ~550 MB, also OK.
Connection:
Here is an example of the connection lag happening, the ping goes way up and then goes down in steps it seems.
Have a look at player Manu and player Matty connection ping.
After Matty you see the start of our race with 18-19 riders.
Tchemi in the bottom left disappears for very short times, i observed that more times with him.
Close too the start we see one or more riders (Tonygas, Tusrat ?) fooling around on the front row.
So the jump start there is to be expected, but Uberslug in the right bottom never moved and got a jumpstart.
Session(s):
Dont know if this is the correct place but i also observed lag / stuttering in the 30 min. practice session.
they where periods of 2 to 5 sec. in lenght, and riders where in server at the time.
The server was restarted 15 min. prior the start of the event.
I mention this because i did not experience the same behaviour in 15 min Qualyfing or in the 16 lap race.
Core:
3x Napalm Nick One in practice when i went to Settings, One on my Qualifying out lap, One going back to pits after race
1x Tchemi I had not installed the CBR, The game stuck on 'syncing' and I had a core.
2x Tommaso Levato I had one just before qualifying and one after coming back to the pits after the race.
2x finpower I had 2 times core-exe yesterday evening. both times in the practice session.
1x PeterV in the practice session.
https://www.youtube.com/v/5mBs_zL8G3s
Another good vid Peter.
As it goes hand in hand...
Reminder for everyone here (http://forum.piboso.com/index.php?topic=5206.0)
Wow :o iv not seen this happen yet on the grid.. but i see this happens when people spawn in the pits..
Thank you for the report Peter, it was interesting for me to see what happens at the other side of the server.
To complete your report:
- the replay size was 512
- the dedicated server didn't core during the whole session
In general the bandwidth usage of beta12(b) is much lower than it used to be in previous betas. Older betas used 2,5 - 3,5 Mbit/s for 16+ players and went nuts after a short while.
The stability of the dedicated servers seems to have improved too.
Hopefully PiBoSo finds the reason for the high pings during connects and the jumps when entering the track.
Did you also experience such a high number of cores at the first test race (Victoria /default bikes)?
Quote from: dibu on September 13, 2017, 06:22:18 AM
Did you also experience such a high number of cores at the first test race (Victoria /default bikes)?
As far as i know we did not have any cores or stuttering in that race, syncing was better as well.