Yeah I'd be happy to contribute to LFS Record. The first thing I'd do is port the InSim code over to InSim.NET, which shouldn't be very difficult. It's not so much about testing every part of the code, most of it is fundamentally unchanged, but just taking care of those small things that only crop up when you're running in a real environment.

Once I'd done that I can take a look around and help with anything else that needs doing. I must admit that I've already had a peek at the disassembly, but it's hard to see exactly what's going on if you don't have the original source files.

So yeah, sounds good.

Last edited by DarkTimes, Fri, 24 Dec 2010 20:36.

I have decided that the best way to test the new version of the library is to write an application that uses it. So... if you have a good idea for a InSim program or tool, let me know and I might write it for you. And no, I'm not going to write a cruise server.

At the moment I'm thinking I might build a LFSRemote/LFSSpecator style tool with WPF, that lets you spectate races outside of LFS. I already have the track rendering code written, and I think drawing all the cars and stuff would be quite easy and fun.

But I'm open to suggestions.

Last edited by DarkTimes, Wed, 15 Dec 2010 23:38.

I prefer to have to click them.

Quote from 5haz :

I suppose thats why you quoted the huge picture again.

Oh sorry, the images don't get loaded for me, they appear as links.

Anyway, I'll shutup, I should have learned by now not to look at or post in this part of the forum.

Quote from deggis :

<snip />

Really not a nice picture dude. Some of us don't like to see such things.

Last edited by DarkTimes, Wed, 15 Dec 2010 23:13.

Quote from thisnameistaken :

I was getting terrible performance from my 10Mb Virgin line the other day, so I called their Indian tech support call centre and my technical advisor 'Nitin' advised me to visit a speed test website.

After literally ten minutes of sitting in silence on the phone with him whilst waiting for the speed test page to load it miraculously declared my speed to be 9.53mbps and Nitin - with no hint of irony whatsoever - told me that I was receiving an excellent service!

:banghead:

Yeah, I've had that before. I called up the guy at TalkTalk to tell him I was only getting about 100 kbps, when he proudly informed me that my line was running at 8 mbps. OK - great, my phoneline gets better broadband that I do, but that doesn't help me when I'm trying to watch an episode of Doctor Who and the screen freezes every ten seconds.

