Jump to content

Recommended Posts

Posted

Subject says it all. I got fix dig out the file for the blue cockpit mod to KA-50 and a bunch of the other mods I did (load screen/minimal ID's/skins...). I mean really-the updates have to wipe out everything with cockpit color. One time all my missions with modded skins were altered-nothing but yellow/orange KA-50's.

I'm sure this update screwed up other modules to. :mad:

Posted

The updater cleans all mods out and puts them in a backup folder inside the main DCS folder.

 

It's the way it has to be.

 

I recommend that you manage mods with a mod installer and before running an update back them all out.

Posted

The updater could not possibly work correctly if it did not remove mods.

ASUS ROG Maximus VIII Hero, i7-6700K, Noctua NH-D14 Cooler, Crucial 32GB DDR4 2133, Samsung 950 Pro NVMe 256GB, Samsung EVO 250GB & 500GB SSD, 2TB Caviar Black, Zotac GTX 1080 AMP! Extreme 8GB, Corsair HX1000i, Phillips BDM4065UC 40" 4k monitor, VX2258 TouchScreen, TIR 5 w/ProClip, TM Warthog, VKB Gladiator Pro, Saitek X56, et. al., MFG Crosswind Pedals #1199, VolairSim Pit, Rift CV1 :thumbup:

Posted

Thanks for getting back. I see what your saying.

 

Just ran Mi-8 and have to change some skins.

I have too many mods and tweaks in DCS World.:joystick:

Posted

Try using JSGME to disable mods, update, then enable mods again. Simple.

Windows 10 Home, Intel Core i7-9700K @ 4.6GHz, Gigabyte GTX 1070 G1 Gaming (8GB VRAM) on 34" LG curved monitor @ 3440x1440, 32GB RAM, TrackIR 3 (with Vector Expansion), Thrustmaster Warthog HOTAS, Saitek Combat Pedals, Thrustmaster Cougar MFDs.

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...