Quote from Dygear :

FOM Overlays & Timing and Scoring Plugin.

So, I've started work on this plugin, and I've got the basic timing parts down on your own car and it looks pretty good. But this is using some features of 0.4.2, and some updates that I've not released yet. But it's a good starting point of code to see how I'm programming this, and I hope people can use this to learn.

I now own SimFIA.com, SimFIA.net, and SimFIA.org once again. SimFIA.com now has a host so do expect to see some content ... fairly soon.

Figures ... Something had to screw up a good thing.

Quote from ivantod :

@ avetere

Be nice.

No, there is no command, or combinations of commands, that allows for the player to exit the pits.

Oil + Rain = Skid Pad Fun!

Rain brings the oil on the tarmac to the surface, so it gets even worse then just being wet. This often happens at intersections as all cars will travel that section of road so it can get, 2 times or even 3 times the normal amount of oil.

There was a patch of road where I live that once I got wet you could do donuts in a 4 cylinder giving it only half throttle. It was great fun if you knew about it, scary if you did not.

Quote from ATC Quicksilver :

I bet he wishes he was Italian, after watching Valentino Rossi for so many years I know the Italian anthem better than the British one.

I know the Italian anthem better then the British only because of one M.Schumacher and his Ferrari days.

I'm pretty sure that PRISM can handle the extra load, even if the update was say, 1 time a second, times 32 players.

So MCI packets unformat string would look like this would look like this.

bSize/bType/bReqI/bNumC/[NumC]Info{SNode/sLap/bPLID/bPosition/bInfo(tBlue/tYellow/t3/tLag/tFirst/tLast)/bSp3/lX/lY/lZ/sSpeed/sDirection/sHeading/sAngVel}

The only limitation is that back references, and in references would have to be same level only to avoid ambiguity. If I knew C++ better, and I had the PHP SDK, I would make this function and add it to PHP myself. I think this it a worth wild project. I also think that JavaScript should have these functions as well with the upcoming WebSocket support for binary data.

Last edited by Dygear, Tue, 27 Sep 2011 07:52.

I'm not so sure about that, I think that every driver would have to setup OutGuage, and then provide the connection details to PRISM some how, so that PRISM could listen for the OutGuage packet from their client. But there should only be the need for one instance of PRISM, and that's on the server side. But I don't know if OutGuage packet's will route outside of a local network, I've never tried it.

The AI thing was obviously out of the scope of this right now, it would be something that Scawen would have to work on. But as far as getting information about the engine we can get that from OutSim or OutGuage. PRISM could handle this without any problems at all if I add the OutSim packet to PRISM. This way we can monitor the engine temps of each of the car.

Version 1.9.7 includes full support for what was added in Version 1.5 of Victor's LFS World Pub Stats. Even more show case pages where updated, but not all of them are done.

Changed my mind, here is 1.9.6 with support for LFS Pub stats version 1.5 and so all of the things that come with it. All showcase pages are present, some have been updated, some have not.

Ok, I'll merge that in as well.

[Edit] The next version will be 1.9.9, and it will be the last version of this branch.

I'll be sure to update that when I get home, expect a fix in the next 12 hours.

Quote from T3charmy :

Although this is nice, it brings me to worry about some things... How exactly are servers that have multi-LFS dedi's going to use PRISM? will we still be able to set up manually?

Most people will only want to use PRISM with just one server, I see that being the greatest use set. But the people like you, who have jumped on right now, are really power users, and so of course there will still be options available to you to setup multiple servers. Something along the lines of a question on if you want to load the settings from the detected LFS instance, or use them and add more, or ignore the detected LFS instance and setup a whole thing on your own.

As I have said before, PRISM really is meant to be installed under the LFS directory, in a sub directory called addons. This is so that PRISM can make use of configuration files that LFS has, and to make use of any assets that LFS uses (Like the path files, or AutoX layouts.) The point of this being not only to make addons clearer, where things like Airo would be installed to $LFS/addons/Airo/ and PRISM would be installed to $LFS/addons/PRISM, it also give us access to LFS directly.

Knowing where LFS.exe is very helpful to PRISM when used on the same computer as the LFS instance. It give us direct access to the configuration files, allowing us to read and parse this data. This means that, as long as PRISM is installed correctly into the $LFS/addons/PRISM directory, PRISM, in the coming versions, will not require any configuration at all. It will simply work with LFS. You don't need to give it any passwords, or anything of that nature, as it has access to that already in the config files. You don't need to setup the hostname, or tell it the InSim port, because it also has that information already. It will just work. I think in many cases, this will get around any problems that people might have with installing PRISM on their computers and servers.

The only draw backs is that it will not configure the HTTP interface, or the telnet interface. But for people that don't use it, I don't see it being a problem. If I do add the HTTP interface to PRISM as apart of the NCN setup, then it would be on port 8080 as to get around the permission problem with Windows Vista / 7.

Just something to throw out there for the future. If a car times out during an endurance race, it would be nice if the AI would take over the car and bring it to the pits where it can then be taking by over from by another player in that team.

First off, don't get me wrong, I feel for you. But the way I see it personally, is that a disconnection should be seen as a mechanical failure of the car, and as such it should be retired.

That said, I like the technical challenge this presents, and when I get some time I'd be willing to do this. But it would be in the forum of a PRISM plugin, and the whole solution could come from PRISM it self, down to the web interface as well.

The only thing PRISM needs a wrapper for, the only thing it can't do on it's own, is colors within the console. That's the only time I would really consider using C# or anything .NET for this project.

Quote from GreyBull [CHA] :

Meanwhile in Somalia...

Well said.

Quote from bunder9999 :

i was under the impression that we hit an impasse, hardware-wise... i mean, isn't that why they started making the I series, and adding more cores?

Yeah, everyone was up in arms about Moore's Law being broken, because it was no longer about GHz, as Intel said it. Coming from Intel that was something as it was Moore was the co-founder of Intel. Then it became a balancing act, of both getting more information processed, get the GHz right, and adding cores to make sure that performance doubles every two years. We continue to hit these milestones, but it is a wonder for how long we can keep it up.

Quote from bunder9999 :

at least a prescott knows to downclock itself when it's overheating. an athlon (t-bred or barton) will keep going until the core cracks.

I've seen on blow a hole clear into the motherboard, but that was a Intel Chip.

Thank you Bob.

Supply and demand. Most people want the whole system, not just the chip, so OEMs are making people pay more.