Auto update would be very awesome. It was one of the corner stones of what I wanted to see in PRISM. Filur did something like that for his InSim app that he never released.
Ok, so I've merged these changes into my branch. If you'd like to make a release for PRISM 0.4.5 following to format that myself and Victor have used that would be great!
Lol, git really is quite good. I've learned a lot of the stuff I needed from github's introduction to git. You'll pick it up pretty quickly. Once you get used to it let me know, and I'll give you write access to my repo of PRISM.
You can start making releases for PRISM at that point on here. I really don't have the time for this currently, so I'm happy to give it to someone who can maintain it. I can ask Vic to give both you and Jay access to mod this forum as well so you can do releases property.
Ok, now that I see the full code block it all makes sense now. I've been living in the world of bridged connections for the past few weeks as I'm been fiddling with network settings within WiFi routers. I just assumed that packets can be seen by other InSim instances. I've forgotten most of the the stuff that I've myself wrote and most of the rules that InSim uses. Not an inspiring bit of news from a Dev, huh!?
This is from what I understand of the InSim.txt file. Nowhere does it say that a ISM packet will also get all of the information for the clients and players. It simply get's the information about a host that you join or create in so far as it's host name. The requests you see are needed when PRISM is running by it's self. So that it can get the information. I think that AIRIO is doing the same thing that I am doing in so far as questing all connections, all players and then all results. That's why you are seeing the double packets.
Well, the state handler does get it's stateful information at startup from there. But as you said AIRO is already getting those packets, then PRISM does not have to request them. But if you were running PRISM standalone, then you would want to keep those lines in there. Unless you are saying that PRISM is it's self request two sets of cars and clients data.
As long as you understand the ramifications of doing that, then it's fine. Your not running PRISM stand alone, so it does not really matter. On another note, PHP 5.5.0 was released two days ago. I have it up and running on half of my web servers. So far, so good.
That's the point tho. Just because it's supposed to only be used by the program it's still an attack vector for someone to use if the file was writable on the server it could become an attack surface for something else. Whereas file_get_contents would be a much more appropriate use as it does not introduce this attack vector.
I can't load any of your images, Tim, so I don't know for sure what went wrong. But it looks like you got the answer from Dustin anyway.
[Edit]Never mind, they are loading for me now. The last image you posted with color is as much data as you can get out of the SMX files unfortunately. There is some sort of relationship between that and the texture files as well, I'm sure of it but I never really got so far as to check it out.