<?xml version="1.0"?>
<rss version="2.0"><channel><title>Before installing skyrim 32bit Latest Topics</title><link>https://www.loverslab.com/forum/207-before-installing-skyrim-32bit/</link><description>Before installing skyrim 32bit Latest Topics</description><language>en</language><item><title>READ before doing anything</title><link>https://www.loverslab.com/topic/101906-read-before-doing-anything/</link><description><![CDATA[
<p>
	<strong>really bad news for all have installed Mod Organizer 2.... </strong>
</p>

<p>
	 
</p>

<p>
	this version works NOT well with all external tools like WryeBash, FNIS and Merge Plugins and skyrim32 bit (Legendary Version)...
</p>

<p>
	 
</p>

<p>
	<strong>WryeBash</strong> puts the patch into the game-dir\data... can be tolerated but is not MO-style
</p>

<p>
	<strong>FNIS</strong> (XXL-Version 7.4.5) creates only two dirs (scripts and tools) "meshes" is missing
</p>

<p>
	and worse of all <strong>Merge Plugins</strong> (standalone) is not able to get access to the modlist.txt resulting in missing mods, wrong loadorder. In short, not able to merge something...
</p>

<p>
	 
</p>

<p>
	my guess is, that the new internal VFS of MO2 is messing up with elder (maybe not updated) tools... or simply some references are hardcoded and not easy changable
</p>

<p>
	 
</p>

<p>
	<strong>so it is not recommended to use MO2 with skyrim32 bit</strong> as long, as somebody will find a trusty solution.
</p>

<p>
	 
</p>

<p>
	For <strong>switching back with MO to 1.3x</strong> there is some good news... backup from MO2 the directories "downloads", "mods" and "profiles"... then install MO 1.3x into game-dir\data\ModOrganizer... after this copy the backuped directories inside this new version.... *** be aware, that for version 1.3x you need the update to have access to nexus and downloading again
</p>

<p>
	Now go for the topright pushdown-button and verify the correct locations of all activated tools, correct them, if needed...
</p>

<p>
	 
</p>

<p>
	Done.... verify yourself the changes in the behaviour with the mentioned tools above...
</p>

<p>
	 
</p>

<p>
	test, if you have access to download new files from nexus (otherwise link the nmx.manager again, sometimes this must be done for your browser, too
</p>

<p>
	 
</p>

<p>
	p.s.: with MO 1.3x the handling of BSA is different... we have to ckeck now, if all needed BSA are ckecked after changes (like merging). Keep this in mind
</p>
]]></description><guid isPermaLink="false">101906</guid><pubDate>Wed, 20 Jun 2018 18:09:41 +0000</pubDate></item><item><title>general information</title><link>https://www.loverslab.com/topic/101879-general-information/</link><description><![CDATA[
<p>
	this is a "work"-shop... so feel free to suggest changes, better mods (with the intended feature), report difficulties during install (and workarounds, if possible)... we all will learn and build up a better personal - and hopefully bugfree - skyrim
</p>

<p>
	 
</p>

<p>
	it is NOT about installing the best mods ever, but to see, how they have impact to your installation... so please use your reference-saves to test it (wait time enough for setting up all new scripts, menus -- do your changes inside MCM)... but look for FPS, bugs during gameplay, CTD... no special WryeBash Patch (we will do it after the whole changes)... everytime LOOT, FNIS also... and don't forget your Dyndolod-update
</p>

<p>
	 
</p>

<p>
	and yes, if there is a nice suggestion how to provide better steps/topics for following up the stages, feel free to suggest (and show) it, also... I will try to do it, if it make sense
</p>
]]></description><guid isPermaLink="false">101879</guid><pubDate>Wed, 20 Jun 2018 13:22:17 +0000</pubDate></item><item><title>what we will NOT install for a basic skyrim</title><link>https://www.loverslab.com/topic/101738-what-we-will-not-install-for-a-basic-skyrim/</link><description><![CDATA[
<p>
	steam provides HighRes-textures... but we will not install them (if installed during the steam-installation, we will DELETE them)
</p>

<p>
	 
</p>

<p>
	first, they are worse than other textures, found on Nexus. Second, they are not needed, since we will install USLEEP (and the Highres-Patch is outdated)... and with other textures (having best textures and performance in mind) we will change skyrim to our liking, so the highres-textures will be overwritten, mostly
</p>

<p>
	 
</p>

<p>
	and... just for showing, that it is possible to have a stable, interesting looking and fast skyrim, we will often go for the highest textures, possible
</p>
]]></description><guid isPermaLink="false">101738</guid><pubDate>Mon, 18 Jun 2018 20:40:15 +0000</pubDate></item><item><title>basic preparations to install skyrim 32bit</title><link>https://www.loverslab.com/topic/101735-basic-preparations-to-install-skyrim-32bit/</link><description><![CDATA[
<p>
	to install a stable game it is mandatory, to check your installed OS... virusfree, stable, all needed updates, graphicdrivers... you know the drill
</p>

<p>
	 
</p>

<p>
	after this we will do a clean steam-install into our game-hdd/-partition (here D:\) with a fresh skyrim installation
</p>

<p>
	 
</p>

<p>
	MO2 will have an own directory inside the steam-directory ... \steamapps\common... it will not be installed inside the ...\common\skyrim-dir
</p>

<p>
	Dyndolod will be installed inside the root-directory of D:\
</p>

<p>
	 
</p>

<p>
	<strong>Attention: after installing merge plugins (essential for modding) you will find out, that the right directory for modorganizer2 is INSIDE the gamedir as LOOT, WryeBash... see comments for installing merge plugins topic</strong>
</p>

<p>
	 
</p>

<p>
	SKSE will be installed inside the game-directory of skyrim...
</p>

<p>
	 
</p>

<p>
	after this we will try to install as much other tools with MO as possible, since it will be easier to manage updates within MO. If it is better to do it otherwise, we will explain it with the special tool itself
</p>
]]></description><guid isPermaLink="false">101735</guid><pubDate>Mon, 18 Jun 2018 19:50:47 +0000</pubDate></item></channel></rss>
