frihyland

rename your ini's files and start up skyrim from the launcher to build default ones and test. If it fixes it you know where to look, if not delete your new ini's and rename the old ones back to default. It probably is an improperly formatted dds file though, never seen that particular artifact myself though.

By default a 32 bit windows application will never ask for more than 3GB of memory from the system, memory management above that would have to be specially coded. One of the primary differences between 32 and 64 bit applications is the radical increase in memory supported, from 3GB to 64GB but until consoles go 64bit we won't see any games that do. Since skyrim was coded for consoles and only ported to pc later and it only supported 2GB on launch, its more than a little unlikely that this special above 3GB code has been written. Actually getting some use out of that much ram is rather a problem, one solution is to buy a ramdisk application that turns your unused memory into a virtual harddisk that is roughly 8000 times faster than the fastest ssd. You can copy all of your skyrim directory here and launch skyrim, needless to say load times will be a thing of the past and so should any ctd's or slowdowns involving any type of memory management or disk management. FYI if you encounter any type of drm issues you can probably circumvent them by judicious use of symbolic links, ask again if it arises and many here could help with that. Additionally there are special ini settings which should increase ram usage for specific game uses. Many of these have been tested fairly exhaustively back in November with little to no effect on memory usage or gameplay excepting uGridsToLoad and uExterior Cell Buffer. Posted merely in case you want to try them out of curiosity to see if something has changed since then. In skyrim.ini [General] uGridsToLoad=9 uExterior Cell Buffer=200 uInterior Cell Buffer=18 fMasterFilePreLoadMB=200.0000 iPreloadSizeLimit=419430400 [Papyrus] iMaxMemoryPageSize=16384 iMinMemoryPageSize=4096 [budgetCaps] uActorMemoryBudgetCap=20971520 uLoadedAreaNonActorMemoryBudgetCap=371195904 uWaterMemoryInterior=20971520 uTextureMemoryInterior=20971520 uGeometryMemoryInterior=20971520 uWaterMemory=10485760 uTextureMemory=20971520 uGeometryMemory=10485760

Just downloaded V4 with sunrays :D Any progress on the really dark nights and dungeons? I want a mandatory torches version when underground or between midnight and 4am.

According to some unconfirmed preliminary testing on my part NMM uses a -# as a pattern to locate data and uses the - as a delimiter for separating useful data in the filename. This means that if a modder uses that pattern in their filename NMM will substitute this random filename data for the essential information that the nexus appends. This leads to situations where one mod is mistaken for another or the titles are messed up or version information is incorrect. NMM is just so dependent on modders rigorously adhering to unpublished documentation its silly. Now you know why its happening.:ox: To confirm just add 2-6-1 to the front of any filename, then import with nmm and it will be recognized as BOSS.

That's why I wrote the hardware guide :(

ahh ok the memory leak is probably what killed me than, must be very constant to happen at exactly the same point each time.

trying to optimize the DLC with the DDSopt_v080pre2 and crashing whenever it tries to process \architecture\highhrothgar\hhdragoncol01_n.dds Tried many different settings to no effect.

Yeah header files for esm's changed in 1.5.26 so if you have an early version of bash and a new esm version they don't play well, vice versa is also true. So you will either need to update your bash or the author will need to update the mod depending on which is outdated. Also remember that all esm's are hacks, bethesda does not support creating an esm with the creation kit, so it may be an actual error or omission in the file besides just the header change issue. Here is a very short summary of esm . Wrye bash is very diligent about verifying file integrity :D

Did you follow all the steps on the nexus page to configure? Make sure you are using the high performance enb.ini and that you edit it to set ssao and dof to false.

that was enb .111 the latest .112 works fine for amd reportedly (I'm nvidia myself so I can't confirm)

Camera INI Tweaks for Wrye Bash For bash users this replaces Centered Third Person Camera by PeterTran, Instant Camera POV switching by Graxster and PROPER Third Person Horse Camera by mtgAzim

Oh yeah, Boris lists a whole lot of utilities that use d3d as completely incompatible.

I tried it back in march when they were really going head to head, at that point each had some points that where better than the other. Sadly the competition ended abruptly when crimson tide stopped being updated 2 months ago. Enhanced blood has quite surpassed it in every way now.

I just retested my fps and I'm actually getting a 4fps gain with all ultra+ (with STEP edits) settings running vanilla skyrim (no mods or dlc) and full vibrancy enb without ssao or dof :P, I've confirmed for myself a few dozen times now. Need some more peeps to check this out and make sure I haven't gone off the deep end.

were you using non power of 2 parameters to your shadow settings in ini? That kind of thing will make your gpu blow a gasket, the math gets exponentially harder. i.e. If you do something like lower a parameter from 2048 too 500 (instead of 512) you can actually be increasing load on your gpu/cpu while decreasing quality. Any parameter (not just shadows) that starts out in power of 2 format by default should probably stay in it when adjusted up or down.

I find that a bit hard to believe, but its certainly not something that can be done without documentation. Is that only in Stoppings brain at this point? Paging Mr. by4now

I'll just mirror your wb installation section when your done with it, I was gonna add a link to the new troubleshooting section in case people ran into the can't find skyrim dir problem. edit: added it myself and mirrored, let me know if you make any further changes, or just mirror it yourself. :D

language problem I think, that's what he just did :P

First paragraph "click play from steam, this will start the launcher it will autodetect your game hardware and select a default option set for you. Accept the defaults for now (this will create your ini files) and click play, (this will create some essential skyrim registry entries) if you do not do this no programs will be able to find your skyrim directory. Click quit when you reach the main menu." edit: added it to troubleshooting guide as well.

Covered here

Updated Wrye Bash installation section.

Updated Wrye Bash installation section.

Huzzah, Wrye Bash has a new Nexus release.

Discussion thread: Project Parallax-Windhelm by Osmodius Wiki Link The stunning series continues, now you get awesomeness right next to the eyesore that is the vanilla Windhelm :P

Need to label those in highslide, I have no idea what I'm looking at as I go through the gallery.