PiBoSo Official Forum

Dont know where too put it as it is not a real bug, but here it goes.

Yesterday we did an 18 lap wet race on Assen, at least we thought we would.
But no one could get onto the server it gave an "connection timeout" , so what caused this then?
we never ever had that before, so i handed in a ticket too Dibu our server host.

1. I thought it might have to do with the fact i had a folder shared on dropbox for the riders to get the latest
version of the bikes, but we quickly found out that was not the case.

2. The other thing that was changed was....the replaybuffer on the server side.
We went from 1 GB too 2.5 GB too capture the replay of a full 18 lap wet race, so we thought.

It seems that a replay buffer above 2 GB is not possible due too the fact that Core.exe is a 32 bit application.
Setting the replay buffer back too 1 GB solved the issue and we could get in again. (thx Dibu for youre quick thinking)

Hope this is useful too some others

My 19 lap wet race at Assen only used just under 1GB Peter.

DD

Yeah the one from yesterday is also 0.94 GB but does it have everything saved?
Im gonna check now.

Edit:
Just checked the replay it has saved the warmuplap and the full 18 lap race.
The practice, and Qualifying session from 15 min. each are not available in the replay.

Mine is the same only save 55.28 mins so 2.48 mins of warmup plus the race?

Its a known fact that GPB can not make its mind up about replays and sometimes will only save 10 mins another time 3 hrs!!! That is with the same buffer size lol.

It is a major issue for replays and can ruin some fun and stop folks getting to study how they ride to better themselves.

Shame

DD

@Peter: This is just a thought with you saying in your initial post about core.exe being a 32 bit app?
Have you got your GPB install in the "Program Files(86) folder? If so then try installing in the "Program Files" 64 bit folder. I have my install as a 64 bit app and works fine. It does say GPB is for 32 or 64 bit yes?  :)

I'm now wondering if this is why some who have installed GPB in their "Program Files(86)" folder are having issues with setting their replay buffer at a higher MB or GB rate??  :-\
I haven't had any problems with setting my replay buffer at a higher level.

As I say this is just a thought and might be worth giving a try.  ;)

Hawk.

Its not for me client side its on the server side (Dibu)

Its a 32 bit app, it wont turn into 64-bit by putting it in the 64-bit folder (Program files (x86) )
32-bit is maxed at a usage of 2GB memory use.

I have Core.exe installed on a seperate drive (D:) where i install all my games.

Quote from: PeterV on August 01, 2016, 03:37:21 PM
Its not for me client side its on the server side (Dibu)

Oh I see.... So I presume by that, that the server script on Dibu's server side is 32 bit only and not both 32 and 64 bit compatible like the GPB core.exe? Sorry Peter, I don't know anything about this sort of thing, just putting forward ideas.  ;) 8)

Hawk.

Quote from: Hawk on August 01, 2016, 03:41:13 PM
Oh I see.... So I presume by that, that the server script on Dibu's server side is 32 bit only and not both 32 and 64 bit compatible like the GPB core.exe? Sorry Peter, I don't know anything about this sort of thing, just putting forward ideas.  ;) 8)

Hawk.

Hi Hawk, this has nothing to do with any of my scripts. It's a fact that all PiBoSo sims are 32bit apps witch can be run in 32bit or 64bit Windows OS.
The hosting server runs Windows Server 2008R2 Enterprise (64Bit OS) and the racing servers are installed in a seperate folder(s) (of course not Program Files or Program Files(x86)).

Edit:
The strange thing which really wonders me is: Before Beta8, when replay size was set in bytes instead of megabytes, we never had replays which were bigger than about 500-700MB. Now, depending on wheather and track even 1GB is to small.

I run all my servers on WIN 10 Pro 64bit and none are installed in Program Files or Program Files(86) as they are each on a separate Hard drive and each server has its own partition (Drive's G,H and I)

I run all 3 plus my own GPB that actually is in (86) as I did not think about it and just let GPB do its own install except for the folder name as I have beta 7 and alpha 7 still installed.

Just so you can see a servers will work when not on your C drive, where it should not be if YOUR GPB you use to ride is. That is where you will get possible conflicts.

Make sure also not to just port forward to a group of ports, open a specific port for the server and then make sure Windows Defender also has a rule for that port.

DD 

EDIT: As for the replay buffer my riding GPB buffer is 400MB but the server is 1GB yet I can transfer the 900plus MB replay of Assen to my GPB from the server and watch it!!!

Quote from: dibu on August 01, 2016, 03:56:47 PM

Quote from: Hawk on August 01, 2016, 03:41:13 PM
Oh I see.... So I presume by that, that the server script on Dibu's server side is 32 bit only and not both 32 and 64 bit compatible like the GPB core.exe? Sorry Peter, I don't know anything about this sort of thing, just putting forward ideas.  ;) 8)

