AarinFaust Posted January 19, 2016 Share Posted January 19, 2016 Longwar 1.0, no other mods. Enemy Within installed, but no other DLC (e.g., no Slingshot). INI edits to lower will loss from critical wounds to 0 and put Arc Throwers in the pistol slot. When I attempt to enter a terror mission, the loadout etc. part happens normally. However, once the skyranger flies and I hit "Begin Assault," the load screen comes up and INSTANTLY says Launch Mission (as if it has finished loading). If I click it, it takes me to the hologlobe though without a UI. Escape doesn't enter the menu etc., all I can do is force exit with Alt+F12. Third time this has stopped a campaign. This time it let me do a couple terror missions before this issue came up. I imagine that it isn't loading a map properly or something. I guess I can just skip this mission and sacrifice the U.K., but I would prefer not to, especially with the fear that this might just happen against next time and I'll be wasting my time. I have tried fresh installs of both LW and XCOM. This has stopped several campaigns in their tracks and I'm getting frustrated. I would greatly appreciate any help. Link to comment Share on other sites More sharing options...
dubiousintent Posted January 21, 2016 Share Posted January 21, 2016 Standard boilerplate LW response follows:Long War bug reports should be checked first in the "Long War" download page "Bugs section" and then in the appropriate Beta Feedback thread in it's "forum section" before posting to ensure a response. (The LW Team has stated they don't check the main forum at all anymore for problems. Really, the dev team is the most likely to be able to help with a LW issue but anyone else who can also will be there.) You may also find that the answer is already known and posted in those sections.Check that you have Steam in "offline" mode.Review the "checklist" in the "Basic Guide" (see below).Disable your Anti-Virus while installing.Be sure to read the "Readme" and "Detailed Troubleshooting" documents included with the LW download before reporting bugs. They need all the information requested there (including which OS platform: Windows, Linux, OS/X, ARM/IOS, etc.) to be able to help. If they can't reproduce the problem, they can't fix it. You increase your odds of getting help by re-reading included documentation and following instructions on reporting bugs, and then documenting what you have already tried ... in detail. Short "it's broke" reports simply generate requests for more detail; wasting time. Better too much detail than not enough. (Remember: This is all volunteer support, including the LW dev team. If you won't put in the effort to provide a good bug description, why should they spend time prying it out of you if it sounds vague enough to likely be something covered already?)While the LW installer handles any code modifications for you, it is still necessary to prepare your system for mods as laid out in the wiki article "Basic Guide to installing mods". The "Environment" section in particular still applies to LW, and the "OS/X mod installation" section has specifics for Mac versions. There is also a "Linux Differences" section. -Dubious- Link to comment Share on other sites More sharing options...
Recommended Posts