TBH, Making a contest in a sence, isnt fair. It makes people rush and ruin stuff just to get it done. Qute possibly make people annoyed with other people, because someone wins and not the other. On that front. You can count me out. If you want to say "Will someone make me X program for X money" then i'll happyly help you, but I wont contest my skills as a programmer. Sorry.
Burnsy, There is a few issues there, you could fix with a few simple checks. That said, InSim still wont be best to create someting like this. Sadly, i dont think InSim will get anymore attention in S2...
The first bug is a little issue with the InSim packet SMALL_SSG. Basically, As InSim.txt says: You have to give a uVal to SMALL_SSG. In this case, Its the port. If you set the uVal to 0. OutGauge will say its closed. If you set this to anything higher then 0, LFS will say "OutGauge : UDPPort was not specified".
The second bug is a issue with running InSim and OutGauge together. Basically, Setup OutGauge in cfg.txt as required. Then once in LFS, OutGauge data will be sent. If you try to inatilize InSim("/insim PORTNUM"). OutGauge will close instantly, And upon closing LFS. It will also adjust cfg.txt and set OutGauge mode = 0.
The way to reproduce this is as follows...
Get an InSim app. Load LFS. Type "/insim PORTNUM" to match the InSim app. Make the InSim app send a SMALL packet with a SubT = SMALL_SSG. Set the uVal = OutGauge_PORTNUM. Then start the InSim app. If you specified 0 as uVal, LFS will say OutGauge is closed. If its higher LFS will give an error saying you didnt specify a port.
Get an OutGauge app. adjust cfg.txt to the correct settings for your OutGauge app. Start LFS and then goto single player. Join the race. OutGauge data is being received fine. Type into LFS, "/InSim PORTNUM". The instant you do that. OutGauge will stop sending data. = Bug reproduced(Patch Y through to Y16).
I hope that helps. Ive tested the reproduction methods a few times each to the same results.
E: Sorry for not explaining better in the other thread.
Hello, I have made a .Net SDK for this aswell. At the moment this is version 1.0.0(starting version). Ive tested this a little bit and it seems to be ok. The way it works, You must first make an instance of the client.
LTCPubstat.Client Stats = new LTCPubstat.Client();
You must then fill in your ident key. This will be issued by krammeh atm.
Stats.IDKey = "SomeKey"
Once that is done, You must hook up the events the library can fire. Once you have done that, You can start getting some data from LTC system. To do that, You call a method. for example.
GetUserStats("mcgas001");
Then some code will be returned to the event handler. What you do with it from there on is upto you. As Ive said, This is a very basic version. I will update a lot more and add features. Any bugs please let me know. I'll sort them out. Thanks