sheson Posted February 1, 2014 Posted February 1, 2014 Here is a video that explains what a shortcut is and yes it also shows how to add arguments/paramters/commandlines - whatever you want to call it - to a shorcut. [video=youtube] 18 and half minutes to become an ITPro.
z929669 Posted February 1, 2014 Posted February 1, 2014 But I'm not using MOFair enough, but youare missing out. STEP 2.2.8 will default to MO, and life is much simpler if you do use it. Many very nice tools are included (Trust me, I am the last convert over here ... I was dedicated Wrye Bash until this past Fall). RE sheson's solution (the topic of this thread). STEP will give it honorable mention and point users to the three variant methods by which to employ this currently, but we won't be including this as an official 'mod' until it stabilizes intot he final SKSE solution (I only hope that they incorporate the entire thing in the most sustainable manner possible).
TechAngel85 Posted February 1, 2014 Posted February 1, 2014 Yeah, you really should give MO a try. We never thought we'd talk Z into it but I think he's feeling the love now. WB's development has been fairly non-existent for a long while now and you shouldn't be using NMM with STEP if that is the case. Sent from my Moto X using Tapatalk.
EssArrBee Posted February 1, 2014 Posted February 1, 2014 Yeah, you really should give MO a try. We never thought we'd talk Z into it but I think he's feeling the love now. WB's development has been fairly non-existent for a long while now and you shouldn't be using NMM with STEP if that is the case. Sent from my Moto X using Tapatalk.Actually, I think a couple guys are working on WB again. Sharlikran and Utomuo (I think that's what he goes by) have just released a new dev version. Hopefully they are porting lojacks stuff for the bashed patch, that is all I care about at this point.
Aiyen Posted February 1, 2014 Author Posted February 1, 2014 With the latest version of ENBoost then Boris has decided to implement support for up to 192Gb of memory use with compression..... Talk about securing for the future!
Freyrgjurd Posted February 1, 2014 Posted February 1, 2014 I just started fooling around with the ENBoost and this Memory patch. I'm using skse alpha build and all seems fine. ENBoost gave me a bunch o tearing, even using VSync from NVidia Inspector's config. Found out that if you enable ENBoost own VSync, the tearing ends, but the input lag goes crazy high. So I enabled in the inspector's the Frames Ahead option with 1 or 2 and it all went to the right place. Summary for tearing on my rig: 1. Use internal ENBoost VSync. 2. Configure Frames to Render Ahead to 1 or 2 in nvidia inspector's configuration. Just puting out there. Didn't find the right place ;)
EssArrBee Posted February 1, 2014 Posted February 1, 2014 I think vsync can be iffy from system to system. Good that you found what works for you. Sent from my iPhone using Tapatalk
Freyrgjurd Posted February 1, 2014 Posted February 1, 2014 I thought it could be because the driver's vsync gets applied after the ENBoost processing, so it couldn't filter it. Using the internal would help it. I guess.
EssArrBee Posted February 1, 2014 Posted February 1, 2014 It is hard to say, I think driver stuff is actually loaded into the GPU somewhere, but ENB also tries to share that part of the hardware with the GPU. I get screen tearing from the driver and enb vsync, but I have a laptop with Optimus, so my experience cannot be applied to everyone else. Also, I've noticed some distinct differences between Nvidia and AMD users. It is really a crap shot.
Freyrgjurd Posted February 1, 2014 Posted February 1, 2014 On my rig, anything higher than 256 in the "scrapHeapSizeMB" variable leads to crashing at start screen. No mods whatsoever, just the trio *StableUGrids, Sheson's Patch and ENBoost* and USKP. Maybe I don't need it ._.
Octopuss Posted February 1, 2014 Posted February 1, 2014 Allright, I took the time and really read all 42 pages in one go.I thought I got the idea, until I reread some stuff more carefully. There seem to be some contradicting information.First, the post on ENB forum says those two memory blocks are each 256MB by default.Then everyone uses 512MB for block1 and every post says it's the default value.And THEN someone claims 512 is in reality 768 or something, and then I gave up and decided to add this post. For the love of god and my big green pencil, explain this to a humble human being!
Freyrgjurd Posted February 1, 2014 Posted February 1, 2014 You need to add 256 to your value, 'cause SKSE alpha implementation "eats" that from it. If you input 256, then it will be 0. If you input 512, it will be 256. 768 - 256 = 512 1024 - 256 = 768. SKSE ''eats'' 256 form the informed variable, in lame terms. EDIT: It only does that for Block 1. Block 2 is what you input. EDIT 2: To clarify, in my .ini: [Memory] defaultHeapInitialAllocMB=768 <---- this equals 512, since SKSE will eat 256. scrapHeapSizeMB=256 <--- this equals this. Mehhh
EssArrBee Posted February 1, 2014 Posted February 1, 2014 ELI5: Skyrim's default mem block 1 is 256. The patch changes it to 512. This changes the approach to memory allocation so the engine doesn't go bonkers. The alpha version of SKSE says to set an extra 256MB to their settings because they are still testing stuff and working out how they are going to implement everything. There is a version that does not affect SKSE called SSME, you may have saw it on the Nexus hotfiles the last few days, and it is a compiled version of the same mod. Follow directions for install very carefully.
Recommended Posts