Jump to content

Troubleshooting project build


Azworai

Recommended Posts

There are some rather jaw-dropping bugs in the software. The duplicates thing sounds like a headache, glad I haven't encountered it yet.

 

The thing that's driving me nuts is when you have a build error, and double-click a line to jump to it, any changes I make to that file are forgotten. It's like it opens up some parallel-dimension version of that file and then promptly forgets about it.

Link to comment
Share on other sites

There are some rather jaw-dropping bugs in the software. The duplicates thing sounds like a headache, glad I haven't encountered it yet.

 

The thing that's driving me nuts is when you have a build error, and double-click a line to jump to it, any changes I make to that file are forgotten. It's like it opens up some parallel-dimension version of that file and then promptly forgets about it.

 

The thing that's happening here, I think is the following :

 

1) Your src files are stored in your project folder

2) The build script copies your src files to the XCOM 2 SDK / Development folder, where they have to be to be compiled by UDK.

3) The build errors end up pointing to the copies in said Development folder, so if you make changes to them, they are in the wrong place

4) When you hit build again, the src files in Development are deleted and overwritten with what is in the project

Link to comment
Share on other sites

So... seems modbuddy deleted one of my script folders. Bravo Modbuddy, bravo... and when I attempt to make the new one from scratch, Modbuddy asks if I want to overwrite the existing file, that it tells me doesn't exist when I try to work with it.

Link to comment
Share on other sites

 

There are some rather jaw-dropping bugs in the software. The duplicates thing sounds like a headache, glad I haven't encountered it yet.

 

The thing that's driving me nuts is when you have a build error, and double-click a line to jump to it, any changes I make to that file are forgotten. It's like it opens up some parallel-dimension version of that file and then promptly forgets about it.

 

The thing that's happening here, I think is the following :

 

1) Your src files are stored in your project folder

2) The build script copies your src files to the XCOM 2 SDK / Development folder, where they have to be to be compiled by UDK.

3) The build errors end up pointing to the copies in said Development folder, so if you make changes to them, they are in the wrong place

4) When you hit build again, the src files in Development are deleted and overwritten with what is in the project

 

 

That makes sense. I just wish the editor was intelligent enough to reconcile and jump to the line in the file in your current solution. I'm scratching my head thinking of any use they would have doing it the current way.

Link to comment
Share on other sites

So... seems modbuddy deleted one of my script folders. Bravo Modbuddy, bravo... and when I attempt to make the new one from scratch, Modbuddy asks if I want to overwrite the existing file, that it tells me doesn't exist when I try to work with it.

 

You may want to check the filesystem to see if the file/folders are present or not. ModBuddy may have just lost it project-wise, even if it's really in the filesystem. I think you can do a File > Open > File in Modbuddy to re-add files and folders back into Modbuddy.

Link to comment
Share on other sites

The file exists in modbuddy apparently, with all the scripting intact... but when I go INTO modbuddy and open the project, it does not appear.

 

Edit: went through modbuddy to re-add the file to the project and am attempting a build now.

Edited by Azworai
Link to comment
Share on other sites

 

 

2) The build script copies your src files to the XCOM 2 SDK / Development folder, where they have to be to be compiled by UDK.

 

That is explanatory, but unbelievable. I don't know of any other compiler which *has* to copy files from your directory to its own directory in order to compile.

Link to comment
Share on other sites

Building but non executing code is generally a normal step in the process of building a mod ^_^. At least it's not causing the game to CTD, which is a frequent occurrence for me...

 

So yes, if you want more concrete feedback, you'll likely need to post the specific code so we can try and pick apart why it isn't functioning as expected.

Link to comment
Share on other sites

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...