Ошибка unable to create the error report

• пожаловаться
• скопировать ссылку

• пожаловаться
• скопировать ссылку

• пожаловаться
• скопировать ссылку

Лерок
Пора кончать с наркотой

• пожаловаться
• скопировать ссылку

• пожаловаться
• скопировать ссылку

• пожаловаться
• скопировать ссылку

• пожаловаться
• скопировать ссылку

• пожаловаться
• скопировать ссылку

• пожаловаться
• скопировать ссылку

такая же проблема. не могу поиграть. есть строчка с хп, прицел и какие то текстуры в виде облаков. видно только меню помимо этого(при нажатии Esc) при запуске тоже самое — куски от видео и брызги крови. но в основном черный экран с пикселями. пробовала переустановить, сделала проверку файлов, все-равно та же музыка =___=

• пожаловаться
• скопировать ссылку

• пожаловаться
• скопировать ссылку

• пожаловаться
• скопировать ссылку

• пожаловаться
• скопировать ссылку

• пожаловаться
• скопировать ссылку

• пожаловаться
• скопировать ссылку

CockroacH21rus
отключение не помогает. я там все и отключала и включала, в разных комбинациях(((

• пожаловаться
• скопировать ссылку

• пожаловаться
• скопировать ссылку

• пожаловаться
• скопировать ссылку

snec да пока эти патчи будут, а поиграть то охота сейчас (

У мну такая проблема: Почти начало игры нужно добратся до бункера с имперцам, доходим до него и изображение мутнеет, сбоку справа появляется надпись загрузка и дальше тупо грузит,грузит,грузит… и так до посинения, я хз чё делать(

• пожаловаться
• скопировать ссылку

У меня не хочет в игру заходить((( во время ролика ошибка вылетела и всё(

• пожаловаться
• скопировать ссылку

• пожаловаться
• скопировать ссылку

Мне вот с этим — http://steamcommunity.com/id/lightingshadow/screenshot/577807679161458017/? кто-нибудь сможет помочь?Видеокарта HD 5550,драйвера самые свежие.

UPD.Нашел путь вслепую,дошел до чего-то там.Появилась надпись «Загрузка…»( http://steamcommunity.com/id/lightingshadow/screenshot/577807679162449442 ).Но до сих пор ничего не загрузилось,и это притом,что начало миссии загружается довольно быстро.Плюс эта самая долгая,если не бесконечная,»Загрузка» может появляться,если попробовать выйти в меню или загрузиться с чекпоитна.В мультиплеер тоже по этой причине зайти не могу,зато почему-то могу «наслаждаться» пердежом других игроков,у которых есть микрофон.

• пожаловаться
• скопировать ссылку

• пожаловаться
• скопировать ссылку

Народ, а у меня вообще игра незапускается ;D
Захожу в игру, на секунду черный экран, и всё..

• пожаловаться
• скопировать ссылку

• пожаловаться
• скопировать ссылку

• пожаловаться
• скопировать ссылку

• пожаловаться
• скопировать ссылку

• пожаловаться
• скопировать ссылку

• пожаловаться
• скопировать ссылку

Как поставит разрешение 1440х900(это кажись 16:10). У меня монитор широкоформатный , 19 дюймов. Вы на таком монике с каким разрешением играете?

• пожаловаться
• скопировать ссылку

• пожаловаться
• скопировать ссылку

• пожаловаться
• скопировать ссылку

• пожаловаться
• скопировать ссылку

• пожаловаться
• скопировать ссылку

• пожаловаться
• скопировать ссылку

• пожаловаться
• скопировать ссылку

• пожаловаться
• скопировать ссылку

• пожаловаться
• скопировать ссылку

• пожаловаться
• скопировать ссылку

• пожаловаться
• скопировать ссылку

• пожаловаться
• скопировать ссылку

• пожаловаться
• скопировать ссылку

• пожаловаться
• скопировать ссылку

• пожаловаться
• скопировать ссылку

• пожаловаться
• скопировать ссылку

• пожаловаться
• скопировать ссылку

• пожаловаться
• скопировать ссылку

• пожаловаться
• скопировать ссылку

• пожаловаться
• скопировать ссылку

• пожаловаться
• скопировать ссылку

• пожаловаться
• скопировать ссылку

• пожаловаться
• скопировать ссылку

• пожаловаться
• скопировать ссылку

• пожаловаться
• скопировать ссылку

• пожаловаться
• скопировать ссылку

• пожаловаться
• скопировать ссылку

• пожаловаться
• скопировать ссылку

• пожаловаться
• скопировать ссылку

• пожаловаться
• скопировать ссылку

• пожаловаться
• скопировать ссылку

• пожаловаться
• скопировать ссылку

• пожаловаться
• скопировать ссылку

• пожаловаться
• скопировать ссылку

Тема закрыта. Публикация новых комментариев отключена.

Back to the main page.

Campaign Issues

Crashes in connection with the Campaign Strongholds

First of all. Did you merge? (i.e did you press the «merge» button)?
If so. Read this first.

The campaign has a number of potential glitches, many of which are actually vanilla bugs and have nothing to do with unification. If you crash sometime between initializing the last victory cutscene and reaching the campaign map again when playing a stronghold. Then here are six cumulative possible solutions to fix that.

Listed in order of least intrusive to most intrusive.

0 Be on latest version: 6.9

1 Have LAA on.

2 Continually mash the esc key when you win.

3 Fuggles2k solution to Mishra:

• Step 1 - Play the stronghold mission as you normally would but right before you complete the mission save the game. Watch the cinematic at the end if you wish and let the game crash or simple quit the game after saving.
• Step 2 - Run the GraphicsConfig.exe file from the local game files and hit the safe mode config option.
• Step 3 - Run the game, load from the saved point where you are about this complete the mission. Complete the mission and the game should progress past the point where it was crashing and then save the game and exit.
• Step 4 - Run the GraphicsConfig.exe file again and set your original settings.
• Step 5 - Run the game and play through untill you reach the next stronghold mission then repeat from Step 1.

4 Disable the EnableCampaignBases option in the campaign configurator if the option is on. Remember to click «save settings».

‘5 Remove the 39 files that are located in the » ...steamappscommonDawn of War SoulstormUnification_BugfixMovies » folder.

6 Create new profile and restart campaign.

Weird Visual Glitch in Campaign

First of all. Did you merge? (i.e did you press the «merge» button)?
If so. Read this first.

All races, but seemingly especially Dark Eldar can have a strange mashed visual glitch in campaign when selecting them or doing other things in the metamap.

Solutions:

1) make sure you are on latest version: 6.9

2) disable discord overlay.

Crashing after non-stronghold campaign missions completed

First of all. Did you merge? (i.e did you press the «merge» button)?
If so. Read this first.

Also make sure LAA is on in the mod manager.

This error may or may not include a fatal scar error message.

Turn off EnableCampaignBases in the campaign configurator, and/or create a new profile.

General Issues

RAM issues (temp folder and dump file errors, 183 errors, sudden crashes)

First of all. Did you merge? (i.e did you press the «merge» button)?
If so. Read this first.

Before going deeper into things: due to how DoW handles memory, it can have «hiccups». If you crash, try to start the exact same match again and there is a good chance it will load this time. If it doesn’t it was most likely a genuine out-of-ram crash, in which proceed with the reading. NOTE that this can happen even if you have managed your ram equation, you will know this by it working the second time you load the exact same match.

A relatively common problem that arises is memory related crashes. These may manifest themselves in a few different ways, most commonly crashing with the “TEMP folder — not enough space” or “Unable to create the temporary folder. Error 183”. Sometimes this error may manifest as «freezing» whilst loading the match, but often there is a error message in the background waiting to be have the «ok» button pressed before the actual CTD occurs.

Let’s start with a very basic understanding of DoW:SS. It’s an old 32b game from 2004. Out-of-the-box it’s monothread (meaning it can only use one CPU) and can only utilize 2Gb of RAM. Using LAA (LargeAdressAwareness) on a 64b system the engine will be able to access and utilize up to 4Gb of RAM. On a 32b system LAA only increases the available RAM to 3GB. This means that you need to understand that the bottleneck is not your system, but the engine itself.

All factions in any given match setup are preloaded (including all branching paths) into the RAM when starting a game. The Unification mod gives all vanilla races a visual facelift and add new units if enabled in the game rules. Many of the race mods have great visuals built in from the get-go, and some have extensive rosters. Some also have a lot of shiny fx, or even some old legacy unoptimised fx which will be updated later on. This means that not all race mods take up the same amount of RAM when preloaded. This is also important to understand. Emperor’s children are the most RAM hungry race atm. Dark Angels, Imperial Fists, World Eaters and Inquisition are also heavy ones, and Admech explorators and Chaos Daemons take more ram than their sga’s suggest due to fx.

Some addon’s like FX addon can add an additional small footprint, as can lots of units from game modes like survival or unlimited addon. The latter can have a much bigger footprint than FX addon.

The facts stated above means you cannot expect to play an 8p match on a big map with a bunch of heavy race mods with every setting maxed out. That will crash. Number of units will also impact so game rules with very high pop caps need to be factored in. Even if the match loads and plays well, it might still crash with large pop caps if other factors aren’t compensating. FX can drain RAM quite heavily, so maxed out fx with a bunch of races that preload a lot of flashy fxs might require sacrifices somewhere else. Equation.

You have to manage your RAM in regards to the setup you want to play.

Having understood these basic principles the followings actions below can be taken to minimize memory errors. But before we list those, do note that the mem situation is an equation. For example if you love persistent bodies, you may want to keep those at  a higher setting, but in compenstation lower other settings or play smaller games. Test what works for you and determine what’s most important to you. You can probably max all the settings in a 1v1 for example. Also note that the visuals of Unification are good enough to take some lowered graphics settings in big games, especially since most players play those games zoomed out anyway.

Without further ado, this is what you can do to minimize mem crashes.

Tier 0. Everyone needs to do this.

• Use the DoW Mod Manager. If you for some reason don’t have it: get it here: https://www.moddb.com/mods/unification-mod-dawn-of-war-soulstorm/downloads/dow-mod-manager-v231
• Activate LAA so that is on (green texts). It’s the “Toggle LAA” button in the mod manager.
• Due to how DoW handles memory, it can have «hiccups». If you crash, try to start the exact same match again and there is a good chance it will load this time. If it doesn’t it was most likely a genuine out-of-ram crash, in which proceed further down the list.
• Be aware of the fact that (once again) due to DoW engine, looking in army painter before playing a game may cause memory issues, the more you look, the higher the risk of issues. Safest option is to restart if you have spent time in army painter.
• Resolution plays a part, lower your resolution if you have high ones. More than 1080p not recommended.

Tier 1. Highly recommended for everyone.

• Make sure the –forcehighpoly setting is off.
• Make sure the “High Res Textures” is off. This setting is found in Mod manager—>Settings—>Video. »
  • High Res Textures» determines whether your badges and banners ingame will be high res. This has minimal impact on your visiual enjoyment when turned off, but saves memory. This is the same thing as setting “fullres_teamcolour=0” in your “…Dawn of War Soulstormlocal.ini” file. Fullres_teamcolour=0 means that the High Res Textures is off. If you don’t have this line in your local.ini, then just add it.
• Set “Persistent Bodies” and “persistent scaring” to their lowest settings. This setting is found in Mod manager—>Settings—>Video. These settings should be self-explanatory.
• Get the «Soulstorm_DXVK.zip» from the Unification Discord (pinned in General chat by Fuggles2k). Download it and extract it’s contents in your soulstorm folder.
• If having issues (which you have since you are reading this) set «Shadow details» setting to lowest, i.e «None». This is due to engine glitch that means it can cause crashes by itself, some have more of this than others.

Tier 2. For those still suffering regular crashes.

1. Disable the «AI MapDB» game rule. This will slightly decrease the pathing performance of your units. But free up some mem.
2. Disable the «Heroes» win condition if using it.

Tier 3. Still issues. Aka are you trying to play 8p games or heavy 6p games?

Remember that not all races take up the same amount of RAM? Those having done the previous steps and are still having problems can try any combination of the four following solutions:

1. Play smaller games.
2. Use less RAM heavy mod races. Emperor’s Children being the hungriest. But Inquisition: Daemonhunt, World Eaters, Dark Angels and Imperial Fists are also big ones.
3. Reduce pop cap if you have raised it.
4. Reduce graphics settings and/or screen resolution (yes, that plays a part too). You may not need to tank every setting, start with what’s least important to you.
5. Toggle Team color off. This is done by pushing the small 2-coloured oval button next to your chosen race in skirmish, do this for all players in a match to save some RAM. Note that this will disable your ability to choose badges and colour schemes. Vanilla races will use the default campaign standard settings and races with any vanilla race associations (like Space marine race mods) will at least partly use the default campaign standard colour and badge scheme.

Find the balance and solution that works for you.

Missing Races

First of all. Did you merge? (i.e did you press the «merge» button)?
If so. Read this first.

Secondly: make sure you are launching «unification new races» and not «unification bugfix»

Thirdly, these are the races currently included in 6.9:

• Adeptus Mechanicus Explorers
• Black Templars
• Blood Angels
• Chaos Daemons
• Dark Angels
• Death Guard
• Death Korps of Krieg
• Ynnari
• Emperor’s Children
• Harlequins
• Imperial Fists
• Inquisition Daemon Hunters
• Legion of the Damned
• Salamanders
• Steel Legion
• Thirteenth Company
• Thousand Sons
• Tyranids
• Witch Hunters
• World Eaters

So if you think you are missing something like ultramarines or custodes, then you are not. They are not out yet.

With that out of the way: if you lack any (or more commonly) all of the races above, then that most likely means you lack the race sga archives. All of these races are localised into single sga archives in the «…Dawn of War SoulstormUnification_Bugfix» folder.

Go to that folder.

If it looks like this, then you have the most common error, with a simple fix.

Your «Unification_Race_Mods.7z» archive contains this:

if you feel confused about what this file is, then you haven’t followed the installation instructions properly since this is a file you download when installing (unless using torrent or the google driver full installer), please consult installation instructions to make sure you installed correctly.

Open that archive in for example 7zip and click the «test» button to make sure it isn’t corrupted.

if there are issues, delete the archive and redownload, test again.

Once you have a non-corrupted archive (may never have been corrupted hence the testing) extract it.

Get the content shown above into the bugfix folder, so that it looks like this:

Once it looks like above, the problem is solved.

If you have the reverse situation where you have the stuff from the race archive pic but not the stuff from the first «this is not how it’s supposed to look» pic. Then do this process with the «Unification_Core_Mod.7z» archive instead. (re)apply any patches you have done afterwards.

6.9 worked but it crashed when i patched to latest version

First of all. Did you merge? (i.e did you press the «merge» button)?
If so. Read this first.

Second of all. Try launching base game. Yes. Even «if it worked fine yesterday». Dow and steam are fickle, and they can and have spontaneously ceased to function.

If it launches ok proceed to instructions below.

If it doesn’t that’s your issue, you could have more than one issue, but that’s the first you need to fix.

If you’re on steam the first thing to try is to verify file integrity. Reenable LAA afterwards since verifying disables it.

With that out of the way. If base game works, and 6.9 worked but then it suddenly stopped working when you patched.

you got the wrong patch.

no no. you did. yes 6.925 is latest. you still got the wrong one.

6.91+6.925 is for new installations. (click the «read more» button, they are your friends)

repeat: running 6.925 on 6.9 will cause it to crash.

right one is 6.91+6.925.

Right. Still crashes when you used right patch?

That either means base mod is not properly installed, or that patch was not properly applied.

For the latter:

1) Rerun the patcher if using patcher. Sometimes it doesn’t take the first time.

2) Apply it manually

The .7z contains the above. That right there, as is, goes into soulstorm folder.

I.e those 4 things individually go into soulstorm folder.

Do not create a folder called «Unification-v6.9.1-6.9.25-Combined-Patch».

Do not dump them inside unification_bugfix folder.

I just installed and it crashes when i try to launch.

First of all. Did you merge? (i.e did you press the «merge» button)?
If so. Read this first.

Second of all. Try launching base game. Yes. Even «if it worked fine yesterday». Dow and steam are fickle, and they can and have spontaneously ceased to function.

If it launches ok proceed to instructions below.

This is always either a faulty base mod installation or a faulty patching.

Go to your soulstorm folder. Go to «unification_bugfix» folder. open it.

Does it look like that?

If yes: first place to look at is at the patching.

if no: most common things that go wrong are

1) you didn’t download both «Unification_Core_Mod.7z» and «Unification_Race_Mods.7z» archives, you need both.

2) one or both of those archives have (1), (2) in their file name. Installer will only read the one with exact correct name. Delete your unification_bugfix folder in soulstorm, rename the archives to correct name and then reinstall. Note if you did manual this will not affect anything.

3) you didn’t get and use the 6.9 installer, instead thinking that the 6.925 *patcher* is all you needed. As per instructions: use installer to install base mod, and then use patcher afterwards. Solution: delete your unification_bugfix folder in soulstorm, get the *installer* and install using that. Or delete said folder and do manual installation. Either way works.

4) you actually did get all the things and use them correctly, but there is corruption in your download. Very common for opera browser users for some reason.

Check your files using their files size, test function in extractors like 7zip (the «test» button in the top row of button tests archives) and/or MD5 hash.

Correct sizes and Hashes are:

Part 1: Installer, size 60.24mb (63,167,954 bytes) MD5 Hash d15d81dce47afd0fe1a343f16a756f5e

Part 2: Core_files, size 6.03gb (6,475,936,928 bytes) MD5 Hash 27a9beea5d500aa82a06e1fa2eebfb13

Part 3: Race_mods, size 8.12gb (8,714,732,442 bytes) MD5 Hash af79072a9cef5bc2c628b507e1f5a091

Part 4 Music Pack, size 1.01gb (1,080,311,099 bytes) MD5 Hash 0a40da54defecdffe6dd496b3fe5a11c

If it’s corrupted. Delete your unification_bugfix folder in soulstorm, delete the files you use to install (i.e «Unification_Core_Mod.7z» etc), redownload, and check again. Install when it’s right.

5) Does your unification_bugfix folder look like this?

Then see this: missing races.

None of these 5 common things? (do actually check), ask in tech-support on the discord.

Problems downloading the mod

First of all. Did you merge? (i.e did you press the «merge» button)?
If so. Read this first.

Secondly: download is not install. Don’t confuse these terms. If you are unclear: here.

That out of the way:

1) try mirrors, when clicking download you get the option to click both the archive name to download now, and a mirror button to get a list of different mirrors

