Skip to content

Commit 48ed8d2

Browse files
Add new debugger for Unity 2019
1 parent ba51c74 commit 48ed8d2

11 files changed

Lines changed: 26 additions & 1 deletion

File tree

338 KB
Binary file not shown.
Binary file not shown.
994 KB
Binary file not shown.
2.6 MB
Binary file not shown.
Lines changed: 12 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,12 @@
1+
Quoted from JPLRepo
2+
1) Install 2019.2.2f1 to utilise these two exe's to convert the pdb to mdb:
3+
<install directory>\Editor\Editor\Data\MonoBleedingEdge\bin\mono.exe
4+
<install directory>\Editor\Editor\Data\MonoBleedingEdge\lib\mono\4.5\pdb2mdb.exe
5+
6+
2) Unity No longer uses PlayerConnectionConfigFile instead you edit boot.config file (in the data directory where this file used to go) and add the line:
7+
player-connection-debug=1
8+
9+
3) For the game exe. You must copy the WindowsPlayer.exe (rename if you want) UnityPlayer.dll and WinPixEventRuntime.dll into the KSP install directory.
10+
11+
4) Execute this sequence:
12+
"C:\Program Files\Unity\Editor\Data\MonoBleedingEdge\bin\mono.exe" "C:\Program Files\Unity\Editor\Data\MonoBleedingEdge\lib\mono\4.5\pdb2mdb.exe" "$(TargetFileName)"
3.95 MB
Binary file not shown.
513 KB
Binary file not shown.
59 KB
Binary file not shown.
Lines changed: 13 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,13 @@
1+
rem Generate the MDB file needed by UnityVS and Monodevelop for debugging
2+
3+
@echo off
4+
5+
rem get parameters that are passed by visual studio post build event
6+
SET TargetName=%1
7+
8+
rem make sure the initial working directory is the one containing the current script
9+
SET scriptPath=%~dp0
10+
11+
echo Generating Unity Monodevelop Debug file...
12+
echo %TargetName%.dll -^> %TargetName%.dll.mdb
13+
"%scriptPath%\mono.exe" "%scriptPath%\pdb2mdb.exe" %TargetName%.dll
3.75 MB
Binary file not shown.

0 commit comments

Comments
 (0)