Thanks for making that clear. As I said before many of us appreciated all the hard work you put in to it and it is a shame it will be lost to the LFS community.
Unfortunately I do not have the skills or the time to learn to do something like this myself so hopefully someone will take it on in another form.

Best of Luck with you other projects Smith.

Quote from Oliv76000 :

I know also his answer.

So what is his answer? I am guessing it won't be open sourced.

Hi Smith,
Oh no, it very sad news to hear you will no longer continue to develop such a great application, I know my fellow colleagues in AUS will also miss the fact that stats will no longer be provided for our league races.
Thank you for all your hard work in providing this to the LFS community it will be missed.

(P.S. It would be nice if you someone can continue to develop something along the same lines, even if it is not exactly the same).

Thanks Ian, Got it now, I will try and report what I think later.

Links aren't working for me for some reason?

Quote from Freddy_P :

@ Smith

Is version 1.49 incompatible to the W17 patch ?

Error:
InSim : first byte in packet does not match size

Freddy, no it won't work with the test patch any longer as Scawen has changed how insim packets are derived, they are now TCP instead of UDP. What it means is every insim app (incl Stats) will need to be updated. More than likely Smith won't do this until the official patch X is released with the new insim changes.

Quote from deathracer1923 :

i followed the instructions on how to do it but it kept saying "Unknown Command" y is that??
do you need a license to do it??

Yes you need a full licence as it is a sound file that can only be used for the XRR, which as a demo racer it is locked out. I assume that is why you get the error.

Scawen I know this has been said before but I have noticed again that the join & pit entry/exit lag is still occurring with test patch W17. Although it may seem minor it did have a big impact on the server that had 30 cars on it tonight. I can't remember if you said you can actually do much about it but just thought I would re-mention it in case you can.

Hi Smith,
Sorry to bug you with this as I am sure you are aware & looking into it but I am wondering if you will be updating your stats program, given the changes to insim which I understand will be part of the next official release - patch X.

Quote from smith :

The question seemed interesting enough for me to investigate, so I've added the MCI counter.
Using test replay with 16 players, I can confirm that the number of MCI packets sent to stats halves down with each replay speed increase.
The consequences are obvious

Wow, so you are right in saying that 1x replay speed is the most accurate.
Is the issue you found something that Scawen may also find interesting enough to look into?
Given I am hearing whispers that they are planning on having some form of stats as part of the LFS package on the master server side!

Last edited by flinty72, Wed 18 Apr 2007, 14:36.

Quote from smith :

Speed values do vary a little bit between runs even at 1x speed.
It looks like LFS has some bandwidth/rate limit set on UDP MCI packets generation, what prevents recording the proper top speed values.
So logically you should get lower speeds recorded for high speed replayed mprs compared to 1x replays.
I've decreased the period of sockets polling just in case, but that won't do anything good in this case I suppose.

Thanks Smith, makes sense just a shame it is that way but at least I now know it is the limitation of LFS not a bug or some other anomaly. I can go back to doing the stats at 4x to get them done quicker.

BTW loving the new stats info for pit stops, flags etc.

Last edited by flinty72, Tue 17 Apr 2007, 23:55.

Quote from brasi :

I saw tha same case on version 1.49 . The top speed can vary

Was it varied using the same speed or from different replay speeds like 2x, 4x, 8x??

Hey Smith,

Not sure if this has been detected before but I have found that if you run stats via a replay that is speed up then the Top Speed calculation seems to differ (increase in fact with the replay speed).
I know that the optimum use of stats is @ 1x replay speed but I am wondering if this is some other bug as all the other data is exactly the same.
Below are to examples, the first at normal replay speed (1x) the other at 4x speed.
http://www.ozsport.org/stats/z ... Rd2%20DivB%20R1%201x.html
http://www.ozsport.org/stats/z ... Rd2%20DivB%20R1%204x.html
The replay file is here (3mb): http://mondaynightracing.com/s ... 007/ofr/r2/OFR_R2_B_1.mpr

Just in case you were going to ask I am using stats ver:test3 & my PC at 4x is smooth and steady - no stutters, so that should not be effecting the data capture imo.

Last edited by flinty72, Tue 17 Apr 2007, 11:15.

Awesome, I never knew of LFS back then. I have only played LFS since S2 so I am going to give this a go, just to see what it is was like.

Thanks to the Dev's for allowing this.

O.K makes sense and thanks guys.
Thought as much but like I said, I just had to ask the LFS guru's just in case.

Sorry if this has been brought up before, I can't seem to find anything on it.

So can a RAF file be created from an SPR file without having LFS installed?
Is there some other application available to do this & if not could one be created to do so?

I suspect not but had to ask.

Quote from smith :

flinty72, the problem does seem interesting enough. It seems that there are no PLA or PIT packets generated for Patto when he enters/exits pitlane and makes pit-stop. The only explanation I can think of is Paato running an older LFS. Host might check client version and avoid sending new insim packets in case of version dicrepancies.

