Ube1 wrote:Here! I hope it's the right one because i have 6 of them. (hs_err_pid5024...)
It doesn't matter. Each JVM-crash produces one of these. I assume, they're all the same.
Unfortunately I cannot see the reason in that file. It doesn't even seem to execute any Java code when the crash happens.
Could you please also attach the rfdynhud.log?
Ube1 wrote:ps: i forgot to mention, rfDynHUD_v1.0.1 is working just fine. But i think it's incorrect because engine life is running out fast, in race session i got engine to -800% and still was working. Also with brakes and tires.
Event if I theoretically got the correct math for brakes wear, it never really worked. So you shouldn't pay too much attention to this display. But engine wear should be correct. It is very well possible for this value to go below 0%, if the engine lifetime has a variance. You can setup the WearWidget to never go below 0% (keyword: 100%-base). But if the engine has a variance - like all of the CTDP 2006 cars do - it won't blow up at exactly 0% then.