Unit TreadMarks sometimes defective

speed2

Try clearing the shader cache

Nomander

Unfortunately I haven't been able to replicate it but I've seen it happen to the Viper (cybran MML, like in your pic) and the Fatboy. It started happening after the latest patch (3829). I don't remember any reports of it happening to any other units.

The shader cache gets cleared on every game startup, so that shouldn't be the issue.

zhanghm18

I recently encountered this issue as well. I found that this problem only occurs with the tracks that appear in the "second type" of game. If I replace all the tracks with the same type, there is no such issue.

Jip

This issue has been happening for years now, although I only noticed it on the Fatboy. It happens when the game is overwhelming the feature as far as I am aware. Not sure what triggers it exactly.

Saver

Thank you for your answer.

@jip I hope my hardware isn't overloaded by SupCom ^^. I did upgrade recently. (CPU: AMD Ryzen 7 9800X3D 8-Core Processor (4.70 GHz) / GPU: Nvidia GeForce RTX 5080 / RAM: 64 GB/6000MT-s).

@speed2 I'm always slow on the uptake. Could you explain your response a little more clearly? You wrote that I should clear the shader cache, but unfortunately I don't know where to do that. Unfortunately, I couldn't find any shaders in the ProgramData\FAForever\cache folder.

@zhanghm18 What exactly do you mean?

I'll try to find a test that can be reproduced to get to the bottom of the problem.

Saver

I was probably a little lucky with the first test and was able to reproduce the error right away.

What did I do? I ran a standard game with the basic AI in observation mode. I did NOT create the units using cheats, but let them be created automatically.

Only after the regular creation did I use cheats to test all land units with chain drive.

As can be seen in the image, three units are affected by the error.

I therefore looked at the blueprints of the units. They all use the same TreadMarks = “tank_treads06_albedo”.

Fatboy

Viper

Trebuchet

I would now try to rename this specific albedo in my mod and run another test. Let's see what happens ^^ I hope I can reproduce it again, at least.

Saver

I have now run 10 test games, as described in my last post.

I ran 5 games without mods and 5 with mods. However, I was not able to reproduce the error 100%. It did occur in 80% of the games, though.

Incidentally, a new image was created that shows how various albedo files are mixed in the error.

This track does not belong to the unit in any way.

Okay, so what did I do as a counter-test? I simply referenced a new albedo in my mod. And I was unable to reproduce the error in five further tests. I now have to readjust the track, but the error is clearly in the core game.

However, I couldn't find any errors in the logs. Maybe the file, the affected albedo (“tank_treads06_albedo”), should be renamed to solve the problem.

Saver

I have now changed the modified Albedo files in the units and initially integrated them into my unit mod. At least I couldn't find any more errors in the last test.

This variant at least solves the problem for everyone who uses the mod. Unfortunately, I cannot offer a general solution. But maybe it will help to find a real solution to the error. Here are a few pictures, although the difference should not be too noticeable.

Viper:
TreadMarks = {
{
TreadMarks = "tank_treads03_albedo",
TreadMarksInterval = 0.2,
TreadMarksSizeX = 0.3,
TreadMarksSizeZ = 2,
TreadOffset = { 0.3, 0, -0.2 },
},
{
TreadMarks = "tank_treads03_albedo",
TreadMarksInterval = 0.2,
TreadMarksSizeX = 0.3,
TreadMarksSizeZ = 2,
TreadOffset = { -0.3, 0, -0.2 },
},

Trebuchet
TreadMarks = {
{
TreadMarks = "tank_treads03_albedo",
TreadMarksInterval = 0.2,
TreadMarksSizeX = 0.3,
TreadMarksSizeZ = 2,
TreadOffset = { 0.5, 0, -0.3 },
},
{
TreadMarks = "tank_treads03_albedo",
TreadMarksInterval = 0.2,
TreadMarksSizeX = 0.3,
TreadMarksSizeZ = 2,
TreadOffset = { -0.5, 0, -0.3 },
},

If there is a better solution, I would appreciate some information.

That's all from me for now

Nuggets

Btw, i do not know what happened but this is now happening every single game.

Saver

@Nuggets Perhaps adjusting the markers for mass and energy deposits caused the error

If I understood correctly, these were improved in one of the latest FAF updates, but caused this error. However, I haven't looked into the problem enough.