Hawk.

Hi Hawk, this has nothing to do with any of my scripts. It's a fact that all PiBoSo sims are 32bit apps witch can be run in 32bit or 64bit Windows OS.
The hosting server runs Windows Server 2008R2 Enterprise (64Bit OS) and the racing servers are installed in a seperate folder(s) (of course not Program Files or Program Files(x86)).

Edit:
The strange thing which really wonders me is: Before Beta8, when replay size was set in bytes instead of megabytes, we never had replays which were bigger than about 500-700MB. Now, depending on wheather and track even 1GB is to small.

Hi Dibu.
Ah I see... I understand what your saying there.  ;)

It seems the servers are having to have a bigger replay buffer size at the moment than the client needs to save the same event in GPB itself. That seems strange to me, but as I say, I don't know anything about the server side of things and so I presume that the server has more data to take into consideration for a replay file than the client side replay file?

I have my replay buffer set at 700MB and haven't had any issues for saving replay files on my side, though I've been thinking of setting it to 1GB as a full wet race is pushing the 700MB limit. But with 700MB replay buffer the practice and some of the qualy are missing in my replay file due to my buffer size, but that's fine for me personally because I'm only interested in the main race event as a record. So if I wanted to save the whole event session I would probably have to set my replay buffer to 1.5GB to be sure but I would need to test to know if that size was enough to capture the whole event.

But for sure there does seem to be something strange going on with the replay buffer size and file sizes of the replay files compared to other betas.

Hawk.

Hi Hawk, I'm not sure whether the client side needs less buffer than the server side. If you still have your replay of yesterdays race, can you please check how much time your 700MB client side replay recorded and compare it to the replay of my server (1024MB)?

For the next test I increased the replay buffer to 2000 at the server. I didn't want to use the full 2048MB to leave some space for core.exe itself.

Btw I still have all replays (416)  of the races which were run at my servers during the last 3.5 years and the two biggest replays before Beta8 were 488MB and 386MB.

I just did a quick test: I set a 2MB (two megabytes, yes) replay buffer, did two laps (offline) at aragon and saved the entire replay. The file is 3MB, bigger than the replay buffer size.
That's exactly what I'd expect: the max size we precise is the buffer size (RAM), not the max file size. A bigger buffer just means you'll write to the disk less often (but each time you'll write more).
At least that's the usual interpretation of the term buffer.

So I'm a bit lost: are you guys saying that when the replay buffer size is (example) 1GB then you never see a replay file bigger than 1GB ?

At any rate, if we ask for a buffer of XXXX MB and GPB cannot allocate that (for whichever reason), then it should probably allocate whatever it can and log a warning somewhere.

Quote from: HornetMaX on August 01, 2016, 05:27:29 PM
So I'm a bit lost: are you guys saying that when the replay buffer size is (example) 1GB then you never see a replay file bigger than 1GB ?

Yes MaX, the replay buffer was set to 1024 and the resulting replay size is 977MB. The first part of the session is not contained in the replay.

Quote from: HornetMaX on August 01, 2016, 05:27:29 PM
At any rate, if we ask for a buffer of XXXX MB and GPB cannot allocate that (for whichever reason), then it should probably allocate whatever it can and log a warning somewhere.

The core.exe process allocated about 1GB in taskmanager and there was enough free RAM at the server.

Edit:
The race was in Assen, a track which also caused bigger replay files in former Betas and it was a wet race which also increases the replay files.

Quote from: dibu on August 01, 2016, 05:10:05 PM
Hi Hawk, I'm not sure whether the client side needs less buffer than the server side. If you still have your replay of yesterdays race, can you please check how much time your 700MB client side replay recorded and compare it to the replay of my server (1024MB)?

