Recent content by Mee

Once started in rF2-mode, go to Settings -> Options -> uncheck "Autostart in rFactor 2"

Nice work TheLichten! I can see CarStat is in very good hands :).

Yes, he took over the project and you can find the new version(s) here: https://forum.studio-397.com/index.php?threads/carstat-2-2-turbo.58106/

I installed the rF2 steam version a couple of days ago on my pc and can confirm the auto-detect doesn't work anymore :). I'll create a fix for it soon... (and for the tire problem with a couple of mods)

To put it friendlier: we can't see the image :). Can you upload it to another website like imgur? What mod is it that gives the error?

Can you run an older rFactor 2 build on Steam or will you always have to run the newest build?

I would like to, the problem is I don't know how...

Because with those values you give the AI only a quarter of the normal power... As Lazza said: you're talking about a multiplier here, so use small multipliers (1.005 or 0.995) to get small differences in lap time.

Small new update, not really rFactor 2 related: you can now open GTR 2 and GT Legends cars in the old (included) CarStat. rF2 related: I put up a warning in the engine tab when a car has a turbo -> "not yet implemented". http://www.mediafire.com/download/scqp47cfx4twbta/CarStat_2.zip

The version for rF1 is included in CarStat 2. You've got the choice between rf1 and rf2 on startup. If you don't get this choice, uncheck "Autostart in rFactor 2 mode" in the settings menu and restart CarStat.

Everyone here is saying "no problems running max on a GTX970". I don't agree about that. I have a GTX970 (albeit with an i5 2300 so running on PCI-E 2.0), but running in a VEC-race I'm not running at max settings. 30+ cars on track and a FPS-heavy track will probably result in dips under 60 fps...

You're talking about the Camaro. If you ask me, the wets on them don't work and are just the same as slicks (bug in the mod). I created a thread for this problem, but received no reply: http://isiforums.net/f/showthread.php/21607-Camaro-no-wet-tires?highlight=

Use a longer polling interval?

That's a serious problem! I ran the benchmark here (MSI GTX 970 Gaming 4G) and it did make the display driver crash (4101 error in Windows events). Had the same error a little under 2 hours in an rF2 endurance race, so I would be very happy if this will get fixed. But reaching 3,5 GB of VRAM...

I'll look into it, but that's some complicated stuff!