Unable to add argument to executable "SKSE"

[dx1]

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.

[TechAngel85]

Your second block should never be more than 256. Additionally, in your MEMORY settings in enblocal.ini make sure ExpandSystemMemoryX64 is set to false.
 

[dx1]

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:

 

[General]

ClearInvalidRegistrations=1

[Memory]

DefaultHeapInitialAllocMB=768

ScrapHeapSizeMB=512

[Display]

;iTintTextureResolution=512

[Debug] 

WriteMinidumps=1

[interface]

; EnableContainerCategorization=1

 

enblocal.ini (shortened from [iNPUT] downwards:

[PROXY]

EnableProxyLibrary=false

InitProxyFunctions=false

ProxyLibrary=other_d3d9.dll

 

[GLOBAL]

UsePatchSpeedhackWithoutGraphics=true

UseDefferedRendering=false

IgnoreCreationKit=true

 

[PERFORMANCE]

SpeedHack=true

EnableOcclusionCulling=true

 

[MULTIHEAD]

ForceVideoAdapterIndex=false

VideoAdapterIndex=0

 

[MEMORY]

ExpandSystemMemoryX64=false

ReduceSystemMemoryUsage=true

DisableDriverMemoryManager=false

DisablePreloadToVRAM=false

EnableUnsafeMemoryHacks=false

ReservedMemorySizeMb=64

VideoMemorySizeMb=6144

EnableCompression=false

AutodetectVideoMemorySize=false

 

[WINDOW]

ForceBorderless=false

ForceBorderlessFullscreen=false

 

[ENGINE]

ForceAnisotropicFiltering=true

MaxAnisotropy=16

ForceLodBias=false

LodBias=0.0

AddDisplaySuperSamplingResolutions=false

EnableVSync=true

VSyncSkipNumFrames=0

 

[LIMITER]

WaitBusyRenderer=false

EnableFPSLimit=false

FPSLimit=60.0

 

But I'm pretty sure these INI-settings have nothing to do with MO not letting me add arguments to the SKSE executable.

[Greg]

I tested this with Mod Organizer 1.3.8 and it works fine, so I suggest removing the non-working SKSE entry.

 

I also noticed that an executable being grayed out doesn't mean that it is inactive or that it can't be edited. I searched a bit, but I don't see anything indicating why it shows certain entries grayed out like this. When I opened the Modify Executables dialog, it showed Creation Kit and Loot grayed out even though both were working fine and could be edited. I just entered a space and backspaced over it in the Start in textbox, clicked Modify, and now they're no longer gray.

[GrantSP]

It seems you are correct, there is a bug in the 1.3.9 version.

I have now installed a fresh 1.3.9 installation in Win10 and pointed it to Skyrim as the game. No matter what I do the default entries in the executables list cannot be modified.

 

I have post a Bug Report.

[GSDFan]

GrantSP beat me to the bug report.

I can also verify this, but I have noticed that this also happens with the “Overwrite Steam App ID†check box and edit field. The other two check boxes hold their states. I added this to the bug report.

[TechAngel85]

@dx1,

 

You'll find this information useful for the memory blocks:

https://forum.step-project.com/topic/634-enbseries-by-boris-vorontsov/page-9?do=findComment&comment=135635

https://forum.step-project.com/topic/634-enbseries-by-boris-vorontsov/page-9?do=findComment&comment=135670

[Tannin]

Could someone else confirm this is NOT in 1.3.8 (its currently 1:1)? There has been some work on this dialog in 1.3.9 so it's plausible this was introduced there. This bug in 1.3.8? Less plausible

[GrantSP]

1.3.8 is fine.

[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.