For the next test I increased the replay buffer to 2000 at the server. I didn't want to use the full 2048MB to leave some space for core.exe itself.

Btw I still have all replays (416)  of the races which were run at my servers during the last 3.5 years and the two biggest replays before Beta8 were 488MB and 386MB.

Unfortunately I didn't save the last Assen wet race, but I did save the previous Assen Wet test race the previous week to that one. The replay file size for that is 488MB.....
Strangely the 500cc Brno test race the previous week to that was also 488MB but that was a dry race. I say strange because I was under the impression that wet weather created a larger replay file size?

Both replay file sizes recorded approx 50 mins of time +/- a couple of mins. So my replay buffer is only just catching the actual race event itself and 2-3 mins on either side of the test race. This is why I want to increase my replay buffer size to 1 - 1.5GB but just haven't got around to it yet.  :)

Hawk.

Hawk, are you sure that your replay buffer is 700MB? Both replays files 488MB smells like "replay=500".

Quote from: dibu on August 01, 2016, 05:36:17 PM

Quote from: HornetMaX on August 01, 2016, 05:27:29 PM
So I'm a bit lost: are you guys saying that when the replay buffer size is (example) 1GB then you never see a replay file bigger than 1GB ?

Yes MaX, the replay buffer was set to 1024 and the resulting replay size is 977MB. The first part of the session is not contained in the replay.

Weird because offline (and maybe on client side too) it doesn't do that. Worth investigating setting a very low buffer server side, do a race and see what happens.

Quote from: dibu on August 01, 2016, 05:36:17 PM

Quote from: HornetMaX on August 01, 2016, 05:27:29 PM
At any rate, if we ask for a buffer of XXXX MB and GPB cannot allocate that (for whichever reason), then it should probably allocate whatever it can and log a warning somewhere.

The core.exe process allocated about 1GB in taskmanager and there was enough free RAM at the server.

I was talking when 2048 was requested (causing the "connection timeout" reported by PeterV).

Quote from: HornetMaX on August 01, 2016, 06:41:31 PM
Weird because offline (and maybe on client side too) it doesn't do that. Worth investigating setting a very low buffer server side, do a race and see what happens.

That we can do ofc, we will test that as well.

Quote from: HornetMaX on August 01, 2016, 06:41:31 PM

Quote from: dibu on August 01, 2016, 05:36:17 PM

Quote from: HornetMaX on August 01, 2016, 05:27:29 PM
So I'm a bit lost: are you guys saying that when the replay buffer size is (example) 1GB then you never see a replay file bigger than 1GB ?

Yes MaX, the replay buffer was set to 1024 and the resulting replay size is 977MB. The first part of the session is not contained in the replay.

Weird because offline (and maybe on client side too) it doesn't do that. Worth investigating setting a very low buffer server side, do a race and see what happens.

Your test was with a replay size of 2MB but the default replay buffer is 10MB and I'm not sure if you can set less.

Quote from: HornetMaX on August 01, 2016, 06:41:31 PM
I was talking when 2048 was requested (causing the "connection timeout" reported by PeterV).

Peter requested more than 2GB, that's why I've set "replay=2560" (without thinking about the 32bit limit, my fault). With these settings everybody got a "connection timeout". Now next test will be "replay=2000".

Quote from: dibu on August 01, 2016, 05:59:30 PM
Hawk, are you sure that your replay buffer is 700MB? Both replays files 488MB smells like "replay=500".

This is what is set in my .ini file.  ;)

[core]
replay  = 700
texture_quality = 1

Hawk.

Quote from: dibu on August 01, 2016, 07:00:02 PM

Quote from: HornetMaX on August 01, 2016, 06:41:31 PM

Quote from: dibu on August 01, 2016, 05:36:17 PM

Quote from: HornetMaX on August 01, 2016, 05:27:29 PM
So I'm a bit lost: are you guys saying that when the replay buffer size is (example) 1GB then you never see a replay file bigger than 1GB ?

Yes MaX, the replay buffer was set to 1024 and the resulting replay size is 977MB. The first part of the session is not contained in the replay.

Weird because offline (and maybe on client side too) it doesn't do that. Worth investigating setting a very low buffer server side, do a race and see what happens.

Your test was with a replay size of 2MB but the default replay buffer is 10MB and I'm not sure if you can set less.

