dx1

Thank you all and thank you TechAngel for the information regarding the SKSE.ini settings even if I did not ask for them. I hope I did not come along too rude. If I did, I apologize.

Thanks, I googled around and found there probably is a discrepancy between the original Memory Patch by Sheson and the settings in the SKSE.ini. Something with first and second block sizes and SKSE.ini translating 768 to 512 or what do I know. I read it is recommended to increase the second block to 512 if the first ist 768 or more. But in SKSE.ini I set a variable called "DefaultHeapInitialAllocMB" to 768 (default 512) and another variable called "ScrapHeapSizeMB" to 512 (default 256). So, with all due respect I thank you for your input and will read more about first and second blocks of something, but I don't think your answer is really relevant to my problem: In MO 1.3.9 (and 1.3.8) I can't add argument(s) to SKSE in the respective field of the executable window. SKSE.ini atm looks like: enblocal.ini (shortened from [iNPUT] downwards: But I'm pretty sure these INI-settings have nothing to do with MO not letting me add arguments to the SKSE executable.

Yesterday I had the issue of "SKSE Memory Patch does not work correctly". I found out when I tried to increase the Blocks to 768 and 512. I followed the instruction to add the argument "-forcesteamloader" to the executable. Now the problem is this: "SKSE", together with "Skyrim" and "Skyrim Launcher" is greyed out, and any change I make will not be saved when I hit "modify". I run 1.3.9 but on a quick check 1.3.8 showed the same behaviour. As a workaround I made a second entry for SKSE (in the list as SKSE+) where I can add the argument. I use that to start the game and it works. It would be nice to need only one entry for SKSE and make that modifiable. I found no indication of this behaviour as intended, but if it is I hope someone's telling me.

The readme of the "fixed FOMOD version" of this mod states: So I think manual installation according to the STEP guide could be like: Move the folder "meshes" out of "04 Meshes Fullsize Vanilla" to → "08 Fullsize Textures/". Move the folder "dlc01" out of "05 Meshes Fullsize DG Vanilla/" to → "08 Fullsize Textures/meshes/". Move the folder "dlc02" out of "06 Meshes Fullsize DB Vanilla/" to → "08 Fullsize Textures/meshes/". Set folder "08 Fullsize Textures" as data directory.I chose "Greatsword Sheaths and Scabbards Redux — Fixed the FOMOD installer (hopefully)" instead of the recommended "… NMM Installer" because the folders are named much more descriptive compared to the NMM version, with the prefixes like "Textures" and "Meshes" and all. Animated it looks like this: https://www.youtube.com/watch?v=e3kLi2CXYyA PLEASE, correct me if I screwed this up.

Tannin found the problem. It was an way too old .dll belonging to openSSL. I updated it and now MO works like a charm. Thank you again, Tannin.

I put the dumps on dropbox and left links in the bug tracker. https://issue.tannin.eu/tbg/modorganizer/issues/1297 But I'm going to send you that email, too.

Tried adding the MO folder to the exceptions before, no dice. My AV is NOD32. Quarantine folder was clear of MO-related files too.

The problem still exisits with MO 1.3.9 — also whenever I click a download link on the nexus pages Windows asks me if I want to start MO, even if it's up already, like it does with 1.3.8. I seem to be the only person on the internet to experience this kind of problem, which I find highly unlikely. I still think there's something messed up within my windows installation itself, but I can't find out what. When I search for 'faulting module name qt5gui.dll' I find no useful informations. :confused: EDIT Okay, I created a .dmp but was to stupid to install the correct symbols to have a look at it in windbg. Then I found: https://blog.inventic.eu/2014/08/qt5-application-crashed-with-error-0xc0000005/ Maybe one of you can help me sort this out? I now looks to me it is a bug inside QT5 and I have to post a bug report on the MO bug tracker.

Hello everyone, first I'd like to say this is no bug report because the problem seems to be completly on my end. I repeatedly get an Appcrash with "Fault Module Name: Qt5Gui.dll". I run MO 1.3.8 on Windows 7 64, installed it with and without admin rights and tried to run it normal and "as admin". Doesn't matter. I close the program → appcrash. I download something from the nexus while MO is running → appcrash. I download something from the nexus without MO running → MO starts → no appcrash. While I can just close the window regarding the crash and continue to install and manage mods, I better do not download another file while MO is running. I would get another appcrash. Yesterday I copied all my downloads from NMM to MO/downloads and started to query infos from the nexus, sorted some out, downloaded updated versions and so on, just closing any appcrash-info that popped up. This resulted in a freeze of the program. After kicking the process from Task Manager and restarting MO I realized all downloads and mods were gone. I found the whole bunch of them in the bin. In case my writing is hard to understand, I recorded what I described: https://www.youtube.com/watch?v=ZBxU1AqEDTM Nevermind I did highlight the wrong line in the first appcrash window. I hope you can help me figuring out what's the problem with this dll. It's the one that came with the installer, I did not deselect the option to install the QT-dlls. Problemereignisname: APPCRASH Anwendungsname: ModOrganizer.exe Anwendungsversion: 1.3.8.0 Anwendungszeitstempel: 55854f4d Fehlermodulname: Qt5Gui.dll Fehlermodulversion: 5.4.1.0 Fehlermodulzeitstempel: 5554efe6 Ausnahmecode: c0000005 Ausnahmeoffset: 0001e8de Betriebsystemversion: 6.1.7601.2.1.0.256.1 Gebietsschema-ID: 1031 Zusatzinformation 1: f2bb Zusatzinformation 2: f2bb90e3966911598f7489f5fe9100af Zusatzinformation 3: d9fe Zusatzinformation 4: d9fecf93a522eb346e86e7882efb7800