Nebulous112

Mobile graphics are usually one generation down. I equate performance from my 970m to around a GTX 870. Except it still retains most of the new "features". Just the performance is less. When researching the purchase of my laptop about 6 months ago or so, I found that there were a lot of issues online about the Lenovo brand. Screen quality was one big one. Also, try to avoid any touchscreen models, or ones with 4k screens. Ups the price significantly, when you can use those laptop dollars on better internal hardware.

I'd suggest an MSI laptop, if you can find a decent price. I recently bought an MSI GE-62 2QF. Great laptop. The most important component will be the video card. Video cards can't be changed on laptops, so it's important to note that this will be the limiting factor on the life of the laptop. It is the most important component for gaming. You also want 4GB of RAM or more, preferably at least 8GB. Lastly, the most noticeable speed "boost" for the average user is when using an SSD vs. an HDD. Boot time can got from minutes to literally less than 10 seconds. Among other benefits. Final piece of advice would just be to shop around. If you're looking for a notebook on a budget, the Internet is the best place to buy, for sure. You can find refurbished laptops (with warranties) from places like Newegg that are the same exact product, but cheaper. Check out many different websites, and just look around. I purchased a laptop for a friend (not my MSI) for $500. I had seen a very similarly specced laptop sold for around $1300 elsewhere. So it is definitely worth it to search around once you have an idea of what you are looking for. Anyway good luck!

Note that with the newer LOOT versions, it will not move plug-ins if it finds no issues. This can lead to completely different load orders using the same plug-ins. Specific load order will depend on how the plug-ins were ordered before LOOT was ran. Not sure if that's the issue here, but just a heads-up.

Looks like Groovtama quit development, on both this, and the standard XP32 Skeleton mod. See the sticky on the Nexus posts page. Hopefully only temporarily, but who knows. Looks like he's been having to deal with a lot of ignorant posts on the Nexus page. He released one final update (at least for now), 3.49.

Just to add: I had posted in the 2.2.9.2 STEP Compilation thread, but it got erased with the server rollback. I noticed a few of the mods from the new 2.2.9.2 Compilation list were also on the DDSopt Quick-Start Guide list of mods that would benefit from optimization. I had asked if the non-optimized mods in the compilation had been optimized (as I wasn't sure if the compilation will be safe to optimize after release), and I believe Ess replied that he doubted it. Anyway, I just thought I'd add to this thread so you had a reference for whenever you update the recommended optimization list in the DDSopt quick-start guide again. I find the guide quite intriguing for potentially squeezing all the performance I can out of the non-optimized STEP mods. Cheers, and thanks again. Edit: (clarity)

Makes sense to leave it if a bunch of testing is needed to determine recommended values. However, regardless of the "correct" values for the settings, if your suggested use of those settings in the Skyrim Enhanced Camera .ini will keep FOV from resetting, then that is phenomenal. I'm excited to try those settings out.

I figured the X would make it blank, and the changing FOV in console, then saving, would overwrite those Xs with real values. I assumed the guy was trying to insert the lines into the INI without any value, perhaps to make the console overwrite and save the lines. I put the info in about the decimals, etc. because I wasn't sure why he would not just use one X. He used a specific number for each of the three lines, and I believe one of those lines had a decimal place, with more Xs afterward. I'll see if I can dig up the link. EDIT: Link I was trying to dig up was in fact the link Z already posted on the previous page, Preserving FOV in Skyrim.

Nice! Thanks, MissShaoHuan and DoubleYou! If this fixes the FOV permanently I will be very happy! :-) I've been looking for a permanent solution for a while...in all the wrong places, it seems. Par for the course. LOL It would be good to keep the numbers for alternative aspect ratios in the Enhanced Camera wiki, as well, alongside the standard recommendation for 16:9. This release just keeps getting better and better! :-D Edit: And thanks Z as well! Took too long writing this post it seems.

I tried researching why the FOV tweaks are believed not to persist, and I kept reading that the issue is believed to occur with special scenes, such as the introductory scene. I also read from different sources that if you edit the INI with the FOV tweaks listed on STEP, but put "X"s in place of the numbers (specific amount of "X"s listed, with decimals for some, etc.), then in-game, console the fov number you were looking for, save and quit, fov will persist. The latter doesn't really make sense to me, as how would this make it any different than putting the numbers in yourself in the INI? Unless it puts in different numbers, with decimal places. Anyway, regardless, I think it would be a good addition (maybe with a note that the FOV tweaks might reset, and may have to be added again). Like Tech mentioned above, I also forget to change FOV using the console, about 50% of the time. Would be great to not have to have the hassle of having to console it every time. Even if we have to check every once in a while that it didn't reset.

It would be great if the quick-start guide itself could be updated with a link. Also, Better Bones should be removed from this list, as it was dropped.

Looks like this mod is now required for the latest version of CACO (1.12).

This mod looks awesome! I'm going to have to try this out. I love the fact that this is using official material from the Bethesda Devs leftover in the Creation Kit.

This solution got deleted due to server rollback, but the issue ended up being the optional plugin for RaceMenu. With it moved to optional, no more severe fps drop during character generation.

