Skip to content

v1.3.0

Choose a tag to compare

@blueshank-gh blueshank-gh released this 04 Aug 15:59
· 18 commits to master since this release
de7bbe9

What's Changed

  • feature - high performance profiler for c -> lua transitions by @blueshank-gh in #21

Full Changelog: v1.2.2...v1.3.0

Warning

We recommend not using "require" GMCL on single-player, as the pause mechanics break the watchdog.
We are working on fixing this by detecting for single-player pause mechanics.
Please see #10 for further tracking of this problem.

This contains a new high performance runtime profiler.
Unlike traditional profilers such as lua-based profilers to vprof, this can be run with virtually no noticeable performance loss.
Implementation of #19
Fixes #12

Using the profiler functions you can create your own high performance profiler dashboard like this:

{F803B7FD-367C-46FA-963F-6BD597BFCB88}

high performance profiler dashboard example

Windows

  1. Rename the CL/SV binary into version.dll and place it near the executable of garry's mod
  2. Rename the CL/SV binary as gm(cl/sv)_crashcapture_win(32/64).dll and place it in the lua/bin folder for require
  3. Place the SV binary as a plugin in lua/bin folder and create a .vdf in the addon's folder to load it
  4. Inject the CL/SV binary into the garry's mod process

Note

Some garry's mod branches contain different locations for where gmod.exe real executable may be.
For no.1, we recommend that you do not place crash capture next to the gmod.exe launcher

Linux

  1. Rename the CL/SV binary as gm(cl/sv)_crashcapture_linux(null/64).dll and place it in the lua/bin folder for require
  2. Place the SV binary as a plugin in lua/bin folder and create a .vdf in the addon's folder to load it
  3. Inject the CL/SV binary into the garry's mod process

Note

Client native linux builds are experimental due to a lack of testing infrastructure.