LFSLib.NET v0.12b (this is a test version)
I've just put v0.12b on the server. This version does bring LFS 0.5X compatibility, but it does not expose the new functionality. The goal of this version is primarily to let 0.11b code work against LFS 0.5X with the least amount of changes (some data just isn't represented the same anymore and caused breaking changes). This version is also ill tested, as I'm not going to go through an exhaustive set of tests until i get full 0.5X feature exposure (yeah, I know, i should be doing this test driven.. But that means a mock LFS or an LFS test harness and I haven't had the patience for that).So what has changed? Here are the notes:
- Moved to .NET 2.0 and Visual Studio 2k5
- Swapped out back-end for dealing with InSim packets to more closely resemble the native LFS formats and removed the intermediate Msg* classes (all internal changes)
- Finally mostly functional Unicode support for LFS message in and out transfers
- Updated existing functionality to work against patch X, with some breaking changes in what is available in Events and how that data is represented.
- Full patch X protocol implemented, just not yet exposed, so new packets don't come across as unknown packets
An extra note on "mostly function Unicode support". Basically for conversion of unicode to LFS encoding, I am using a lookup table from unicode to codepage+byte and there are a couple of LFS specific characters that screw up under Japanese encoding. And split messages have some issues. This will be fixed in 0.13b.
The new version can be found here and the home of the lib is here
Labels: InSim, LFS, LFSLib.NET, live for speed, patch X

5 Comments:
Hey, I'm lucky I found a C# implementation of insim, and downloaded 0.12b today to play with. I've also downloaded the Tester project and converted to VS 2005, and also went through everything to make it work properly with 0.12b.
I got the Tester working (no more compiler errors, no exceptions thrown while running) but OutGauge and OutSim do not seem to work at all - all fields remain blank all the time. Everything else seems to be working properly, even camera setting (eventhough it behaves a bit strange).
Do you have any idea why OutGauge doesn't work? That's what I'd love to use the most - I just want to build a very simple fuel warning thing.
Thanks!
Rado
The tester is a beast i created to check on the lib and it's usually in ill-repair and a great example of bad coding practices :)
Anyway, check out this post for a simple OutGauge example:
http://www.claassen.net/geek/blog/2007/06/simple-outsim-outgauge-samples.html
Ahh, thanks a lot! The samples are very nice. :-)
The OutGauge sample is working, but I get a lot of crashes/exceptions (such as ArrayIndexOutOfBounds or NullPointers). Do you think this is a problem with LFSLib 0.12b, or do I have to take care of something? The crashes occured when restarting race, when passing first lap, but even in the middle of the race.
Thanks again!
Rado
I don't think it's the lib. I've never had problems and can't reproduce your issues right now in 0.13b and OutGauge really hasn't changed since 0.10b.
To be sure get the new version, which was just released
Thanks, I can't wait to try out with 0.13b, but have a lot of work to do this evening so I'll see if I can do it today or tomorrow.
Thanks for all your work on LIBLfs :)
Post a Comment
<< Home