Quote:
Originally Posted by b][rch.Co30
Tinkering with this on a test server. Nice work.
|
Thanks
Quote:
Originally Posted by b][rch.Co30
The download links use Beta 1 in the name, the mutator is BetaF inside the RAR.
In the DefaultScreenSenderConfig.ini file in the RAR file, the INI headers are Beta1
[ScreenSenderBeta1.ScreenSenderMainConfig]
[ScreenSenderBeta1.ScreenSenderAutoConfig]
When testing I had to change these to Beta F to match the files for the mutator.
[ScreenSenderBetaF.ScreenSenderMainConfig]
[ScreenSenderBetaF.ScreenSenderAutoConfig]
|
Damn xD Yep, the default-configuration-headers are wrong. Of course it isn't ScreenSenderBeta1 but ScreenSenderBetaF.
I name this mutator ScreenSenderBeta1, only the package is named ScreenSenderBetaF. If I remember correct, the F stands for First.
Quote:
Originally Posted by b][rch.Co30
It seems to ignore my MaxBytesPerSecond=1000 setting doing the "auto" shot, and lags out the client during low resolution 240x180 greyscale4 or grayscale2 shots. To the point were the client needs to diconnect and rejoin. Vicious circle ensues... Anyway i'll keep tinkering with settings to see what works.
|
Uhm... Very strange because I use the exact same algorithm for the manual and auto screenshots. Only the input values are different.
Perhaps it isn't a problem of sending too much data, but that the client switches into windowed mode (GeforceFix) or something like that. The various algorithms to modify the data are also not that performance-friendly (because of the amount of data and calculations they do) and causes clients to lag for ~2 seconds.
Have you activated RLE-Compression?