2) no luck?

Try the google drive versions for the two archives: «Unification_Race_Mods.7z» and «Unification_Core_Mod.7z»

[insert any 6.9 links here]

Note that these have a limit per day of how many times people can download them.

3) still no luck? try another browser

and ofc moddb can be having temporary issues in general, in which case try again later.

Army Painter Questions

First of all. Did you merge? (i.e did you press the «merge» button)?
If so. Read this first.

«X unit is missing from army painter»

Army painter can only show a max of 31 units/buildings. hardcoded.

«It crashed when i look at unit x»

Vast majority of cases this is a ram crash due to LAA being off.

Solution: turn LAA on in the mod manager.

Push the button to make the two lines green.

I can’t turn LAA on

First of all. Did you merge? (i.e did you press the «merge» button)?
If so. Read this first.

1) make sure the game isn’t running when you are trying to apply LAA

2) make sure mod manager is running with admin rights.

3) Make sure soulstorm.exe and graphicscongif.exe do not have «read-only» checked.

Right click and select properties.

4) If it still won’t take. Try restarting the computer, and then try again.

Note that some pirated versions will have issues with this.

Solution: buy the game. it’s frequently on sale for a little under 4€.

I have a bunch of red race mod entries in mod manager and can’t start the mod.

You merged…

Read this.

