aceviper

First option is folder containing second correct option. And liveries are arranged into aircraft name.....otherwise they wont show in game. Last 4 options are the official installation. Best practice is to use savedgames...windows prefers it that way. In saying that I have liveries in the coremods (bottom)option. Some skin makers have made it their preferable way. Check install instructions. If you have to reinstall DCS those will not come back. In a clean-up command situation you will have the option to remove or keep all non official files including skins. Best practice is to keep your install clean and official.

Second option for official paid module skins...third option for unofficial mod skins.

I quite like the earlier bluish version...Im going to hold onto those too

Looks good so far...but need to test in different lighting conditions in-game.

https://www.digitalcombatsimulator.com/en/files/3345896/ Try this fantastic mod....but single player only. It breaks integrity check. In all honesty a vast improvement to the in-game ones. Makes night flying much more enjoyable. Hopefully ED add a version of this to the sim in the future.

Have not seen DCS fill 64gb yet...but who knows in the future. You should be good for a few more years with 64gb.

Better ground clutter like on Afghanistan map would be appreciated too. And I dont mind paying for the update.

Anyone else getting briefing stuck in middle of screen on mission 2?

Yeah?........like some guy pointlessly commenting on a new guy mistakenly replying a 20 year old thread. Them guys?

Looks like the authors google drive is acting up and I cant download the skins. But if you already have the skins follow the instructions carefully in the pdf. Edit...no issues my end. Its just a skin if you have the uh60 mod installed.

Post the link to the texture(skin)

It's time for ED to hard lock some options depending on hardware.

Start trackir before DCS. Rescan devices in settings if it doesnt hook up.

Still works Chris666 I use a mod manager...JSGME.

I have seen this last couple of months. Using a firewall in interactive mode and denying a connection after initial login seems to trigger it. Kicking your session to offline mode seems to be the obvious solution.