[REL] rFactor2 Log Analyzer ver. 2. With offline and league Championship Manager

Nibo said:
Oops, looks like that monitor works only in single player mode, not on rF2 dedi. Maybe you can try that.
Click to expand...
Ok, will give it a go, thanks.
Ah not possible, just remembered, dedi server has only rF2 SteamCMD on it, it is a standalone PC only running rF2 dedi and rF2 Log Analyzer, nothing else.
 
Somebody said that installing runtimes from rFactor 2\Support\Runtimes directory helped when memory plugin was not working. I know you didn't re-install windows, but you can still try.
 
Nibo said:
Somebody said that installing runtimes from rFactor 2\Support\Runtimes directory helped when memory plugin was not working. I know you didn't re-install windows, but you can still try.
Click to expand...
Thanks very much @Nibo !
Running the Runtimes again brought back Live Timing !
Just in time for tomorrow nights league ;)
I appreciate your taking the time with dumb clucks like myself :D
 
I installed this on our DEDI following the instructions, but can't access the website from outside the dedi server. Do we need to open ports, and if so, which ones and which type?
 
Default port is 8000, so I guess that's the one. Also you can select any port to host on if you will start r2la by rF2 Log Analyzer ver. 2.058.12\web2py\web2py.exe Don't forget to add port to link when you accessing r2la from client machines.
 
Nibo said:
Default port is 8000, so I guess that's the one. Also you can select any port to host on if you will start r2la by rF2 Log Analyzer ver. 2.058.12\web2py\web2py.exe Don't forget to add port to link when you accessing r2la from client machines.
Click to expand...
Thanks for your reply. I've tried many different ports just now, including 80 which is the default internet port, but the site is never reachable. When I ping the IP it does return packets, so the port has to be the issue.
Does anyone have r2la dedi running and could let me know firewall settings or port numbers to get this working?
 
I don't really know much on why that maybe happening. Firewall can block it, but I don't know exactly about ports. Maybe make sure that web2py determines your public IP correctly (google "whats my IP" in on server browser to be sure). Try selecting public server IP 0.0.0.0. when starting web2py server.
 
Last edited:
Would it be possible to have some more tire-info from the pistops? It now shows the compounds before/after the stop, but when the compound stays the same, you can't tell if the driver changed tires or not. In our league we have in one class a mandatory pitstop with a minimal of two changed tires.
Right now, we have to manually check the tire wear (per wheel) before/after a pitstop to check if 2 or more tires have been changed. Or we could check all pitstops in the replay and check if the car goes up/down for tire change.
Maybe it's possible to automatically detect if a tire has been changed, based on the tire wear percentage (per wheel) after a pitstop being higher then before the pitstop? And then count the number of changed tires per pitstop.
 
Lenniepen said:
Would it be possible to have some more tire-info from the pistops? It now shows the compounds before/after the stop, but when the compound stays the same, you can't tell if the driver changed tires or not. In our league we have in one class a mandatory pitstop with a minimal of two changed tires.
Right now, we have to manually check the tire wear (per wheel) before/after a pitstop to check if 2 or more tires have been changed. Or we could check all pitstops in the replay and check if the car goes up/down for tire change.
Maybe it's possible to automatically detect if a tire has been changed, based on the tire wear percentage (per wheel) after a pitstop being higher then before the pitstop? And then count the number of changed tires per pitstop.
Click to expand...
This data is already in the program !
Go through the menu and scroll down.
 
There is no specific data for number of changed tires in r2la. This is because it is not possible to show it consistently with the way log files are created by rF2. Because tire compound value is taken at pit-in line crossing, but tire wear data (and fuel data) is taken at start-finish line when you drive in the pitlane. And, unlike real life F1 where s-f line must be before 1st pit stall, in rF2 s-f line is in different place for every track. This creates inconsistency with tire wear data in case of pit stops depending on where specific car has its pit stall, before s-f line or after. There is no way to know where pit stall for this particular car is/was. This makes determining if tires were changed or not for 1st lap of the race impossible if they are the same compound. For all other laps of the race to determine tire change from tire wear data I must compare this lap and previous lap for pit stall before s-f line and this lap and next one for cases after s-f line. I think this would work, but would create a mess if somebody will stop 2 times in a row on consecutive laps.

If you want, you can look at this test xml data. I made a pit stop on lap 1 and 4, before s-f line. Tire compounds are logged correctly, but tire wear on that laps is logged for a small distance between pit stall and s-f line:
Code: 
<Lap num="1" p="1" et="9.9010" s1="37.3411" s2="42.3040" s3="46.5154" fuel="0.216" twfl="1.000" twfr="1.000" twrl="0.996" twrr="0.996" fcompound="0,Soft" rcompound="0,Soft" pit="1">126.1604</Lap>
<Lap num="2" p="1" et="136.0614" s1="38.7719" s2="42.0269" s3="28.7029" fuel="0.196" twfl="0.984" twfr="0.988" twrl="0.992" twrr="0.992" fcompound="1,Medium" rcompound="1,Medium">109.5016</Lap>
<Lap num="3" p="1" et="245.5631" s1="26.8179" s2="42.0593" s3="28.4667" fuel="0.180" twfl="0.969" twfr="0.976" twrl="0.984" twrr="0.984" fcompound="1,Medium" rcompound="1,Medium">97.3439</Lap>
<Lap num="4" p="1" et="342.9070" s1="26.6652" s2="41.5347" s3="42.2602" fuel="0.161" twfl="1.000" twfr="1.000" twrl="0.996" twrr="0.996" fcompound="1,Medium" rcompound="1,Medium" pit="1">110.4601</Lap>
<Lap num="5" p="1" et="453.3670" s1="35.1907" s2="41.5807" s3="28.2870" fuel="0.145" twfl="0.988" twfr="0.988" twrl="0.992" twrr="0.992" fcompound="2,Hard" rcompound="2,Hard">105.0585</Lap>

So if I did this, I don't want to create a false impression with the cases where I can calculate number of changed tires versus where I can not. Then in cases where I can not calculate it admins will think that there was no change. Now they are looking themselves at data as you describe and can determine tire change with various factors. So I'm not sure what to do. I think its better to not provide any data on this, because I can not make it consistent in all cases.

While looking at this I found a small bug with re-fueling amount calculation on lap 1 of the race. Its not possible to determine it as with tire wear, I will set it to 0 in this case in future.
 
Small bug:
I was editing an xml-clone, trying to change the finish position of a driver with engine-failure in the final lap, the finish condition 'engine' is not available from the drop down list, resulting in an error. I can only save the edit using a different finish condition.
 
Having issues now with the viewer for the first time in almost 2 months...
Everything was right until I wanted to put the results of my last week's league race, but this appeared clicking and putting the race result:
upload_2018-10-13_12-30-44.png

If I click that, it says invalid function (admin/default).
(http://127.0.0.1:8000/admin/default...12-59-57.0532b576-0bb7-4324-80db-9fab4810eea7)
But on the other results I had assigned, I see this:
upload_2018-10-13_12-31-44.png


I opened and did things like other times but this is the first time that happens.
@Nibo how can I solve it?

Thank you!
Waiting for an answer,
Regards
Nico
 
Zip your rF2 Log Analyzer ver. 2.058.12\web2py\applications\r2la\errors folder and send it to me. Also send me xml files for quali and race that you were attaching when error happend.
 
You must log in or register to reply here.
Back
Top