MrJonton01 [GER]

Please reinstall and check, if the selected path for ETS2 is correct, because it seems like the launcher is pointing to a wrong path with an outdated version of ETS2.

It's just, that TruckersMP in general get's updated. It's just the multiplayer system.

Normally they should unban you. If you did appeal, try writing back saying that you are still banned.

How about completely reinstalling Steam?

Currently it's not supported, but I hope it'll come with the 1.32 update

Did you try restarting Steam and your computer?

Did you try reinstalling your drivers completely? Did you try to turn some graphics ootions down?

Anything that's possible without using any mods, if that's what you mean. There is the option of save-editing, too, but you have to keep a look at the rules regarding it: https://truckersmp.com/rules

World of Trucks is only compatible with 1.32, but Multiplayer isn't. That's why you won't be able to play WoT in Multiplayer at the moment.

Yes, Multiplayer will be updated. You will be able to play WoT in Multiplayer, when the Multiplayer is completely updated. You just have to wait ^^

What do you mean with permanent? If you want to play Multiplayer and WoT with 1.32, you will have to wait, because Multiplayer is not updated yet

Try relogging, or go to your Account Settings here in the forum. If there is a Change button next to your displayname, then change it there.

Gebannt, da du der letzte warst, der den noch (halb) lebenden Thread gesehen hast

Try the save, or use an older one from 1.31, because some things from 1.32 won't be compatible with 1.31

Have you tried verifying the game files via Steam?

No. https://truckersmp.com/rules At 3.3 it says that truck parts in cars and vise-versa are not allowed, that means you only can save-edit car parts into the Scout.

Similar for me. Mine worked until 3 or 4 months ago. You probably have to use some other software for assigning keys at the moment. But I would still suggest you contacting the Logitech support to report the problem.

That's what I suspected. I have this problem too and I just can't find a solution for it. It's either a SCS Bug (Because the same happens in ATS), or a Logitech Bug, probably in the software. I think there is no other way than getting in contact with the Logitech support, because this is definitely not a TruckersMP issue and isn't only happening in ETS2.

When you are in-game and the button/makro doesn't work, and you tab out of the game, does the X get written into Notepad? You also can try it with the profile testing feature in LGS. When you exit the game, does the makro still work?

Is the key mapping in the Controls settings correct?

Does the clutch work? You can check it in the Controller settings, there you should be able to see if all pedals work.

You need to use temporary_1.31. After selecting it, let Steam automatically update the game. Then ETS2 should be sucessfully downgraded.

I would suggest the following: Do it the same as TMP currently handles not having the headlights turned on at a certain time. When you enter an area with 25+ players and you have your beacons enabled, you first get a normal warning message to turn off your beacons. After, let's say 5 seconds, you have 10 or 15 seconds left, to turn them off. If you don't do it on time, you get kicked. Additionally I would suggest to add generally add messages (and maybe not just in chat, so it's more obvious), that warn you, when you are getting into a 25+ player zone or leaving one. That's way it would be better for players to act better. I think on PCs & Laptops that (not even) meet the minimum hardware requirements of the game, this is a problem. You have to keep in mind that every single beacon and LED strobe creates it's own (moving) field of illumination, resulting in reflections, etc. That stacks up and requires processing power, that those Low-End-PCs & Laptops need.

In what region are you driving? Because in scandinavia double trailers are allowed and you can get them normally there.

Please tell us the context of this error by showing more screenshots or a description of what you did to get this error.