Since I upgraded to Test Patch S2V4 (from S2V) I have been experiencing weird pedal automatic-recalibration issues on my break pedal.
Equipment:
- Logitech DFP wheel with latest Logitech drivers.
- ECCI 6000 pedals
Symptoms:
- After a few minutes the pedal invertion magically swaps so that I have to go into the Options and deselect Invert on the break pedal. Once the invertion has swapped it seems to stabilise and stay in the opposite pedal calibration until I next start the game. Upon starting the game the pedal works fine and then the invertion swaps again magically in the background.
- Sometime after the invertion issue the break pedal will just automatically recalibrate itself. The result of this is usually that the pedal "bars" ( the things showing the amount of pedal application) show about 30% pedal applied when the actual pedal is released. One press and release of the break pedal then takes that to around 50-60%~ish. A 2nd press and release of the break pedal then seems to get the calibration back in so that upon release it is back set to 0% again and I can resume lapping as usual.
This is definitely new since I applied the test patch V4 (I did not apply test patches V2 or V3).
Has anyone else seen this at all?
Equipment:
- Logitech DFP wheel with latest Logitech drivers.
- ECCI 6000 pedals
Symptoms:
- After a few minutes the pedal invertion magically swaps so that I have to go into the Options and deselect Invert on the break pedal. Once the invertion has swapped it seems to stabilise and stay in the opposite pedal calibration until I next start the game. Upon starting the game the pedal works fine and then the invertion swaps again magically in the background.
- Sometime after the invertion issue the break pedal will just automatically recalibrate itself. The result of this is usually that the pedal "bars" ( the things showing the amount of pedal application) show about 30% pedal applied when the actual pedal is released. One press and release of the break pedal then takes that to around 50-60%~ish. A 2nd press and release of the break pedal then seems to get the calibration back in so that upon release it is back set to 0% again and I can resume lapping as usual.
This is definitely new since I applied the test patch V4 (I did not apply test patches V2 or V3).
Has anyone else seen this at all?
Pedal Bounce & Calibration
Guys,
I am not sure if this is a bug or not, but am interested if anyone else is seeing this.
In recent times I have been experiencing a decalibration issue with my brake pedal. My hardware is the Logitech DFP, with the latest drivers, using the ECCI6000 pedals. It has been stable, no issues, for almost 12 months. This is a recent issue.
What appears to be occuring is that if I release the pedal in such away as it does not stop moving smoothly, that is the physical movement of the pedal itself, resulting in a bounce in the pedal as it gets to 0%, the calibration for the brake pedal is lost slightly, resulting in about 5% application of the brake within the game.
If I then recalibrate within the game it is fine until the next time the bedal bounces upon being released.
Is anyone else seeing a decalibration issue as they release a pedal, possibly when the pedal bounces?
What else, Scawen, should I be looking at to see if it is an issue within the game?
What I have done so far is:
- Check all pots. All working fine.
- Check all drivers (confirmed as no change in many, many months).
- Adjusted brake pedal characteristics within Logitech driver, reduced sensitivity, increased dead zone, etc... No fix achieved.
I am not sure if this is a bug or not, but am interested if anyone else is seeing this.
In recent times I have been experiencing a decalibration issue with my brake pedal. My hardware is the Logitech DFP, with the latest drivers, using the ECCI6000 pedals. It has been stable, no issues, for almost 12 months. This is a recent issue.
What appears to be occuring is that if I release the pedal in such away as it does not stop moving smoothly, that is the physical movement of the pedal itself, resulting in a bounce in the pedal as it gets to 0%, the calibration for the brake pedal is lost slightly, resulting in about 5% application of the brake within the game.
If I then recalibrate within the game it is fine until the next time the bedal bounces upon being released.
Is anyone else seeing a decalibration issue as they release a pedal, possibly when the pedal bounces?
What else, Scawen, should I be looking at to see if it is an issue within the game?
What I have done so far is:
- Check all pots. All working fine.
- Check all drivers (confirmed as no change in many, many months).
- Adjusted brake pedal characteristics within Logitech driver, reduced sensitivity, increased dead zone, etc... No fix achieved.
Scawen, I was just wondering if you use a version control tool (like CVS, or RCS) at all, and if this change control tool can generate email messages containing something like "file blah.c just got updated with comment: foobar".
If so, could a mail-list be created that such update messages go to, like they do in open-source software development projects? That way people can subscribe, or even just watch an archive, to see that stuff is going on, and even get an idea of the type of stuff that is going on. It doesn't have to provide any access to the code itself, only show that a file has been updated with a comment when it is submitted to the version control system that may hint as to what changes were made.
Is this viable, or do you think it would create more panicked chatter than worth the hassle?
If so, could a mail-list be created that such update messages go to, like they do in open-source software development projects? That way people can subscribe, or even just watch an archive, to see that stuff is going on, and even get an idea of the type of stuff that is going on. It doesn't have to provide any access to the code itself, only show that a file has been updated with a comment when it is submitted to the version control system that may hint as to what changes were made.
Is this viable, or do you think it would create more panicked chatter than worth the hassle?
It certainly puts the last modified setup at the top of the list, but this is common across all tracks. So if you modify a car on as2r and then load the same car on so1, the car last modified on as2r will appear at the top of the list for so1.
Last used and Fastest setups
A feature that occured to me today that might be useful is if when you are in the Setup window for a car the last used and fastest laping saved setups were flagged in some way.
What I mean is that the local copy of LFS keeps two little matrices of data. Matrix 1 is lastUsedSetup and records a matrix of Cars Vs Tracks and in the data cell it stores the setup name used last. Then when you load a track and select a car it (perhaps) places an "L-" beside the setup name for the last one used on this track for this car.
Similar for the fastest lap time. A data matrix is created, perhaps called PBSetup, that records a matrix of Cars Vs Tracks and in the data cell it stores the setup that last set a PB for that car/track combination. Then when you load a track and select a car it (perhaps) places an "PB-" beside the setup for the last car to achieve a PB on this track with this car.
This would be great in situations where you have and are working with multiple car setups across multiple tracks and need an easy way to pick up where you last left off or if your just going to race to easily pick which car is giving you the best lap times.
Thoughts?
(Appologies if this has already been suggested.)
What I mean is that the local copy of LFS keeps two little matrices of data. Matrix 1 is lastUsedSetup and records a matrix of Cars Vs Tracks and in the data cell it stores the setup name used last. Then when you load a track and select a car it (perhaps) places an "L-" beside the setup name for the last one used on this track for this car.
Similar for the fastest lap time. A data matrix is created, perhaps called PBSetup, that records a matrix of Cars Vs Tracks and in the data cell it stores the setup that last set a PB for that car/track combination. Then when you load a track and select a car it (perhaps) places an "PB-" beside the setup for the last car to achieve a PB on this track with this car.
This would be great in situations where you have and are working with multiple car setups across multiple tracks and need an easy way to pick up where you last left off or if your just going to race to easily pick which car is giving you the best lap times.
Thoughts?
(Appologies if this has already been suggested.)
RFC: S2-Patch T: BF1 Tyre temperature loss
This is as much for discussion and comment, as my opinions may be wrong.
I was observing the other day, having done a few laps in the BF1 and got some temperature in the tyres, that the tyres loose their heat very, very slowly.
The temperature in the tyre was in the red, up around the 110 degrees mark. When sitting idle they were loosing temperature at about 1 degree every 30-60 seconds.
Now I have distinct recollection that in the real world of F1 drivers often complain because they loose race temperature within 1 lap behind the pace car.
So they are loosing temperature whilst the tyres are still moving (I would assume race temp is more than a 3 degree difference), yet in LFS you would loose at most 3 degrees per lap of BL1.
This can be critical in racing LFS, as if you suffer a wheel spin or a wheel slide you can very quickly overheat your tyres loosing you traction. However the tyre temperature may not come down to a suitable racing level for 6 or more laps, thus meaning a minor incident with relatively little tyre wear can affect you for the next 6 or more laps.
Thoughts?
I was observing the other day, having done a few laps in the BF1 and got some temperature in the tyres, that the tyres loose their heat very, very slowly.
The temperature in the tyre was in the red, up around the 110 degrees mark. When sitting idle they were loosing temperature at about 1 degree every 30-60 seconds.
Now I have distinct recollection that in the real world of F1 drivers often complain because they loose race temperature within 1 lap behind the pace car.
So they are loosing temperature whilst the tyres are still moving (I would assume race temp is more than a 3 degree difference), yet in LFS you would loose at most 3 degrees per lap of BL1.
This can be critical in racing LFS, as if you suffer a wheel spin or a wheel slide you can very quickly overheat your tyres loosing you traction. However the tyre temperature may not come down to a suitable racing level for 6 or more laps, thus meaning a minor incident with relatively little tyre wear can affect you for the next 6 or more laps.
Thoughts?
Just to stick in my 2 cents...
STFU and drive :: Live for Speed
STFU and drive :: Live for Speed
FGED GREDG RDFGDR GSFDG