richardo11

Hei to everyone and thanks for the work your are doing.. a big one Aside of showing my appreciation also i would like to post some feedback.. I know is utterly impossible to build a mod list that suits everybody, but I think that (AFIK) totally unimportant mods like -don't talk with your mouth full- or - spinning logo- that for me only bloats the long list .... Cannot those mods be optional instead of core?? How a spinning logo that you see only for a few seconds in the whole gaming experience can be "Core"? Still, grateful for your work and generosity, dunno want to push anyone, just i don't get it :)

Well, the thing is that Run for YOur Lives, from Arthmoor himself, does not forward MHDT from Skyrim and all DLC's .... and the mods works like a charm, why, who, how, shoulda-cuda ... bet that even Bethesda has a clue :)

In order to be absolute sure (I know i did download from github and nexus) I went over nexus and downloaded the installer, it is not exactly the same version as you comment - Wrye Bash 307.2018.070.40057 Reinstalled (Deleted first ALL mopy/WryeBash) --- The same problem, MO2 blocks, cmd console flash for a second,, and MO2 un-blocks, WryeBash does not even lunch One thing i did see, in task manager, wrye Bash.exe*32, fires up, remains there for 1 second or less, then WerFault.exe*32 fires, and half a second after, wryebash*32 shuts down from task manager How damn that could be, this computer has had Wrye Bash installed many times...