I have issues with adding more races.

First of all. Did you merge? (i.e did you press the «merge» button)?
If so. Read this first.

Secondly: note that there are only six semi-supported races you can add:

• Angry marines
• Praetorians
• Vostroyan Firstborn
• Renegade Guard
• Night Lords
• Space Wolves (for this one, read this)

Thirdly. What does «semi supported mean»?

It means that they can not be attacker in survival (but you can play as them as a defender), cannot be used in last stand, no survival rules (reinforcements etc) will apply to them, they have no titan tier units, they lack updates, they have some bugs and are not balanced for the rest of the mod.

With that out of the way, I’ll quote brother Gambit on how to properly add one of the semi supported races.

One note is that you must install the race mod in question correctly into the soulstorm folder first.

I get a red entry in mod manager when trying to add space wolves to unification

First of all. Did you merge? (i.e did you press the «merge» button)?
If so. Read this first.

The New races module has a syntax error.

Simple fix.

Open the module with notepad.

Click the cursor to the right of the space wold entry. The X here indicates where the text cursor will be.

Press backspace 3 times so that the text cursor rests snuggly against the final «s» in Space_Wolves.

Save. Problem solved.

Issues installing addons (unlimited, FX, redux, gridkey etc)

First FIRST of all.: no addons are updated to 6.9 yet (written 2022-07-29), so move along citizen.
First of all. Did you merge? (i.e did you press the «merge» button)?
If so. Read this first.

By far the most common error here is people not understanding how to install them.

Using the gridkey addon as an example:

The «Unification_Gridkeys.rar» contains the files and folder above.

All of that, goes as is, into the soulstorm folder.

If you got a «Unification_Gridkeys» folder in the soulstorm folder, then open that, cut everything inside and paste directly into the soulstorm folder.

That is it.

MultiPlayer Issues

MP desync issues and not being able to see one another’s games

First of all. Did you merge? (i.e did you press the «merge» button)?
If so. Read this first.

The basic principle for MP is that you need to have matching setups. MP can be very sensitive and even things like making minor changes to a soundtrack can cause issues.

Here’s a list of things to check when experiencing desyncs and not being able to see one another’s games. Note that ALL people trying to play must do this and sync up. And you need to be thorough and pay attention to detail. Many have been the cases in Discord tech-support of people reading this list, swearing they checked it, just for it later to turn out they missed a point. So be thorough.

All those trying to MP need to:

1) Have the LAA option on in the Dawn of War Mod Manager .

2) Have -dev checkbox unchecked in the Mod Manager .

3) Have functional full installations of Unification.

4) Verify your file integrity in steam. 2 of the files found will be LAA. More than that might be the source of your issue. Once the verification is done, re-enable LAA.

5) Not have added any extra races or map mods, or have added the same races or map mods.

6) Have the «high res textures» box unchecked in the Mod Manager settings tab. Unverified, but just to be safe.

7) Be on 6.91 Mod manager should not say «4.68», «5.91», «6.0» or «6.9» in regards to the unification modules displayed.

Everybody has to launch the same module (e.g Bugfix, New Races or Unlimited). If launching Unlimited, make sure everyone has the same (the latest) version from moddb or from #announcements.

9) CD copies do not work on Steam. Either use DoWonline or contact SEGA for a steam key.

10) Your Anti-Virus may block one party’s connection (which needs to be fixed in such cases). You may need to whitelist soulstorm.exe.

11) Make sure you have the same version of Mod Manager. The latest of course being preferable. It can be found here: https://github.com/Fragjacker/DoW-Mod-Manager/releases

12) Not to have made any model or RGD modifications within the DXP2 W40k or Engine folders. Or made any changes to the World_Race_Themes.scar file.

13) Sometimes, and for some people, Steam is very uncooperative due to warpstorms. You can if you wish try DoWOnline and see if it works there.

14) Some «desyncs» are actually out-of-memory issues. If someone runs out of RAM during a match, then that can manifest as a «desync» and that player be kicked. See Ram Issues section.

15) Of course, all people involved all need to use Steam (via Mod Manager) or DoWonline. They cannot mix.

16) for desync errors: all involved can try deleting the dxp2 folder in soulstorm folder and then verifying file integrity, forcing it to redownload fresh untampered version of that folder.

Why are some races greyed out and unselectable in multiplayer?

Due to the way Relic made the expansions, you can only play as certain races in multiplayer if you own the previous games and expansions. For example you will need the original Dawn of War to play as Space Marines, Chaos, Eldar or Orks in multiplayer, you will need Winter Assault to play as Imperial Guard and you will need Dark Crusade to play as Necrons or Tau.

If you are on Steam, simply having the keys for these games should allow you play as the races for them, otherwise you would need to have them installed as well, or at the very least have the CD keys for those games in your Windows registry.

List of misc issues (windowed, shadows, alt-tabbing etc)

First of all. Did you merge? (i.e did you press the «merge» button)?
If so. Read this first.

• The Game can have issues when running in windowed mode. Know issues includes crashing when in game and the mouse disappearing.
• The Game often dislikes alt-tabbing whilst it is loading. it can take a very long time to respond to the alt-tab, and for some people even crash or cause a graphical glitch.
• Shadows can by themselves cause crashing, this is a vanilla bug. If suffering crashes that are not connected to any other issue, try disabling shadows and see if that helps.

ANYTHING concerning a process in which you used the merge button

You done goofed playa. You put salt in your game…

Never use the merge button with unification.

«Not even..?»

No, not even that one.

«But then how..»

Nope. There is another correct way that you have missed. Merging is never the answer, m’kay.

«I thought it was part of the installation process?»

…. bruh …

«I now realize that I shouldn’t do things that installation instructions do not tell me to do.»

Good.

«But, why is the button there then?»

It’s nostalgia and being busy with other things that means the button is still there.

Think of it as a remnant from evolution: long ago it served a purpose, it doesn’t now but it’s still around.

«But I once merged two race mods and that worked.»

Yeah, merging simpler mods might work fine. But this is troubleshooting for unification. W/e stories of glorious past merging successes you have is not relevant here.

«I dunno.. My buddy says..»

Go back to the beginning of this text and reread.

«I dunno.. I merged a race with UA..»

1) UA not relevant here,

2) It didn’t function fully as intended,

3) Go back to the beginning of this text and reread.

«Well.. maybe… But can’t i just the merge function to undo it?»

That’s not optimal, load orders might have been messed with, and entries have def been lost.

«OK. I have now seen the light and repented. Thank you anonymous internet denizen for delivering me to salvation. »

Np. Now we’re getting somewhere.

First step: undo the merging you did. If you are on a later version of mod manager it has created a new module called [we_didn’t_need_to_be_merged]merge. Delete that and launch the proper modules.

If you are on an old version of mod manager. Delete the merged file and run the 6.91+6.925 patcher again. And ofc update your mod manager.

If problems persist then proceed to the relevant troubleshooting section, you are now ready to fix any remaining issues.

Terminology

Download:

copying files from a server down to your harddrive.

Analogy: buying bags of groceries from the store and taking them home. Once you arrive home, they are «downloaded»

Install:

Putting all the files you have downloaded into their proper place. Can for programs and games (on a technical level the same as a program) include key registering, but that is not relevant for unification.

Analogy: Once you have the grocery bags home from the download analogy, you now put all the groceries in their proper place. Rinsing fruit, placing things into cupboards and the fridge, opening some packages perhaps. This is «installing».

Extract:

Archives (see below) are extracted using extracting programs like winzip, winrar or 7zip.

If you don’t have an extracting program, 7zip is free and works very well.

https://www.7-zip.org/

File:

You can think of them as sheets of papers with written information on them. Some files like archives contain files and folders that you extract, some files that are called «apps» or «executables», they have the file extension: *.exe

File extension.

All files have an extension. for example «Unification-v5.9.0-Full.1.exe». The .exe is the file extension, telling you what kind of file it is.

NOTE: what icon a file has HAS NO bearing on what kind of file it is. None. zero. That just tells you what program your system associates with that file. I.e what program it thinks should be the default program to open it with. Only file extension tells you what kind of file it is. Not the icon.

Archive:

Archives are a subset of files. They can have file extensions such as .rar or .7z for example. These are extracted, note that if using installers do not extract these yourself, the installer does that for you. This is just explaining the term. Archives contain other files and/or folders.

Folder:

Folders are entities where you can put files and other folders in. For example «Dawn of War soulstorm» is a folder, it contains other folders like «engine» and files like «Unification_New_Races.module»

Vintage: Manual installation of 0.5b3 tyranids (for when the installer cannot run without errors)

— First of: launch the installer with admin rights.

— No worky? Then rule out corruption. Delete the nid installer and try redownloading it.

Still no worky? Do things desc below:

1) If you don’t have 7zip. Then get it. Winrar and winzip cannot do this. https://www.7-zip.org/

2) open 7zip

3) open the 0.5b3 installer.exe with 7zip using «open inside»

4) you should see this:

Click on the archive in the middle (TyranidMod_005b3) Open it using «open inside»

5) You should see this:

Mark all those 4 files and use the extract function.

When prompted: choose the soulstorm folder.

You should now have a functioning installation of the Tyranids.

Company of Heroes

unable to create the error report. please verify that there is enough space in your TEM.

unable to create the error report. please verify that there is enough space in your TEMP folder.

this is the ERROR i have been getting for the last 2 weeks.
it seems to only occur during 3v3 or 4v4 games.
i have not had this error during a 1v1 or 2v2 YET.

i have DOMAIN ADMINS rights on this computer, so i know it is not a rights issue.

unable to create the error report. please verify that there is enough space in your TEMP folder.

this is the ERROR i have been getting for the last 2 weeks.
it seems to only occur during 3v3 or 4v4 games.
i have not had this error during a 1v1 or 2v2 YET.

i have DOMAIN ADMINS rights on this computer, so i know it is not a rights issue.

