rFactor2 Replay format needed

Hello,
I have made a replay tool for rFactor1 and i would like to support rFactor2.

Unfortunatly, i cannot find the new format of replay files. (i only succeed to collect drivers).

ISI, could you provide the format of the replay file, please ?

Thank you in advance.

 

Hello.

ISI, could you provide me a response please?

Thanks

 

+1

Enviado desde mi GT-I9505 mediante Tapatalk

 

No one of ISI to at least say a world? ...

 

Maybe post in technical or bug reports, I don't think the guys who would know check the general threads.

 

Is the tool you refer to rfVCRmerge? That would really be needed to get ported to rF2. It's rather unlikely that an ISI dev will respond here other than Tim. I could ask about this as I have a bit better contacts, if you specify what you want to know about the replay format.

 

Hello, no it is no the rfVCRmerge. It is another tool i have done recently.
http://isiforums.net/f/showthread.php/18256-rFactor-Replay-Tool

What i need is the new rf2 replay format. Actually i can retrieve only driver info, but i need a relatively detail file structure description to be able to parse the file and maily retrieve the (pos, speed, break, throtle, rotation, pit events, etc...)

If you can have an anwser i will greatly appreciate.

Don't hesitate if you need more details.

 

Cool. Gerald Jacobson, do you know if exists or if it is possible to exist some tool that convert replays files in some extension playable by any media player?

 

The replay format and compatibility can still change. Would giving you the info not be wasting your time, or are you OK with this at the moment as it would be an easy adjustment?

 

Hello Tim. Thanks for the reply. There is no problem if the reply format evolve sometimes. If i can have it now i could start to convert my tool and then update it if change occurs on some build. I prefer that than awaiting a definitive format.

Thanks again to provide me this.

 

I'll forward this onto the dev, thanks.

 

Luis, the replay files contain no video. You can't convert data (not video) to a video format. The game has to take the data in the replay file and draw what happened. This can't be done by a third-party tool.

If the replay was just video, you wouldn't be able to move around in the virtual world during a replay (like recording a sporting event, you're stuck with what they showed you - you can't go moving cameras around). It seems to be a common misunderstanding that the replay files are actually video.

 

Thanks for the info Lazza. I think i got it now. rf2 is like "the media player" which comprehends this kind of file.

Will have to wait for nvidia shadow play to work in surrounded mode. Tested fraps once but didn´t like.

Cheers.

 

Yeah, I was about to say that
This is how it works - replay file is like a record of all that was happening with the car. You need a program, that can load this car (and track), recreate it's movement according to this replay file and render everything in 3D on your screen, where you can play with various cameras. Obviously, rFactor 2 is the only such program

 

Hello Tim. Still no news about replay format?

 

No, but it's not unusual for a little delay in reply from devs.

 

Which part are you stuck on? The driver listing is almost at the end of the header, so you're pretty far along. Then you've got four 32-bit values (number of time slices, number of events, record start ET, record end ET). And then the timeslices, just like the rF1 format as far as I can tell.

Of course many of the events are changed or new ... is that what you need?

 

Hello,
yes, i succed to collect drivers, but cannot retrieve ETYPE_ZIPLOC_XXX, ECLASS_SYS...etc.. like i did on rFactor1 replay.

 

Did you figure this out with the info above? There's no bookmark info after the driver list now. Just those four 32-bit values and then the same format as rF1.

 

I will redo the test, as you say it is the same format than rf1. I must have a wrong offset somewhere (my many tries seems to have corrupted my original rf1 working code)

Thanks for your replay.