Artifacts on the Velikie Luki winter map in the FMB

[DarkWolf29]

Is anyone else seeing these odd square patches on the Velikie Lukie winter map when viewed in the FMB?

 

 

Seems to affect a handful of the airfields and rail yards. In game it looks fine.

 

Anyone know of a fix?

 

DW

[JimTM]

All OK with my FMB. Does it happen when you create a new Velikie Luki mission?

 

You could try resetting your editor (run ResetEditorSettings.cmd in your game folder under /bin/editor).

[AEthelraedUnraed]

Do you have Mods Off? If so, your local SurfaceTex.txt file is likely bugged. Did you attempt to edit it? Otherwise, just delete the file (data\graphics\LANDSCAPE_Velikie_Luki\SurfaceTex.txt - I'm writing this from memory so the exact spelling may slightly differ).

Edited December 19, 2022 by AEthelraedUnraed

[DarkWolf29]

That screenshot was taken with a newly created mission. I tried resetting the editor and also verifying the game files (its a Steam install) and updating my video card driver but the issue persisted.

 

I do not use mods nor have I edited the SurfaceTex.txt. Removing the SurfaceTex.txt from the folder did not fix the problem but it caused a change in the solid white rectangles, giving them some blue and purple streaks. So I tried removing the other file in that folder as well, Surface.dat. Removing both files seems to have fixed it, I no longer see the artifacts in the FMB. I tried returning just the SurfaceTex.txt to the folder but again it caused some artifacts.

 

My question now is, are these files needed? I re-verified my game and launched it a couple times after removing these two files and they were not re-downloaded or replaced. Are they leftovers from some previous build? Will I have some other graphical issue without them?

 

DW

[JimTM]

5 hours ago, DarkWolf29 said:

...

My question now is, are these files needed? I re-verified my game and launched it a couple times after removing these two files and they were not re-downloaded or replaced. Are they leftovers from some previous build? Will I have some other graphical issue without them?

...

 

I don't have these files in my copy of BoX, which I installed (v4.605 I believe) fresh on a new system in November of 2021. So, perhaps the files are leftovers from a previous build, as you mentioned.

Edited December 20, 2022 by JimTM

[DarkWolf29]

Thats interesting, it could well be the case as I think my copy was originally installed in November of 2018. Perhaps a fresh install is in order.

 

DW

[AEthelraedUnraed]

On 12/19/2022 at 9:56 PM, DarkWolf29 said:

I do not use mods nor have I edited the SurfaceTex.txt. Removing the SurfaceTex.txt from the folder did not fix the problem but it caused a change in the solid white rectangles, giving them some blue and purple streaks. So I tried removing the other file in that folder as well, Surface.dat. Removing both files seems to have fixed it, I no longer see the artifacts in the FMB. I tried returning just the SurfaceTex.txt to the folder but again it caused some artifacts.

Yes, you need to delete both files. My bad. The fact that you use the Mods Off setting is the reason they don't appear in game (see below).

 

On 12/19/2022 at 9:56 PM, DarkWolf29 said:

My question now is, are these files needed? I re-verified my game and launched it a couple times after removing these two files and they were not re-downloaded or replaced. Are they leftovers from some previous build? Will I have some other graphical issue without them?

They're not needed. Basically, the game loads (almost) every file from the several .gtp files inside the data directory, unless there's an identically named file in the "normal" directories and you've got Mods On (hence the reason you didn't see it in-game - the mission editor doesn't check for the Mods On setting). By deleting the surface files, you're simply ensuring that the game loads Surface.dat and SurfaceTex.txt from the .gtp files. Deleting them will not cause any graphical issues whatsoever.

 

They're not leftovers from some previous build, but I've seen them suddenly appear before. I don't know exactly what causes it, but I think it relates to the mission editor. For some reason or another, those files got bugged in your case.

[DarkWolf29]

Ok good to know, thank you for the help and explanation.

 

DW