Lino Banfi

hi, sorry for barging in your discussion. just wanted to say that i have the same problem, bur it shows only when compiling in release mode (eg: using "-O3" and "-g0" parameters when configuring with ./configure). if compiled in debug mode (-O0 -g3) the problem doesn't show. i will try both your solutions.

hi, is it just me or is not possible to access the source code repository anymore? if so, can i ask why? i have read this announcement: This SourceForge project will be kept as a read-only archive and will be eventually removed! and i get the first part, but why delete it? one day someone might want to see what the state of the project was at the "svn times". why not keeping it around? thanks in advance.

Hi Xavi, your solution might not be optimal but it works perfectly, and perfection is good enough for me. Thank you very much for the suggestion!

hi! i was experimenting with saving the time/space "correctly". i don't know if this is the correct way to do this but here is my first step into the problem. https://github.com/protomielino/sdExps/tree/frankenstime [*] it seems to me that the (easily solvable) memory issues of saving a proper telemetry are far surpassed by the benefits of being able to index the correct time. i forgot to translate the comments, but they're easily figureoutable (is that a word?). [*]didn't want to risk creating problems...

as side, unrelated note: while rummaging torcs, i had the feeling that it has better damage scaling, i have absolutely no experience in driving cars over the city's speed limits, but i think that car accidents have greater consequences than those in speeddreams. in torcs feels... righter. or maybe it's just a gameplay decision.

Hello everyone, my mouse buttons "bounce". Long story short, they "double-click" on they're own. I would say on average 75% of the times. It makes it difficult to use manual shifting, as you can imagine (left-up, right-down). To (almost) solve this problem I've made a little change in src/libs/robottools/rthumandriver.cpp. I've added a 50ms pause to wait for the micro-switches to settle: /* Up shifting command */ if ((cmd[CMD_UP_SHFT].type == GFCTRL_TYPE_JOY_BUT && joyInfo->edgeup[cmd[CMD_UP_SHFT].val])...

Thank you. The changes I've made don't feed back into the simulation, as far as I can tell. Only some "quality of life" adjustments. About the (great) lap time, I'm just waiting for you guys to crush my spirit once again... About the computer's specs, I should have added a disclaimer. This computer is extremely limited in resources: AMD phenom II, less than 2 gigabytes of RAM, graphics card AMD RS780, the hard drive is slightly newer than this one). The above video shouldn't be taken as reference...

Thank you. The changes I've made don't feed back into the simulation, as far as I can tell. Only some "quality of life" adjustments. About the (great) lap time, I'm just waiting for you guys to crush my spirit once again... About the computer's specs, I should have added a disclaimer. This computer is extremely limited in resources: AMD phenom II, less than 2 gigabytes of RAM, graphics card AMD RS780, the hard drive is slightly newer than this one). The above video shouldn't be taken as reference...