Installer Steam
log på
|
sprog
简体中文 (forenklet kinesisk)
繁體中文 (traditionelt kinesisk)
日本語 (japansk)
한국어 (koreansk)
ไทย (thai)
Български (bulgarsk)
Čeština (tjekkisk)
Deutsch (tysk)
English (engelsk)
Español – España (spansk – Spanien)
Español – Latinoamérica (spansk – Latinamerika)
Ελληνικά (græsk)
Français (fransk)
Italiano (italiensk)
Bahasa indonesia (indonesisk)
Magyar (ungarsk)
Nederlands (hollandsk)
Norsk
Polski (polsk)
Português (portugisisk – Portugal)
Português – Brasil (portugisisk – Brasilien)
Română (rumænsk)
Русский (russisk)
Suomi (finsk)
Svenska (svensk)
Türkçe (tyrkisk)
Tiếng Việt (Vietnamesisk)
Українська (ukrainsk)
Rapporter et oversættelsesproblem
afaik the only thing that could persist information across campaigns is profile.bin
I don't know of any mods that write to that
If mods are not enabled and user config. files have been cleared, then there's nothing to take effect
As I said, no mods loaded that changed ammo types in this fresh campaign, yet it didn't work. So it has to be global or something. Dunno.
That's pretty much my understanding, but I thought the deck that items are picked from is "generated the first time you completed the relevant proving grounds experimental project" so what mods you had loaded in a previous campaign won't matter.
The way I understand it, the pool for "select next random ammo" is global, not savegame specific, and LW had added stuff into that pool that now no longer exists because the mod is disabled. As a result, when a random ammo type was picked, I got types that no longer exist. This mod always refreshes that global pool with current ammo types. As a result, one may get the same ammo twice in a row and such. Did I get that correct?
I think the WotC Highlander fixes that, but check its change log
Use something that works
https://github.com/X2CommunityCore/xcom2-launcher/wiki/Installation
Workshop.
If you never add or remove mods during a campaign then, AFAIK, there's no point in using this mod.
Steam's probably having one of its moments. Close and restart the client, unsubscribe and re-subscribe.
Oh, and mods will only show up after they've downloaded not during.
The log file is saying:
Line 1: Trying to load game ID 268500 (XCom2), Mod ID 665435869 (Reward Decks Refresher)
Line 2: success
Line 3: Trying to load game ID 268500 (XCom2), Mod ID 667104300 ([WotC] Mod Config Menu)
Line 4: success
Line 5: Trying to load game ID 268500268500 (*invalid*, XCom2's ID twice), Mod ID *blank*
Line 6+: crash
I suspect you have a corrupted download of a mod, maybe MCM. Check D:\Games\Steam\steamapps\workshop\content\ and see if there is a folder "268500268500". Also check D:\Games\Steam\steamapps\workshop\content\268500\ for "268500" or "268500268500". None of those 3 are valid (at least not as of right now). If there is a <ModName>.XComMod file, it'll tell you what mod it thinks is there.
I would unsubscribe (via Steam workshop) any mods found in an invalid folder, delete the folder, and resubscribe. Also, look at mod problem guides like the one from this mod's description.
How to bypass the launcher:
1. In steam, right click xcom2 - properties - local files - browse local files
Open: Binaries - Win64 - Launcher
2. You should see an app called "ModLauncherWPF"
- Open it.
From here you can select XCOM2 or XCOM2 WOTC, and select mods.
3. Select XCOM 2 WOTC and ensure that Rewards Deck Refresher is selceted.
4. Launch the game.
** When you launch the game from this launcher you will get some "red screen errors". I was
able to escape out of them but just be aware that you'll probably see a few.
At this point you can load a saved game or start a new game. Doing so should allow Rewards Deck Refresher to do it's thing. You should then be able to exit the application and play from the default launcher with no issues.
[0005.50] Log: Checking DLC installation for D:\Games\Steam\steamapps\workshop\content\268500\665435869 ...
[0005.50] Log: IS INSTALLED : , YES
[0005.50] Log: Checking DLC installation for D:\Games\Steam\steamapps\workshop\content\268500\667104300 ...
[0005.50] Log: IS INSTALLED : , YES
[0005.50] Log: Checking DLC installation for D:\Games\Steam\steamapps\workshop\content\268500268500 ...
[0005.50] Log: IS INSTALLED : , YES
[0006.12] Log: Crash Detected: Dumping C:\Users\DENIS\Documents\My Games\XCOM2 War of the Chosen\Binaries\Win64\..\..\XComGame\Logs\XCom-DENIS-COMP-CL374751-2020.11.06-16.22.32-Crash\XCom-DENIS-COMP-CL374751-2020.11.06-16.22.32_Minidump.dmp
[0006.12] Log: Crash: GettingNameData
[0006.12] Log: Suspending Threads
[0006.15] Log: Writing Minidmp
[0006.34] Log: Crash: Saving Names Array
[0006.34] Log: Crash: Saving Names Array Data
Working fine here, have a read of some great Mod Troubleshooting advice
That recommends the excellent Alternate Mod Launcher [github.com] Everyone who uses mods should be using it
As well as AML's own wiki and FAQs, this guide gives some more detailed advice on using the Alternate Mod Launcher: Troubleshooting: Mods not working properly / at all
If you're using the Community Highlander then read its specific troubleshooting advice [github.com]
Yes! Exactly what I was hoping to hear! Thank you!
If the latter is true, then the issue with the Useful Autopsy mods can be solved by simply disabling Reward Decks Refresher after it does its job (I hope).
Okay, I think I understand what you're saying. I haven't looked at his code, so I'm not sure if that's what is going on. I myself have a hard time wrapping my head around template management in xcom2. It's very easy to get something slightly wrong and not know it.
It would be great if the Reward Decks Refresher included an editable exclusion list .ini to prevent this sort of thing from happening.
RequiresXPACK=true
Here is an example of it within Grimys loot mod which I also had to adjust to make it work
[mod]
publishedFileId=1142377029
Title=GrimyLootModWOTC
Description=This is a port of Grimy's Loot Mod for WOTC.
RequiresXPACK=true
Two mods you've reported don't work are working fine for me, albeit in the Character Pool.
2K's new launcher won't enable mods made in the base game's SDK, like this one, in WotC. Use the Alternate Mod Launcher.
https://www.reddit.com/r/xcom2mods/wiki/mod_troubleshooting
This mod works in WOTC, I've used it for over 1,000 hours.
PSA - If you are not using the Community Mod Launcher [github.com] instead vanilla then go check it out. It informs you of actual record conflicts and loads about 500% faster.
Yes. Compare the release dates of this and WotC.
The AML is simply checking for the presence or absence of the text "RequiresXPACK=true" in the mod's .XComMod file.
And finally, check out -bg-'s commits [github.com] to the AML.
I enabled a bunch of mods close to the end of this game, so a bit of instability might be expected. But disabling this specific mod before the expected CTD, then re-enabling it after let's you progress.