We could have released it last week but some other work got in the way. I have reserved Tuesday this upcoming week to get the loose ends together for release.
Did you guys sort out that resonance (grit) reported by few testers?
that is one of the remaining items to analyze before release.
I tried the new one 2024.3 (ACC and LMU) but feeling is not so reactive and it is somewhat lacking in details with dead zone in the center. I specify that I did not use any filter. With reconstruction filter “off” or 1 as recommended is very noisy and sand feel and the car seems to have wooden wheels without rubber. Anyway it’s not to my liking and reverting to the old one.
Hello everyone
I can’t see in which tab this setting is mentioned. Could you please tell me?
“The last tab in True Drive will indicate HighDataRateFFB when the mode is active”
Sounds similar to this issue.
I remember getting cursed for the statement that even with reconstruction filter off it’s pretty good to drive.
Now, recon off is not heresy but
a recommended setting.
Default profile setting doesn’t work for me now more. It’s impossible to get it work. Even activating another profile, then going back doesn’t work.
The experimental filter: I apply a value, close, and then have to rely on you telling me it’s working and it’s applied. Because the next time I open the setting it’s at zero again. Without an indicator (active, not active) it’s a total “guess/maybe” situation. IF it is something you think it’s a good thing, why make it not “on/off”, not providing the value active at the moment? Rather than “believe me, it’s on”, and “it’s so good that we didn’t make it a permanent choice. We let you set it over and over again”.
The “high ffb data rate FFB” isn’t clear to me neither. Is it for Iracing only, or for other games aswell? Where/when/why does it show up, and how should we determine what a high rate is, and what not? Should it be on or not, or is it broken, or deprecated
What exactly is “Constantforce Damping”? I have it activated in the debug information, in the info tab, although I don’t have any damping applied.
Is that information from @Mika , that all slew rate above 1.5Nm isn’t helpful in simracing an obsolete statement now? Like “recon off is as stupid as it can get” is obsolete?
The latest TD release delivers a very different sensation: weaker, less precise, spongy.
Not recommended, but worth to test. And only with iRacing 360 Hz feedback which is not released by iRacing yet.
What is “default profile setting”? I don’t understand your report.
Experimental settings are meant for testing. Probably if you don’t get the idea on what to test, you shouldn’t do the testing.
Only for iRacing. No other games have such low FFB update rate otherwise.
When the mode is ON, it will appear in the firmware status bits:
iRacing enables it automatically.
iRacing controls the torque to the wheelbase via Directinput’s ConstantForce effect. It also always creates a Damping effect, but does not use it in any way.
No, recon off is not the new recommended setting. It may be worth to try because I feel that reconstruction filter at 1 is a bit too “rubbery” feeling to me right now when I drive with the iRacing 360 Hz mode, and we need to gather feedback and re-tune the filter / release reconstruction filter v2 that would be the best option.
Probably placebo as there are no other FFB related changes to firmware. It is impossible for the firmware to feel different from release to release when no code changes have been made.
Paddock, profile, use profile xy as default: it doesn’t accept the setting no more. When I push “set as default” it isn’t marked as default.
Constant damping: it’s active although I don’t have Iracing.
Shouldn’t test: all I say is it’s not clear for the user that it’s really active. Even something experimental should give an indicator of beeing activated or not.
Or: ESPECIALLY something experimental and new should let the user know that it’s working, that it’s actually active. Alternatively you can implement a box labelled: Guess, it’s on or off.
I cannot reproduce this issue. It is working at my end - set as default is greyed out after pressing it.
AC and ACC also create those effects.
It is perhaps not the most obvious thing to test as the effect only starts to reduce torque once the wheel has been turned quite a lot.
Hello,
I don’t understand how some of you can play with the rebuild filter set to 0. For me, in AC - ACC - LMU games, it’s absolutely impossible, the simucube 2 pro becomes super noisy and sounds like the wheels are made of metal.
You still haven’t decided to release a version of True Drive to read the FFB using game telemetry? even beta at first.
Doesn’t creating FFB effects based on telemetry increase latency too much?
I always use recon at 1. Setting it to 0 indeed gives a bit more detail but it is absolutely intolerable in terms of noise. Going above 1 the wheel becomes smoother but also sluggish for my taste.
Even with Irffb and vjoy etc. there wasn’t any noticeable latency. So doing this at a firmware level i wouldn’t expect any latency at all.
Hi. I use offline profiles and an old profile I already deleted keeps getting loaded by true drive.
Are there cached files I need to clear or something?
Maybe there is an issue now - I tried to fix a bug that deleted profile when only the letter case of the profile name was changed but its not all out of the question that there is some other bug.
Have you made another one a default profile after deleting the old one? I did this just couple of weeks ago and it worked.
Yeah, it may be that a profile that is in the device set as a default profile is loaded but that file does not actually exist on the PC anymore. One thing that is very difficult to implement into offline mode.
I misunderstood the issue. I made a cached paddock profile the default, then deleted it and made another offline profile the default. Since the original still existed in paddock I guess it kept loading it instead of the new profile that I tried to set as default, even though ‘use offline mode by default’ option was checked. After I deleted the paddock version the right profile was loaded up on startup.