Jump to content

hakeador3000

Citizen
  • Posts

    23
  • Joined

  • Last visited

Everything posted by hakeador3000

  1. Here's proof of the problem being fixed. In the end this whole big mess I had came down to a letter 'k' added to a line in the skse.ini Once again thank you all for your help. Attention to detail is important!
  2. Done and done. Thank you all so much for your help and your time. It means a lot!
  3. Yup it's all working properly here it is. Another thing I forgot to mention which was in fact the source of all this trouble was that my skse.ini was inside a file named skse INSIDE the skse file. So there were 2 skse files. major facepalm, I know.
  4. yeah logs ini are exactly as yours. lowering the default heap initial alloc to 768 seems to have done it. my last logs showed similar memory usage and are now showing the maximum capicity
  5. no its not that. If you look at previous posts you can see that I already went through that
  6. oh yeah it didnt inmeadiately crash to desktop. I knew that a vanilla skyrim takes a while to completely fill the memory blocks so what i did to make the process faster is i increased the ugridstoload to 10 and then once i was in game i turned noclip and godmode on, increased the speed of my character 4 times and just flied around until the game crashed. This was only to fill the memory blocks faster and lo and behold the crash occured around 256mb. that is precisely the problem: my memory blocks havent increased DESPITE having the skse.ini set like this so i made sure the automatic archive invalidation check box was unchecked and it actually wasnt. Afterwards i backdated all bsa's like the guide said I also made made sure that i had mo manage all archives. however despite this when i went into skyrim the logs showed a maximum memory of 256mb again
  7. MO's archive invalidation? I dont understand, what should I do to my skyrim.ini then? All of my bsa are checked, I don't have any missing bsa's as far as i know. I also don't have any missing masters. I did the new profile thing and even without any mods active the game still crashes once both memory blocks reach 256mb. All I want to do is have bigger memory blocks but as said before, editing the skse.ini hasn't done anything
  8. Sure. Here's my mod list: skyrim.ini: skyrimprefs.ini: and finally my system specs:intelcore i7 CPU 1.73 ghz (8cpu's) 8192mb ramsystem model asus g73Jwnvidia geforce gtx 460M 4096mb memory if you need more data on my computer let me know. I hope we can fin a fix Please use spoiler tags for large blocks of text: [spoiler]...text...[/spoiler]
  9. yes it is a steam version
  10. Help please skyrim still crashes after 256mb
  11. I have windows showing file extensions. I dont have any skse.ini.txt my skse.ini is as it should be
  12. haha you mean like mistakenly having put ".txt" at the end of the ini? no i havent done that
  13. yes there is only one skse.ini in my computer. and yes that's how my SKSE folder looks like
  14. 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
  15. 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: so apparently I didn't increase at all my memory blocks? Someone please help tackle this issue so i encounter less ctd'sthanks
  16. umm i have no idea what happened. Apparently I'm a ******: after i did the java steps that you guys told me to do i didn't re install DSR. It occurred to me to do it after you said to install it somewhere else and so now that i have reinstalled it thorugh MO and ran the patcher again it works. I'm confused but happily so.
  17. how do i install it without using MO?
  18. i mean i checked the path again and there were no spaces
  19. no it doesnt, that was just a typo on my part.
  20. I just did buy I got the same error. I also tried making the javaw.exe run as administrator by going to its properties and making run as administrator but it didn't work either
  21. Yes as soon as i installed the new java I updated the path in the executables in it was correct. Java is installed in program files (x86) and I have MO and my steam library in an external hard drive. this is what happens when I try to update the patcher: Error: Unable to access jarfile H:\Mod Organizer\mods\Dual Sheath Redux\SkyProc Patchers\Dual Sheath Redux Patch\ Dual Sheath Redux Patch.jar This hasn't happened before
  22. I got the paths right, how do I check what wether or not I have the x86 version of java? EDIT: I googled it and installed the latest x86 java version and still nothing, MO is still unable to access the jar file
  23. Whenever I try to use the patch it always says that it's unable to access the jar file. I have the current MO update as well as java being up to date (8.71). I tried to solve this on my own and the best fix I could use (which I've successfully done before) was replacing the hook.dll with the hook.dll from version 1.3.5. When I tried doing that however none of the files on the MO nexus page contained the 1.3.5 version of hook.dll ... even the 1.3.5 MO file. Odd right? Even the current hook.dll which comes with the most recent version (1.3.11) when looking into its properties it says that its version is 1.3.6. In any case, that is just a side issue; I could care less what hook.dll version I have, all I want is to be able to patch Dual Sheath Redux and get back to playing. Please help me.
×
×
  • Create New...

Important Information

By using this site, you agree to our Guidelines, Privacy Policy, and Terms of Use.