Been modding Skyrim for years, never have had this problem Skyrim SE is installed outsdide C:/ drive MO2 and all others tools (LOOT, XEdit ....etc) are installed in a separate folder than Skyrim launcher MO2 and all other applications launch properly, LOOT, xEdit, Performance Monitor, SKSE Launcher, sEdit ..... , no problem at all The game launchs and plays without issues.... Tryed to install Wrye Bash many times, in a separate folder where all the other tools are, in the main skyrim folder, in C:/ drive, with Python, without Pyton, with/out extra location... Run the app with Administration permission.. etc Running from Windows7 Once the WryeBash executable is set in MO2, once i click, MO2 block (like anyother executable) for a couple of seconds .. and then un-blocks, WryeBash simply does not launch, no messages or warnings of any kind.. I am in a state of desesperation, googling for days, posting everywhere ... Can's make a Bash patch .... Please help WryeBash Carsh Dump: Version=1 EventType=APPCRASH EventTime=132049989732206010 ReportType=2 Consent=1 UploadTime=132049989732806010 ReportIdentifier=583914ba-8eb7-11e9-97f4-ac9e17b4e9b8 IntegratorReportIdentifier=583914b9-8eb7-11e9-97f4-ac9e17b4e9b8 WOW64=1 Response.BucketId=3446077172 Response.BucketTable=373684609 Response.type=4 Sig[0].Name=Application Name Sig[0].Value=Wrye Bash.exe Sig[1].Name=Application Version Sig[1].Value=307.2018.731.1531 Sig[2].Name=Application Timestamp Sig[2].Value=49180193 Sig[3].Name=Fault Module Name Sig[3].Value=KERNELBASE.dll Sig[4].Name=Fault Module Version Sig[4].Value=6.1.7601.24475 Sig[5].Name=Fault Module Timestamp Sig[5].Value=5cdd8011 Sig[6].Name=Exception Code Sig[6].Value=e06d7363 Sig[7].Name=Exception Offset Sig[7].Value=0000c5af DynamicSig[1].Name=OS Version DynamicSig[1].Value=6.1.7601.2.1.0.256.48 DynamicSig[2].Name=Locale ID DynamicSig[2].Value=1044 DynamicSig[22].Name=Additional Information 1 DynamicSig[22].Value=ad0e DynamicSig[23].Name=Additional Information 2 DynamicSig[23].Value=ad0e4577e1fbfd6243b60ca89f681c02 DynamicSig[24].Name=Additional Information 3 DynamicSig[24].Value=368c DynamicSig[25].Name=Additional Information 4 DynamicSig[25].Value=368cfefa7fa92b8bc4b5e7c8499d4d7a UI[2]=D:\Mopy\Wrye Bash.exe UI[3]=Wrye Bash has stopped working UI[4]=Windows can check online for a solution to the problem. UI[5]=Check online for a solution and close the program UI[6]=Check online for a solution later and close the program UI[7]=Close the program LoadedModule[0]=D:\Mopy\Wrye Bash.exe LoadedModule[1]=C:\Windows\SysWOW64\ntdll.dll LoadedModule[2]=C:\Windows\syswow64\kernel32.dll LoadedModule[3]=C:\Windows\syswow64\KERNELBASE.dll LoadedModule[4]=C:\Windows\WinSxS\x86_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.6161_none_50934f2ebcb7eb57\MSVCR90.dll LoadedModule[5]=C:\Windows\syswow64\USER32.dll LoadedModule[6]=C:\Windows\syswow64\GDI32.dll LoadedModule[7]=C:\Windows\syswow64\LPK.dll LoadedModule[8]=C:\Windows\syswow64\USP10.dll LoadedModule[9]=C:\Windows\syswow64\msvcrt.dll LoadedModule[10]=C:\Windows\syswow64\ADVAPI32.dll LoadedModule[11]=C:\Windows\SysWOW64\sechost.dll LoadedModule[12]=C:\Windows\syswow64\RPCRT4.dll LoadedModule[13]=C:\Windows\syswow64\SspiCli.dll LoadedModule[14]=C:\Windows\syswow64\CRYPTBASE.dll LoadedModule[15]=C:\Windows\system32\IMM32.DLL LoadedModule[16]=C:\Windows\syswow64\MSCTF.dll LoadedModule[17]=C:\Windows\syswow64\SHELL32.dll LoadedModule[18]=C:\Windows\syswow64\SHLWAPI.dll LoadedModule[19]=C:\Windows\system32\CRYPTSP.dll LoadedModule[20]=C:\Windows\system32\rsaenh.dll LoadedModule[21]=C:\Windows\syswow64\ole32.dll LoadedModule[22]=C:\Windows\syswow64\OLEAUT32.dll LoadedModule[23]=C:\Windows\syswow64\COMDLG32.dll LoadedModule[24]=C:\Windows\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.7601.24460_none_2b1e532a457961ba\COMCTL32.dll LoadedModule[25]=C:\Windows\system32\msimg32.dll LoadedModule[26]=C:\Windows\system32\VERSION.dll LoadedModule[27]=C:\Windows\system32\secur32.dll LoadedModule[28]=C:\Windows\system32\uxtheme.dll LoadedModule[29]=C:\Program Files (x86)\Ruiware\WinPatrol\PATROLPRO.DLL LoadedModule[30]=C:\Windows\syswow64\urlmon.dll LoadedModule[31]=C:\Windows\syswow64\api-ms-win-downlevel-ole32-l1-1-0.dll LoadedModule[32]=C:\Windows\syswow64\api-ms-win-downlevel-shlwapi-l1-1-0.dll LoadedModule[33]=C:\Windows\syswow64\api-ms-win-downlevel-advapi32-l1-1-0.dll LoadedModule[34]=C:\Windows\syswow64\api-ms-win-downlevel-user32-l1-1-0.dll LoadedModule[35]=C:\Windows\syswow64\api-ms-win-downlevel-version-l1-1-0.dll LoadedModule[36]=C:\Windows\syswow64\api-ms-win-downlevel-normaliz-l1-1-0.dll LoadedModule[37]=C:\Windows\syswow64\normaliz.DLL LoadedModule[38]=C:\Windows\syswow64\iertutil.dll LoadedModule[39]=C:\Windows\syswow64\WININET.dll LoadedModule[40]=C:\Windows\syswow64\USERENV.dll LoadedModule[41]=C:\Windows\syswow64\profapi.dll LoadedModule[42]=C:\Windows\WinSxS\x86_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.6161_none_50934f2ebcb7eb57\MSVCP90.dll LoadedModule[43]=C:\Windows\system32\WSOCK32.dll LoadedModule[44]=C:\Windows\syswow64\WS2_32.dll LoadedModule[45]=C:\Windows\syswow64\NSI.dll LoadedModule[46]=C:\Windows\WinSxS\x86_microsoft.windows.gdiplus_6595b64144ccf1df_1.1.7601.24467_none_5c08a697a00c8eef\gdiplus.dll LoadedModule[47]=C:\Windows\system32\WINSPOOL.DRV LoadedModule[48]=C:\Windows\system32\WINMM.dll LoadedModule[49]=C:\Windows\system32\atl.DLL LoadedModule[50]=D:\Mopy\loot_api.dll LoadedModule[51]=C:\Windows\system32\WINHTTP.dll LoadedModule[52]=C:\Windows\system32\webio.dll LoadedModule[53]=C:\Windows\syswow64\CRYPT32.dll LoadedModule[54]=C:\Windows\syswow64\MSASN1.dll LoadedModule[55]=C:\Windows\system32\MSVCP140.dll LoadedModule[56]=C:\Windows\system32\VCRUNTIME140.dll LoadedModule[57]=C:\Windows\system32\api-ms-win-crt-runtime-l1-1-0.dll LoadedModule[58]=C:\Windows\system32\ucrtbase.DLL LoadedModule[59]=C:\Windows\system32\api-ms-win-core-timezone-l1-1-0.dll LoadedModule[60]=C:\Windows\system32\api-ms-win-core-file-l2-1-0.dll LoadedModule[61]=C:\Windows\system32\api-ms-win-core-localization-l1-2-0.dll LoadedModule[62]=C:\Windows\system32\api-ms-win-core-synch-l1-2-0.dll LoadedModule[63]=C:\Windows\system32\api-ms-win-core-processthreads-l1-1-1.dll LoadedModule[64]=C:\Windows\system32\api-ms-win-core-file-l1-2-0.dll LoadedModule[65]=C:\Windows\system32\api-ms-win-crt-heap-l1-1-0.dll LoadedModule[66]=C:\Windows\system32\api-ms-win-crt-string-l1-1-0.dll LoadedModule[67]=C:\Windows\system32\api-ms-win-crt-stdio-l1-1-0.dll LoadedModule[68]=C:\Windows\system32\api-ms-win-crt-convert-l1-1-0.dll LoadedModule[69]=C:\Windows\system32\api-ms-win-crt-locale-l1-1-0.dll LoadedModule[70]=C:\Windows\system32\api-ms-win-crt-math-l1-1-0.dll LoadedModule[71]=C:\Windows\system32\api-ms-win-crt-filesystem-l1-1-0.dll LoadedModule[72]=C:\Windows\system32\api-ms-win-crt-time-l1-1-0.dll LoadedModule[73]=C:\Windows\system32\api-ms-win-crt-environment-l1-1-0.dll LoadedModule[74]=C:\Windows\system32\api-ms-win-crt-utility-l1-1-0.dll State[0].Key=Transport.DoneStage1 State[0].Value=1 State[1].Key=DataRequest State[1].Value=Bucket=-848890124/nBucketTable=373684609/nResponse=1/n FriendlyEventName=Stopped working ConsentKey=APPCRASH AppName=Wrye Bash AppPath=D:\Mopy\Wrye Bash.exe