OK, could do the test with 10 or 15 it's fast anyway: 1 lap at aragon (dry) is almost 2MB (single player, offline)

Quote from: dibu on August 01, 2016, 07:00:02 PM
Peter requested more than 2GB, that's why I've set "replay=2560" (without thinking about the 32bit limit, my fault). With these settings everybody got a "connection timeout". Now next test will be "replay=2000".

I tried getting in with this "replay=2000" same thing "connection time out"

It now has been set too "replay=1900"
I can get in now, we will see what happens with more riders this Sunday.

Quote from: PeterV on August 05, 2016, 12:50:59 PM
It now has been set too "replay=1900"
I can get in now, we will see what happens with more riders this Sunday.

Oke this report was not correct, i'm sorry for that.
I had not set....[replay] save = 1 without this the replay buffersize gets ignored.
Thats why i thought it was oke with a "replay=1900" buffer setting.

Dibu has tested some more (thank you very much Dibu) and he came too the following discovery:
Any value above replay=1592 will give a "connection timeout" aka server crash.
This was tested on Victoria circuit and Silverstone_nds circuit on dry and wet track.

Sundays Testrace will be with more then 1 rider so we can check that as well.

Quote from: PeterV on August 06, 2016, 08:30:16 AM
Any value above

Code Select Expand

replay=1592 will give a "connection timeout" aka server crash.
This was tested on Victoria circuit and Silverstone_nds circuit on dry and wet track.

Sundays Testrace will be with more then 1 rider so we can check that as well.

The value 1592 isn't fixed, it's the value for exactly this server. If I run a dedicated server at my working PC (Win10-64) the maximum value is 1278. The maximum value has to be tested individually for each PC running dedicated servers.

A test with a non-dedicated server (local & world) showed a different behaviour. It was not possible to allocate more than 1GB memory for core.exe, doesn't matter how high you specify the replay size. But it doesn't crash even if you choose a replay size of some gigabytes in gpbikes.ini   

It seems that more tests are needed to solve this secret.

@PiBoSo - can you please explain how core.exe calculates the max value after which it starts crashing.
I don't understand it.

I've run some Windows updates at Peter's server today. After the restart the new max value is reduced from 1592 to 1538. Taskmanager and Sysinternals RamMap show some Gigabytes of free memory (standby and completely free).

I also did some more tests with my working pc. As I wrote before here my max value is 1278 despite I have about 10GB free RAM. Even if I start some virtual machines which reduces the free memory dramaticly, the value 1278 still stays the same and doesn't get reduced.

All values are far away from the 32bit limit and there is enough free memory. How does this magic work?

Okay the race yesterday @ Silverstone wet surface and 5 riders.

Same settings as always, Server replay buffer was now set @ 1500 (the maximum for this server)
The saved replay is 867,2 MB and does not work, wont load due too core.exe.
(tried loading it with a client replay buffer of 10, 100, 300, 600, 750, 1500 mb)

I had the same if the GPB version I use to ride had the replay buffer set lower to stop cores ie: 450, I would get a core if I tried to watch a 600MB video?

Server and gaming buffers cant be the same as the gaming one will crash if too high when trying to get on certain circuits.

Its the whole damn core issue not being fixed!!!

This is not krp which has all the attention right now!!!

DD

Quote from: PeterV on August 08, 2016, 09:01:57 AM
Okay the race yesterday @ Silverstone wet surface and 5 riders.

Same settings as always, Server replay buffer was now set @ 1500 (the maximum for this server)
The saved replay is 867,2 MB and does not work, wont load due too core.exe.
(tried loading it with a client replay buffer of 10, 100, 300, 600, 750, 1500 mb)

Peter, I can run yesterday's replay without problems at my working PC.

The replay size at my local installation doesn't matter. I've tested 1524, 1024 and replay completely remarked in my local gpbikes.ini

My working PC:
I7-2600 @ 3,4 GHz
16 GB RAM (9,6 GB free before starting GP-Bikes)
NVIDIA GeForce GTX970 (Driver 10.18.13.6839)
Windows 10 Enterprise 64-Bit 1511 (Build 10586.494)

Taskmanager shows 1375,9 MB for core.exe when running the replay.

Well thats weird cause i have roughly the same specs as you mentioned.