here is my DXDIAG.txt

here is my WARNINGS.log

This post has been merged by aramonkg: Oct 9 2009, 16:30 PM

Attached image(s)

Attached File(s)

	DxDiag.txt
Size: 37.34k
Number of downloads: 782

AFAIK it uses the default folder: C:Users%username%AppDataLocalTemp

You’re not the first to report this problem but tbh I have no idea what causes it.

have you tried running the game with normal clock speeds? you seem to have overclocked your system quite a bit and i guess you wouldnt be running it with those specs if it wasnt stable, but nonetheless for troubleshooting it probably wouldnt hurt running everything with default timings.
apart from that, i think you will have checked it but still: is there enough free space on your system partition or the partitio you store your temp folder on respectively?
i guess you have also tried to set all the details and everything to the lowest possible options, right? and do the errors occur upon playing 3v3 matches only or also when watching a 3v3 replay? and do they occur right in the beginning or just randomly during the game or always at a given point?
additional info might help narrowning down the exact cause for your problem.
regards,

have you tried running the game with normal clock speeds? you seem to have overclocked your system quite a bit and i guess you wouldnt be running it with those specs if it wasnt stable, but nonetheless for troubleshooting it probably wouldnt hurt running everything with default timings.
apart from that, i think you will have checked it but still: is there enough free space on your system partition or the partitio you store your temp folder on respectively?
i guess you have also tried to set all the details and everything to the lowest possible options, right? and do the errors occur upon playing 3v3 matches only or also when watching a 3v3 replay? and do they occur right in the beginning or just randomly during the game or always at a given point?
additional info might help narrowning down the exact cause for your problem.
regards,

i empty the temp folder each morning. so it is empty.
i have 400gb of free space.
the computer in my specs is my home computer. my work computer (the one with issues) is not overclocked at all.
so far it only happens during a game of 3v3 to 4v4. it takes around 20-25 minutes for the error to occur. there seems to be no pre situation to let me know it is about to happen.

i have not lowered my settings (they are all at max settings) — except it is not using dx10 rendering. it is running under dx9. this error started after the 2.600 patch.
i used to play 3v3 and 4v4 with no problems.

Try following the procedure I detailed in this thread involving Process Monitor.

If there is any file that cannot be created it should show up as an event of the RelicCOH.exe process, including the details of the specific path of the that file. It may be a hint to what is going on.

A friend of mine suffers really badly from this — every 4v4 game he crashes out of. I saw it once on my machine when I ALT+Tabbed out of a game, but not apart from that.

Just to test this memory leak theory, we played a 2v2 game last night — it lasted 52 minutes and he didn’t crash.
It is also something that started since ToV.
What really annoys me is that Relic appear to be keeping quiet about this problem, which seems to be affected a fair number of people.
My friend went through the support procedure with THQ, got the latest drivers, reinstalled the game, blah, blah, blah — but so far no fix and they don’t appear to have any idea how to fix it.

A friend of mine suffers really badly from this — every 4v4 game he crashes out of. I saw it once on my machine when I ALT+Tabbed out of a game, but not apart from that.

Just to test this memory leak theory, we played a 2v2 game last night — it lasted 52 minutes and he didn’t crash.
It is also something that started since ToV.
What really annoys me is that Relic appear to be keeping quiet about this problem, which seems to be affected a fair number of people.
My friend went through the support procedure with THQ, got the latest drivers, reinstalled the game, blah, blah, blah — but so far no fix and they don’t appear to have any idea how to fix it.

tell your friend that misery loves company.
i am sure relic will fix it, or we will find the fix.

then you should all report the problem to relic. there’s no other way making them work a patch
the more it gets reported the higher are the chances thex will put some effort into solving it.
regards,

Relic should know about it already, seeing as it was reported to THQ Support and is still unresolved.

(If you try posting any technical problems on their CoH Community forums you get told to report it to THQ Support).

still they have limite ressources. and of course they’ll start working on patches first, that affect many people, not just 1 or 2. if you dont report your problems, you cant blame anyone if they wont get fixed
regards,

so apparently, not enough people reported the issue, for them to consider it worth building a quick fix. that is why i’m telling everyone (not only you), that they should report the problem as well, since it will help top speed up getting a patch. i know the attitude of many people too well: ahh, someone already reported it, so i dont have to, i’ll just wait.
i wanted to appeal to those people, not to you. what you and your friend did was exactely the right thing, so others should follow your example.
hope it is clearer now what i was trying to say.
regards and good luck,

unable to create the error report. please verify that there is enough space in your TEMP folder.

this is the ERROR i have been getting for the last 2 weeks.
it seems to only occur during 3v3 or 4v4 games.
i have not had this error during a 1v1 or 2v2 YET.

i have DOMAIN ADMINS rights on this computer, so i know it is not a rights issue.

Well, first off, can you be a little more descriptive about the circumstances of the error. Do you notice any instance of CoH running on the taskbar? Is there any other error message beyond that? Does a crash window pop-up after this, like this one?

It may be the case that the error message is a side effect of a crash and not the cause of the crash itself. In any case, you can either wait for Relic to deal with it (given past behaviour, it may take a while) or try something. Since, I can’t reproduce the error, here is what I suggest.

To start with, there is no visual indication on the error message window that it comes from RelicCOH.exe, the game’s process. In order to identify who «owns» that window do the following.

NOTE: Stage 1 and stage 2 better be configured and run simultaneously so as to economize on time

Stage 1

1. Download and run Process Explorer
2. Keep Process Explorer running in the background and launch CoH
3. Whenever the error occurs, do not close the error window but switch over to Process Explorer
4. In Process Explorer’s toolbar click «FInd Window’s Process» and hover over to the error message

If it is RelicCOH.exe then you can make use of the information gathered in stage 2. Otherwise, let me know what process came up, so that we get to know if any use of Process Monitor is relevant, or if we have to take a different route to troubleshooting it.

Stage 2

1. Download, unzip and run ProcMon as administrator (if not already)
2. Select Filter->Filter (Ctrl+L) and choose «Process Name» from the left topmost dropdown menu and «is» from the one next to it
3. Type RelicCOH.exe in the textbox to the right
   
4. Click Add and then OK
5. Now fire up CoH and when the error message pop-up make sure you note down your system time, as shown on the taskbar.
6. Scroll down to the events logged around the specific time and notice if there is weird or repeating behaviour. Note down the text in the Result column and look for things such as, NAME_NOT_FOUND, SHARING_VIOLATION, NAME_COLLISION etc. In short anything that doesn’t say SUCCESS.

Or you can save the whole Process Monitor event log using File->Save As and making sure the options are set as follows.

Then compress the resulting file and upload it somewhere so I can take a look.

This post has been edited by aramonkg: Jul 21 2009, 14:49 PM

Источник

So I decided to try out both the unification mod and the ultimate apocalypse mods for soulstorm. Both have been well reviewed and seemed like a good way to get back into the game after a long absence. However, when I try to play they both keep crashing and the game is basically unplayable. I’ve tried different factions, turning off the different modifiers for skirmish and even a campaign run(looking at you Necron Soulstorm campaign).

Most common crash areas are in the loading screen, during a mission(I can barely make it past the five minute mark), or after a battle and before the reward screen or cutscene for campaign. The game window freezes and once I ctrl+Esc there is an error tile added to the taskbar. The only solution is to select Ok and close the game. The message is always the same and is provided below. Even when I save in mission and try to reload it just keeps going down after a few minutes of battle or when transitioning to the battle summary after a campaign mission. As for the Necron campaign I was able to finish 2 missions after many reloads but when I tried to take out another faction it got to the end scene and just keeps crashing.

This forum is basically my last resort before just giving up and rage-quitting so any suggestions would be appreciated.

The error message is singularly unhelpful:

Unable to create the error report.
Please verify there is enough space in your TEMP folder.

Источник

Company of Heroes

unable to create the error report. please verify that there is enough space in your TEM.

unable to create the error report. please verify that there is enough space in your TEMP folder.

this is the ERROR i have been getting for the last 2 weeks.
it seems to only occur during 3v3 or 4v4 games.
i have not had this error during a 1v1 or 2v2 YET.

i have DOMAIN ADMINS rights on this computer, so i know it is not a rights issue.

unable to create the error report. please verify that there is enough space in your TEMP folder.

this is the ERROR i have been getting for the last 2 weeks.
it seems to only occur during 3v3 or 4v4 games.
i have not had this error during a 1v1 or 2v2 YET.

i have DOMAIN ADMINS rights on this computer, so i know it is not a rights issue.

here is my DXDIAG.txt

here is my WARNINGS.log

This post has been merged by aramonkg: Oct 9 2009, 16:30 PM

Attached image(s)

Attached File(s)

	DxDiag.txt
Size: 37.34k
Number of downloads: 782

AFAIK it uses the default folder: C:Users%username%AppDataLocalTemp

You’re not the first to report this problem but tbh I have no idea what causes it.

have you tried running the game with normal clock speeds? you seem to have overclocked your system quite a bit and i guess you wouldnt be running it with those specs if it wasnt stable, but nonetheless for troubleshooting it probably wouldnt hurt running everything with default timings.
apart from that, i think you will have checked it but still: is there enough free space on your system partition or the partitio you store your temp folder on respectively?
i guess you have also tried to set all the details and everything to the lowest possible options, right? and do the errors occur upon playing 3v3 matches only or also when watching a 3v3 replay? and do they occur right in the beginning or just randomly during the game or always at a given point?
additional info might help narrowning down the exact cause for your problem.
regards,

have you tried running the game with normal clock speeds? you seem to have overclocked your system quite a bit and i guess you wouldnt be running it with those specs if it wasnt stable, but nonetheless for troubleshooting it probably wouldnt hurt running everything with default timings.
apart from that, i think you will have checked it but still: is there enough free space on your system partition or the partitio you store your temp folder on respectively?
i guess you have also tried to set all the details and everything to the lowest possible options, right? and do the errors occur upon playing 3v3 matches only or also when watching a 3v3 replay? and do they occur right in the beginning or just randomly during the game or always at a given point?
additional info might help narrowning down the exact cause for your problem.
regards,

