Richard Burns Rally motion?

Hi

I would like to ask if anyone tried (and found) a way to extract motion data from Richard Burns Rally?

I have seen it used in Force Dymamics motion sims but there is no info about how they did it! :no:


Regards, Thanos

Hello Thanos

I just found this site: http://www.richardburnsrally.de/ It contains much mods and usefull things - and a richard burns plugin crater.
I d'ont know at this point if its usefull, but it seems to be... perhaps we can do a bridge to the lvs outsim !?

Greetings, martin

Well, this will not help, but I found who has written the data extraction tools for the force dynamics platform!!!

http://reg.3dactionplanet.gamespy.com/f ... php?t=2685

Dave Skotnicki from http://www.game-editing.net/

Now, how can we approach him??

Regards, Thanos

Perhaps with the standart mail adresses: d.skotnicki or david.skotnicki at game-editing.net. :hi: Or an PN in the tocaedit
forum to racer_s...

But how ever - do you've seen this diskussion: http://www.tocaedit.com/forum/viewtopic.php?t=615 ?
It seems that sirnoname has this intress bevor 2jears ago...

Greetings Martin

I had a look into Vladimir Kadlec' files, which he offers for download.

I've found this:

Code:

typedef struct {
       char pad[0xC];
       float speed;  //0xC
       float rpm;    //0x10
       float temp;   //0x14
       float turbo;  //0x18  ??? in Pascals ???
       char pad2[0x154];
       char gear_number;
} __attribute__((__packed__)) RBRCarInfo;

Regards
Christian

No, the GIDLL extracts the gauge data from RBR in a format that is the same as OutGauge (through IP packets).

But thats only OutGauge support, not OutSim that we need...

I guess, only Dave Skotnicki could help us...

Thanos

I've asked Vladimir via email for help. Let's see if he answers...

It is obvious, that the offset adresses are in a quite compact area. Perhaps we are able to find some additional offsets by trial&error some hex values.

For example:
float ? ; //0x...9
float rpm; //0x10
float ? ; //0x11...13
float temp; //0x14
float ? ; //0x15...17
float turbo; //0x18
float ? ; //0x19...

At least g-forces are needed to drive our simulators!

Regards
Christian

Unfortunatly no reaction yet

:uups: I've seen that we have done the same thing Christian...

Vladi was wrote back to me today:

Perhaps Vladimir should be named as 'autor' in the X-Sim database for the RBR offset adresses.

Regards
Chrisitan

Hello everyone,
I'm sorry for the late answer. I'll try to be more responsive .

No, the 'float' value takes 4 bytes in the memory, so there is no undiscovered value between 'rpm' and 'temp' (similarly for 'temp' and 'turbo', ....). The undiscovered parts are hidden in the 'pads' and probably there is also other car info after the 'gear_number'.

I'm not sure if force feedback gives you the lateral force in all cases (e.g. a car sliding on ice sideways, it hits a rock -> no force feedback at all).

In my opinion the forces are not present in the RBR's memory. But they could be computed from the change of the car's position, what do you think about it? It should be possible to discover the car's coordinates in the RBR world, I'll try it. One could compute velocity vector from two following car's coordinates in the time, the resulting force vector is computed according Newton's second law.

No need for searching over network in RBR. There is file named RichardBurnsRally.ini in your RBR directory. Search for 'Fullscreen' and put 'false' instead of 'true' there. RBR will run in a window, it's paused when any other window takes a focus.

That would be nice .

Hi Vladimir,

The fact, that ForceDynamics get g-forces out of RBR, show that there is at least a way to achieve those data.

The calculation to get g-forces out of car orientation should be similar to the calculation we had to do with LFS outsim.

Have you been able to dig out some car orientation data out of RBR?

Regards
Christian

Position of the car (Floats): X -- offset 0xEF8, Y -- offset 0xEFC, Z -- offset 0xF00. These offsets are relative to the beginning of the car structure (found at double pointer 0x0165FC68, as described in previous posts).

Unfortunately I didn't found (yet ) yaw, pitch, roll.

After some digging I found sinus of the yaw. Actually, I discover, that the value is the sinus of the angle by writing this post . I painted a really really nice picture, and I was going to ask you for your help, how this value could work. But after look at the whole picture, I was enlightened. I'm posting this only because I don't want to put the image to the trash .

I'm sure that the cosinus of the yaw, and pitch&roll are somewhere near. Now I know, what should I look for. I'll post these offsets later.

Brilliant! Thanks alot for your efforts! :thbup:

Perhaps you could upload those offsets directly to the X-Sim community server, so they will be directly usable for us.

-> open Force-Injector (included in the X-Sim² package)
-> enter basepointer(hex)adresses of the offsets + descriptions (effect names + game + patchvers.#)
-> enter your name/alias as author
-> upload offsets to the X-Sim server
-> repeat procedure above for additional games or game-versions

Thanks and regards,
Christian

Hello Kada

This are real great news :thbup: Perhaps there are also the g-forces!?? (no calculation ned :hi: ) And can you tell me how you found these offset's? (Programs?)

:

Martin

The Force-Injector allows to select some offset post-calculations as well. When the forumula for g-forces via car orientation data is determined, this formula can be added to the drop-down menue.

Regards
Christian

@Kada

Have you been able to develop an algorithm? Perhaps following hint can help.

Code:

LatAcceleration = (Cos(Orientation0) * Acceleration0 + Sin(Orientation0) * Acceleration1) / 9.81

LongAcceleration = (-Sin(Orientation0) * Acceleration0 + Cos(Orientation0) * Acceleration1) / 9.81

Regards
Christian