Anyway, after getting more and more angry with this poor guy (I always try not to get pissed at them, it's not their fault), I eventually hung up. Within a few days my speed was miraculously back to normal all by itself. I guess those three inches of cable between my phoneline and the computer must have recovered.

Send a TINY_SCP to request a CPP packet.

In keeping with my other projects I've codeplexified this. You can find the project page at:

http://insimdotnet.codeplex.com/

I've uploaded the current codebase, although it still needs a few tweaks and fixes here and there. I'm going insane trying to get encoding stuff to work, so I've just included a modified version of the old LFSLib encoding code, which works great for single-byte character sets, but not double-byte characters such as Chinese. Also now included is full OutSim and OutGauge support, plus lots of other API improvements. I need to create some documentation for the changes, amongst other things.

I'm trying to get all this stuff finished to I can stop bloody working on LFS related things and program something more interesting.

He means colon is on the shift modifier (or whatever it's called) for that key.

This image might help.

http://pages.slc.edu/~support/ ... yboard-layout-spanish.png

I added a release for InSimSniffer 1.2 to CodePlex and added some screenshots and documentation.

http://insimsniffer.codeplex.com/

I have uploaded a new version to CodePlex.

It has all new sniffer code, so again it may have one or two bugs. I also rewrote the options dialog to make it easier to use.

Please report any bugs or issues you may have.

Last edited by DarkTimes, Tue, 14 Dec 2010 10:13.

Hmm quite a few errors in this beta it seems.

I had added some stuff that generates a default filename for you when you click export, and while it works on this PC, that doesn't seem to be the case for you. I think it may be an internationalization issue, as the filename in that error report is slightly different from how I intended it to look. Anyway, I've simplified all that stuff now which should get rid of it.

I was't planning on releasing a new version until I had finished the new sniffer code, but I have uploaded BETA 3 which is just BETA 2 with a few bug fixes.

In addition to confirming the export now works (hopefully), I'd also appreciate it if you could report back on whether the Launch LFS code is any better.

Thanks!

I fixed the messy looking error on keyboard interrupt and pushed the change onto the repository.

Quote from RenvoN :

def yellowflag():
flashing = 0

while(YellowFlag):
if(flashing == 0):
texto = chr(46) + ' ' + chr(46)
remover_botao(255, 0)
insim.send(pyinsim.ISP_BTN, ReqI=255, UCID=255, ClickID=0, BStyle=32+1, L=90, T=25, W=20, H=10, Text=texto)
flashing = 1
sleep(1)
else:
texto = chr(46) + ' ' + chr(46) + ' ' + chr(46)
remover_botao(255, 0)
insim.send(pyinsim.ISP_BTN, ReqI=255, UCID=255, ClickID=0, BStyle=32+1, L=90, T=25, W=20, H=10, Text=texto)
flashing = 0
sleep(1)

Where in your code is the YellowFlag variable being set to false? You will need to set YellowFlag to false at some point, otherwise the code will enter an infinite loop, which would indeed stop the thread from ever exiting. I would double-check your code to make sure that variable is being correctly unset.

Additionally I would not suggest using a thread for this, a better idea would be to use a timer set to elapse every second. Check out the threading.Timer class.

Last edited by DarkTimes, Sat, 11 Dec 2010 17:08.

OK, thanks for those reports. I just haven't checked the tab stop order for a while, so I guess it must have gotten mixed up.

I can try adding a call to Process.WaitForInputIdle() to the LFS launch code, which will cause InSimSniffer to wait until LFS has finished creating its main window and the message pump goes into an idle state. Hopefully by then the socket code should be ready for it to connect.

The exception thing was something I put in to allow me to test the unhandled exception code and I decided to leave it. It lets people see what happens when an error occurs. I don't remember where the Monty Python references came from.

Last edited by DarkTimes, Fri, 10 Dec 2010 20:48.

LFS should reply with an error when you set the wrong admin password in the ISI packet. Even something as simple as adding a TINY_APR (Admin Password Refused) packet before closing the connection would work.

Last edited by DarkTimes, Fri, 10 Dec 2010 01:41.

Quote from RenvoN :

I found the problem.

At least on the stable version, it's not passing the IP correctly. I type 192.168.1.2 (which is correct to connect to my LFS) and it's shown as 127.0.0.1 on BeginInitialise().

Since I don't know how to fix that, and I needed to know if it was the real problem, so I putted:

settings.Host = "192.168.1.2";

And it connects perfectly now, so it must be a problem with getting the IP from the field.

Hope I have helped somehow!

OK I understand the bug now and I have fixed it. I have uploaded a fixed version to the beta post.

Thanks for the help, it's great to get these issues sorted, so often people don't even bother to report them.

Edit:Reporting bugs is like voting in an election. If you don't report bugs, you don't get to complain about errors.

Last edited by DarkTimes, Fri, 10 Dec 2010 03:43.

Edit: Ignore, it turns out it was my bug.

Last edited by DarkTimes, Thu, 9 Dec 2010 23:26.

OK - I have fixed the password miss-match bug and the illegal path bug and uploaded a new version to the beta post. The illegal path bug was introduced by a change I made to make the LFS.exe browse dialog work better on Windows 7, the admin password bug was in code unchanged from the old version but had just never been reported before.

Quote from RenvoN :

Now I can select the path manually without any problem, it even launches LFS correctly. BUT, I still can't connect to my LFS.

It says:
"Make sure LFS is running and configured to accept connections on the correct port."

I tried connecting after launching LFS by my own and setting insim to 29999, tried 127.0.0.1, tried 192.168.1.2, nothing works.

Have you got any idea to help me?

Thanks,
Lucas

I can't say for certain what the problem is, but that message is ConnectionRefused, which means that either LFS is not running or the host/port information your provided is incorrect.

Do you get this error with the old/stable version of InSimSniffer?

Last edited by DarkTimes, Thu, 9 Dec 2010 23:39.

Dear Microsoft,

Please fix the bugs in the Visual Studio forms designer.

KTHXBYE

I've uploaded a new version where the status bar actually works. Seriously every time I edit the application resources things mysteriously go missing from the form.

Last edited by DarkTimes, Thu, 9 Dec 2010 22:01.

I set about to add some new features to this, but I was embarrassed by how poor the code was, so before I started working on it I decided to refactor the existing codebase to bring it up to a much higher standard.

There are no new features in this version, so to speak, but everything has been improved and brought up to date and many things run better. The code is also easier to follow and less-complex to understand (which is a benefit to me above all else). Other things such as security and compatibility have also been improved.

Anyway, it will have a few bugs here and there, and I still plan to refactor the actual packet sniffer quite a lot, but I decided to release it now in beta form so as to get feedback on any problems there are with the current code revision.

You can download 1.2 later in this thread. Please note that it will have bugs, but then every program has bugs, so meh.

Last edited by DarkTimes, Sun, 12 Dec 2010 16:51. Reason : Added link to 1.2 RC1

I uploaded 1.1.3 with the bug fix.

Note: I also updated the screenshot to show Windows 7 instead of Fisher-Price era XP.

Last edited by DarkTimes, Mon, 6 Dec 2010 20:02.

OK - I looked at the code harder and saw the bug, which I've now fixed.

Thanks!

Last edited by DarkTimes, Mon, 6 Dec 2010 20:01.

You could try using UDP for the position updates, although it seems that your program might require that the packets arrive in the correct order, which UDP does not guarantee.

It sounds like the culprit may be the Nagle algorithm, which improves network efficiency by sending packets in batches. You can learn more about Nagle on the WinSock FAQ.

Another option might be to to use OutSim or OutGauge packets, which do include a timestamp when they are sent.

Last edited by DarkTimes, Sun, 5 Dec 2010 16:08.

Quote from wsinda :

One minor bug: after I moved the location of the LFS installation, InSimSniffer stopped working. It exited with a null pointer exception at startup. (Can send you the details if you want.) Apparently, InSimSniffer assumes that when it finds an LFS registry key, it will also find the LFS install at that location.

I cannot reproduce this bug, so I would appreciate it if you could send a crash report, if one was generated. Otherwise I need step-by-step instructions on how to reproduce it. I have looked through the code and tried moving the LFS location but I can't see anything that would allow this bug to happen.

Last edited by DarkTimes, Sun, 5 Dec 2010 15:53.