sutex Posted December 17, 2015 Posted December 17, 2015 It means your SKSE is set up correctly. :-) Oh good , mmmm so there's another reason then Ive been unable to get the last "LOD" step working in Step .. ok
GrantSP Posted December 22, 2015 Posted December 22, 2015 OK, so I was just looking at @Nebulous112's screenshots of his MO install of STEP and was surprised by the comment that this mod is not part of STEP.Have we just assumed everyone will have this installed and not bothered to explicitly explain how to install it, or are we taking a position of this not being needed if STEP is configured as shown?Either way, surely this gem could be part of the "Utilities" or "Extenders" sections?
Greg Posted December 22, 2015 Posted December 22, 2015 I think the assumption is that Memory Blocks Log is not in the STEP 2.2.9.2 Guide, so it is not a part of STEP Core or STEP Extended. Users have been instructed to install it after they experience a crash or infinite loading screen that might be attributed to SKSE configuration issues. I just noticed that it's not mentioned in 3.A.1 Failures to Launch or 3.A.2 Crashes to Desktop (CTD) either. I think I remember something about this being included in the Utilities Pack.
Nebulous112 Posted December 29, 2015 Posted December 29, 2015 (edited) I think Memory Blocks Log definitely should be mentioned in the main guide's Troubleshooting section. As Greg points out, there is no current mention of this tool at all in the main wiki. When mentioning Memory Blocks Log, a link to the wiki page should be added. The wiki page could be edited with basic instructions on using Memory Blocks log to make things even easier for a user. I think this could cut down on the amount of support needed on the forums by a large amount. The first I heard of the Memory Blocks Log was from going into the Troubleshooting section of the forum, and reading Greg or someone else mention it as a useful tool. Since then, I have noticed using Memory Blocks Log is usually the very first troubleshooting step mentioned for crashes, and changing the associated memory settings ends up being the solution in many cases. Mentioning this tool in the guide itself would hopefully help more people to solve their own issues. [insert cheesy line] Knowledge is power! [/cheese] ;-) lol Edited December 29, 2015 by Nebulous112
TechAngel85 Posted January 2, 2016 Posted January 2, 2016 I've moved this to where the other utilities are found.
hakeador3000 Posted June 4, 2016 Posted June 4, 2016 Ok I have a problem with my memory blocks. this is my skse.ini : [General]ClearInvalidRegistrations=1 [Display]iTintTextureResolution=1024 [Memory]DefaultHeapInitialAllockMB=1280ScrapHeapSizeMB=256 yet when i start the game and I produce the memory log this happens: logging of blocks enabledlogging max values onlyTimer disabledBlock1 Block2256MB 256MB85 885 885 985 1085 1185 1285 1385 1485 1585 1685 1785 1885 1985 2085 2185 2285 2385 2485 2585 2685 2785 2885 2985 3085 3185 3285 3385 3485 3585 3685 3785 3885 3985 4085 4185 4285 4385 4485 4585 4685 4785 4885 4985 5085 5185 5285 5385 5485 5585 5685 5785 5885 5985 6085 6185 6285 6385 6485 6585 6685 6785 6885 6985 7085 7185 7285 7385 7485 7585 7685 7785 7885 7985 8085 8185 8285 8385 8485 8585 8685 8785 8885 8985 9085 9185 9285 9385 9485 9585 9685 9785 9885 9985 10085 10185 10285 10385 10485 10585 10685 10785 10885 10985 11085 11185 11285 11385 11485 11585 11685 11785 11885 11985 12085 12185 12285 12385 12485 12585 12685 12785 12885 12985 13085 13186 13191 131105 131106 131106 132107 132123 132123 133125 133127 133129 133129 134130 134131 134132 134133 134134 134135 134136 134137 134138 134139 134139 135140 135141 135142 135143 135144 135145 135150 135156 135156 136156 137156 138156 139156 140156 141157 141158 141159 141160 141161 141162 141163 141164 141165 141166 141167 141168 141169 141170 141171 141172 141173 141174 141175 141176 141177 141178 141179 141180 141181 141182 141183 141184 141185 141186 141187 141188 141189 141190 141191 141192 141193 141194 141195 141196 141197 141198 141199 141200 141201 141201 142202 142203 142204 142205 142206 142207 142208 142209 142210 142211 142212 142213 142214 142215 142216 142217 142218 142219 142220 142221 142221 143222 143222 144223 144224 144240 144240 145240 146240 147240 148240 149240 150240 151241 151242 151242 152243 152244 152245 152250 152255 152255 153 so apparently I didn't increase at all my memory blocks? Someone please help tackle this issue so i encounter less ctd'sthanks
Nebulous112 Posted June 4, 2016 Posted June 4, 2016 First, verify your skse.ini is in the proper location. It should be in Data/SKSE. I.E. in a folder named "skse". If you are sure that is correct, add the "-forcesteamloader" argument to SKSE. If using MO, go to Configure Executables, and select SKSE. Under argument include that text (without quotations). If not using MO, I believe you have to append it to the SKSE_loader shortcut name (I'm not 100% on that). When you do get it working, I would encourage you to stress test with MBL. 1280 is pretty high, and unneeded in most setups. If you can reduce that number without hitting the limit it will increase your performance dramatically.
Greg Posted June 4, 2016 Posted June 4, 2016 If you're using Mod Organizer, also verify you do not have a duplicate skse.ini in the Skyrim\Data\SKSE folder by mistake and that the file is actually named skse.ini instead of skse.ini.txt in the mods/skse_1_07_03/SKSE folder. I'll second Nebulous112's observation that 1280 is most likely wasting memory that could otherwise be used by the game, so try to get this down as much as possible.
hakeador3000 Posted June 5, 2016 Posted June 5, 2016 If you're using Mod Organizer, also verify you do not have a duplicate skse.ini in the Skyrim\Data\SKSE folder by mistake and that the file is actually named skse.ini instead of skse.ini.txt in the mods/skse_1_07_03/SKSE folder. I'll second Nebulous112's observation that 1280 is most likely wasting memory that could otherwise be used by the game, so try to get this down as much as possible. First, verify your skse.ini is in the proper location. It should be in Data/SKSE. I.E. in a folder named "skse". If you are sure that is correct, add the "-forcesteamloader" argument to SKSE. If using MO, go to Configure Executables, and select SKSE. Under argument include that text (without quotations). If not using MO, I believe you have to append it to the SKSE_loader shortcut name (I'm not 100% on that). When you do get it working, I would encourage you to stress test with MBL. 1280 is pretty high, and unneeded in most setups. If you can reduce that number without hitting the limit it will increase your performance dramatically.sorry i forgot to mention that I do indeed use MO. I changed the skse.ini down to 1024 from 1280 and added the argument -forcesteamloader in mod organizer. however my logs produce the same result as before, nothing has changed
Nebulous112 Posted June 5, 2016 Posted June 5, 2016 sorry i forgot to mention that I do indeed use MO. I changed the skse.ini down to 1024 from 1280 and added the argument -forcesteamloader in mod organizer. however my logs produce the same result as before, nothing has changedVerify that your SKSE file structure looks like this: (From the STEP SKSE installation instructions)
Greg Posted June 5, 2016 Posted June 5, 2016 Have you verified you have the skse.ini file in the proper location? See this post from Nebulous112 for a screenshot showing the correct folder layout in Mod Organizer. If this is correct, verify you don't have any duplicate skse.ini files in some other mod or in the Skyrim game folder that might be conflicting. https://forum.step-project.com/topic/4985-memory-blocks-log-by-sheson/page-4?do=findComment&comment=167825
hakeador3000 Posted June 6, 2016 Posted June 6, 2016 yes there is only one skse.ini in my computer. and yes that's how my SKSE folder looks like
Nozzer66 Posted June 6, 2016 Posted June 6, 2016 Absolutely certain you don't have the old SKSE.ini.txt issue?
hakeador3000 Posted June 6, 2016 Posted June 6, 2016 Absolutely certain you don't have the old SKSE.ini.txt issue?haha you mean like mistakenly having put ".txt" at the end of the ini? no i havent done that
Nebulous112 Posted June 6, 2016 Posted June 6, 2016 If you don't have Windows showing file extensions, that will happen automatically and you would never know.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now