[REL] Delta Best plugin for rFactor 2

Nice appreciation, thanks guys

 

Hey Cosimo thanks for that fix. But what about this?

 

I'll see what I can do in the next version, but don't expect miracles

 

Customize appearance through the DeltaBest.ini file

Just wanted to add quickly, since I've been asked privately in mail by a few people, how to customize the ini file.

• First of all, you should rename the DeltaBest.example.ini to DeltaBest.ini, otherwise the file will be ignored
• Second, you should decide what settings you want to change and find them in the ini file. I've tried to add full documentation for each and every option, so that shouldn't be difficult
• Once you found the line you want to change, make sure there is no ";" character at the beginning, since that means it's a comment line, so the program will ignore such line. Removing the ";" character makes the line effective.

That's all, hope this helps someone out there

 

If anyone would know, Gerald would . I'd gladly chip in a beer or two for this amazing tool. Anyone else with me?

 

I just bought rF1

 

I guess we're both in for a treat then

 

Hey Gerald,

I don't see how I can make a rF1 version. It appears there is no ScreenInfoV01 data structure and no Screen*() methods in the rF1 InternalsPlugin example (v3)?
Do you have any insights? Maybe rF1 also supports InternalsPlugin V06?

 

Yes, the display process is much more tedious than in rF2. Indeed you do not have directly access to the D3D device, you need to create your own device using the application handle. Unfortunatly i do not have an code example to provide to you. May be you can find if you find source of an rF1 plugin (i know rFDynHud is open source, but it is not the more simple plugin to extract the D3D part)

 

Thanks Gerald, that's enough to put me on the right track.
Looking a bit more in depth into the source code, I determined I need to use the GraphicsInfoV2 structure's mHWND and go from there.
I wasn't sure whether I could just create my own D3D device or there was a pre-allocated one. I'll create my own and see what happens.
Still, I agree rF2 is miles ahead in this respect too.

 

Just thinking out loud but I wonder if useful/possible to have a multi/lap comparison vs. a lap to lap comparison, for example to encourage/measure consistency. So if I was on lap 7 of a race (without AI in the way, of course, or practice or qualify session if didn't count out lap, for example) I would see my TOTAL time for this lap + the first 6 laps compared to my TOTAL time at this point for my fastest total/average time the last time I did a session like this. Obviously some questions to answer and may be stupid but thought I'd throw it out there. Could also serve as something of a race against yourself

 

For me that v15 is perfect! I just checked it (using v13 until now): no spikes (from telemetry data I suppose), time is centered without the bar, and now resets correctly.

thank you cosimo!

 

thenk you Cosimo, great job.
We are waiting for some news about the new project

 

I love this plugin, but I get inaccurate timings (says I'm several seconds faster than I am) and lots of toggling between plus and minus times after a few laps. I'm using 798, 32-bit.

 

Cosimo will have to answer Flatspotter, but I have noticed that some tracks offer screw-ups as far as track timing goes. Far from expert but I think my problems with the bad timing problems I see sometimes are due to the track I'm running.

 

The up/down timing jump can happen if you either crash or the direction of the car changes drastically.

This is a consequence of the time tracking algorithm used.

That said, what track/car was this Flatspotter and Jim?

 

Also, any chance you could make a video?

 

OK, I crash a lot, so that seems to be what's causing it. I've seen it at Nordschleife Tourist 1.81 with the GTR, and Longford (the most recent version) with the Howston G4.

 

Released new version (v16) of the plugin, and updated the first post with a changelog!

 

Brilliant, thanks Cosimo!