torminater

This belongs in the support and troubleshooting forum. Can you reproduce this glitch?

Same goes for me. Just updated my signature, since I hang around a lot in the support forum xD

Really interesting: Skyrim is almost in all of the cases installed on a SSD. At least somewhere is an SSD directly involved... Maybe a sign of data leaks?

Thing is: higher ugrids causes higher instability which makes it more probable that at some point your save will go to hell since errors stack up and bring it down at some point of time. I never was able to do a whole playthrough with 7 ugrids even playing only vanilla. Not to mention what you are intending. Changing ugrids will not automatically instantly corrupt your save as far as i know at least. I'ld recommend you to try it out on a new save. SPOILERALERT!!!! Then look at your save game size and reflect about how you felt playing with higher and even higher ugrids and whether it was really worth it. That should be a matter of a few hours of testing - if your game stays stable at least :D

Yep, and I tried it in about 2 billion variations. I cannot get it working this way. There is something I'm overlooking but it is just out of my grasp. I already posted in the thread you quoted from about my issues. EDIT: Apparently the newer Wrye Bash versions don't support 64 bit python anymore... unfortunately.

Please tell us your: System Specs - Including model and clock rate of the CPU and GPU, whether you use an HDD or SSD, and screen resolutionGraphics driver version and settingsSkyrim launcher settingsSTEP version and any additional mods usedTexture/quality resolution options - "highest available", "only 1k", etcInstallation method - Wrye Bash, Mod Organizer, NMM, or manual

1. If you start a game with a ugrid-setting you have to play with that value or a higher one until the end. Yeah, there are ways to drop ugrids in a playthrough, but it's rough and might cause issues. 2. Skyrim is not made for high ugridsettings. You will always encounter more issues than with default setting.

I know there are mods out there allowing you to leave houses through windows. I guess you've used one of those.

You have to find a character who interests you first. For example I was very frustrated about something, so I created one big brute of an orc who double-wields a greatsword and smashes everybody into the ground who opposes him. I enjoyed it a lot :D Maybe you want to use a very difficult type of playthrough? Using no weapons, or no magic can make things a lot harder if combined with certain difficulty enhancements. Also try out some combat mods! That makes the "normal" Skyrim experience consisting of a whole lot of fighting more interesting for a veteran.

Well two things stop me. 1. I don't want to install the python version of WB because it only uses 32 bit applications - just like the standalone 2. I don't know whether I can just port my bash.ini file to the mopy directory of the python version without issues. If you could provide me with a detailed step by step tutorial how to set up WB Python to use only 64bit applications, I'll do it. Otherwise... rather not. I spent too much time reading too many forum threads about too many too vague things that had literally nothing to do with what I intended to find out via google. I just don't get why the official WB readme doesn't tell ya how to get it to work in 64bit mode. Even how to set LAA flags for the standalone version I had to find out myself with google which took ages by the way, since apparently nobody ever thought it might be worth mentioning how to do so in these really awfully helpful readmes. Edit: Oh a 3rd reason is, that I don't know whether all of WB functionality is the same when running WB or if there are things that are different and you have to note so that you don't run into problems. Edit2: Replaced WB.exe with the original exe since my antivirus doesn't seem to be able to remember that this exe is no virus and informs me every 2 seconds that it has found a new virus.

Well... whatever. I'm too tired right now - been a long day. I just don't feel like setting up Wrye Bash python. I really don't like python AT ALL. I had to use it 1 year in our equivalent to high school and I hated every moment of it...

hmm. Let's say I set all texture installers to not refresh and I then optimize my Skyrim\Data directory and overwrite the Data directory with the optimized files, will WB still uninstall textures that got processed by DDSopt when uninstalling the mod where those textures originally came from?

it won't let me ... ?! :-/RU sure you click on directories, not archives?Well...???I only have 7zip archives in WB installers tab. Why should I have uncompressed folders anyway? Edit: I see, well so it's either having more space on my HDD or less loading time with WB xD Isn't it a bad idea to tell WB to not refresh any of the texture/mesh mods?

Well it does look better... although I personally think it could even look better. :-) An improvement is an improvement though. Let's see what the others think.

