{"action":"created","issue":{"url":"https://api.github.com/repos/loot/loot/issues/463","labels_url":"https://api.github.com/repos/loot/loot/issues/463/labels{/name}","comments_url":"https://api.github.com/repos/loot/loot/issues/463/comments","events_url":"https://api.github.com/repos/loot/loot/issues/463/events","html_url":"https://github.com/loot/loot/issues/463","id":93023614,"number":463,"title":"v0.7.1 won't load in ModOrganizer.","user":{"login":"ROODAY","id":5439867,"avatar_url":"https://avatars.githubusercontent.com/u/5439867?v=3","gravatar_id":"","url":"https://api.github.com/users/ROODAY","html_url":"https://github.com/ROODAY","followers_url":"https://api.github.com/users/ROODAY/followers","following_url":"https://api.github.com/users/ROODAY/following{/other_user}","gists_url":"https://api.github.com/users/ROODAY/gists{/gist_id}","starred_url":"https://api.github.com/users/ROODAY/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/ROODAY/subscriptions","organizations_url":"https://api.github.com/users/ROODAY/orgs","repos_url":"https://api.github.com/users/ROODAY/repos","events_url":"https://api.github.com/users/ROODAY/events{/privacy}","received_events_url":"https://api.github.com/users/ROODAY/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":1,"created_at":"2015-07-04T15:51:13Z","updated_at":"2015-07-04T16:27:34Z","closed_at":null,"body":"I was using 0.6.1 without any issues before I noticed the upgrade message, which I then followed and installed 0.7.1. I'm able to run LOOT.exe on its own without a problem, but running it in ModOrganizer opens a blank LOOT window, and nothing from the LOOT interface loads. Here's a screenshot of it looks like for me. \r\n![Broken LOOT in MO](http://i.imgur.com/mCjQjCB.png)\r\nIs this a known issue?"},"comment":{"url":"https://api.github.com/repos/loot/loot/issues/comments/118528070","html_url":"https://github.com/loot/loot/issues/463#issuecomment-118528070","issue_url":"https://api.github.com/repos/loot/loot/issues/463","id":118528070,"user":{"login":"pStyl3","id":10406657,"avatar_url":"https://avatars.githubusercontent.com/u/10406657?v=3","gravatar_id":"","url":"https://api.github.com/users/pStyl3","html_url":"https://github.com/pStyl3","followers_url":"https://api.github.com/users/pStyl3/followers","following_url":"https://api.github.com/users/pStyl3/following{/other_user}","gists_url":"https://api.github.com/users/pStyl3/gists{/gist_id}","starred_url":"https://api.github.com/users/pStyl3/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/pStyl3/subscriptions","organizations_url":"https://api.github.com/users/pStyl3/orgs","repos_url":"https://api.github.com/users/pStyl3/repos","events_url":"https://api.github.com/users/pStyl3/events{/privacy}","received_events_url":"https://api.github.com/users/pStyl3/received_events","type":"User","site_admin":false},"created_at":"2015-07-04T16:27:34Z","updated_at":"2015-07-04T16:27:34Z","body":"Try to add the \"--single-process\" argument (without quotes) to LOOT within MO's \"Modify Executable\" window. This should bypass the problem!\r\n\r\nAside from the mentioned \"fix\" above, does this happen every single time you start MO? Or did you 'start MO via downloading a mod from Nexus priorly', so that MO wasn't running when you clicked on 'Download with Manager' .. and thus, got started that way?\r\n\r\nAlso, where do you have Steam/MO/LOOT installed to? Please provide file paths."}}