The difference was intent. Schumacher knew that Rubens was there, and forced him to the wall. Button did not see Lewis and this was the result. They are similar, but not the same.
Yeah, I was in the middle of updating that, because I relized that not everyone was going to go from Z28 to A1, so strictly speaking that's not always going to be true. Thus I retracted that statement. Although I did provide my hosts.ini file as an example for the lost souls.
You can get a LFS 0.6A1 InSim Version 5 compatible patch for PRISM here. Actually, even 0.3.5 should still work with the current patch, due to how PRISM handles packets. But, anyway, this version includes the new packets in the 0.6A1 patch for LFS. There is only one thing that I've not worked on that I must, and that's sending IS_AXM packets to InSim from PRISM.
Please do test, and you can all expect the next official patch pretty soon after this if no one finds major bugs. Any issues please report them here or in PRISM's Issue Tracker. Thank you all for using PRISM, and I hope to continue this development pace over the coming weeks.
One last quick note, in order to get all of the new fetures from the new InSim packets you must change the flags in your hosts.ini file.
My hosts.ini file looks like this for my local server.
That's a good question, as it should not really be possible to incercept messages in this way. Unless I've missed something within the InSim.h file ... What your saying is something I would like to see also, the power to handle messages from a client to sanitize them would provide a great level of power to any InSim application.
Only on new users. This bit of information should really be cached for S2 users, until S3 comes out. But then on each connection for someone with a Demo or S1 license. (I wonder what the break down is of Demo vs S1 vs S2 licenses is.)