My PC:
I7-4770K @ 3.50GHz
16 GB Ram (12,7 GB free before starting GPB)
Geforce GTX 780 3GB Vram TI (driver 10.18.13.6881)
Windows 8.1 64-bit (version 6.3 build 9600)

gpbikes.ini entry:

[CORE]
replay = 300 ;;300
bike_shadow = 2048
bike_reflections = 512
texture_quality = 1


GPBikes Graphics settings:

(http://i.imgur.com/FzTIeN2.jpg) (http://i.imgur.com/FzTIeN2.jpg)

My installation was completely default as I don't play at this PC.
bike_shadow, bike_reflections, texture_quality and replay were not set at my final test.

My graphics settings were 1024x768, Fullscreen=off, Bits=32 bits, Refresh=default, Antialialising=off, Textures size=High, Filtering=Bilinear, Anisotropic=1
Dynamic Shadows, Reflections and Shaders=On, Draw Distance and Model Details=High, 3D Grass=Off

Replay not set you mean on default off replay = 10 ?

Ill set mine too you're specs and try again tommorrow,
(already tried setting everything too low, still did not work) but i suspect some corrupt memory, because
when i tried too play GPB it cored also, after stopping several tasks in memory , which seemed already closed to me
but where apparently not, like firefox, and 2 others applications i had used before.

So ill try you're settings with a fresh restarted computer in da morning.

Quote from: dibu on August 08, 2016, 08:00:43 PM
My installation was completely default as I don't play at this PC.
bike_shadow, bike_reflections, texture_quality and replay were not set at my final test.

My graphics settings were 1024x768, Fullscreen=off, Bits=32 bits, Refresh=default, Antialialising=off, Textures size=High, Filtering=Bilinear, Anisotropic=1
Dynamic Shadows, Reflections and Shaders=On, Draw Distance and Model Details=High, 3D Grass=Off

I tried you're settings, same result core.exe when pressing view.
Also tried re downloading the replay, created a new profile, basically put everything too default nothing seems too work.

Hi,  just a question :
Has piboso the possibility to implement saves for the replay,  every 100mo a save is done and the buffer goes to 0?

Just had a few wierd replays on one of my servers, 3 replays each around 2 hours long on Silverstone and max size was 122MB and one was only 91MB was up to 10 riders ?

Dont make sense as to why so small for once

DD

Ok,  i said that because on previous page some talked about more than 1go

Quote from: doubledragoncc on August 10, 2016, 06:43:30 PM
Just had a few wierd replays on one of my servers, 3 replays each around 2 hours long on Silverstone and max size was 122MB and one was only 91MB was up to 10 riders ?

Dont make sense as to why so small for once

DD

Same observation here, e.g. one of the replays of the last month is 156 MB /2:06:51 and 11 riders. Another one 1000 MB /50:55, 9 riders and the start of the session ist missing.

What replay size did you use in gpbikes.ini?

I have my servers set to 1GB (1000) and my personal sim to 400MB

DD

Ok, here my results:
- the 156 MB replay was saved with replay=500 (usable for all)
- the 488 MB replay were saved with replay=500 (usable for all)
- the 1 GB replays were saved with replay=1024 (usable for all, but problems with time in replay. Peter already reported.)
- the 867 MB replay was saved with replay=1500 (NOT usable for all)

At the client side the max value which I could achieve was about 1 GB.
Maybe I'm wrong but my suspicion is that values above 1000 in the server's gpbikes.ini are dangerous.

I've also tested the 867 MB at two other PCs and none could play the replay which was saved with replay=1500. Same problem as Peter reported.

Yeah i'm sticking with the replay=1024 we used before, as a maximum on the server, if its needed.

Quote from: PeterV on August 11, 2016, 07:01:17 PM
Yeah i'm sticking with the replay=1024 we used before, as a maximum on the server, if its needed.

Better try 1000 and see if there are still timing errors, maybe 1024 is another limit which we  pass over .

Quote from: dibu on August 11, 2016, 07:19:13 PM

Quote from: PeterV on August 11, 2016, 07:01:17 PM
Yeah i'm sticking with the replay=1024 we used before, as a maximum on the server, if its needed.

Better try 1000 and see if there are still timing errors, maybe 1024 is another limit which we  pass over .

Yeah makes sence, 1000 it is.