Thanks a lot. Much better now.

I am requesting them once at the beginning and it seems to work except in SPRs (I haven't checked MPRs yet).
Should I request them at other times/events?

Here is my current code (using JInSim):

I'm trying to detect a car model of the currently viewed car in a single player replay. I am able to get the state changes with id of the viewed player. However, the only way of mapping this id to a car model (that I know of) is through the data received earlier in IS_NPL packets (new player joining). These packets don't seem to reflect what is happening in a SPR being played, I only get them during an actual race.

From LFS/docs/Commands.txt :

Quote :

Local commands:
---------------
Most of these text commands replicate functions usually controlled by
pressing on-screen buttons but can be useful in other situations, for
example when controlling LFS from an external program using InSim.
...

Maybe it could be used as a workaround and also potentially lead to more efficient way of managing multiple LFS programs.

I have tested on Linux with Wine and an old mobile Radeon GPU using open source drivers which have poor performance. In the worst places on Westhill from the cockpit view the framerate went up by around 40 % in 0.6H5 when compared to 0.6H (in 0.6H4 it was maybe 15 % better then 0.6H). Very impressive!

Here is a 0.3 s time difference from that last log:

Quote :

22:21:15.675668 sched_yield() = 0
22:21:15.675693 gettimeofday({1432498875, 675702}, NULL) = 0
22:21:15.675719 select(0, NULL, NULL, NULL, {0, 4949}) = 0 (Timeout)
22:21:15.680780 clock_gettime(CLOCK_MONOTONIC_RAW, {417569, 108602728}) = 0
22:21:15.998481 futex(0x110070, FUTEX_WAIT_PRIVATE, 0, {5, 0}) = -1 EAGAIN (Resource temporarily unavailable)
22:21:15.998991 rt_sigprocmask(SIG_BLOCK, [HUP INT USR1 USR2 ALRM CHLD IO], [], 8) = 0

But this does not necessarily mean that clock_gettime system call takes that long. Could you add -T option to strace?

Quote :

-T Show the time spent in system calls. This records
the time difference between the beginning and the
end of each system call.

Last edited by w126, Mon, 25 May 2015 05:45.

The DLLs in ~/.wine/drive_c/windows/ are not the proper DLLs, they are just Wine placeholder DLLs. You need to download the real ones, for example, the files from http://www.dll-files.com look ok - just choose zip version.
Here are the checksums of the files that work with LFS on my Linux:

Maybe you copied 64-bit versions of D3D*43.dll files into LFS directory? Did you copy them from Windows? What version of Windows and which directory under Windows?

Quote from Gutholz :

But one can use coordinates from MCI packets. First drive the route slowly and press buttons to place 'notes', then save the notes, then the notes get played back if you come near their location.

I think the difficult part is that the notes should be played before the place where they were set (for example, during recce you know the turn severity only after driving through it). In addition, how much in advance they should be played depends on how fast the car is and on specific driver preferences (RBR has earlier-later slider in the settings, AFAIR, some version of Dirt, too).

Seeing that the autocross system had just got new features (not just bug fixes), could we also get the slab object equivalent that has gravel texture and behaves like gravel when driven on?

Some like LFS-Trackmania, some LFS-Minecraft. Why not LFS-RBR?

This is great!
But... on such a large drivable terrain I could not find any gravel road section or gravel area. I'm not sure if it's a bug.

Quote from blackbird04217 :

In my first implementation of a GA each gene has a value from -1 to 1. I may later change this to be from 0 to 1, but it seems like a reasonable approach. If the application of a particular gene needs a larger range it can always be multiplied later. If there are 100 reference points along the track, then there would be 200 genes in each chromosome which the driver gets. One for steering input, one for brake/throttle input where negative is braking.

Taking this approach I will then compute the current and next reference points and interpolate their genes for the input of the car.

[...]

Any driver that falls off the track will stop moving, and fitness will remain the distance where they went off the track.

Just a few thoughts... A combination of GAs and racing seems interesting^2.

The approach you described could maybe slightly improve a prescription for already good lap around a track, but I don't think it has a chance to work from a random population. The desired steering inputs at any situation are strongly dependent on the lateral position on the track, car heading (relative to the road axis) and its current speed, not only on the reference points which you use. The "genes" should somehow express this dependence on many parameters. In this way virtual drivers evolved by the GA could be able to recover from errors. This is needed because at the beginning they will almost always be far from the perfect line and speed.

Regarding the fitness function, there should be a penalty for driving off the track, but the simulation of a single driver should not be stopped then. By stopping you are not allowing off-track virtual drivers recover and potentially shine in other places on the track.

Last edited by w126, Thu, 12 Jun 2014 17:36.

Quote from CodieMorgan :

Were is africa? 0.o

Wasn't it sunk in revenge for Black Hawk Down?

Quote from JeffR :

Note that lateral peak force is related to the component of force perpendicular to the direction of travel.

Someone might choose to describe and model tyre forces this way, but it is not the standard method of doing it used by almost everyone.
See the figure on page 2 of http://zzyzxmotorsports.com/li ... uencing-tire-modeling.pdf . I think most of published tyre data is compatible with the coordinate system described in this document.
Lateral force is perpendicular to the direction of wheel heading, not the direction of wheel travel.

Quote from Bob Smith :

you end up with your car sliding side to side with a magnitude of the relaxation length.

That must have looked funny, as the typical value of relaxation length for lateral behaviour is around 1 m, FWIR. I must say all these things are pure theory for me, I haven't really experimented with them in code.
Here is another damping method (which you may have seen already): http://groups.google.pl/group/ ... tors/msg/509e0cfe0516548a

Some solution for low/0 speed and oscillation problem is described in Development of an Intermediate ... or Optimal Design Studies, formulas (7.3.8) to (7.3.12).

Quote from The Very End :

I hope they manage to sort this crisis out, having most of the people in the current ruling government out, it got to be hard getting everything back on track.

The current government having the leading role in ruling the country is almost not affected by this. The prime minister and 'full' ministers were not on the plane. In Polish political system the president mainly represents the country and is able to veto the parliament legislation (which again may be rejected by parliament with more votes).

Quote from obsolum :

I understand they were all very important people but still... ~3000 vs. 132?

You are definitely right. In this tragic situation it is really sad that in the lists of victims published by many Polish sites they only mention VIPs and neglect pilots, flight attendants, bodyguards etc.

Last edited by w126, Sat, 10 Apr 2010 12:33.

Quote from Shotglass :

wouldnt you only need a relatively straight forward set of 4d data to reproduce a tyre in all its behvioural characteristics?
doesnt sound too complicated to me... maybe 5d if you add aligning torque too

And normal load, camber, temperatures...

I think there is always too much talk about force combining in such discussions, as if we were Flatland citizens.

Quote from MadCat360 :

There are, TC 22 America and scroll down.

If they were competing in WRC, their final time would've put them 24th out of 26 WRC cars (25 WRC cars competed).

You mean these 25 cars? http://www.wrc.com/jsp/index.j ... son=2010&rally_id=MEX
These are not all WRC cars. The last 2 are Peugeot 206 XS in A6 class (FWD with probably not much more than 150 hp).
Entry list: http://www.wrc.com/jsp/index.j ... son=2010&rally_id=MEX
Did they even run on the same stages exactly? Does comparing the total times make any sense?

Last edited by w126, Tue, 23 Mar 2010 22:44.

It seems the device is produced by this Czech company: http://www.motion-sim.com/

The copy of the video you linked to and the donation links look very fishy indeed.

The data available from real-time official LFS interfaces are very limited, so this problem looks difficult. However, RAF contains slip fraction.

Quote :

Slip fraction
-------------
This is the dynamic value of the current combined slip ratio relative
to the combined slip ratio that would provide the greatest force.

0 to 254 - slip ratio increasing up to maximum force available
255 - slip ratio exceeds the maximum force slip ratio

Obviously, it's not real-time data, but maybe it could be used to construct a model of very high-level "distilled" grip characteristics of a given car and setup.

Such a model could be a function which takes:

• linear acceleration vector,
  
• angular acceleration vector,
  
• linear speed (needed for cars with downforce),
  
• car orientation (e.g. up-vector, needed to take driving on banked surfaces into account, and forward-vector to distinguish between cases of moving on the same trajectory with varying amounts of drift)
  

and returns the slip fraction values for all four wheels.

The above data (function inputs and outputs) can be logged quite easily with simple calculations from RAF of test runs of a given car and setup with near to optimal tyre temperatures. Then the hard part would be to find a mathematical expression that approximates the function with sufficient accuracy. The inputs of the function can be retrieved in real-time from OutSim (with some simple calculations) and the AI could use the approximating function to get "predictions" of slip fraction values when driving.

This ignores real-time tyre temperature and wear, but AI could deal with cold tyres by not using 100 % of the optimal grip at the beginning and gradually going closer to the limit as tyres warm up. Also, adding steering inputs to the parameters of the function may seem useful, however, they already influence existing function parameters.

Quote from brt900 :

cmon 2002 turbo beat mk2 escort wtf is wrong with these people i need that escort

Just one example from this forum:
http://www.lfsforum.net/showthread.php?p=1352885#post1352885

Quote from brandons48 :

I wonder what would happen if Block completely dominated the WRC?

Hell would freeze over?

Using the data from CAR info binary format is for sure better than 1/4 of unsprung mass. FWIR exporting of it was added in LFS later than the discussion in this thread took place.