i empty the temp folder each morning. so it is empty.
i have 400gb of free space.
the computer in my specs is my home computer. my work computer (the one with issues) is not overclocked at all.
so far it only happens during a game of 3v3 to 4v4. it takes around 20-25 minutes for the error to occur. there seems to be no pre situation to let me know it is about to happen.

i have not lowered my settings (they are all at max settings) — except it is not using dx10 rendering. it is running under dx9. this error started after the 2.600 patch.
i used to play 3v3 and 4v4 with no problems.

Try following the procedure I detailed in this thread involving Process Monitor.

If there is any file that cannot be created it should show up as an event of the RelicCOH.exe process, including the details of the specific path of the that file. It may be a hint to what is going on.

A friend of mine suffers really badly from this — every 4v4 game he crashes out of. I saw it once on my machine when I ALT+Tabbed out of a game, but not apart from that.

Just to test this memory leak theory, we played a 2v2 game last night — it lasted 52 minutes and he didn’t crash.
It is also something that started since ToV.
What really annoys me is that Relic appear to be keeping quiet about this problem, which seems to be affected a fair number of people.
My friend went through the support procedure with THQ, got the latest drivers, reinstalled the game, blah, blah, blah — but so far no fix and they don’t appear to have any idea how to fix it.

A friend of mine suffers really badly from this — every 4v4 game he crashes out of. I saw it once on my machine when I ALT+Tabbed out of a game, but not apart from that.

Just to test this memory leak theory, we played a 2v2 game last night — it lasted 52 minutes and he didn’t crash.
It is also something that started since ToV.
What really annoys me is that Relic appear to be keeping quiet about this problem, which seems to be affected a fair number of people.
My friend went through the support procedure with THQ, got the latest drivers, reinstalled the game, blah, blah, blah — but so far no fix and they don’t appear to have any idea how to fix it.

tell your friend that misery loves company.
i am sure relic will fix it, or we will find the fix.

then you should all report the problem to relic. there’s no other way making them work a patch
the more it gets reported the higher are the chances thex will put some effort into solving it.
regards,

Relic should know about it already, seeing as it was reported to THQ Support and is still unresolved.

(If you try posting any technical problems on their CoH Community forums you get told to report it to THQ Support).

still they have limite ressources. and of course they’ll start working on patches first, that affect many people, not just 1 or 2. if you dont report your problems, you cant blame anyone if they wont get fixed
regards,

so apparently, not enough people reported the issue, for them to consider it worth building a quick fix. that is why i’m telling everyone (not only you), that they should report the problem as well, since it will help top speed up getting a patch. i know the attitude of many people too well: ahh, someone already reported it, so i dont have to, i’ll just wait.
i wanted to appeal to those people, not to you. what you and your friend did was exactely the right thing, so others should follow your example.
hope it is clearer now what i was trying to say.
regards and good luck,

unable to create the error report. please verify that there is enough space in your TEMP folder.

this is the ERROR i have been getting for the last 2 weeks.
it seems to only occur during 3v3 or 4v4 games.
i have not had this error during a 1v1 or 2v2 YET.

i have DOMAIN ADMINS rights on this computer, so i know it is not a rights issue.

Well, first off, can you be a little more descriptive about the circumstances of the error. Do you notice any instance of CoH running on the taskbar? Is there any other error message beyond that? Does a crash window pop-up after this, like this one?

It may be the case that the error message is a side effect of a crash and not the cause of the crash itself. In any case, you can either wait for Relic to deal with it (given past behaviour, it may take a while) or try something. Since, I can’t reproduce the error, here is what I suggest.

To start with, there is no visual indication on the error message window that it comes from RelicCOH.exe, the game’s process. In order to identify who «owns» that window do the following.

NOTE: Stage 1 and stage 2 better be configured and run simultaneously so as to economize on time

Stage 1

1. Download and run Process Explorer
2. Keep Process Explorer running in the background and launch CoH
3. Whenever the error occurs, do not close the error window but switch over to Process Explorer
4. In Process Explorer’s toolbar click «FInd Window’s Process» and hover over to the error message

If it is RelicCOH.exe then you can make use of the information gathered in stage 2. Otherwise, let me know what process came up, so that we get to know if any use of Process Monitor is relevant, or if we have to take a different route to troubleshooting it.

Stage 2

1. Download, unzip and run ProcMon as administrator (if not already)
2. Select Filter->Filter (Ctrl+L) and choose «Process Name» from the left topmost dropdown menu and «is» from the one next to it
3. Type RelicCOH.exe in the textbox to the right
   
4. Click Add and then OK
5. Now fire up CoH and when the error message pop-up make sure you note down your system time, as shown on the taskbar.
6. Scroll down to the events logged around the specific time and notice if there is weird or repeating behaviour. Note down the text in the Result column and look for things such as, NAME_NOT_FOUND, SHARING_VIOLATION, NAME_COLLISION etc. In short anything that doesn’t say SUCCESS.

Or you can save the whole Process Monitor event log using File->Save As and making sure the options are set as follows.

Then compress the resulting file and upload it somewhere so I can take a look.

This post has been edited by aramonkg: Jul 21 2009, 14:49 PM

Источник

8 ноя. 2020 в 19:54

Ребята, Help! Никогда не было проблем с запуском, но после некорректного выключения компа перестала запускаться данная игрушка, выдаёт каждый раз BugSplat с соответствующим текстом:

Unable the create the error report.

Please verify that there is enough space in your TEMP folder.

Как бы я не пытался, игра так и не заработала (от отчаяния переустанавливал игру 4 раза).
Если кто-то сталкивался с такой проблемой, очень прошу помочь с этим!

9 ноя. 2020 в 6:31

Turn off Steam and delete the KillingFloor2 folder in C:DocumentsMy Games. Launch Steam and start KF2, don’t click or tab out while its loading.

(Additional note: Make sure you are not using backup software such as GoogleDrive or OneDrive, they are known for interfering with the Documents folder.)

Иногда при запуске Killing Floor появляются ошибки. Неприятно, но установленная вами игра может не запускаться, вылетая, зависая, показывая чёрный экран и выдавая ошибки в окнах. Поэтому возникают вполне логичные вопросы: «Что делать?», «Из-за чего это происходит?» и «Как решить проблему?». Мы постарались собрать всю необходимую информацию с универсальными инструкциями, советами, различными программами и библиотеками, которые призваны помочь решить наиболее распространённые ошибки, связанные с Killing Floor и другими играми на ПК.

Отсутствует DLL-файл или ошибка DLL

Для начала следует объяснить, как вообще возникают ошибки, связанные с DLL-файлами: во время запуска Killing Floor обращается к определённым DLL-файлам, и если игре не удаётся их отыскать, тогда она моментально вылетает с ошибкой. Причём ошибки могут быть самыми разными, в зависимости от потерянного файла, но любая из них будет иметь приставку «DLL» .

Для решения проблемы необходимо отыскать и вернуть в папку пропавшую DLL-библиотеку. И проще всего это сделать, используя специально созданную для таких случаев программу DLL-fixer – она отсканирует вашу систему и поможет отыскать недостающую библиотеку. Конечно, так можно решить далеко не любую DLL-ошибку, поэтому ниже мы предлагаем ознакомиться с более конкретными случаями.

Ошибка d3dx9_43.dll, xinput1_2.dll, x3daudio1_7.dll, xrsound.dll и др.

Все ошибки, в названии которых можно увидеть «d3dx» , «xinput» , «dxgi» , «d3dcompiler» и «x3daudio» лечатся одним и тем же способом – воспользуйтесь веб-установщиком исполняемых библиотек DirectX .

Ошибка MSVCR120.dll, VCRUNTIME140.dll, runtime-x32.dll и др.

Ошибки с названием «MSVCR» или «RUNTIME» лечатся установкой библиотек Microsoft Visual C++ (узнать, какая именно библиотека нужна можно в системных требованиях).

Избавляемся от ошибки MSVCR140.dll / msvcr120.dll / MSVCR110.dll и других DLL раз и навсегда

Появляется цветной экран

Появление цветастого экрана часто связано с тем, что используются сразу две видеокарты. Если в материнской плате присутствует встроенный графический процессор, но играете на дискретном, игра в любом случае запустится на встроенном. Поэтому и возникают «цветные» проблемы, поскольку монитор подключён по умолчанию к дискретной видеокарте.

Не менее часто цветной экран появляется в том случае, если появились проблемы с выводом изображения. Подобное вызывает самые разные причины, но существуют две наиболее распространённые: 1 – стоят устаревшие драйвера; 2 – ваша видеокарта не поддерживается. Поэтому рекомендуем обновить в первую очередь драйвера.

Низкий FPS, Killing Floor тормозит, фризит или лагает

Современные игры крайне ресурсозатратные, поэтому, даже если вы обладаете современным компьютером, всё-таки лучше отключить лишние/ненужные фоновые процессы (чтобы повысить мощность процессора) и воспользоваться нижеописанным методами, которые помогут избавиться от лагов и тормозов.

Запустите диспетчер задач и в процессах найдите строку с названием игры (Killing Floor). Кликайте ПКМ по ней и в меню выбирайте «Приоритеты» , после чего установите значение «Высокое» . Теперь остаётся лишь перезапустить игру.

Лучшие видеокарты для комфортной игры в 1080p

Необходимое ПО для Killing Floor

Мы настоятельно рекомендуем ознакомиться со ссылками на различные полезные программы. Зачем? Огромное количество ошибок и проблем в Killing Floor связаны с не установленными/не обновлёнными драйверами и с отсутствием необходимых библиотек.

Последняя версия драйвера Nvidia GeForce .
Последняя версия драйвера AMD Radeon .
Пакет DirectX .

Библиотека Microsoft Visual C++ 2015
Библиотека Microsoft Visual C++ 2013

