CSE Crash when opening scripts dialogue

[Ironman5000]

This has bugging me lately and can't pinpoint the cause so I will ask here - I use CSE often for modding but when I want add scripts I have to close and just use the CS, as the extender 'scripts' dialogue crashes the program with this 'Assertion Failed' message

New Workspace == nullptr

at Workspace.Container.InitiateNewWorkspace(ScriptData*InitScript)
at Workspace.Container..ctor(ScriptData*InitScript, UInt32 PosX, UInt32 PosY, UInt32 Width, UInt32 Height)
at
ScripteditorManager.AllocateNewWorkspaceContainer(ScriptData*InitScript, UInt32 PosX, UInt32 PosY, UInt32 Width, UInt32 Height)
at ScripteditorManager.PerformanceOperation(OperationType Op, OperationParams Parameters)
at <module>.InstantiateEditor(ScriptData*InitScript, UInt32 PosX, UInt32 PosY, UInt32 Width, UInt32 Height)

 

It's more of a pain now i'm adding new magic effects because after making them the old CS doesn't recognise them and deletes them

I have Abort, Retry, Ignore as the options and none are helpful.

Does anybody know why this happens and how I can fix it? I am using the required OBSE 21 Beta.

[eric31415]

I just tested this. CSE will open the script dialog no problem for me.

 

If both CSE and OBSE have full read/write privileges, and running as admin doesn't help, then I would redownload CSE and OBSE and reinstall them.

 

Edit - Try reinstalling the NET Framework 4.0, Microsoft Visual C++ 2010, and DirectX requirements first. It is possible that another program has made changes to one of these.

Edited September 19, 2013 by eric31415