the debug actions menu isn't working

[Discount Duo]

when i try to open it, it just opens up the error log

[Canute]

Hi,
when you use mods, one of the mods cause errors so it can't open it. Take a look at the error maybe it show you a modname then try to deactivate that mod.
If you have no clue, check if the problem still happen on a new colony (use the hugslib quickstart feature the top right icon to create pretty fast test colonies).
Then deactivate mod until you can use the debug menu again and identify the mod at this way.
50% methode is very effective (half of the mods). Maybe deactivate all none 1.2 mods at first.

If the problem happen without mods, manual delete the Data folder at the rimworld installation and reinstall/repair the installation.
If you still got problems try to delete the Config folder at the saved data location.

[Discount Duo]

this is what comes up

Exception filling window for Verse.ImmediateWindow: System.TypeLoadException: Could not resolve type with token 0100001e (from typeref, class/assembly OgsCompOversizedWeapon.CompOversizedWeapon, 1CompOversizedWeapon, Version=1.18.0.0, Culture=neutral, PublicKeyToken=null)
  at (wrapper managed-to-native) System.Reflection.MonoMethodInfo.get_method_info(intptr,System.Reflection.MonoMethodInfo&)
  at System.Reflection.MonoMethodInfo.GetMethodInfo (System.IntPtr handle) [0x00000] in <567df3e0919241ba98db88bec4c6696f>:0
  at System.Reflection.MonoMethod.GetPseudoCustomAttributes () [0x00002] in <567df3e0919241ba98db88bec4c6696f>:0
  at System.MonoCustomAttrs.GetPseudoCustomAttributes (System.Reflection.ICustomAttributeProvider obj, System.Type attributeType) [0x0000a] in <567df3e0919241ba98db88bec4c6696f>:0
  at System.MonoCustomAttrs.GetCustomAttributesBase (System.Reflection.ICustomAttributeProvider obj, System.Type attributeType, System.Boolean inheritedOnly) [0x0001f] in <567df3e0919241ba98db88bec4c6696f>:0
  at System.MonoCustomAttrs.GetCustomAttributes (System.Reflection.ICustomAttributeProvider obj, System.Type attributeType, System.Boolean inherit) [0x00037] in <567df3e0919241ba98db88bec4c6696f>:0
  at System.Reflection.MonoMethod.GetCustomAttributes (System.Type attributeType, System.Boolean inherit) [0x00000] in <567df3e0919241ba98db88bec4c6696f>:0
  at Verse.GenAttribute.TryGetAttribute[T] (System.Reflection.MemberInfo memberInfo, T& customAttribute) [0x00000] in <d72310b4d8f64d25aee502792b58549f>:0
  at Verse.Dialog_DebugActionsMenu..ctor () [0x0003e] in <d72310b4d8f64d25aee502792b58549f>:0
  at Verse.DebugWindowsOpener.ToggleDebugActionsMenu () [0x0001c] in <d72310b4d8f64d25aee502792b58549f>:0
  at (wrapper dynamic-method) Verse.DebugWindowsOpener.Verse.DebugWindowsOpener.DrawButtons_Patch0(Verse.DebugWindowsOpener)
  at Verse.ImmediateWindow.DoWindowContents (UnityEngine.Rect inRect) [0x00000] in <d72310b4d8f64d25aee502792b58549f>:0
  at Verse.Window.InnerWindowOnGUI (System.Int32 x) [0x00165] in <d72310b4d8f64d25aee502792b58549f>:0
Verse.Log:Error(String, Boolean)
Verse.Window:InnerWindowOnGUI(Int32)
UnityEngine.GUI:CallWindowDelegate(WindowFunction, Int32, Int32, GUISkin, Int32, Single, Single, GUIStyle)

i have no idea what it means

Respectfully,
Duo

[Canute]

Me either, but if you look closer you will see "Oversizedweapon".
I found
JecsTools (SMM uses the oversizedWeapon comp for some weapons)

So the problem is either you use the wrong jecstools or one of the weapon mods that use jecstools cause the problem.
But you need to find the mod, with deactivation mod until the problem disappear.

[Discount Duo]

i disabled jecstools and any mod that requires it but it still isn't working

[Canute]

On your existing safe or on a new colony ?
And it is the same error with "Oversizedweapon" ?

At the error msg. there is "DrawButtons_Patch0" too. Use CTRL-F12 to use the hugslib feature to upload the modlist,patchlist and logfile. Open it and search for "DrawButtons_Patch0".
Maybe that lead you to a modname.

If you don't found any, you need to disable mod until you can use the debug menu on a new colony.

[Discount Duo]

the error comes up on the main menu as well though

[Canute]

Then the best way would be, deactivate all mods (delete modconfig.xml or use an Rimpy to modify your modlist before you start rimworld).
Then rebuild your modlist at small steps and verify that no error appear at the log after the activation and if the debug menu is working.
Better don't use mod's that throw out error's after activation.