Then you got me wrong. I just wanted to say that we not only have to say "let's lynch them" but we have to _do_ something. For we can't lynch anybody, we should ban them from our servers.
... did I say so? No! Why do you think I take part of this discussion? Right, because these cheaters destroy our game. The only thing I intended to point out was, that we should do what we can to clean our servers form those cheaters. That's all.
I have searched the forum for some detailed information about the charakter codes - unfortunately in vain. I know that there are color codes ^0 -> ^9, but are there other codes which could be interesting for insim/outgauge tools?
in a way it is not that bad that these cheats appeared. If Neo hasn't done this cheating tool, it would have been created by another person and probably would habe been used in a more secret way. Are you really sure that there haven't been such tools out there? Just 3-5 km/h more top speed and noone would have had a suspect. We all thought that there weren't any cheats out there, now we are proofed wrong.
Of course it would have been much better to inform the devs without letting it spread out. This was really a big mistake by Neo and the other Portuguese. Now it is out and the worst thing about this is that every fast driver is assumed to be a cheater.
Of course we all want Scawen to work on other things like weather, better A.I., LX8 But on a long-term basis for Scawen it is not wasted time to make LFS safer.
And hey, why don't we create a cheater list, so all teams could keep their servers clean by banning those cheaters?
... yup, that's right. This is the way I change position and size of LFS window:
var TheWindowHandle: THandle; . . . TheWindowHandle := FindWindow(nil, 'Live for Speed'); if TheWindowHandle <> 0 then begin MoveWindow(TheWindowHandle, Left,Top,Width, Height, True); BringWindowToTop(TheWindowHandle); end;
Left, Top, Width and Height stand for the size and position of LFS window.
Ciao
Veit
Becky, thx for that hint! With these settings it is possible to run both LFS Companion and LFS Display, but unfortunately LFS Display does not receive any race progress data. But at least you'll see all the other information (rpm, speed, fuel and so on). I am sure that Becky is working on a solution for that issue.
If you like to see all the information LFS Display provides (take a look at screenshot in 1st posting), you have to run it without LFS Companion. Otherwise just follow Beckys instructions.
in LFS please go to Multiplayer -> Create new game . Then you'll see a screen, which is similar to the one I have posted here. If there are passwords in the mask, please remove them.
Have you made a right click on "LFS Display" to click on "Start connection to LFS" as mentioned in the Readme.txt? If so maybe you have set an admin password in LFS or there's another insim tool running?
But it should not be a big problem for the coders of these nice tools to check, if you are watching other cars or your own car. For instance they could check if LFS reports an empty string for outgauge.display2 (in this case this is not your own car). Anyway, it is for sure an improvement, that outgauge does not send the right fuel data of other drivers!
Scawen, thx for that fix.
Ciao
Veit
BTW, my own little outgauge tool needed to be updated too...
in my opinion it would be cool, if LFS could prevent the screensaver to start and the monitor to switch into powersafemode while LFS is running in window mode.
I use SendMessage (Windowes API), which expects an integer value for virtual key code. Unfortunately I forgot to upcase taste (variable of char), in order to create a right virtual key code:
... it's me again. There is a strange problem with sendmessage too. I send keys to LFS using this code:
. . . TheWindowHandle:=FindWindow(nil, 'Live for Speed'); if TheWindowHandle<>0 then SendMessage(TheWIndowHandle,WM_KEydown,ord(taste),0); . . .
It works quite well to simulate key presses of numbers (0..9). But if I send an "114" for a "r", lfs reacts like I have pressed F4. Could someone please tell me, what I have done wrong?
...yup, while watching other cars, outgauge.fuel is reporting their amount of fuel (take a look at red pointer). Outgauge .display1 is '' as it should be, but Outgauge.fuel isn't 0. If someone is using an outgauge tool, he has an advantage.
I really like the new track selection screen and the improved server list. Really nice work! Thx!
My idea was to define that car xyz is able to reach accelerations from -x m/s² (brakes) up to y m/s² (engine). Then you could say that accelerations far beyond these "native" acceleretions must be caused by hits, crashs and so on. If you define, at which accelerations car glas would pop out of its frame, you could play a sound when Outsim sends such data.
There are acceleration inforamtion in Outsim. You could check, if there are great negative or positive accelerations, which cannot caused by engine or brakes. Initialization and use of Outsim is described in Insim.txt.
I was just playing around with insim and was hoping to activate my flasher by sending an insim pack. In LFS options I bound '8' to the flasher and sent a package to LFS. Unfortunately the flasher did not flash. But if I open the chat window, the '8' appears.
Here is the code. Maybe someone of you can tell me, what I have done wrong?