• Библиотека Microsoft Visual C++ 2012 Update 4
• Библиотека Microsoft Visual C++ 2010 (64-бит)
• Библиотека Microsoft Visual C++ 2010 (32-бит)
• Библиотека Microsoft Visual C++ 2008 (64-бит)
• Библиотека Microsoft Visual C++ 2008 (32-бит)
• Библиотека Microsoft Visual C++ 2005 Service Pack 1

Killing Floor вылетает в случайный момент или при запуске

Ниже приведено несколько простых способов решения проблемы, но нужно понимать, что вылеты могут быть связаны как с ошибками игры, так и с ошибками, связанными с чем-то определённым на компьютере. Поэтому некоторые случаи вылетов индивидуальны, а значит, если ни одно решение проблемы не помогло, следует написать об этом в комментариях и, возможно, мы поможем разобраться с проблемой.

Первым делом попробуйте наиболее простой вариант – перезапустите Killing Floor, но уже с правами администратора.

Как увеличить объём памяти видеокарты? Запускаем любые игры

Ошибка «Недостаточно памяти»

Возникает ошибка, связанная с недостатком памяти, практически по десятку причин. Конечно, наиболее распространённые – это либо нехватка оперативной памяти «железа», либо маленький размер файла подкачки. В последнем случае, даже если вы ничего настраивали, всё запросто мог испортить сторонний софт или банальное отключение файла подкачки.

Необходимо попробовать увеличить файл подкачки ( «Пуск» «Параметры системы» в строке наверху вводите «Производительность» выбирайте «Настройку представления и производительности системы» «Дополнительно» «Изменить» убираете галочку с функции «Автоматически выбирать…» выбираете размер ).

Появляется чёрный экран в Killing Floor

Появление чёрного экрана часто связано с конфликтом видеодрайверов и ПО. И реже всего с определёнными файлами Killing Floor. Впрочем, существует довольно много других причин, связанных с появлением «чёрного экрана смерти».

Первым делом при появлении проблемы следует обновить видеодрайвер. Многие пренебрегают этим совсем, но мы настоятельно рекомендуем сделать это, потому что для многих современных игр следом выходят и важные обновления, которые помогают запустить ту или иную игру.

Ошибка DirectX в Killing Floor

Первым делом необходимо установить «чистую» версию драйвера вашей видеокарты (то есть не стоит сразу спешить устанавливать тот же GeForce Experience, ничего лишнего от AMD и аудио).

Распространённые сетевые ошибки

Не вижу друзей / друзья в Killing Floor не отображаются

Неприятное недоразумение, а в некоторых случаях даже баг или ошибка (в таких случаях ни один способ ниже не поможет, поскольку проблема связана с серверами). Любопытно, что с подобным сталкиваются многие игроки, причём неважно, в каком лаунчере приходится играть. Мы не просто так отметили, что это «недоразумение», поскольку, как правило, проблема решается простыми нижеописанными способами:

Убедитесь в том, что вы вместе с друзьями собираетесь играть в одном игровом регионе, в лаунчере установлен одинаковый регион загрузки.

Создателю сервера нужно открыть порты в брандмауэре

Многие проблемы в сетевых играх связаны как раз с тем, что порты закрыты. Нет ни одной живой души, друг не видит игру (или наоборот) и возникают проблемы с соединением? Самое время открыть порты в брандмауэре, но перед этим следует понимать как «это» работает. Дело в том, что программы и компьютерные игры, использующие интернет, для работы требуют не только беспроблемный доступ к сети, но и вдобавок открытые порты. Это особенно важно, если вы хотите поиграть в какую-нибудь сетевую игру.

Часто порты на компьютере закрыты, поэтому их следует открыть. Кроме того, перед настройкой нужно узнать номера портов, а для этого для начала потребуется узнать IP-адрес роутера.

Закрытые порты, или что делать, если игр не видно/не подключается?

• Открываете командную строку с помощью команды «cmd» в Пуске.
• Вновь прописываете команду «ipconfig » без кавычек.
• Запускаете команду «netstat -а» , после чего отобразится полный список с номерами портов.

Обязательно следует убедиться в том, что вы обладаете правами администратора Windows.

Изображение в Killing Floor мерцает

Как правило, проблема связана с перегретой видеокартой. Первым делом следует проверить провода, вдруг они перекрыли вентиляторы системы охлаждения, но если там полный порядок, тогда самое время сбросить разгон видеокарты: нужно войти в приложение MSI Afterburner (или подобное) и нажать на «Reset» .

Не работает мышь, клавиатура или контроллер

Чаще всего, если такие проблемы и возникают, то строго на стороне игрока. В процессе подключения нового девайса ОС моментально пытается установить необходимый пакет драйверов, но проблема в том, что он стандартный, а значит, будет совместим далеко не с каждым устройством, поэтому проверьте наличие необходимых драйверов. Кроме того, на управление могут повлиять вирусы, так что обязательно проверьте систему.

Эмуляция джойстика Xbox 360

Свежее видео на канале Coop-Land:

OS: Windows NT 6.1 (Build: 7601)
CPU: GenuineIntel PentiumPro-class processor @ 3220 MHz with 1975MB RAM
Video: NVIDIA GeForce 9800 GT (1070)

Could not spawn a GUI Controller!

Ищи файл killingfloor.ini
Секция «[Engine.Engine]» должна выглядеть так:

После построй алтарь, принеси жертву Слаанешу и можешь играть в КФ

Shikki,
Продолжение:
А если по существу. Перевод ошибки: Игра не может определить твой ДиректX 3D

I have been getting crashed out of the game for this error many times recently. I adjusted the number I found on a Steam thread off google, which seemed to fix it.. until 16 waves into the next game when it did it again. I have plenty of disk space. What is this error and how do I get rid of it?

New comments cannot be posted and votes cannot be cast

Звук в Killing Floor отсутствует или пропадает в заставках

Чаще всего проблема связана с высоким звуковым разрешением в параметрах Windows, а именно – с частотой разрядности и дискретизации. Поэтому избавиться от проблемы можно лишь одним способом – понизить это разрешение.

• В трее нажмите ПКМ по значку динамика;
• В открывшемся меню необходимо выбрать пункт «Звуки» ;
• Следом необходимо выбрать устройство (это могут быть либо динамики, либо наушники) и нажать на «Свойства» ;
• Перейти на соседнюю вкладку «Дополнительно» ;
• Отыщите меню под названием «Формат по умолчанию» , чтобы задать значение, но оно должно быть ниже текущего;
• Нажмите «Применить» , откройте Killing Floor и проверьте результат проделанной работы.

Проблему, которая связана с отсутствием звука в заставках, решить первым способом не получится, поэтому сделайте следующее:

• Вновь в трее ПКМ по значку динамика;
• В меню отыщите функцию под названием «Пространственный звук» , чтобы отключить;
• Остаётся лишь перезапустить Killing Floor и проверить результат.

Ошибка 0xc0000142 / 0xe06d7363 / 0xc0000906

Эти ошибки относятся не только к одним из наиболее часто встречаемых проблем, но и к наиболее сложным в процессе исправления. Потому что никогда сразу непонятно, почему они появляются. С другой стороны, известно, что подобное происходит только в двух случаях: 1 – в процессе запуска какой-нибудь программы или игры, 2 – буквально сразу после того, как удалось войти в систему.

Причём в первом случае чаще всего это касается недавно установленного приложения, поскольку ни одна из этих ошибок никогда сама по себе не появляется. В любом случае существует несколько способов, которые помогают избавиться от них. Рекомендуем внимательно ознакомиться с каждым.

Отключите антивирусную программу

Ни для кого не секрет, что часто всему виной является антивирус. Только вот в случае с перечисленными ошибками лучше программу не просто отключить, а временно удалить. После чего попробовать запустить приложение. Однако если это не поможет, тогда сделайте следующее:

Полностью удаляете приложение, чтобы не осталось никаких папок и остаточных файлов.

Отключите «Защитник Windows»

Помимо антивирусной программы, также следует попробовать отключить «Защитник Windows». Поскольку он тоже запросто может быть причиной появления этих ошибок. Для этого нужно сделать следующее:

Открыть «Центр безопасности Защитника Windows» выбрать настройки нажать на раздел «Защита от вирусов и угроз».

Проверьте путь на наличие кириллицы

Обязательно проверьте, что путь к приложению не содержал наличие кириллицы. Причём стоит отметить, что наличие в адресе «Пользователи» никак не влияет на это. Так что если после «Пользователи» идёт кириллица, тогда придётся создавать нового локального пользователя, у которого имя будет иметь латинские буквы. В таком случае также, возможно, придётся переустановить и само приложение на новом пользователе.

Воспользуйтесь чистой загрузкой

Решить проблему в таком случае можно чистой загрузкой. Как правило, это помогает в тех случаях, когда ошибка появляется при запуске Windows 10. Поскольку причина практически всегда связана с какой-то определённой программой или службой, что находятся в автозагрузках.

• Открываете в Windows 10 окно «Параметры», используя меню

или сочетание клавиш

Проверьте целостность файлов

Вполне возможно, ошибка возникает из-за того что была повреждена целостность системных файлов. И для их проверки у Windows 10 существа два инструмента – DISM.exe с командой Repair-WindowsImage для PowerShell и SFC.exe. Мы рекомендуем воспользоваться последним, поскольку он наиболее привычный и простой. А осуществить проверку можно следующим образом:

Откройте «Командную строку» от имени администратора (для этого в поиске просто введите «Командная строка).

все найденные ошибки будут автоматически исправлены.

Измените значение в реестре

Реестр в операционной системе Windows 10 – это большая база данных. И именно эти данные определяют свойства и поведение системы. Поэтому редактирование в нём иногда помогает избавиться от ошибок. Только вот без должного опыта или надёжной инструкции лезть туда самостоятельно крайне не рекомендуется.

Поэтому предлагаем воспользоваться нижеописанной инструкцией. Только перед тем, как начнёте что-то менять, убедитесь в наличие нужного раздела. Сделать это можно следующим образом:

