:\ It now reflects the no worky state I got intoĪfter this step Launch KSP with the KSP_圆4_Dbg.exe and check that you have "Development Build" in your lower right corner I went back to checked i hadn't typoed || fat fingered or something and my outputlog.txt was different. How and when do outputlog.txt get created. I now have slightly different problem then. So if you are seeing 2017.1.3p1 in your logs something is definitively wrong with your install. After reinstalling KSP to ensure that it was 'fresh', doing the same worked. I remembered that I also had to copy over UnityPlayer.dll and WinPi圎ventRuntime.dll, but it didn't work the first time.
I'm going to give up and wallow in my frustration for nowĮDIT: Managed to figure it out. Unable to find corresponding location." Debugging information is set to Portable, if that matters. I tried the simplified method by and it let me attach through Visual Studio at least, but when I use breakpoints I get "The breakpoint will not currently be hit. Am I using the wrong version of Unity? According to this and the details tab of the properties of the ksp. What's more frustrating is that the same procedure works immaculately for KSP 1.9. Worst of all, I'm getting no error message telling me what's wrong, it's just completely silent. The development mode label and console isn't there, and I can't attach the Unity instance to Visual Studio. When I launch through the debug exe, KSP launches as if it's through a normal install. And renamed WindowsPlayer.exe to KSP_圆4_Dbg, and edited player-connection-debug=1 into the nfig.
I linked KSP_圆4_Data to KSP_圆4_Dbg_Data, moved WindowsPlayer.exe from windowsstandalonesupport\Variations\win64_development_mono in my Unity 2019.2.2f1 install. I'm trying to make a debug installation out of a fresh installation of 1.8.1.
0 kommentar(er)
