It's broken.
Fix it immediately
[BUG] Tiny Terror : No shrinking.
lundi 26 juin 2017
[BUG] Tiny Terror : No shrinking.
It's broken.
Fix it immediately
[BUG] Tiny Terror : No shrinking.
Server Takeover Feature
- After a successful takeover, the server just defaults to "normal difficulty" and "7 waves", ignoring my previous settings.
- I have Soloplayers doing a passworded takeover. That's what solo offline is for. Can servers really be taken over by solo players? Or did I just look into the admin panel at a moment, when his friends were already gone?
Regarding 2: If it is possible for soloplayers to do takeovers, how can I prevent it? I don't want to let singleplayers block a server. Is there a way to set the minimum player count for takeovers to 2? I don't want to set the minimum player count for non takeover games on 2 though.
Server Takeover Feature
KF2 Was Better Before The Zed Head-Blocking Mechanic Was Added
I just wanted to talk a bit about the Zed head-blocking mechanic that has been in the game for awhile now. For me personally, this change to the game is unnecessary and 'anti-gamer' towards perks that rely on headshots. As a Commando main, I greatly enjoyed the game before zed-blocking was a thing -- now I find the tediousness of losing precious ammo to zed-blocking to be ruining a lot of my enjoyment. The mechanic itself wouldn't be an issue if it wasn't a guaranteed chance of happening whenever a Zed takes damage. In my opinion, it just needs a few tweaks to make it less obnoxious in a game that focuses on being a satisfying bullet-hell shooter.
In its current state, Zeds with blades will always block their heads after taking damage on Sui/HoE. Why is it this way? Were perks like Commando and Sharpshooter too powerful in skilled hands? Before I go further, let me mention that my gripe with headblocking is only with Gorefiends and Bloats. Both are tanky and powerful Zeds already, so why do they have to be more annoying with blocking?
According to the wiki: "Gorefiends can block gunfire. When shot at, Gorefiends will cross their swords in front of their face to block bullets. When blocking, Gorefiends take 20% less damage, and incapacitating effects are 80% less effective. On Suicidal and Hell On Earth, Gorefiends have a very medium chance to block when shot at."
'A very medium chance?' That's funny, last time I shot at any zed with melee weapons (probably over tens of thousands of times now,) they seem to block their heads no matter what.
The cooldown for blocking is ~2 seconds, making it incredibly easy for zeds like Gorefiends to close the distance on a player. For example: if a Gorefiend gets hit by a stray bullet, he will block his head and start sprinting towards a player. For a Commando, Sharpshooter, Medic, or SWAT with early weapons, you have to wait for the Gorefiend to stop blocking so you can shoot his head off. But by the time he gets in range of you, his block is up AGAIN, and he will keep his head safe then proceed to spin-to-win -- without the player ever having a chance to get a clear shot at his head beforehand.
It just confuses me why adding a mechanic that punishes players who are skilled at headshotting was added. Do Demolitions or Firebugs have to play around this mechanic? No. Do players enjoy dying to 5 gorefiends who all block their heads in complete safety, while sprinting at full speed? No. Do players just want to play a shooter game where they can be rewarded for aiming at heads without anti-fun mechanics punishing them for doing so? Yes.
I know it's very possible to quickly decapitate these Zeds before blocking, but that doesn't mean that even the best players can do it 100% of the time. Zeds will get hit by stray bullets, which then prompts them to block before you can decapitate them. Zeds will lift their swords in mobs and protect each other's heads as well by random chance, making big groups of Gorefiends and Gorefasts a sprinting death-ball of blocking metal.
Here are several suggestions to tweaking the zed-blocking mechanic that I think would help make it insanely less 'anti-gamer.'
(Note that I don't want ALL of these changes, I just want to throw out a bunch ideas)
-Zeds will only block when taking head damage
-Zeds will only block when below 70% health
-Zeds move 25% slower when blocking
-Zeds can only block once every 10 seconds
-Zeds will not block if they are within 1 meter of a player
-Zeds will stumble if their blades are shot while blocking
-Players can shoot off Zed's arms
So, if you manage to read through my wall of text -- Thank you for reading! As a closing statement, I just want to say that I adore this game and I am grateful for all the updates Tripwire has given us. I might come off as another complainer, but I truly want to try and help this game be the best that it can be. So what do you think about Zed-Blocking, do you agree or disagree with my post? Let's make it a discussion thread.
KF2 Was Better Before The Zed Head-Blocking Mechanic Was Added
Patch Scheduled For Tomorrow - 1.01b
Major Update (Hitching/Stuttering)
- Addressed ‘hitching/stuttering’ that many players would experience during gameplay on all maps. Please note, this will only address those users who have 6GB+ RAM only. Please also note, players will experience slightly longer load times upon initially launching the game, as some previously ‘streamed’ content is now loaded on game client launch. As always, please be sure to report your feedback on the official Tripwire Interactive RS2: Vietnam forums: http://ift.tt/2uap4rv
Additional Crash Fixes
- Fixed several crashes that would occur when players loaded between maps
- Fixed a crash that would occur when in spectator mode
Patch Scheduled For Tomorrow - 1.01b
Killing floor 2 ps4 Killing Floor 2 - Summer Side Show
Killing floor 2 ps4 Killing Floor 2 - Summer Side Show
Unretarding game mouse settings?
Unretarding game mouse settings?
Competitive PvE Mode Coming?
So is Killing Floor 2 getting something like this soon? Because Playing COOP is pretty boring atm because a lot of people have mastered the game which makes it boring to play with randoms because I can win pretty easily while sucking, b/c a vet can solo with everyone dead or I'm not good enough to carry a bunch of noobs. However pitting vets against each other to see who makes it to the highest wave is an experience that is always challenging because you're putting your ZED killing skills against an enemy team.
Competitive PvE Mode Coming?
KFKF listen server doesn't work
http://ift.tt/2tN6G8F
after opening all 8 required ports no 1 can join my listen server
all mutators turned off
I don't understand y my listen server doesn't work and need some help with it
KFKF listen server doesn't work
[Crash]Game Crashes within 5 minutes of connecting to various servers
I am looking for some help with a issue I am having that makes my game crash within minutes of connecting to a new server. I have tested with 5 or so different servers, also did some testing of general solutions (verify integrity, reinstall, cleared config files from MyGames)
Here is the latest logs:
Code:
Log: Log file open, 06/25/17 20:06:18 Init: Memory Profiling : Disabled Init: WinSock: version 1.1 (2.2), MaxSocks=32767, MaxUdp=65467 Log: ... running in INSTALLED mode Init: Version: 7258 Init: Epic Internal: 0 Init: Compiled (32-bit): Oct 14 2015 15:31:40 Init: Changelist: 641002 Init: Command line: Init: Base directory: D:\Program Files (x86)\Steam\steamapps\common\Red Orchestra 2\binaries\win32\ [0000.13] Init: Computer: EVAN-DESKTOP [0000.13] Init: User: EvanLane [0000.13] Init: CPU Page size=4096, Processors=8 [0000.13] Init: High frequency timer resolution =4.101560 MHz [0000.13] Init: Memory total: Physical=15.9GB Pagefile=22.1GB Virtual=4.0GB [0000.24] Log: STEAMWORKS initialized 1 [0000.30] Init: WinSock: I am Evan-Desktop (192.168.5.11:0) [0000.30] Init: Presizing for 0 objects not considered by GC, pre-allocating 0 bytes. [0000.31] Init: Object subsystem initialized [0000.34] DevDataBase: Connection to "Provider=sqloledb;Data Source=production-db;Initial Catalog=EngineTaskPerf;Trusted_Connection=Yes;Connection Timeout=2" or "10.1.20.20" failed [0038.09] Warning: Warning, Failed to load 'Texture2D EngineMaterials.RandomMirrorDisc': Failed to find object 'Texture2D EngineMaterials.RandomMirrorDisc' [0042.71] DevMemory: Virtual memory allocation size: 310.10 MByte (325165056 Bytes) [0052.10] SteamInfo: ROServerBrowser-Server responded [0052.13] SteamInfo: ROServerBrowser-Server responded [0052.14] SteamInfo: ROServerBrowser-Server responded [0052.14] SteamInfo: ROServerBrowser-Server responded [0052.15] SteamInfo: ROServerBrowser-Server responded [0052.15] SteamInfo: ROServerBrowser-Server responded [0052.16] SteamInfo: ROServerBrowser-Server responded [0052.16] SteamInfo: ROServerBrowser-Server responded [0052.17] SteamInfo: ROServerBrowser-Server responded [0052.17] SteamInfo: ROServerBrowser-Server responded [0052.18] SteamInfo: ROServerBrowser-Server responded [0052.19] SteamInfo: ROServerBrowser-Server responded [0052.19] SteamInfo: ROServerBrowser-Server responded [0052.19] SteamInfo: ROServerBrowser-Server responded [0052.20] SteamInfo: ROServerBrowser-Server responded [0052.20] SteamInfo: ROServerBrowser-Server responded [0052.21] SteamInfo: ROServerBrowser-Server responded [0052.21] SteamInfo: ROServerBrowser-Server responded [0052.22] SteamInfo: ROServerBrowser-Server responded [0052.22] SteamInfo: ROServerBrowser-Server responded [0052.23] SteamInfo: ROServerBrowser-Server responded [0052.23] SteamInfo: ROServerBrowser-Server responded [0052.24] SteamInfo: ROServerBrowser-Server responded [0052.24] SteamInfo: ROServerBrowser-Server responded [0052.24] SteamInfo: ROServerBrowser-Server responded [0052.25] SteamInfo: ROServerBrowser-Server responded [0052.27] SteamInfo: ROServerBrowser-Server responded [0052.28] SteamInfo: ROServerBrowser-Server responded [0052.29] SteamInfo: ROServerBrowser-Server responded [0052.30] SteamInfo: ROServerBrowser-Server responded [0052.30] SteamInfo: ROServerBrowser-Server responded [0052.31] SteamInfo: ROServerBrowser-Server responded [0052.31] SteamInfo: ROServerBrowser-Server responded [0052.32] SteamInfo: ROServerBrowser-Server responded [0052.33] SteamInfo: ROServerBrowser-Server responded [0052.34] SteamInfo: ROServerBrowser-Server responded [0052.34] SteamInfo: ROServerBrowser-Server responded [0052.35] SteamInfo: ROServerBrowser-Server responded [0052.35] SteamInfo: ROServerBrowser-Server responded [0052.36] SteamInfo: ROServerBrowser-Server responded [0052.36] SteamInfo: ROServerBrowser-Server responded [0052.36] SteamInfo: ROServerBrowser-Server responded [0052.37] SteamInfo: ROServerBrowser-Server responded [0052.37] SteamInfo: ROServerBrowser-Server responded [0052.38] SteamInfo: ROServerBrowser-Server responded [0052.38] SteamInfo: ROServerBrowser-Server responded [0052.38] SteamInfo: ROServerBrowser-Server responded [0052.39] SteamInfo: ROServerBrowser-Server responded [0052.40] SteamInfo: ROServerBrowser-Server responded [0052.40] SteamInfo: ROServerBrowser-Server responded [0052.40] SteamInfo: ROServerBrowser-Server responded [0052.40] SteamInfo: ROServerBrowser-Server responded [0052.41] SteamInfo: ROServerBrowser-Server responded [0052.41] SteamInfo: ROServerBrowser-Server responded [0052.42] SteamInfo: ROServerBrowser-Server responded [0052.42] SteamInfo: ROServerBrowser-Server responded [0052.43] SteamInfo: ROServerBrowser-Server responded [0052.44] SteamInfo: ROServerBrowser-Server responded [0052.44] SteamInfo: ROServerBrowser-Server responded [0052.45] SteamInfo: ROServerBrowser-Server responded [0052.45] SteamInfo: ROServerBrowser-Server responded [0052.46] SteamInfo: ROServerBrowser-Server responded [0052.47] SteamInfo: ROServerBrowser-Server responded [0052.47] SteamInfo: ROServerBrowser-Server responded [0052.51] SteamInfo: ROServerBrowser-Server responded [0052.53] SteamInfo: ROServerBrowser-Server responded [0052.55] SteamInfo: ROServerBrowser-Server responded [0052.55] SteamInfo: ROServerBrowser-Server responded [0052.56] SteamInfo: ROServerBrowser-Server responded [0052.57] SteamInfo: ROServerBrowser-Server responded [0052.57] SteamInfo: ROServerBrowser-Server responded [0052.58] SteamInfo: ROServerBrowser-Server responded [0052.58] SteamInfo: ROServerBrowser-Server responded [0052.59] SteamInfo: ROServerBrowser-Server responded [0052.59] SteamInfo: ROServerBrowser-Server responded [0052.60] SteamInfo: ROServerBrowser-Server responded [0052.60] SteamInfo: ROServerBrowser-Server responded [0052.60] SteamInfo: ROServerBrowser-Server responded [0052.61] SteamInfo: ROServerBrowser-Server responded [0052.62] SteamInfo: ROServerBrowser-Server responded [0052.62] SteamInfo: ROServerBrowser-Server responded [0052.63] SteamInfo: ROServerBrowser-Server responded [0052.63] SteamInfo: ROServerBrowser-Server responded [0052.64] SteamInfo: ROServerBrowser-Server responded [0052.65] SteamInfo: ROServerBrowser-Server responded [0052.65] SteamInfo: ROServerBrowser-Server responded [0052.66] SteamInfo: ROServerBrowser-Server responded [0052.66] SteamInfo: ROServerBrowser-Server responded [0052.66] SteamInfo: ROServerBrowser-Server responded [0052.67] SteamInfo: ROServerBrowser-Server responded [0052.67] SteamInfo: ROServerBrowser-Server responded [0052.68] SteamInfo: ROServerBrowser-Server responded [0052.68] SteamInfo: ROServerBrowser-Server responded [0052.68] SteamInfo: ROServerBrowser-Server responded [0052.69] SteamInfo: ROServerBrowser-Server responded [0052.69] SteamInfo: ROServerBrowser-Server responded [0052.70] SteamInfo: ROServerBrowser-Server responded [0052.70] SteamInfo: ROServerBrowser-Server responded [0052.71] SteamInfo: ROServerBrowser-Server responded [0052.71] SteamInfo: ROServerBrowser-Server responded [0052.71] SteamInfo: ROServerBrowser-Server responded [0052.72] SteamInfo: ROServerBrowser-Server responded [0052.73] SteamInfo: ROServerBrowser-Server responded [0052.73] SteamInfo: ROServerBrowser-Server responded [0052.73] SteamInfo: ROServerBrowser-Server responded [0052.74] SteamInfo: ROServerBrowser-Server responded [0052.75] SteamInfo: ROServerBrowser-Server responded [0052.80] SteamInfo: ROServerBrowser-Server responded [0052.82] SteamInfo: ROServerBrowser-Server responded [0052.82] SteamInfo: ROServerBrowser-Server responded [0052.82] SteamInfo: ROServerBrowser-Server responded [0052.82] SteamInfo: ROServerBrowser-Server responded [0052.83] SteamInfo: ROServerBrowser-Server responded [0052.83] SteamInfo: ROServerBrowser-Server responded [0052.83] SteamInfo: ROServerBrowser-Server responded [0052.83] SteamInfo: ROServerBrowser-Server responded [0052.84] SteamInfo: ROServerBrowser-Server responded [0052.85] SteamInfo: ROServerBrowser-Server responded [0052.85] SteamInfo: ROServerBrowser-Server responded [0052.85] SteamInfo: ROServerBrowser-Server responded [0052.85] SteamInfo: ROServerBrowser-Server responded [0052.86] SteamInfo: ROServerBrowser-Server responded [0052.86] SteamInfo: ROServerBrowser-Server responded [0052.87] SteamInfo: ROServerBrowser-Server responded [0052.88] SteamInfo: ROServerBrowser-Server responded [0052.89] SteamInfo: ROServerBrowser-Server responded [0052.89] SteamInfo: ROServerBrowser-Server responded [0052.91] SteamInfo: ROServerBrowser-Server responded [0052.93] SteamInfo: ROServerBrowser-Server responded [0052.95] SteamInfo: ROServerBrowser-Server responded [0052.95] SteamInfo: ROServerBrowser-Server responded [0052.95] SteamInfo: ROServerBrowser-Server responded [0052.95] SteamInfo: ROServerBrowser-Server responded [0052.96] SteamInfo: ROServerBrowser-Server responded [0052.97] SteamInfo: ROServerBrowser-Server responded [0052.97] SteamInfo: ROServerBrowser-Server responded [0053.04] SteamInfo: ROServerBrowser-Server responded [0053.04] SteamInfo: ROServerBrowser-Server responded [0053.05] SteamInfo: ROServerBrowser-Server responded [0053.06] SteamInfo: ROServerBrowser-Server responded [0053.06] SteamInfo: ROServerBrowser-Server responded [0053.07] SteamInfo: ROServerBrowser-Server responded [0053.07] SteamInfo: ROServerBrowser-Server responded [0053.14] SteamInfo: ROServerBrowser-Server responded [0053.15] SteamInfo: ROServerBrowser-Server responded [0053.24] SteamInfo: ROServerBrowser-Server responded [0053.24] SteamInfo: ROServerBrowser-Server responded [0053.30] SteamInfo: ROServerBrowser-Server responded [0053.31] SteamInfo: ROServerBrowser-Server responded [0053.31] SteamInfo: ROServerBrowser-Server responded [0053.32] SteamInfo: ROServerBrowser-Server responded [0053.33] SteamInfo: ROServerBrowser-Server responded [0053.37] SteamInfo: ROServerBrowser-Server responded [0053.37] SteamInfo: ROServerBrowser-Server responded [0053.40] SteamInfo: ROServerBrowser-Server responded [0053.45] SteamInfo: ROServerBrowser-Server responded [0053.45] SteamInfo: ROServerBrowser-Server responded [0053.48] SteamInfo: ROServerBrowser-Server responded [0053.54] SteamInfo: ROServerBrowser-Server responded [0053.56] SteamInfo: ROServerBrowser-Server responded [0054.08] SteamInfo: ROServerBrowser-Server failed to respond ip- -1791484845 [0054.24] SteamInfo: ROServerBrowser-Server failed to respond ip- 1156100536 [0054.88] SteamInfo: ROServerBrowser-Server failed to respond ip- 1504966554 [0055.08] SteamInfo: ROServerBrowser-Server failed to respond ip- 693527707 [0055.08] SteamInfo: ROServerBrowser-Server failed to respond ip- 693527708 [0058.30] Warning: InsertScene: Duplicate scene tag (ROUIScene_ConnectingAndDownloading) detected: NewScene 'ROUISceneConnecting ROGameMenus.MainMenu.ROUIScene_ConnectingAndDownloading' ExistingScene 'ROUISceneConnecting Transient.ROUIScene_ConnectingAndDownloading_0' [0059.47] DevMemory: Virtual memory allocation size: 304.45 MByte (319234048 Bytes) [0081.87] Error: 404: Failed to GET the requested file [0085.97] Warning: ParticleSystemComponent_27 (template: FX_WEP_Gun_Two.ShellEjects.FX_Wep_A_ShellEject_PhysX_Ger_Kar98) needs update but can't be because it's in TG_DuringAsnycWork and indirectly attached! [0087.66] Warning: ParticleSystemComponent_18 (template: FX_WEP_Gun_Two.ShellEjects.FX_Wep_A_ShellEject_PhysX_Sov_7_62_54R_Single) needs update but can't be because it's in TG_DuringAsnycWork and indirectly attached! [0087.72] Warning: ParticleSystemComponent_3 (template: FX_WEP_Gun_Two.ShellEjects.FX_Wep_A_ShellEject_PhysX_Ger_Kar98) needs update but can't be because it's in TG_DuringAsnycWork and indirectly attached! [0093.28] Warning: ParticleSystemComponent_20 (template: FX_WEP_Gun_Two.ShellEjects.FX_Wep_A_ShellEject_PhysX_Sov_7_62_54R_Single) needs update but can't be because it's in TG_DuringAsnycWork and indirectly attached! [0097.09] Warning: ParticleSystemComponent_50 (template: FX_WEP_Gun_Two.ShellEjects.FX_Wep_A_ShellEject_PhysX_Ger_Kar98) needs update but can't be because it's in TG_DuringAsnycWork and indirectly attached!
[Crash]Game Crashes within 5 minutes of connecting to various servers
please..?
please..?
Having trouble posting
Having trouble posting
Weapon Skins and Other Cosmetics
I've been enjoying KF2 since PC early access. I recently started up on PS4 to play with some friends and I'm pleasantly surprised at how well it runs.
One of my only gripes with the PS4 edition is a lack of cosmetics. I wouldn't mind unlocking them again, or even paying for them outright, but the drop rate is just too slow for me to get anything meaningful, as crates seem to almost never drop for me.
Are there plans to add individual cosmetics and weapon skins to the PSN store? Please take my money!
- Love your games, thanks!
P.S.
Dropping weapons is needlessly complicated.
Please let us assign drop weapon to one of the two TouchPad buttons.
< 3
Weapon Skins and Other Cosmetics
Online Mode Brazil
Here in Brazil, we can't play online, looking for a match.
And also we can't invite friends to play together.
Whenever I press the button to invite a friend, nothing happens. And to find match online, never find anyone in any region.
We're limited to playing alone only.
I love this game, congratulations for the great game.
Online Mode Brazil
Not a Glitch, But Damaging to the Community
A friend had a room empty out on wave 1. I joined. We cleared waves 2-4 together. We were nearly finished with wave 5 when a group of 4 joined and immediately voted and kicked us both. I have a video which includes player IDs (which I won't openly post).
I've experienced this abusive form of squad play in The Division and it ruins the game experience. I know that it is tough to police this sort of behavior; however, there should be some protection for the people already playing. If the group didn't want to play with others, they should have left, not hijack someone else's game.
Not a Glitch, But Damaging to the Community
RPG Reload Bug
RPG Reload Bug
dimanche 25 juin 2017
Weekly Outbreaks for all difficultes
Weekly Outbreaks for all difficultes
Username change?
I'm guessing this is the correct area to put this. I'm a new poster but old lurker. Would it be ok if I have my name changed.
Looking to chip in on the KF2 community.
Username change?
Welcome Screen Image not showing.
Welcome Screen Image not showing.
Random game crashes since Summer Sideshow Event
Windows event viewer doesn't show anything, it's a game crash to desktop with the bugsplat window (2 of them to be precise) coming up.
I have no idea what's causing it. The last 2 times was on Evac Point as Sharpshooter when I headshotted a Scrake. Right now it happened on Volter Manor during Hans, me being Berserker.
Random game crashes since Summer Sideshow Event
Huey M60s appear to not work after a helicopter crash.
After exiting the chopper and taking cover behind it I realized the enemy didn't realize I was still alive, to capitalize on this I decided to get back in the crashed chopper and man the M60 that was facing their position(the right side). I started opening fire, shooting directly at a couple of enemies that were moving slowly and were completely stationary. To my disappointment rounds didn't seem to connect with the targets at all, in fact I'm pretty sure in retrospect I wasn't even firing bullets at all as there were not even visual bullet impacts on the ground near them.
This all ended about 5 seconds later when the sniper(one of the guys I was shooting at) noticed the M60 firing(pointlessly apparently) and shot me.
In other words a potential epic moment in the game was completely ruined by the apparently buggy nature of the M60s on a crashed Huey.
Huey M60s appear to not work after a helicopter crash.
Inscription à :
Articles (Atom)