After installing LuaDKMDebugger latest release (0.8.2) all options in the extensions menu are greyed out.

[McKillroy]

As the title says: I can't activate it anymore after installing.
All options are greyed out.
The version before worked, though it slowed down debugging significantly.

[WheretIB]

Can you please check that all Visual Studio background tasks are completed before you go into the menu options (click on lower left corner button)?

Visual Studio might delay extension initialization until all tasks are completed.

In any case, I will still check if it's possible to enable options before extension is loaded completely.

The version before worked, though it slowed down debugging significantly.

What part of debugging was slowed down?
Was it the application launch, Lua execution speed or something else?

[McKillroy]

I just tried waiting for all the tasks to finish, but the options were still greyed out when I tried after them being done. I didn't try anything beforehand - I just started VS, waited until everything was ready and then tried to activate the Debugger, but it was impossible.

Concerning slowing down: Basically the entire application was slowed down extremely, not just a bit like what would be expected when running a debugger. Progress was so slow, it was not debuggable with medium to large workloads. It still is useful for finding certain bugs, but slow - yes. It could have been the Lua execution speed, since we use Lua for the majority of the workload in the moment. I'm not sure what exactly it was.

[WheretIB]

What version of Visual Studio do you use?

[WheretIB]

I have published an update (0.8.7) which includes an 'Initialize...' button that is displayed before Visual Studio finishes initialization of the extension, you can try using that to check if that helps.

Performance of the Lua applications should also improve when breakpoints are not set inside the scripts.

[McKillroy]

The initialize option works nicely.
My VS version is the community edition before the current update, so - pretty recent.
I didn't have time for another speed test yet. Will do ASAP.

[McKillroy]

I did another speed test - it's still very slow when calling a lot into Lua - even without using breakpoints.
And for some reason it didn't reliably show the Lua scripts. Sometimes when stopping the debugger I saw function calls inside the Lua VM, but not the scripts running these calls.
I had this working in the past at least sometimes.
I think it needs further development and fixes to be fully usable. For now I have it disabled, but I will check it out from time to time. I totally like the idea of the tool - when it works it's very useful.

[WheretIB]

I have fixed a performance issue with Lua coroutines.
This might be the slowdown you have experienced in your application.

New v0.9.3 release can be downloaded here (vsix file)
It will appear in the Visual Studio Marketplace in a few days.