tmpid.dll important to all thrustmaster users, i got a t500

Hi

I've updated to the new drivers recently and found something was off.[/QUOTE]
i found a tmpid.dll error in the windows log files.
it caused me serious headache allready , im back on the 2017 drivers now.
i dont get no error's or crashes, u can only find out goin to the windows log files.
now i want to know the best setup cause i had it with this ****.
i got windows 10-64bit (1909)
dynamic damping (100%), minimum ffb (1) , controlpanel settings 60-100-100-0-100 -900°turn
im running on an aluminium rig, and at thrustmaster support site also found out if u got static electricty u should ground (earth) the whole frame.

but i think the ffb levels differs from time to time.
so know i want get it stable
all help is welcome

below u can find a link how i found out about the tmpid.dll issue and that allready was there before the 2020 driver update (i gues but i still need to look into this).
since im in lockdown i got time now..
:)


greetings

Bram Goossens


https://www.assettocorsa.net/forum/...oblem-computer-management-event-viewer.49405/

**i found this in the link above , important 4 all thrustmaster users , the 2020 driver has a tmpid issue with windows 10**

The description for Event ID 0 from source tmpid cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event:

CDIEffectDriver::~CDIEffectDriver() will call CoUninitialize() proc:C:\Steam\steamapps\common\Assetto Corsa Competizione\AC2\Binaries\Win64\AC2-Win64-Shipping.exe

The specified resource type cannot be found in the image file

[/QUOTE]
Attached Files:
 
Last edited:
Hello,
the link you found on the official forum shows an identical problem on AC 1 not ACC.
ACC and AC do not share the same construction at all.
I also own a T500rs and I have no problems, I even find the FFB excellent.
TM panel: 60/100/100/00/00
in game: according to your preferences, 333Htz
remember to go to:
Documents / assetto corsa competizione / config /control json and added this line at the bottom of the page:
"forceFeedbackIntervalSteps": 0
If it does not exist !!
 
Last edited:
Hello,
the link you found on the official forum shows an identical problem on AC 1 not ACC.
ACC and AC do not share the same construction at all.
I also own a T500rs and I have no problems, I even find the FFB excellent.
TM panel: 60/100/100/00/00
in game: according to your preferences, 333Htz
remember to go to:
Documents / assetto corsa competizione / config /control json and added this line at the bottom of the page:
"forceFeedbackIntervalSteps": 0
If it does not exist !!

Thx 4 the answer i will try

i just did a check on usb drivers etc
yesterday i tryed the TM 2017 driver and the error was gone
now i got TM2019 running and its back :)
what TM driver are u running?

would u be so nice and take a lap in acc and look at
computer management/event viewer/windows logs/application
if u see any error about tmpid ??

but i must say the FFB is idd not 2 bad,
but i think it could be better/stronger/more consistent

im goin to test if i feel any difference with the 2017 driver, but i need a break :)

greets

** "forceFeedbackIntervalSteps": 0 ** was allready there ;)
 

Attachments

  • tmpid.jpg
    tmpid.jpg
    171.5 KB · Views: 376
Last edited:
Hi,
I looked in the management of the computer and I have the same information messages.
I do not know what they correspond to but they appear in informative qualities so it is not something critical.
I had never paid attention to this before, but in any case they do not disturb the FFB in any way.
Je vous conseille de faire avec et de peaufiner vos réglages jusqu'à ce que vous trouviez le FFB qui vous convient le mieux.
I have the 1TTRS 2020 pilots and it is a pleasure.;)
Antonn.
Edit: installing and uninstalling drivers may leave traces, this may be the reason why you could not install the latest drivers.
use a cleaner.
 

Attachments

  • Capture d’écran (23).png
    Capture d’écran (23).png
    238.1 KB · Views: 227
Last edited:
Back
Top