в окне «Выполнить» введите команду regedit нажмите

после чего в окне «Редактор реестра» отыщите раздел, представленный ниже.

Запустите восстановление системы

Это касается тех случаев, когда игра работала адекватно, но в определённый момент начала неожиданно появляться ошибка. Хотя игра не подвергалась никаким посторонним действиям. К примеру, не устанавливались моды, патчи и многое другое. В общем, тогда можно запустить процесс восстановления системы.

Другие способы

В обязательном порядке попробуйте вручную установить драйверы для графического процессора. Причём это касается не только интегрированной видеокарты, но и дискретной.

Ошибка 0xc000007b в Killing Floor

В худшем случае ошибка 0xc000007b или «This application was unable to start correctly» связана с повреждёнными системными файлами ОС, а в лучшем – с драйверами видеокарт от Nvidia.

Самый очевидный и наиболее простой способ разобраться с ошибкой – переустановить драйверы для видеокарты, а после запустить игру от имени администратора.

После установки Dependency Walker 64bit , запускайте утилиту и переходите по следующему адресу: «View» «Full Patch» «.exe-файл проблемной игры» (в некоторых случаях после это появляется окно с ошибками, но на него не стоит обращать внимания, просто закройте окно). Переключитесь на раздел «Module» , крутите до конца ошибки, смотрите на значения в столбиках.

Источник

Killing Floor 2 Исправление ошибок Bugsplat, нет MSVCR100.dll, критическая ошибка, нет XAPOFX1_5.dll, сбой при запуске, нет Bugsplat64.dll

На компьютере Killing Floor 2 возникают такие ошибки, как ошибка Bugsplat, критическая ошибка, сбой при запуске, отсутствие MSVCR100.dll, отсутствие Bugsplat64.dll и т. д.

Здесь мы обсудим все ошибки и проблемы, связанные с игрой, а также их исправления и обходные пути.

Killing Floor 2: черный экран, сбой и исправления

Killing Floor 2 — это шутер от первого лица, разработанный Tripwire Interactive. Игра была запущена еще в 2016 году и набирает обороты благодаря базе преданных игроков, поскольку студия постоянно выпускает новый контент.

Однако версия игры для ПК сталкивается с ошибками, такими как фатальная ошибка, черный экран при запуске, сбой при запуске, отсутствие файлов .dll и т. д.

Ниже приведены ошибки и проблемы, с которыми сталкиваются игроки с Killing Floor 2, а также их исправления и обходные пути.

Исправление ошибки Bugsplat

Игроки Killing Floor 2 сообщают, что они сталкиваются с ошибкой Bugsplat во время игры. Исправить эту ошибку довольно просто. 

Перейдите в «Документы Мои игры KillingFloor2 KFGame Config» и откройте файл KFEngine.ini. Найдите в файле конфигурации следующее и установите для них значение 0.

[Core.System]

MaxObjectsNotConsideredByGC = 0

StaleCacheDays = 30

MaxStaleCacheSize = 0

MaxO TotalCacheSize = 0

PackageSizeSoftLimit = 0

Сохраните изменения, и ошибка Bugsplat будет исправлена. Если проблема не исчезнет, ​​просто удалите папку Config.

Проверить исправление временной папки

Игроки сообщают, что не могут играть в Killing Floor 2, поскольку при запуске игры у них возникает ошибка «Убедитесь, что в папке TEMP достаточно места».

Исправить эту ошибку очень просто. Перейдите в «Документы Мои игры KillingFloor2» и удалите папку KillingFloor2. Затем зайдите в Steam и проверьте файлы игры. Это исправит ошибку.

Исправление фатальной ошибки

По словам игроков Killing Floor 2, они испытывают фатальную ошибку при запуске и не могут играть в игру. Эта ошибка связана с драйвером графического процессора: либо установите более старую версию, либо попробуйте другую версию драйвера для графического процессора.

Выполните чистую установку, и фатальная ошибка Killing Floor 2 будет исправлена.

Если вы получаете эту ошибку во время игры на ноутбуке с выделенным графическим процессором, убедитесь, что игра переключается на выделенный графический процессор.

Для пользователей графического процессора Nvidia откройте Панель управления Nvidia> Управление настройками 3D> Настройки программы> выберите игру> выберите «Высокопроизводительный процессор Nvidia».

Как пользователи AMD GPU, пером Radeon Settings> Preferences> Additional Settings> Power> Switchable Graphics Application Settings. Выберите игру из списка и назначьте игре «Профиль высокой производительности» в разделе «Настройки графики». Это исправит фатальную ошибку.

Игра не запускается, исправление сбоя при запуске

По словам игроков, Killing Floor 2 вылетает сразу после запуска, а у некоторых даже не запускается. Вот как можно исправить этот сбой при запуске Killing Floor 2.

Если у игры нет прав администратора или учетная запись Windows не является администратором, это может быть причиной того, что Floor 2 вылетает при запуске. Убедитесь, что у учетной записи WIndows есть права администратора. 

Щелкните правой кнопкой мыши исполняемый файл игры> свойства> вкладка «Совместимость»> «Изменить настройки для всех пользователей»> установите флажок «запустить эту программу от имени администратора». Запустите игру, и проблема будет устранена.

Утилиты сторонних производителей также могут вызывать сбой игры при запуске. Отключите такие инструменты, как MSI AFterburner и GeForce Experience, и проблема будет исправлена.

Если вышеуказанное исправление не сработало, скорее всего, ваш антивирус / WindowsDefender может блокировать игру. Либо отключите антивирус, либо исключите папку установки игры и документы. Проверьте файлы игры, и проблема будет исправлена.

MSVCP110.dll, MSVCR100.dll, Bugsplat64.dll Отсутствует исправление

Игроки Killing Floor 2 сообщают, что не могут играть в игру из-за ошибки отсутствия файлов .dll при запуске. По словам игроков, MSVCP110.dll, MSVCR100.dll и Bugsplat64.dll появляются как отсутствующие.

Ошибка «MSVCP110.dll отсутствует» может быть устранена путем установки распространяемого пакета Visual C ++ 2012 как для x64, так и для x86 версии.

Ошибка «MSVCR100.dll отсутствует» может быть исправлена ​​путем установки версий Visual C ++ 2012 и 2010 для x64 и x86. Программа установки находится в двух местах в папке Steam. Перейдите в «Steam SteamApps common killingfloor2 _CommonRedist». Установите Visual C ++ 2015, и ошибка «MSVCR100.dll отсутствует» будет исправлена.

Что касается ошибки «Bugsplat64.dll missing», перейдите в «Документы / мои игры» и удалите папку «KillingFloor2». Это исправит ошибку, и Killing Floor 2 снова начнет работать.

X3DAudio1_7.dll, XAPOFX1_5.dll, XINPUT1_3.dll, d3dx9_43.dll Отсутствует исправление

Killing Floor 2 Игроки сообщают, что им не хватает следующих файлов .dll, что мешает им играть в игру.

X3DAudio1_7.dll
XAPOFX1_5.dll
XINPUT1_3.dll
d3dx9_43.dll

Исправить эти отсутствующие файлы .dll просто: установите DirectX. Перейдите в «Steam steamapps common Steamworks Shared _CommonRedist DirectX». Установите DirectX, и ошибки будут исправлены. 

В противном случае вам придется загрузить последнюю версию DirectX с официального сайта Microsft, и ошибки отсутствующих файлов .dll будут исправлены.

Исправление черного экрана

Черный экран при запуске — обычная проблема для компьютерных игр, и, очевидно, Killing Floor 2 не исключение. Игроки сообщают, что при запуске у них появляется черный экран с нормальным воспроизведением звука в фоновом режиме.

Чтобы исправить это, запустите игру и, когда появится черный экран, нажмите «Alt + Enter». Игра перейдет в оконный режим и начнет отображаться. 

Перейдите в настройки видео, установите разрешение, соответствующее вашему дисплею, и вы сможете играть в игру в полноэкранном режиме. Если это не решит проблему, попробуйте обновить драйвер графического процессора.

Вот и все, что касается наших исправлений Killing Floor 2 для таких ошибок, как ошибка Bugsplat, фатальная ошибка, отсутствие Bugsplat64.dll, отсутствие X3DAudio1_7.dll и Больше.

Если вы сталкиваетесь с ошибками и проблемами в других компьютерных играх или на вашем ПК, также посетите наш центр, где вы найдете часто встречающиеся ошибки ПК и их исправления.

Killing Floor 2 Исправление ошибок Bugsplat, отсутствие MSVCR100.dll, критическая ошибка, отсутствие XAPOFX1_5.dll, сбой при запуске, отсутствие исправления Bugsplat64.dll

Просмотров сегодня: 758

The most common cause of this is corrupt files in the user directory or missing prerequisite files. Please try the following:

If you run security software such as an anti-virus or firewall (and other similar software), make sure the game is on any allowed/ignore list. If the game starts to misbehave after an update, try removing and re-adding the game to any such lists.

For the best connection results, please add these IPs to any security software permission/exclusion list:
analytics.tripwireinteractive.com
tripwireinteractive.com
playfabapi.com
epicgames.dev

Common Solutions

Corrupted Configuration:

1. Navigate to: C:Users[your name]DocumentsMy Games.
2. Delete the «KillingFloor2» folder.
3. Try playing the game now.

Irregular Compatibility Setting:

1. Navigate to Steamsteamappscommonkillingfloor2BinariesWin64.
2. Locate the KFGame.exe and right-click it.
3. Now select «Properties».
4. Click on the «Compatibility» tab.
5. If checked, uncheck «Run this program in compatibility mode».
6. If checked, uncheck «Run in 256 colors».
7. If checked, uncheck «Run in 640 x 480 screen resolution».
8. If checked, uncheck «Disable visual themes».
9. If checked, uncheck «Disable display scaling on high DPI settings».
10. If checked, uncheck «Run this program as an administrator».
11. Click «Apply» to apply changes».
12. Click «OK» to close the window.
13. Try playing the game now.

