shifting gears

[alex25]

is shifting gears really working with the latest revision? i've tried it only with F1-02 but i don't see any drop in the rpm when i shift gears, the car doesn't seem to go faster than about 130 mph (except when the speedometer goes crazy and tells me i am going at thousands of miles per hour even though i am almost standing still), i can re-start the engine in any gear (which kind of makes me believe i am always in first gear). also (again with F1-02) traction control doesn't seem to work either. is anybody else seeing this?

--alex--

[alex25]

nevermind, just removed my .vdrift directory and reassigned the controls and now shifting gears seems to work properly. traction control still doesn't really seem to work though.

and following up on this. it works only if autoclutch and autotrans are set to true. if i set them to false then gear shifting doesn't seem to have any effect. i'm sure now this is a bug in the new code somewhere.

--alex--

[joevenzon]

Hmm, with autoclutch off then the clutch is by default always disengaged (if no control is assigned to the clutch). Pre-refactor it was by default always engaged. I'm not sure which one makes more sense. Do you think this could be the root of the problem you're seeing?

[joevenzon]

Also, are you on a 64-bit system? thelusiv noted some odd bugs when he tried running the refactored code on his 64-bit system.

[alex25]

Also, are you on a 64-bit system? thelusiv noted some odd bugs when he tried running the refactored code on his 64-bit system.

yes, i am on a 64-bit system (linux running debian unstable).

--alex--

[joevenzon]

Okay, that's got to be the problem. I've got it in the issue tracker as #99:
http://code.google.com/p/vdrift/issues/detail?id=99

I doubt I'll be able to figure this out without getting a 64-bit system myself (I have a 64-bit CPU but am running a 32-bit linux distro at the moment). Where's that spare hard drive....

[alex25]

more oddities: in the assign transmission controls menu the engage clutch button doesn't work. the error message seems to be:

ERROR: Input named engage couldn't be assigned because it isn't used

i have mouse button 1 assigned to shift up and button 3 to shift down. previously i had both buttons assigned to engage clutch but now it doesn't work. could this be the problem?

--alex--

[joevenzon]

The refactor doesn't use the engage clutch control anymore (I'll remove it from the menu pretty soon). Once you assign the buttons to shift up and shift down everything should work.

[alex25]

The refactor doesn't use the engage clutch control anymore (I'll remove it from the menu pretty soon). Once you assign the buttons to shift up and shift down everything should work.

shifting gears works only if i enable auto clutch. without auto clutch i seem to be stuck in first gear even though the screen would seem to indicate i shift gears. hope this helps.

--alex--

[joevenzon]

without auto clutch i seem to be stuck in first gear even though the screen would seem to indicate i shift gears

Well, when you turn off autoclutch, do you have a pedal or joystick axis or something assigned to the clutch control? If not, and if you have autoclutch off, then you don't have any way to engage the clutch. So the behavior you described sounds correct. Pre-refactor you could turn off autoclutch and the game would still work the clutch for you, which I think was a bug.

[alex25]

Well, when you turn off autoclutch, do you have a pedal or joystick axis or something assigned to the clutch control? If not, and if you have autoclutch off, then you don't have any way to engage the clutch. So the behavior you described sounds correct. Pre-refactor you could turn off autoclutch and the game would still work the clutch for you, which I think was a bug.

no, i don't have anything. the way i understand it, this is what the engage button used to do before. that's why i had button 1 and 3 assigned to engage so as i shifted gears it also engaged. i guess in the refactor you got rid of engage and now you have to use autoclutch.

so, maybe you should bring back the engage button but maybe autoclutch will do, i guess.

--alex--

[joevenzon]

I was thinking about this more and you're right, the refactor behavior is a little weird. I opened issue 108 to address it:
http://code.google.com/p/vdrift/issues/detail?id=108