FREEMλN Posted Wednesday at 05:56 PM Posted Wednesday at 05:56 PM Guys, I'm customizing my cockpit and two texture errors popped up, and no matter what I do, I can't fix them. I've been trying for a week. Pls help me
G.J.S Posted Wednesday at 06:37 PM Posted Wednesday at 06:37 PM Repair DCS function, available in the launcher I believe. - - - The only real mystery in life is just why kamikaze pilots wore helmets? - - -
FREEMλN Posted Wednesday at 06:51 PM Author Posted Wednesday at 06:51 PM I tried this many times but it didnt work
Art-J Posted Wednesday at 07:04 PM Posted Wednesday at 07:04 PM Did you place any of these customized files in Saved Games folder? Repair command doesn't affect that one, so if source of problem is buried somewhere over there, neither repairing nor module reinstall will help. It's easy to check - rename your Saved Games / DCS folder temporarily, launch the game so that a new clean folder is created and see if problem persists. 1 i7 9700K @ stock speed, single GTX1070, 32 gigs of RAM, TH Warthog, MFG Crosswind, Win10.
FREEMλN Posted Wednesday at 07:26 PM Author Posted Wednesday at 07:26 PM I dont think the problem stems from the files but rather from description.lua. I got the texture files from Program Files and .lua from ModelViewer So if the problem is with these files wouldnt the game be broken?
fagulha Posted Wednesday at 07:48 PM Posted Wednesday at 07:48 PM 20 minutes ago, FREEMλN said: I dont think the problem stems from the files but rather from description.lua. I got the texture files from Program Files and .lua from ModelViewer So if the problem is with these files wouldnt the game be broken? Check if this line is in your description.lua if not add:  {"Pilot_F18_FP_Map", 0, "mfd3", true};  Then leave feedback please. About carrier ops: "The younger pilots are still quite capable of holding their heads forward against the forces. The older ones have been doing this too long and know better; sore necks make for poor sleep.'  PC: 14th I7 14700KF 5.6ghz | 64GB RAM DDR5 5200 CL40 XMP | Gigabyte RTX 4080 Super Aero OC 16 GB RAM GDDR6X | Thermalright Notte 360 RGB | PSU Thermaltake Tough Power GF A3 Snow 1050W ATX 3.0 PCIE 5.0 / 1 WD SN770 1TB M.2 NVME + 1 SSD M.2 2TB + 2x SSD SATA 500GB + 1 Samsung 990 PRO 4TB M.2 NVME (DCS only) | Valve Index| Andre“s JeatSeat.
FREEMĪ»N Posted Wednesday at 08:04 PM Author Posted Wednesday at 08:04 PM While going through the files i noticed this code I thought āMaybe this will solve the problemā but for some reason it didn't work i know this code should work but it didnt
Mach3DS Posted 3 hours ago Posted 3 hours ago (edited) On 9/24/2025 at 1:04 PM, FREEMĪ»N said: While going through the files i noticed this code I thought āMaybe this will solve the problemā but for some reason it didn't work i know this code should work but it didnt Are you using someone else's work as a basis for yours?Ā This looks like you took someone's texture set to start from.Ā Including the description.lua which likely contains those elements as custom textures.Ā If so, that's your problem.Ā You have lua callouts for textures you don't have in your folder.Ā I point this one first because it's the easiest thing that could happen. Ā A missing texture is only caused by 3 things: 1.Ā Missing the physical texture file from your folder. 2. Calling out a texture in the lua file with a different name than the one in your folder or the default file. 3. Calling out a texture in the lua that does exist in your folder with a different name than the default file but using the "true" or "false" command incorrectly. Edited 3 hours ago by Mach3DS MACH 3 DESIGN STUDIO Heatblur Rivet Counting Squadā¢
Recommended Posts