Device Detection Failure:

1. Disconnect any xbox, playstation, VAKOSS, DS2 or mayflash controllers. This includes usb adapters.
2. Try playing the game now.

For users who have a graphics chip built into their CPU from Intel or AMD, make sure that the game is set to launch with your dedicated GPU via the video card control panel software that comes with it. The game does not support CPU graphics chipsets.

Nvidia — Follow the instructions below to change the default graphics processor:

1. Open the NVIDIA Control Panel.
2. Click the Manage 3D Settings link.
3. Click the Global Settings tab.
4. In the Preferred graphics processor drop down menu, select “High-performance NVIDIA processor).

AMD

1. If your Catalyst Control Center has the Switchable Graphics tab go there and browse to locate vngame.exe and set it for High Performance

Improper Physx Installation:

1. Go to your control panel for add/remove programs
2. Uninstall «NVIDIA Physx».
3. Then navigate to: Steamsteamappscommonkillingfloor2_CommonRedistPhysX9.14.0702
4. Run the Physx installer.
5. Try playing the game now.

We have also seen some cases where doing a clean install of the PhysX driver (uninstall completely and reinstall the latest: http://www.nvidia.com/object/physx-9.15.0428-driver.html ) has helped.

Improper Microsoft C++ Redists Installation:

1. Go to your control panel for add/remove programs.
2. Uninstall all versions of 2010 Microsoft C++ Redistribs.
3. Uninstall all versions of 2012 Microsoft C++ Redistribs.
4. Navigate to: SteamsteamappscommonSteamworks Shared _CommonRedistvcredist
5. In the 2010 folder, install the x64 version, and right-click run as admin.
6. In the 2012 folder, install the x64 version, and right-click run as admin.

Hidden Errors:

1. Try running the KFGame.exe as an administrator.
2. Sometimes this will cause a hidden error to appear.
3. Navigate to Steamsteamappscommonkillingfloor2BinariesWin64.
4. Locate the KFGame.exe and right-click it.
5. Now select «Run as Administrator».
6. If you get an error about a missing .dll, most likely you are having Microsoft C++ Redist installing problems.
7. If you get an error about «0xc000007b», skip to the end of the advanced solutions and read the directions specifically for that.

Deep Cache Verification:

1. Navigate to Steamsteamappscommonkillingfloor2
2. Delete the binaries folder.
3. Navigate to Steamsteamappscommonkillingfloor2KFGameBrewedPC
4. Delete the file: GlobalShaderCache-PC-D3D-SM4.bin
5. Delete the file: GlobalShaderCache-PC-D3D-SM5.bin
6. Go to Steam Library.
7. Right-click on Killing Floor 2.
8. Select Properties.
9. Go to Local Files tab.
10. Click the button «Verify Integrity of Game Cache…». This should take 10-15 minutes.
11. Try playing the game now.

Advanced Solutions:

Eliminating Variables:
If none of the common solutions worked for you then let’s go ahead and eliminate some variables. Please disable your firewall and/or antivirus for the next thirty minutes. After that is done, let’s force the game to launch in a dx10, windowed mode.

1. Go to your Steam Library.
2. Right-click on Killing Floor 2.
3. Select Properties.
4. You are on the General tab. Click on «Set Launch Options».
5. Type in: -windowed -dx10
6. Click OK.
7. Try playing the game now.

Remote Desktop Configuration:
If you recently installed a Window’s 10 update and you see an error in your logfile stating that «this application cannot be run over a remote desktop configuration.» then you should do the following:

1. Change your desktop resolution.
2. Reboot your computer.
3. Change your desktop resolution back.
4. Try playing the game now.

Missing nvcuda.dll:
If you see errors in your logfile relating to a missing nvcuda.dll, then you should do the following:

1. Navigate to C:WindowsSysWOW64.
2. Locate the file «nvcuda.dll» and right-click it.
3. Select «Copy».
4. Navigate to C:WindowsSystem32.
5. Right-click inside this folder to paste your copied file.
6. Try playing the game now.

Serial Size Mismatch:
If you see errors in your logfile relating to a «[file name] Serial Size Mismatch», then you should do the following:

1. Go to Steam Library.
2. Right-click on Killing Floor 2.
3. Select Properties.
4. Go to Local Files tab.
5. Click «Browse Local Files».
6. Perform a search for the [file name]. Do not include the file’s extention when you search (omit .stg44, etc).
7. Once located, delete that file and close the window.
8. Now you’re back on the Killing Floor 2 properties. Click the button «Verify Integrity of Game Cache…» This should take 10-15 minutes.
9. Try playing the game now.

ReadFile Beyond EDF:
If you see errors in your logfile relating to a «EOF [long number]/[long number]», then you should do the following:

1. Go to Steam Library.
2. Right-click on Killing Floor 2.
3. Select Properties.
4. Go to Local Files tab.
5. Click «Browse Local Files».
6. Navigate to the folder that houses the file.
7. Once located, delete that folder and close the window.
8. Now you’re back on the Killing Floor 2 properties. Click the button «Verify Integrity of Game Cache…» This should take 10-15 minutes.
9. Try playing the game now.

Bad Name Index:
If you see a reference to «Bad name index [numbers]» in your logfile, then you should do the following:

1. Go to Steam Library.
2. Right-click on Killing Floor 2.
3. Select Properties.
4. Go to Local Files tab.
5. Click the button «Verify Integrity of Game Cache…». This should take 10-15 minutes.
6. Try playing the game now.

Fatal Error Problem 1:
If you see a reference to «=== Critical error: === Fatal error!» in your logfile, this usually means there is some sort of driver conflict happening. Windows 10 automatically pushes updates sometimes so your computer may have changed overnight. You should do the following:

1. Find out what NVIDIA driver version you curently have.
2. Find out what the newest NVIDIA driver version is.
3. If you are not on the newest, uninstall your current NVIDIA drivers and upgrade to the newest version.
4. Try playing the game now. If that doesn’t work then:
5. Since you are on the newest GPU version, locate the oldest version available to your GPU from NVIDIA.
6. Uninstall your current NVIDIA drivers and downgrade to the oldest version.
7. Try playing the game now.

Fatal Error Problem 2:
If you see a reference to «=== Critical error: === Fatal error!» in your logfile followed up with this specific set of text:

Address = 0x76ad0944 (filename not found)
Address = 0x5bf168 (filename not found)
Address = 0x5880bed0 (filename not found)
Address = 0x1 (filename not found)
Address = 0xf34bca97 (filename not found) [in D:Windowssystem32dxgi.dll]
Address = 0xf34c2dae (filename not found) [in D:Windowssystem32dxgi.dll]

You should do the following:

1. Please reference the known software conflicts section.

Assertion Failed:
If you see something around the lines of: «Critical: appError called: Assertion failed» then the most likely culprit is your crossfire is preventing the game gathering all necessary files during startup.

1. Find out what GPU you are using.
2. Figure out how to disable crossfire or force use a single gpu.
3. Try playing the game now.

Corrupt Favorites (crashing on menus):
If you are crashing when clicking on menu’s then it is likely you have corrupted weapon favorites for some reason. If you see errors in your logfile relating to «Adding Weapon to favorites: string_#», then you should do the following:

1. Disable Steam Game Cloud Storage for Killing Floor 2.
2. Turn off Wi-Fi or unplug your ethernet cable.
3. When you launch Killing Floor 2 it should look like everything has «reset».
4. Now quit your game and turn on your Wi-Fi or plug your ethernet back in.
5. Launch Killing Floor 2.
6. Minimize it and activate the steam cloud storage.
7. Taken from thread: https://steamcommunity.com/app/232090/discussions/1/1694923613878834990/

0xc000007b Error:
If you are getting «0xc000007b» error when you’re running your KFGame.exe as an administrator, see below:

1. Download Dependencies (https://github.com/lucasg/Dependencies/releases) or Dependency Walker (http://www.dependencywalker.com/)
2. Launch Dependencies/Dependency Walker and hit the «open» icon.
3. Navigate to G:Steamsteamappscommonkillingfloor2BinariesWin64
4. Select KFGame.exe.
5. In the middle of the screen you’ll see a column for CPU. Click it to sort all the files by it.
6. Right-click on a random row and select «show full file path».
7. Scroll either all the way up, or all the way down, looking for any files that have «x86» in the CPU column. If they are API or EXT .dlls you can skip them. You can also skip the one named nvcuda.dll. Note the filepath it is in.
8. Download that .dll from online. Make sure it is the x64 version. Please be careful what site you use and do a virus check on your downloaded file if necessary.
9. Replace the existing .dll in the appropriate folder.
10. Rinse and repeat. Feel free to try clicking play after each one.

Crashing frequently on map change:

1. Navigate to your …DocumentsMy GamesKillingFloor2KFGameConfig… directory
2. Open your KFEngine.ini
3. Run a search for a line containing MaxObjectsNotConsideredByGC=179220.
4. Try changing the value from 179220 to 33476, making sure not to change the values of any other functions. Afterward, save the file and attempt to play two continues matches.

Known Software Conflicts
The following softwares may or may not interfere with Killing Floor 2:

• MSI Afterburner
• RivaTuner
• DAEMON Tools
• DAEMON Tools Lite
• CAM Software
• PlayClaw
• Mirillis Action
• Dxtory: Possible solution: Go to the «Advanced» Tab in DxTory and under «Hook Option» tick the «Delay Hook» box and set a timer of around 6 seconds or more depending on when your game stops crashing. credit to CryCel for finding it.
• FRAPS
• D3Dgear
• RTSS: Possible solution: Set Custom Direct 3D Support to ON.

If the game prompts you to send in a bugsplat error report, please let it
do so along with your email address. This will help us diagnose and
fix the crash (if it isn’t fixed by any of the above). We are
often unable to provide any further suggestions or direct help as we
continue to look into player submitted reports to determine cause and
work on fixes.