can some one make a video on how to make a insim
thx
thx


The Python Library (pyinsim 2.0). Written (obviously) on Python.
The Spark InSim Library. Written on C#. Requirement: .NET Framework 4.0. Or, download the whole Visual C# Express 2010, I believe that should install the .NET Framework 4.0 as well.
The CInSim Library. A C++ Library. I wouldn't recommend that as a start tho. Low level programming manages to spin my head quite easily, so I wouldn't recommend it to any new programmer, that doesn't have a really serious motive to learn it.
The JInSim Library. Written on Java. Instructions on how to get and start programming on Java can be found on the 4th post in that thread. I will quote it, so it would be easier anyway.
There is also LFS_External. Also written on C#. But however, I, personally, wouldn't recommend that library anymore. Spark, imo, is far more freer, because you have a higher control in packet handling(if that made any sense to you... or anybody in that matter..). Also, Spark's source is available, so you can do as much tweaking as you like to the actual library. While LFS_External's (source) is not.
InSimSniffer - Using it's own library (DarkInSim), which is, afaik, an older version of Spark. This application tracks the transfer of packets between itself and the server. It is very helpful if you want to learn more about packets, and right.
Open Source Cruise Application - using LFS_External. This is a basic cruise application, providing a few vital systems, which are needed for the cruise InSim application to actually be... a cruise InSim application.
Open Source Racing Application - Also using LFS_External. This is a racing application, which makes it so every race is limited to 1 car. The winner of the current race picks the car for the next race. There is also a weak attempt for a scoring system, which works with a database. The SQL files are there.






). Tell me if you want me to take those down. 
Let's see how many people can actually get some useful info outta it. And BTW, I just realized that I should've called "insim.isclose()" before exiting to properly close the socket. It's also no really apparent in the video but syntax like "struct* IS_BTC" is complete nonsence, to make the code compile it has to be "struct IS_BTC*" (pointer to a struct of type IS_BTC). I said it was rubbish after all, didn't I?




, I am accepting suggestions for folder structure. Actually, if you think it would be better, you can give suggestions from now too. 