I have a little question regarding the InSim, OutSim and OutGauge protocols. The OutSim and OutGauge packet-rate can be set to 1/100th of a second, but the maximum update rate for the MCI packets is 1/10th of a second. Is there any way that could be brought down to 1/50th or 1/100th? Maybe it will lag LFS too much, but I wouldnt know

Are you sure you are reading the values correct? You should get integers as a result, and you are getting floating point numbers. If those numbers are the coordinates converted to meters, then I think that -1.45 means 1.45 meter in the (negative) direction perpendicular to the (dirX, dirY, dirZ) vector.

Yes, a node has a certain coordinate, but you should think of it as a checkpoint. So it is actually a line, with that point as midpoint (or a point near the middle).

Polygonal areas: yes.
More points on a line: not sure.
FOV: yes, altough Im not exactly sure what would be the best way.

Thank you for making a camera set I was thinking of creating a small webpage with files, so that the camera definitions do get scattered around.

Quote from axus :

Well this could allow users to make pretty looking dashes for the GTR cars without it taking as much time for Scawen...

I guess waiting just a little bit longer until Eric has done new GTR interiours would be the best option

I see EngTemp in there. What about Tyre temperatures and wear? Altough I guess it should then be renamed to OutTelemetry, and I dont think it is the point of this OutGauge thing

tbh, I think the reason for not putting tyre info in there is the size of the packets 48 tyre-simulationpoints, right?

Edit: maybe I should read the complete topic before frantically rushing for the Post Reply button

Quote from Dygear :

Hey, guys, I need a C++ or Java programmer that is willing to make a replica of the Formula 1 Java Live Timming Thingy. It would be for SimFIA . . . So any one up for the job?

I've been planning to make something like that for the masters of endurance. A kind of software version of the tracker website. Cant promise it will be anytime soon though, Im currently drowned with work for university, and that isnt going to change untill July, and then it is summer and I dont want to be inside programming

Here is v0.8.

Changes and fixes (v0.8)
* Not all players were listed.
* Should work better if noobTV is started while a replay is running.
* Primitive yellow-flag detection.
* Option for username/playername display.

Please keep 'em coming, those suggestions and bugreports

Last edited by Frankmd, Sat 13 Jan 2007, 20:57.

People who dont have problems running version 0.7, please post, so I know what kind of problem it is.

It should work with patch T4, but I am not so sure anymore after the post above.

The only time I got the problem with Player0 etc is when I start the tool after the replay has been started. Maybe I should have put that in the readme. For the next update I will try to fix this.

Quote from traxxion :

I was gonna make a silly joke about your skins but I can't really, cos I liked the teamnic skins very much.

Anyway, still in favor of a simple encryption. If people want to crack it, they always can, but I think they won't do it as soon, as much and as easy as they can now and that's what we're trying to achieve, right?

Well, a joke wont hurt in here.

I was refering more to the situation on our highways nowadays. People are so close behind each other, they really dont have any sense of how close it actually is.

I think the speed displayed on speedos in cars should be in m/s from now on. It will cause some awareness of how fast you are actually going. 100kmh doesnt sound that fast, but 28 m/s does. Especially if you are 2m behind the car in front. That means that you are only 0.07 seconds behind him.

Oh, and I think about everyone that managed to pay attention at physics class knows the conversion factor for kmh to m/s and mph to kmh.

It would be possible to make some sort of protection using a fileformat that is very hard to crack, but since it is an image, I think something like that will be cracked pretty soon. And I dont consider the problem big enough to create some kind of uberprotected format. Just think of all the time that has to be put into LFSWorld, LFS itself and for skinners while skinning. A protection will cause more trouble then it would solve.

My vote is to keep it the way it is. What we did with our teamnic skins was to put "This skin is property of teamnic and can only be used by teamnic members". Of course it is not a real protection, but I think it helped a bit, because I dont think we ever saw anyone use our skin after that.

Here is v0.7

I adjusted it to the new InSim packets and changed the way the cameras are stored. Included is a tutorial on how to make your own custom cameras, and a little tool that will help you with that. This tool also allowes you to get higher than 2.6 meter.

Unfortunately I found out that I was wrong about putting the camera besides the track. Even using the CPP packets you cannot set the camera somewhere in a grandstand. I do hope that this will become possible one day, because with some care we could make pretty spectacular camerapositions.


The coming time I will add something that will tell you when a car crashes, or when two cars are overtaking. I cant promise that it will be done soon as I am busy enough with other stuff.

Please report all bugs in the program and in the turotial and dont be ashamed to ask about something, because I know the readme isnt great.

Last edited by Frankmd, Sat 29 Apr 2006, 09:04.

Berliner from Holland

Since the lx4 and lx6 cars feel a bit underpowered now, I really vote for a version with lots of power. Especially if it has slicks.

Shift N is a little bit safer then shift w, because that is so close to shift S

Here.

Quote from ajp71 :

Can't you race online, there's no shortage of BF1 servers atm.

A mere overkill I'd say.

I just noticed that the notification of a downloaded skin is put offscreen partly. See the screenshot.
I use 1280*960 resolution.

Happens in fullscreen and windowed mode.

I think it is the compressed skins feature.

http://www.lfsforum.net/showthread.php?t=6832

Some blur would be nice, but the reason why you dont see the tyregraphics behave as on tv is because the framerate on a tv is fixed at a low framerate. In lfs the framerate fluctuates, and is also at a very high value.

If you limit the fps to 25, you will see exactly the same behaviour as on tv, except from the blur.

I just did an endurance test, to try out how long the tyres hold. I did 67 minutes with the xrr on kyoto gp long, and then the front left tyre popped. I think it is possible to add a few more laps, considering the amount of tyre that is left.

http://teamnic.com/files/67mins.jpg

I have tried the r4s a little bit, but I couldnt get them up to temperature at Kyoto national using 140ish tyrepressure.

I really like the new aero physics, it allowes you to drive a lot closer, much more fun racing.

Another useless thread...