Jump to content

Editor won't run


Shanix

Recommended Posts

  On 2/13/2016 at 6:42 PM, jgbaxter said:

 

  On 2/13/2016 at 5:07 PM, Shanix said:

Wanna post your log file?

 

Could do with instructions.

 

Go to Steam\steamapps\common\XCOM 2 SDK\XComGame\Logs, copy the text in launch.log and paste it to pastebin, then post here.

Link to comment
Share on other sites

  On 2/13/2016 at 6:45 PM, Shanix said:

 

  On 2/13/2016 at 6:42 PM, jgbaxter said:

 

  On 2/13/2016 at 5:07 PM, Shanix said:

Wanna post your log file?

 

Could do with instructions.

 

Go to Steam\steamapps\common\XCOM 2 SDK\XComGame\Logs, copy the text in launch.log and paste it to pastebin, then post here.

 

 

Grats, not sure what I could cut. :smile:

 

Side note, it seems lately I've tried repairing and getting different results, everything is fine, then I need too files, then I need 10 files, then it's fine, then I need more files. I'm going to reinstall a few more times and likely do a primal scream.

 

  Reveal hidden contents

 

Edited by jgbaxter
Link to comment
Share on other sites

  On 2/14/2016 at 1:33 AM, Shanix said:

Oof, you've tried verifying your cache right?

Yup.

 

 

Different result every time.

 

 

I did find someone on reddit that said something worked for them, didn't for me but life is complex;

 

Try this maybe? ...

 

 

Delete the mods folder in xcom 2 sdk/xcomgame/mods then rebuild your current mod, but depends on what you add it could be your current mod that crashes the editor.

Edited by jgbaxter
Link to comment
Share on other sites

jgbaxter, you can use spoiler tag:

[spoiler]
Very long code or log
[/spoiler]

---

 

In your case I'd let Steam verify integrity of tool cache, but you already did it.

 

If you don't mind downloading around 1 GB of data, you can try this:

  • Somewhere on your hard drive create XCOM 2 SDK folder with XComGame subfolder.
  • Locate your XCOM 2 SDK installation and copy __Trashcan and Content folders to newly created XCOM 2 SDK\XComGame. This will save bandwitch and shorten download time.
  • Go to Steam > LIBRARY > TOOLS and right click on XCOM 2 Development Tools and select Properties. Go to LOCAL FILES tab and click Delete local tool content. This will uninstall all XCOM 2 SDK files.
  • Next move your newly created XCOM 2 SDK\XComGame containing __Trashcan and Content folders to a place, where you are going to install the SDK. It will be in Steam(SteamLibrary)\steamapps\common folder.
  • Install the SDK by going to Steam > LIBRARY > TOOLS and right click on XCOM 2 Development Tools and select Install game. Point the installation to drive, where you moved files. You should see Steam discovering files. Steam will say it is going to download over 42 GB, but it will be less, 1 or 2 GB.
Edited by Drakous79
Link to comment
Share on other sites

Hi there, I've been having the same problem with XCom 2 editor not opening. Tried most of the same solutions and was finding files needed verification after every run. Just managed to get it to run again by verifying both cahes (SDK & game) and emptying my Steam\steamapps\common\XCOM 2 SDK\XComGame\mods folder. Going to try and reload the upk I was working on and see what happens.

 

Update:

New to modding so going to post my entire process here since I can't be sure exactly what is relevant

 

-Loaded up my UPK and made some changes; removed a couple of files I was experimenting with, saved and closed editor, no problems.

-Loaded mod in modbuddy and built solution. Did NOT debug; went straight into tools and tried to open XCom2 Editor again

-Same error as before, would not load

-Deleted contents of Steam\steamapps\common\XCOM 2 SDK\XComGame\mods folder.

-Tried to run editor: success

-Loaded my mods UPK, removed Caucasian skin texture & commented out reference to it in modbuddy. All other files had worked in a previous version.

-Saved & built.

-Tried to run editor: Failed

-Deleted UPK files only from mods folder

-Tried to run editor: Failed

-Deleted contents of mods folder again

-Tried to run editor: success

 

So, at this point I'm pretty sure it's something in my mod but not the UPK. Anyone know what else the editor might reference?

Update 2:

Trial and error time, yaaaay...

 

-removed src folder: still broken
-removed localisation folder: still broken

-removed config folder: Working!

-Build solution, removed config\XcomEngine.ini: still broken
-removed config\XcomEditor.ini (I have a good feeling about this one!): still broken

-removed config\XcomGame.ini:

-Build solution, removed config\XcomContent.ini only: Working!

 

OK so here's my XcomContent.ini (don't worry it's a small mod):

 

 

  Reveal hidden contents


And we're off again:
-Deleted all text to check for file corruption (maybe this isn't my fault somehow?): Working

-FINE.
-Replaced all text, removed all comment lines after ;Attempt to change colour palette options for skin: Working
-Replaced all text, deleted everything above ;Attempt to change colour palette options for skin: Broken

-Replaced all text, deleted line: ;[XComGame.XComContentManager] : working

-commented out [XComGame.X2BodyPartTemplateManager] : Working

-Added line: [XComGame.XComContentManager] :Broken

 

So, my conclusion is this: the line [XComGame.XComContentManager] in XcomContent.ini somehow breaks the editor, even if commented out. The question is, does this fix anyone elses problem? Or are there other lines that might be causing this problem?

 

 

 

TLDR: Try DELETING (not commenting out) this line from your XcomContent.ini if it's there:

[XComGame.XComContentManager]

If not, try deleting similar lines (after making a backup) and see if it helps.

Edited by Grubbyfoot
Link to comment
Share on other sites

Same flaws here with XComEditor not loading.

 

Strangely, i have a similar [XComGame.XComContentManager] problem since i'm just trying to expand some Palettes.

 

What gives!?! :sad:

 

EDIT: Well -- after deleting the "qUICk_CLR" mod folder from the XCom2 SDK directories of Mods... the loading process went as far as the PEForce server warning where i had once clicked to NOT verify such a LogIN step. So this step may also be one of the tricky things that prevent the UE3 editor from starting up correctly even if some the files (like **Content.INI) have unacceptable flaws.

 

I would guess some of the Palettes archetypes aren't moddable at all.

Edited by Zyxpsilon
Link to comment
Share on other sites

That's weird. What happens, when your XComContent.ini contains only single line:

[XComGame.XComContentManager]

?

Edited by Drakous79
Link to comment
Share on other sites

  • Recently Browsing   0 members

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