I wanted to report that this rule does not work if you use this panelyou can use the trick to add 42 to the AC udp port number and use that for the stracker listening port. This is what is ment by "<AC udp port>+42"
I wanted to report that this rule does not work if you use this panelyou can use the trick to add 42 to the AC udp port number and use that for the stracker listening port. This is what is ment by "<AC udp port>+42"
you can use any unused port for http connections there are no restrictionsHello @Neys
I have a question about the ports for the pTracker connection.
There are 12 ports in stracker.ini that you can use for the pTracker connection. My question is there is also the HTTP port that you have to unlock to access the page and I have always used a port from the ports that is also used for the pTracker connection but so far I can only run 6 acServers on my server, can I use a different port for the HTTP port than one of the specified ports ? and if so which port range can I use the best for it ?
I hope my question is understandable enough
Yours sincerely
Stefan
Translated with www.DeepL.com/Translator (free version)
{2019-12-26 00:01:08}: stracker[INFO ] | Setting lap to unknown bcause of suspicious lap binary blob |
{2019-12-26 00:01:08}: stracker[INFO ] | Setting first lap to invalid because it is probably an out-lap. |
{2019-12-26 00:01:52}: stracker[INFO ] | Broadcast message: Player Jonah Hax left the server. |
Sounds like you are doing it right. At least that is how I do it. Maybe your server host does not allow modifications to the file?Hello guys,
Restarting game server is equal to restarting stracker? Because I've changed number of records per page in ini file, restarted server and nothing has changed. Am I doing something wrong?
Probably you are doing nothing wrong, but A2B tracks are not properly supported. It might also depend on the mod tracks.Hey NEYS.
We are still trying to figure out why ptracker/stracker is not working properly with A2B tracks. I saw we need to use the A2B tag on those tracks, so we do. Then I saw this in the change log:
"add point-to-point (A2B) track support with special handling for ks_nordschleife-touristenfahrten"
Special handling? Does that mean that A2B only works in nords tourist? IF not, what exactly does ptracker/stracker need to get a valid lap time the first time you drive an A2B track? We can make it work on the second run through, but no one wants to drive for 10 minutes before the time actually counts.
When I add the A2B tag to a hillclimb track, I do get a green light in ptracker so that means it detects the start of the lap and starts the timer. The problem is that the timer doesn't stop at the end, the light stays green and you have to go back to pits. In stracker that run will show up as invalid and this shows up in the log:
What are we doing wrong???
{2019-12-26 00:01:08}: stracker[INFO ] Setting lap to unknown bcause of suspicious lap binary blob {2019-12-26 00:01:08}: stracker[INFO ] Setting first lap to invalid because it is probably an out-lap. {2019-12-26 00:01:52}: stracker[INFO ] Broadcast message: Player Jonah Hax left the server.
I don't think so. It's rackservice. Have you got any experience with that site? I've read somewhere, that stracker process is still running, even you restart a server. Maybe that's the problem. I don't know :/Sounds like you are doing it right. At least that is how I do it. Maybe your server host does not allow modifications to the file?
Nords tourist is even more special because it is an A->B track designed on a lap. Honestly, I don't remember all that stuff anymore. It might depend on the mods, I don't know.But some A2B tracks works? What is the magic ingredient? Did you do something speciel to stracker/ptracker to make it work for nords tourist?
Did you checked the time app from AC? I think the problem is that this track you said has not well done the finish point.Hey NEYS.
We are still trying to figure out why ptracker/stracker is not working properly with A2B tracks. I saw we need to use the A2B tag on those tracks, so we do. Then I saw this in the change log:
"add point-to-point (A2B) track support with special handling for ks_nordschleife-touristenfahrten"
Special handling? Does that mean that A2B only works in nords tourist? IF not, what exactly does ptracker/stracker need to get a valid lap time the first time you drive an A2B track? We can make it work on the second run through, but no one wants to drive for 10 minutes before the time actually counts.
When I add the A2B tag to a hillclimb track, I do get a green light in ptracker so that means it detects the start of the lap and starts the timer. The problem is that the timer doesn't stop at the end, the light stays green and you have to go back to pits. In stracker that run will show up as invalid and this shows up in the log:
What are we doing wrong???
{2019-12-26 00:01:08}: stracker[INFO ] Setting lap to unknown bcause of suspicious lap binary blob {2019-12-26 00:01:08}: stracker[INFO ] Setting first lap to invalid because it is probably an out-lap. {2019-12-26 00:01:52}: stracker[INFO ] Broadcast message: Player Jonah Hax left the server.
Stracker is working because it sees the lap times and shows them on the website, otherwise, it doesn't. But in those tracks, it doesn't keep the times recorded. Don't know why, but it happens that way. As I said, we used to have Hillclimb tracks on the server many times and we did screenshots of the web with our best times.if the time table resets, that means your stracker was not working. Also I doubt the timing worked without an outlap first, but if it did, please tell me which track it worked on..