Hey WizardDoctor, What preset did you use? If High, have you tried Medium? Your specs are impressive, but I have heard that it takes a bloody spaceship to run DynDOLOD on high. References, in case you don't have them: - STEP DynDOLOD recommendations - Sheson's DynDOLOD support thread Note that there are updated scripts as a separate download in the DynDOLOD thread. Sheson has made these available prior to the next release.

I'm very excited for the new release. :-) It looks like it's almost ready! Besides the new patches and possible compilation, the main things left that I can see are: - New INI tweaks addition - Removal of Closer Quiver and Longer Arrows in favor of BSW options - Possible addition of DRAUGR in place of current Book of Silence options??? (assuming from Tech's post and the subsequent replies) Everything else I saw seems very minor, like the small errors on the wiki pages I mentioned earlier. Certainly not important enough to hold you guys back from release. Lol I feel like a kid at Christmas. :D Thanks again for all the hard work you guys put into this project, day-in and day-out! Cheers!

I'm wondering if you guys decided to add this to 2.2.9.2 or not. Seems everyone has given it a thumbs-up.

Greg means the steps in the description of the download page (Nexus page) for Memory Blocks Log. The link he posted brings you to the relevant STEP thread, click the large title text to bring you to the Nexus page. A mod being "dirty" means that it contains "dirty edits". This means it contains ITM records. ITM means Identical To Master (Master being the main Bethesda files from the game itself). Basically if Mod X changes the records for something, and Mod Y is loaded after it, with ITMs that conflict with Mod X, Mod X probably will not work correctly. However, one has to be careful when cleaning mods, because some mods simply will not work if the ITMs are removed (a.k.a. cleaned). However, as Greg said, your problems more likely lie elsewhere. Also, I suggest you use the stand-alone LOOT to sort your load order, if you do not already. Besides the main function of proper load order sorting, LOOT will also tell you if you have ITMs that should be cleaned. It can usually be trusted, but always check the mod description page / posts to see if the author recommends against cleaning.

Also, noticed the same missing MCM text for Lock Overhaul wiki page. Dual Sheath Redux wiki page says instructions current up to 1.7.2. Current version is 1.7.3. On FNIS wiki page, Hotfix no longer needed with update. Weapons and Armor Fixes wiki page is missing the corroborating LOOT rule for WAF and CCOR (along with the warning to disregard rule until CCOR is installed afterward). Lastly, there are a whole ton of mods that are now duplicated in the 2.2.9.2 list, but reading the discussion above, I imagine someone is probably in the Wiki now, playing around with them. Just thought I'd let you know in case you weren't aware. Cheers, Nebulous Edit: Also, noticed the warning on the Wrye Bash wiki page (the one at the top of the guide, not bashed patch wiki page near the bottom) about uninstalling before upgrading to 305. The current version is 306. Edit 2: Also, I love the new LOOT rules listed in the Launching STEP section, but if I may be so bold as to suggest a subtle change in wording: Oh puns...the lowset form of humour. ;-)

One more to add to the LOOT list: Meta Rule Instructions Complete Crafting_TrueWeaponsLvlLists.esp Load after: Weapons & Armor_TrueWeaponsLvlLists.esp Also, on the CCOR wiki page, the hotfix is no longer needed with the new update.

Correct regarding positioning of USLEP, if you just wanted to use Cutting Room Floor, but lack of the old patches will cause other major issues (such as dependencies with the STEP patches). You can't run the old patches and the new Legendary Edition patch at the same time, either. I advise to wait 2 or 3 days...a new STEP version will probably be released by then which should solve everything.

I could be wrong, but I don't think Boris can fix it, Nazgren. I did a little bit of research on this today (for my daily mod knowledge boost), and found a thread on the Nvidia forums started by a user named ENBSeries. This was Boris himself posting, and in the thread he was asking for Nvidia to fix the issue. The thread ends with a link to the page you linked to in your original post. https://forums.geforce.com/default/topic/863242/geforce-drivers/-request-remove-4gb-limit-of-vram-for-dx9-games/1/

Just to clarify, the quote from the SkyFalls and SkyMills page was from the mod author. 3.32 has been removed, only 3.31 is available for download now.

Hey sheson, Just a heads up, cross-posted from STEP 2.2.9.2 Development thread. From SkyFalls and SkyMills - Nexus posts page: Just thought I'd let you know, in case it affects the DynDOLOD settings directly, or if you feel like joining the discussion on the 2.2.9.2 thread. I've never seen you post elsewhere, so I wasn't sure if you'd see it otherwise. And, by the way, I don't think I've ever gotten the chance to thank you yet, for DynDOLOD or the memory patch, etc. Unfortunately, I have no children to offer in sacrifice. I'll let you know when I have my firstborn. Lol. ;-) Cheers, Nebulous

See this note in the Posts section of the Nexus page: STEP may want to look at this for the new release. Edit: Just to clarify, the (last) above quote is from the mod author. The 3.3.2 update has been taken down. The 3.3.1 update is available, as is the 3.3 main file.

I imagine they have not fixed it because it pertains to DirectX9, and I doubt many people have complained to Microsoft. Microsoft tends to look toward the future instead of the past, and I doubt they will ever fix this unless there is some miraculous surge of complaints. As far as a workaround...I personally know of none. But that doesn't mean much. I would suggest going the dual-boot route.