I got this error, and .NET 3.5 installed
Sais something like "character chain input format is not appropriate"

Quote from Töki (HUN) :

I got this error, and .NET 3.5 installed
Sais something like "character chain input format is not appropriate"

Thanks for the report. I'm really not sure what that error is or what's causing it, although I know where it happens. Please download this special debug version of the program. When you run it, after the error has appeared, it should create a file called 'Log.txt' in the same folder as LFSPoints.exe, which should contain much more detailed info about what has gone wrong. If you could post the contents of this text file, I'd be grateful.

Edit: Removed debug version.

Here it is, and thanks

Can you please try this version and report back if it works? It may still not work, but even if it doesn't it will help me narrow down the problem. If it still crashes, can you please post the 'Log.txt' file again. Thanks!

Edit: Removed debug.

Can a mod update the title to 'LFSPoints V2.4'

It's annoying me

Still doesn't work, and now no log file created.

Sorry, I made an error with the code, that's why no log was created. Please try this version instead. Thanks!

Edit: Debug version removed.

Here's the log

OK - thanks. My changes made no difference, I will need to spend time fixing it tomorrow.

OK, good luck, I'll come back tomorrow for some testing. Good luck!

OK - I think I've fixed it. I managed to recreate the bug by changing my OS language and text services to Hungarian. The problem seems to have been caused by the different character encodings Windows uses for different languages, which was throwing errors as I was trying to read XML data out of the Tracks.xml file. Anyway, this version works on my PC in both UK English and Hungarian, and should also work for most (all) other language versions of Windows.

This stuff gets complicated some times! Anyway, please try this and see if it works now.

Hello Darktimes,

Could this be implemented in a next version??
A possibility to have a minimum race % of driven laps. For example if someone hasn't driven at least 50% of the total race distance, he gets no points. (or another % of lap count)


Keep up the good work!!

Thanks Starbert

Quote from DarkTimes :

OK - I think I've fixed it. I managed to recreate the bug by changing my OS language and text services to Hungarian. The problem seems to have been caused by the different character encodings Windows uses for different languages, which was throwing errors as I was trying to read XML data out of the Tracks.xml file. Anyway, this version works on my PC in both UK English and Hungarian, and should also work for most (all) other language versions of Windows.

This stuff gets complicated some times! Anyway, please try this and see if it works now.

Thanks! It works, good job! ( My avatar?!)

Quote from Starbert :

Hello Darktimes,

Could this be implemented in a next version??
A possibility to have a minimum race % of driven laps. For example if someone hasn't driven at least 50% of the total race distance, he gets no points. (or another % of lap count)

Keep up the good work!!

Thanks Starbert

OK - I've added this to the next version.

Edit: V2.4.0.1 uploaded. See the first post for info!

Edit: I'm finished for today, uploaded V2.4.0.2.

Quote from DarkTimes :

OK - I've added this to the next version.

Edit: V2.4.0.1 uploaded. See the first post for info!

Edit: I'm finished for today, uploaded V2.4.0.2.

Well, Darktimes,
Thank you very much!

There is stil a bug with the best laptime of a race. In the last race someone drove 1.14.090 , but it showed up in LFSpoints as 1.14.900.
In the championship standings he got his extra point because 1.14.090 was the fastest lamptime in the race. So internally LFSpoints calculates it right but in the raceresults it showes up wrong.

OK thanks, this is just an old bug with the display that's reappeared again.

I uploaded a new version that should fix it, along with a couple of other small changes.

Found 2 bugs:

1. (you may have fixed this with the latest version) info here
   
2. I uploaded our LFSBC Round 5 replay into it (KY2), and it was unhappy as you've named kyoto as 'kyoto' in tracks.xml, whereas the replay says it's 'kyoto ring'. Simple solution is to rename kyoto ring to kyoto in tracks.xml.

Quote from DarkTimes :

OK thanks, this is just an old bug with the display that's reappeared again.

I uploaded a new version that should fix it, along with a couple of other small changes.

Thank you Darktimes!
Does this update affect the .xsl file of the program, because i made some adjustments to this file, so that the results show better on my website.

Great wok dude.

Quote from Fischfix :

Great wok dude.

What's cookin', doc?

Quote from J@tko :

Found 2 bugs:

1. (you may have fixed this with the latest version) info here
   
2. I uploaded our LFSBC Round 5 replay into it (KY2), and it was unhappy as you've named kyoto as 'kyoto' in tracks.xml, whereas the replay says it's 'kyoto ring'. Simple solution is to rename kyoto ring to kyoto in tracks.xml.

The issued with the average speed isn't actually a bug, even though I know it does look funny. If you look at each 'pair' you'll notice their best lap times (which is what the average speed shows the average speed for BTW) are very close to each other, and given the fact that they're rounded down to two places can give this effect. I will however look at the formula used to determine the average speed and see if it can be made more precise. Edit: To be honest the average speed was just added a little idea, it's just a gimmick more than anything else, it's not precise enough to do anything useful with it. As I said, I'll research different ways to do it tomorrow).

OK - I will change it from Kyoto to Kyoto Ring, I never really thought about it before.

Quote from Starbert :

Thank you Darktimes!
Does this update affect the .xsl file of the program, because i made some adjustments to this file, so that the results show better on my website.

Nope, there were no changes to the XSL file in the last release.

LOL - OK, I take it back, I guess the average speed 'bug' really is a bug. Funny how sometimes you just accept some things because you can justify the way you think they work in your head. I broke the formula down into separate variables so I could watch each step of the calculation in the debugger, and I found that when I was converting the times from milliseconds (which is how LFSPoints treats all times internally) into seconds (EG milliseconds / 1000), I was unintentionally casting the resulting seconds into an integer, which meant I was loosing the decimal part of the result. When I changed it to implicitly cast the seconds into a float, the average speeds suddenly became hugely more varied. Just one of those tiny bugs that can easily pass you by... I'll roll out a fix in the next version.

Uploaded V2.4.0.5...

I've uploaded V2.4.0.6.

I'm quite pleased, as I spent the day learning about and struggling with character encodings, but now LFSPoints supports all the different character encodings used by LFS. Basically, this means no more ???? in driver names, which is a very good thing.

As always I hope it works. There are still a couple of little things to fix mind you... Please let me know if you spot any oddities in driver names.