Does it work in conjunction with the mod that stops the bad scripts in your save?

it won't let me ... ?! :-/ 7zip 64 apparently works with the 64 bit python WB version... at least according to this thread...:https://forums.nexusmods.com/index.php?/topic/390341-so-is-there-a-way-to-get-wrye-bash-working-on-64-bit-systems/page-2

Yeah, I figured it'ld be misleading ... didn't want to double post though. Situation is as followed: - I currently DDSopted all vanilla textures and put the extracted and optimized folders in WB installers directory. After that WB took ages and more to load anything at all. - I didn't like that Wrye was so slow and tried to find means and ways to improve WB performance. I knew that WB Standalone (the version I use) is a 32 bit application and so cannot naturally use more than 2 GB RAM. With all of those huge folders (somewhat like 10 GB on top of Full STEP) it was just overloaded. - Additionally the 7zip version implemented by WB Standalone is 32 bit, too, so the same as above applies here too, when it comes to unpacking and packing those folders and archives for installing purposes... - I then found the optimize 7zip compression method thread under Hints or sth like that in the Guides forum. There were two comments on how to use the improved compression method using multiple cores under WB. I then took the setting recommended by the last of those comments as a base. I then read about using non-solid compression for the optimized vanilla archives (and other big archives like BethHRopt) and thought that it'ld be a great idea to let WB use this automatically, so I set the solid compression to off in the bash.ini file. All the other settings recommended in this comment I didn't look up, so I don't know whether they're good or bad... but at least it works for me. - Now I looked up in the internet how I could improve WB's speed and functionality with a huge load of files and I thought... well, it'ld need to access more RAM to be faster... So I found out how to set LAA flags to any exe using CFF explorer (freeware from Nt). I then set the LAA flag for Wrye Bash.exe as explained above. - I also was aware that WB used 7zip 32 bit as extraction and compretion program and I tried hard to find a way to use the 7zip 64 bit version which is installed on my system... but I couldn't so far. I already posted on the relevant nexus threads but so far no answers were given to my issues... So in absence of a better idea, I set LAA flags up for all three exe files in the compiled folder of Wrye Bash (detailed path found above) so even if it was just a 32bit application it could use all the RAM it could get (I only have 4 GB RAM anyways on my Laptop). So, I hope I was a little clearer now. :-) I can say from my experience that packing and unpacking those huge archives goes much faster now (takes 22 seconds from opening WB til the end of loading the installers tab now... before it was at least 1 minute). Didn't use benchmarks (don't really know how to anyway) but WB starts faster, opens the installer tab faster, packs archives faster and unpacks archives faster, still it takes several seconds (15-20) where WB is "not responding" until it is done loading. Maybe these "non-responsiveness" gets increased by setting the LAA flag, since WB as 32 bit application is actually not made for more than 2 GB of RAM and it takes too long to work off the data overflow... Two things I wished to come true: - Find a way to use 7zip 64 bit with WB standalone (seemingly impossible :-/ ) - Get a 64 bit WB standalone version (would need to be made by the author of WB) which already uses 7zip 64 bit... doesn't seem very likely. I don't know anything about programming but I guess it would take lots of work to port WB from 32 bit to 64 bit...

@alternity: I guess you misunderstood my point. I don't use Skyrim - Textures.bsa anymore since I've extracted it and installed the optimized textures as loose files. If a mod that has it's textures in a bsa gets loaded, will it still overwrite the loose files of Skyrim - Textures.bsa with it's textures or not? I'm not sure whether the new system that loose files win over bsa only applies to official Bethesda bsas or also to all other bsas...

There are two new mountain textures 4k² resolution. One in light color and one in dark color. Big textures but maybe they're still good when resized?

I would include a reference to the Support guidelines you just included in the forum so that people who go through the troubleshooting guide and can't get their issues fixed and want to post about it in the Support forum will be extra reminded that they need to give detailed information about their setup.

trollololooool! :D Oh... I think I just got sick.

Great! I'll try to think of something to add...

... pretty speechless right now.

"limitless" is a positive attribute by the way...