Yes but, That it is right?

I feel confused when installing DynDOLOD In the installation guide states: "Special Installation: Manually install the contents of the main file to its own directory as any other program." "as any other program" (not mod", which i understand to install it the same way we install TES5Edit or Merge Plugin, so I just un-zip the archive and put it in the main Skyrim folder, where TESV.exe is. But when i do the merge of DynDOLOD resources, in the merge instructions statys " Left Pane Placement: Directly After Dynamic Distant Objects LOD - DynDOLOD". (which is not present in my left pane, because i have not installed it as a mod but as a program or app)So i do not know what to make of it.

The Legacy of The Dragonborn Patch Central has been update to 1.9, the installation SREL-E-LOTD still says to install 1.8, but been that a merge done for SREL-E-LOTD I wonder if, despite of the installation guide, we must install the new 1.9 version

I does not solve the issue. I dragged the Smart Souls.ini and the Fuz Ro D'oh.ini - individually to my profile folder and the files are still re-created in the Overwrite folder. I tried to drag to my profile folder the entire SKSE folder created in Overwrite folder when i close the game, and once ended the game the folder is again re-created in Overwrite folder. Any ideas?

Following the install guide, at the height of Alternate Star say to install Version: 3.1.4, but in the mod page/downloads it is only the 3.1.5a version It is safe or good to install that version?

When it comes to merge the Moon and Star patches, once in Merge Plugin Standalone, although is not said or maybe necessary i also fix errors in the main "MoonAndStar_MAS.esp" which contains a bunch of errors that Merge Plugins detects. I do not think that fixing those errors (by the build in fix errors) will do any harm, but because the installation guide does not mention it i just want to be sure I do not do any thing incorrect. It is OK to fix those errors in the main file?

I am slowly progressing through the installation guide, but every time I fire up the game for doing some test, after i get in the overwrite folder two SKSE plugins ini files for Smart Souls and Fuz Oo D'oh. I remember reading something about draping those files to the mod that correspond each one but not positive about what.. A bit of help needed

All is already now, I followed GamerPoets vid and all works fine. Great guy

Hei guys: This is not the first time i install and use Merge Plugins Standalone, but this time, I do not know why, the "Handle script Fragments" it is greyed out, the check box is unavailable. Detect integrations worked fine (I use MO, which is checked) but as I said, the Handle script integrations it is not Any ideas what am i missing?

I have one question i wonder about. I still have this issue where the trees lods pops to much when the transition from Lod to "real" trees occurs. I am playing with de "Distant" tab in Beth to see if i can find a compromise point, but i wonder if there is a way were i can "merge" the new Bet ini setting with the established one, so all other ini settings recommended by the guide does not need to be implemented again. Hope I managed to explain myself, english is not my mother tongue.

No I don't I already click (as the guide says) or checked the viwdowed mode and still that entry it is not present, in any case,this is for let your know, because i just added the entry under "Display"

No, the installation guide says to make sure that you set "bFull in skyrimPrefs.ini" Post Installation: This is only needed if you plan to run Skyrim in Windowed mode. Make sure you set bFull Screen 0 in skyrimPref.ini file And i search in my skyrimPrefs.ini and i do not have that entry, so i wonder under what it goes "Display... GamePlay.... General... etc)

After installing One tweak, the guide says: Make sure you set bFull Screen 0 in skyrimPref.ini file I have not that entry in my SkirimPrefs.ini Under which category should it go this entry?

Skyrim sets it by default to 0, from the author, it is a setting for dual monitors

I have started this new modding adventure from scratch, Skyrim installation included. Up til now I have just installed all the pre-requisites, and i have noticed, that while in exteriors when i turn aroun 360 grades the camera is smoth, but when i go in any interior, feels like the camera is seated in a serrated plate. The camera turns around in small micro-jumps, life being hooked to something and i have not the slighted idea of what can cause that. There is not mod in my mod list, i just used BethINI to configure the game inis.

When setting Beth for the first time in the Display Adapter i have to options,0 or 1 I suppose one is the integrated in the CPU and the other is my video card (gtx980), but which is which?

I am a bit surprised or confused, when we created the SKSE.ini we used this setting: [General] ClearInvalidRegistrations=1 But we do not makes this entries: Memory] DefaultHeapInitialAllocMB=768 ScrapHeapSizeMB=256 in the SKSE.ini,or it is because the SKSE.ini was created before containing those setting?

well, that is an important thing to know.... can you give any suggestion where i can start looking? Worried about that,maybe this is the reason of the popping textures and all that Well, this is an important issue, Can you give me any suggestion where to start to look for? Worried about that, maybe this is what is causing the pop issue i have

When setting the ENB organizer game path, in the exe path, Should i click in the TEV.exe or on the SKSE_Loader.exe??

I got what was happening, the INI path was set to /user name/documents.... Now seems right. One question though In Beth "Basic" tab, under display adapter, is set at 0, so i recon is trying to use the build-in processor graphics, I set to "1", although the name "Nvidia" does not shows, just "0" or "1" As i said i chose "1", hope that is the right one

Going step by step,i run BethINI and I am surprised that my ini files looks "so empty" https://imgur.com/a/XvpyX https://imgur.com/a/tV2X9 It is that right?