-
Notifications
You must be signed in to change notification settings - Fork 97
Development Guide
Developing Kisak-Strike is easy and fun. With full CMake integration: code highlighting, code completion, and Usage tracing all become blazing fast with the right tools. This article is a short guide on what I(LWSS) use to tinker with Kisak-Strike.
Kisak-Strike was made specifically with CLion IDE integration in mind. It is closed-source software, however it has a 30 day free-trial and is bundled with the required Java making it easy to download and instantly run.
** Gamer Tip: If you ever experience lag or want to prevent it, Go to Help->Change Memory Settings in the top-bar. Change it to something higher **
A possible alternative could be QtCreator if you can't stand running something closed-source - However it is definitely not as good.
Clang has not been tried, install GCC!
https://github.com/apitrace/apitrace - This is the only decent tool for OpenGL debugging. It lets you record and playback the entire OpenGL state machine. Mainly useful for comparing states and seeing what changed.
https://www.hex-rays.com/products/ida/support/download_freeware/ - Useful for seeing exactly what instructions the compiler generated and also to reverse engineer the retail game. The free version only lacks IdaPython and Debugging from what I can tell and of course there is no hexrays bundled. Keep in mind any monetization is prohibited with the free version. One more thing, don't run this software on any company network, they will detect your IP range as business-class and ask for compensation.
Tracy profiler support has been enabled. Build your game with USE_TRACY and build the Tracy Server(a Graphical program) in /thirdparty/tracy*/profiler/build/unix.