Debug mode not starting

[ElDiabl00]

I just started my hand at modding with this, trying to add a single flag to the game by hand of the following tutorial.

 

https://youtu.be/ynTcLuVEM9g

 

however when i get to the debug stage of process nothing seems to be happening.

 

the bottom window just says: ------ Build started: Project: Borflags, Configuration: Default XCOM 2 ------

 

and otherwise it just says Build Started or Ready at the blue bar all the way at the bottom.

 

i also cannot do or exit the modbuddy program. saying the build needs to be stopped before i can. The only manner to do this is to open Taskmanager and end the XcomGame.com Or XcomGame.exe process in task manager.

 

the debug game start DOES seem to work if i try to run it for a completely empty mod project.

 

hopefully someone can explain what i might have done wrong

[serratemplar]

i also cannot do or exit the modbuddy program. saying the build needs to be stopped before i can. The only manner to do this is to open Taskmanager and end the XcomGame.com Or XcomGame.exe process in task manager.

Is XCOM 2 (the game) running when you're running the build? If you try to start Debug mode - which will trigger a build - and the XCOM exe is running, it's going to sit and wait...because the XCOM game exe locks resources that ModBuddy needs to run its build.

 

Make sure XCOM's not running then try your build. :)

 

If that's not the issue, first thing I'd check is my SDK's installation: in particular, make certain that the paths you need to set (to the SDK and the game) are set correctly.

 

I hope this helps!

[ElDiabl00]

no it isn't running. the XcomGame.exe is started when i press build or debug but basicly just sits there frozen in precceses tab of Taskmanager when u check.

 

and the paths are correctly set. as said when i run debug or build on a completle empty mod project the game does start in debug mode as it should.

[serratemplar]

I see. Not so bad then. :) Probably just a bug in your code.

The general strategy is to start commenting out stuff you've added until you end up with something that you can build and run (even if it's all the way down to an empty project). Since you *know* empty projects can run, you can use this approach to find which line of your code is the culprit. That's what I'd do. :)

[ElDiabl00]

I see. Not so bad then. :smile: Probably just a bug in your code.

 

The general strategy is to start commenting out stuff you've added until you end up with something that you can build and run (even if it's all the way down to an empty project). Since you *know* empty projects can run, you can use this approach to find which line of your code is the culprit. That's what I'd do. :smile:

 

i would think that, however shouldn't it just give an error or something instead of just freezing endlessly. Also the same things happen when i try to debug the given Exampleweapon mod file for example.

 

Isn't there a working mod i can download somewhere that has the working Mod Projectfile with it. so i can see if that debugs properly?

Edited February 26, 2016 by El Diabl00

[davidlallen]

 

 

Isn't there a working mod i can download somewhere that has the working Mod Projectfile with it. so i can see if that debugs properly?

Yes, that is the purpose of the example weapon mod. So the goal is to figure out why that freezes. Suppose you exit xcom2, and start modbuddy, and choose the build -> build solution menu choice. At the bottom you will see "Build Started", then some messages, then theoretically "Build Finished". Do you see that? If it hangs indefinitely, then this doesn't have anything to do with starting the game in debug, the problem is purely within modbuddy.

[serratemplar]

 

I see. Not so bad then. :smile: Probably just a bug in your code.

 

The general strategy is to start commenting out stuff you've added until you end up with something that you can build and run (even if it's all the way down to an empty project). Since you *know* empty projects can run, you can use this approach to find which line of your code is the culprit. That's what I'd do. :smile:

 

i would think that, however shouldn't it just give an error or something instead of just freezing endlessly. Also the same things happen when i try to debug the given Exampleweapon mod file for example.

Well, if it's a compile/build time error, yea it'll give you a message. But run-time errors can manifest in other ways, like crashes or freezing. It does make them more annoying to track down, I'll grant you.

 

Follow davidlallen's advice there and let us know what you see.

[ElDiabl00]

 

Isn't there a working mod i can download somewhere that has the working Mod Projectfile with it. so i can see if that debugs properly?

Yes, that is the purpose of the example weapon mod. So the goal is to figure out why that freezes. Suppose you exit xcom2, and start modbuddy, and choose the build -> build solution menu choice. At the bottom you will see "Build Started", then some messages, then theoretically "Build Finished". Do you see that? If it hangs indefinitely, then this doesn't have anything to do with starting the game in debug, the problem is purely within modbuddy.

 

 

Thank you. Using the ExampleWeapon mod and following your instructions it just goes to "Build started..." at the bottom then nothing it just stays like that without any other messages and the little keyboard looking icon think just doing it's animation next to Ln1. I can no longer exit or do much in modbuddy since it will pop up with "The build must be stopped before the solution can be closed" The only way i have found to do this is to close XcomGame.exe or XcomGame.com in the Task manager which will cause it to say Build failed and put this:" ========== Build: 0 succeeded or up-to-date, 1 failed, 0 skipped ========== " in the output window

[davidlallen]

I don't know the answer, but at least we have narrowed down the problem. Maybe, try to validate the local files for the sdk?

[serratemplar]

Sounds like the build process (that gets forked off by the IDE) is bombing. Did you install both of the redistributables as instructed? Are your paths set up?