Killing Floor SDK crashing

[Equil]

I was in the middle of some map making, in the static mesh browser, when I clicked an icon which I -think- was the undock icon? Immediately after I clicked it the entire editor crashed with an error, and now whenever I attempt to start it I get another error, sometimes two errors. The game itself works fine however.

Error 1:

Build UT2004_Build_[2004-11-11_10.48]

OS: Windows NT 6.1 (Build: 7600)
CPU: GenuineIntel PentiumPro-class processor @ 3293 MHz with 2047MB RAM
Video: NVIDIA GeForce GTX 460 (9610)

General protection fault!

History: WBrowserStaticMesh::UpdateMenu <- WBrowserStaticMesh::OnSize <- WWindow::WndProc <- WWindow::StaticProc <- WWindow::WndProc <- WWindow::StaticProc <- WBrowserStaticMesh::OnCreate <- WWindow::WndProc <- WWindow::StaticProc <- PerformCreateWindowEx <- WBrowser::OpenWindow <- WBrowserStaticMesh::OpenWindow <- WM_BROWSER_UNDOCK <- WEditorFrame::OnCommand <- WWindow::WndProc <- WWindow::StaticProc

Error 2:

Build UT2004_Build_[2004-11-11_10.48]

OS: Windows NT 6.1 (Build: 7600)
CPU: GenuineIntel PentiumPro-class processor @ 3293 MHz with 2047MB RAM
Video: NVIDIA GeForce GTX 460 (9610)

General protection fault!

History: WBrowserStaticMesh::UpdateMenu <- WBrowserStaticMesh::OnSize <- WWindow::WndProc <- WWindow::StaticProc <- WWindow::WndProc <- WWindow::StaticProc <- WBrowserStaticMesh::OnCreate <- WWindow::WndProc <- WWindow::StaticProc <- PerformCreateWindowEx <- WBrowser::OpenWindow <- WBrowserStaticMesh::OpenWindow <- WM_BROWSER_UNDOCK <- WEditorFrame::OnCommand <- WWindow::WndProc <- WWindow::StaticProc <- FALVoiceModule::NoteDestroy <- UALAudioSubsystem::NoteDetroy <- ULevel::DestroyActor <- (Camera myLevel.Camera0) <- UPlayer::Destroy <- UViewport::Destroy <- (WindowsViewport Package.WindowsClient0.TerrainHeightmap) <- UWindowsViewport::Destroy <- UObject::ConditionalDestroy <- (WindowsViewport Package.WindowsClient0.TerrainHeightmap) <- UWindowsClient::Tick <- UEditorEngine::Tick <- UpdateWorld <- MainLoop

Things i've tried:

1.Verifying the SDK cache
2.Reinstalling the SDK
3.Moving/Deleting Autosave files
4.Moving/Deleting the Killingfloor.ini file like some other threads have mentioned
5.Restarting Steam
6.Restarting computer

Please help, i'm out of ideas

[Murphy]

Delete UnrealEd.ini and try again.

[Equil]

That did the trick, thank you! I looked over this because I thought reinstalling would make fresh copies of those files anyway >.<

[Murphy]

Yeah, the game means well, keeping your configurations intact, even when you reinstall.
Unfortunately these files seem to get messed up regularly and I would say a majority of gamebreaking problems people run into are caused by faulty inis and are fixed by deleting them. It's really quite weird.

What I do now, is I configure everything to my liking and then I protect my UnrealEd.ini and make it read-only!
No more white viewports, no more emitter particles not showing up for no reason, no more crashes when sound gets enabled, no more off-screen property windows,... Just no more little annoyances that are caused by a messed up ini.