Ah yes that could very well be the case. I will investigate which version Patto was running for those races and report back. I also have another racer in another event that had the same problem & I will check with them also. It makes sense to me. Thanks

Hi Smith,
Have tried the new test2 stats (v1.50) and I am not so sure everything is fixed with regard to the pit stop information being captured.

Refer to the following stats from 2 races and the lack of pitstop info for "Patto".
http://www.ozsport.org/stats/m ... _07/RXR_Rd01_DivB_R1.html
http://www.ozsport.org/stats/m ... _07/RXR_Rd01_DivB_R2.html

The replay files are here: (4mb each)
http://mondaynightracing.com/s ... 2007/ofr/r1/rx_r1b_r1.mpr
http://mondaynightracing.com/s ... 2007/ofr/r1/rx_r1b_r2.mpr

Interested to know whether it is stats or something to do with LFS or the replay files themselves. So let me know what you find.

Last edited by flinty72, Mon 9 Apr 2007, 14:07.

CrazyICE,
Is it possible to change the insim port that LFS:AutoMessage uses?
I have tried modifying the LFSAutoMessage.config file but I can't seem to get it to work on the new insim port?
Here is what I did.
[SETTINGS]
Host=127.0.0.1
Port=44444 (changed this to new insim port 65000)
ListenPort=33333
Admin=

Even after doing this LFS:AutoMessage still works if I have LFS use insim port /44444 but not if I change LFS insim port to 65000.
Seems that the config file does not actually change the port.
Any idea & can it be done?

Hey Smith,
Have noticed that some of the pit stop information is not being collected with the new test stats for patch W. Take a look at the following.
http://www.ozsport.org/stats/a ... heeln_07/OW_Rd6_DivA.html
refer to Ben, KNAPPO & Delray25's pit stop stats

This was taken from our AUS league race replay, which can be found here.
http://www.starlyon.com/bugle/lfs/AAL_Fo8_citylong.mpr (19MB)

I have noticed the same problem when doing other stats with other replays. Seems a bit random to me as I can't pinpoint the cause.
I am using LFS S2 Patch W @ 1xspeed to produce the stats with no other programs running in the background

Last edited by flinty72, Fri 6 Apr 2007, 08:04.

Quote from felplacerad :

The numbers are fetched from LFS World, but in order for you to retrieve the data, you must request and enter a pubstatkey.
Go here: http://www.lfsworld.net/?win=s ... hichTab=pubstat&abc=2

<UseAndUpdatePubStats>true</UseAndUpdatePubStats>
<LFSWorldPubStatsID></LFSWorldPubStatsID> <!-- you need to get your own ID: http://www.lfsworld.net/?win=settings&whichTab=pubstat&abc=2 -->

Cheers, all working now.

Smith, keep the development going please.
I use stats for all our team stats for any league races our team do in AUS.
It is the most user friendly, well detailed & easy to read app for stats going around
The new improvements from the patch W stats test look neat.

A question about the WR values, how do they work as all I get is blanks in the columns for the WR values.

Last edited by flinty72, Mon 2 Apr 2007, 23:35.

Or just don't use any spaces, should then fit.

Thought I had an original idea but good to see it is already thought of.
I feel this would be one of the best ways to implement a setup management system that is sorely missing. Surely for the Dev's it would be an easy improvement. Here's hoping Scawen & the LFS Dev team are listening

Quote from Scawen :

I guess you have a high screen resolution, and you did not turn up your LOD when you installed V5. V5 LOD defaults to 0.6, which gives slightly higher LOD than someone using an old version with a 1024 wide screen - my mistake, I think the default should have been 0.8 like it was in V4. You should be able to turn LOD up higher than it ever was before - unless your screen is wider than 1920 in which case you were able to get higher LOD in the past - though that should be unnecessary (except that the moving trees (e.g. the ones at blackwood) are known to pop up too much and I'm going to look into them). Please, anyone who reports LOD or pop-up issues, tell us your new LOD setting and you screen resolution, and your FOV, otherwise we cannot reproduce what you see, and your report is a bit meaningless.

Sorry Scawen , my bad so here are my specs, LOD & POV settings.
I should also mention I am using a mix of 3rd part HiRes Track Textures.

System Specs:
AMD Opteron 146 @ 2.50G
2G DDR500 Patriot RAM
LeadTek 7600GT (running 2 CRT Monitors, LFS on one only)
Graphics Drivers: 6.14.10.9371
AA = 8xS, AF = 16X

Screen Res = 1280x960 (32 bit) 85Hz
FOV = 90
In-Game User LOD = 1.00
Dust LOD = 1.00
Mirror LOD = 0.3
Hardware Vertex Shading = On
Dynamic LOD Reduntion = 0.00