Hi,
Problem - server is only capturing whole event replays up to 1Gb and server buffers unable to be set higher (at some tracks) without causing 'core'.
Result - appx 997Mb of an EVENT replay is saved but cannot be viewed as it 'shut off' the recording at 1Gb in a 'dirty' way.
Notes:
1. Seems to be a B7/B8 thing (unconfirmed). In 6c recording 'seemed' a lot more successful?
2. Might be overcome with more RAM but not a friendly solution.
3. All this based on what my own server is doing only.
Proposal - would it be possible to make the servers auto-save the replays PER SESSION rather than PER EVENT? (More often than not the replay is split anyway before being provided for others to download - so some labour saved there too). This would make replay files smaller, more easy to locate sessions, more likely to record full sessions and more chance of being successful on a wider variety of server specifications.
Thank you for your consideration.
I have major replay problems with 3GB DDR5 dedicated video and 16GB DDR3 working memory!!! Server drive has 400+GB free is a 7200rpm veryfast HDD too.
What is the actual figure you have in the ini file for your server?
DD
Based on B8 change in Buffer nomenclature where 10 = 10MB, my servers are set with 1000.
This seems to be the highest setting I can guarantee ALL tracks will record replays on for AVERAGE race events appx - 10 players.
As has happened in the last 3 events, big tracks with lots of players- the recording stops at 1Gb and is 'broken'.
Before, the replays never used to be broken, the replay would kind of overwrite itself, deleting the earliest parts of the session to ensure the latest was kept. Hence sometimes we had races that missed the first few laps or so. But they worked.
Okay so I will try 1000 and see what happens.
DD
OH and I forgot to ask: HOW do I save a server replay or is it automatic??? DOH
Just call me Homer
DD
AH wait a mo, so it saves it automatically if it is at the end of a race, but I have to hold a race to get a replay............right, I cant just save a practice or qually time?
You set it up in the dedi.ini to save to the folder "Replays" if you used my method. If set to 1 it will save when the server resets after a race.
Got it set to 1 and have the replay folder where I said it is in the ini
Just not run a race yet ::)
DD
I am so tight on time right now lol. Will get there soon
Yeh as long as you get a race started and ended and the server resets it will record everything automatically - practice, qually, race.
As yourself (a client attached to the server) you can still record replays whenever you want but you have to do that manually by saving it in the replay screen.
Okay got it all.
I defo need another system to be dedicated. I need to reboot several time during the day testing hardware and software out. I hate asking guys to leave.
DD
Quote from: Napalm Nick on May 28, 2016, 10:00:54 AM
Proposal - would it be possible to make the servers auto-save the replays PER SESSION rather than PER EVENT? (More often than not the replay is split anyway before being provided for others to download - so some labour saved there too). This would make replay files smaller, more easy to locate sessions, more likely to record full sessions and more chance of being successful on a wider variety of server specifications.
Added to the TODO list.
My box of ManHugs is open again, please take one :) Thanks.
for the silverstone race tomorrow, we could split the replay recording. the server or somebody who is only spectating could save the first half and some rider could save the second half after the race is finished.
Quote from: vin97 on May 28, 2016, 02:58:20 PM
for the silverstone race tomorrow, we could split the replay recording. the server or somebody who is only spectating could save the first half and some rider could save the second half after the race is finished.
That is a good idea Vin! ;) 8)
Hawk.
I am testing today on my server while using a client replay window to see what happens over an hour or so.
DD
ah hold on, i was thinking too complicated, the guy that is spectating can do it by himself, he just needs to save a new segment everytime its beginning is about to disappear on the timeline and then cut out the overlapping part later on.
It is a good idea Vin.
However I am not sure there will be any spectators tomorrow so the best might be for everyone to save their own replays after the race (cut it down to the race only using the red and green markers).
I will make sure the event has a long time before auto reset after race so people have the opportunity.
But if I stream live, I am also in the replay window and can save, or try to save if GPB lets me a replay for all.
DD
Yes DD would be ideal if you are there streaming? Are you going to stream it? ??? :)
I am testing for it now. Running 1080p @30fps with 3696bps and ping is 26-27 ;D on your server, Also doing a reply save test for 1 hour, finished in 10 mins with that test. Will be low MB as only a few riders so less data.
Heres Stream test 1:
https://www.youtube.com/v/8Ovv9MP5Q5A
Problem from Copes to Stowe with pitlane flash backs on TV cam!!!
DD
Okay so my replay for 1 hour of being on your server was 30.9MB but only 30mins long???
Replay set to 1000 in MY GPB.
FFS.............never a consistent replay length!!!
DD
No it is very strange. 30 Mb ? is that all! Makes no sense.
I will have a look at that camera mate. If I can fix it I will send you the updated file.
Ok thanks, yep the frickin replays are pissing me off as it ruins it for everyone to check how they ride too. Just as well I can stream it live lol.
DD
Sorry to say the cameras are fine. I see the pit flashes on your stream though so I went to watch live replay myself and don't see any pit flashes. I can only conclude they are netcode lag errors where your game thinks the bike has left for a millisecond so drops to the default pit view. If it was a camera thing you would see it for every rider at the same place but the cameras are set up quite correctly.
Might be a streaming thing on riders with a poor quality ping? Nowt we can do I think except wait netcode updates. :(