<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>MO2 Reference :: Mad God's Overhaul for Skyrim VR</title><link>https://daveystrus.com/mgo-tutorial/mo2-reference/index.html</link><description>Want to venture deeper into the murky underworld of Mod Organizer 2? Read on!</description><generator>Hugo</generator><language>en-us</language><atom:link href="https://daveystrus.com/mgo-tutorial/mo2-reference/index.xml" rel="self" type="application/rss+xml"/><item><title>MO2 Overwrite</title><link>https://daveystrus.com/mgo-tutorial/mo2-reference/overwrite/index.html</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://daveystrus.com/mgo-tutorial/mo2-reference/overwrite/index.html</guid><description>At the bottom of the list on the left side of Mod Organizer, you’ll see an entry labeled Overwrite. It may appear grayed-out when you first install MGO, but once you’ve played it should be either white-on-orange, or red-on-gray.
Overwrite is there to catch any data that’s written to disk during program execution. For example, the first time you run MGO, Community Shaders will write compiled shaders to Overwrite .
Overwrite appears at the bottom of the list on the left side of Mod Organizer 2. What and why? MO2 uses a virtual file system (VFS) to keep your Skyrim VR installation folder pristine. Every program you run using the Run button in MO2, whether it’s the game itself or one of the other included tools, will run from this VFS. These programs sometimes need to write files to disk, and when they do, they get written to the VFS. When the program finishes running, and the VFS is unmounted, those files would be lost if not for the Overwrite folder.</description></item></channel></rss>