Registered Users
  • Content count

  • Joined

  • Last visited

Community Reputation

12 Green Tag

About deride

  • Rank
  • Birthday
  1. OK, I messed around on the training server again, with GREAT effort i was able to flame a tiger at about 50M side shot with 2lbr, was nearly down to HE before it popped and it's the exact area I was talking about, only from the side and it was leaning towards me by the end cause it was tracked. Now yes, you can get it to smoke a bit from far out but killing it is a different story. Same thing with the sherman, it's fairly easy to get it to start smoking but it's very far away and hard to follow it up unless you are within 300 or so. You really want a video I can provide one, but suffice to say you have to be really close and shoot it a ton, and it gets tricky cause you can't get through the upper hull like at all so you are relying on the area on the skirt. You are almost better off trying to kill off the crew with spall for a forced despawn explosion imo.
  2. I am an allied player and have tried it countless times, training server or otherwise. It simply doesn't work. DAC is a different story. Feel free to try it though and lemme know how it goes. If there is a weakness I don't know about I would be glad to see it actually.
  3. Kazee, I know you get easily impassioned, but trust me, the 2lbr has to have a nearly perfect shot to kill a tiger and it's a very specific shot and it doesn't always work, esp if the tiger is on any sort of incline whatsoever, and to make matters worse it requires elevation, which is why the DAC is actually somewhat capable of doing the job. The pak36 can flame or explode either sherman from 500+ on the side if you get it dialed in, but anything under 300 or so is super easy. The pak36 doesn't do much against a c7, even with the armor leak. It can get it smoke and fuel cloud pretty good, but the flame is difficult if not outright impossible for in-game conditions. I just farted around on the training server, I was able to get a kill on sherman76 from about 600 or so after using all my rounds basically, and then one shotted it at 350 and that simply cannot be done against a tiger with 2lbr. I know you want proof, here it is:
  4. well, it's probably happened the other way more than you think, you just actually get killed much later. Next time you get wounded just RTB, and probably 25% of the time or so you will be KIA. Hell I have lived so long that a dude got kill credit on me, he switched sides, and I see him in the CP with me as a friendly where he was attacking 15 mins ago, then I get finished off by a 111 and i see his name pop up, CSR said he was a "DE rifleman" but he was a reserve sten for like 4 minutes defending with me before I got killed for good. Edit: what is far more infuriating from my point of view is absolutely LACING someone with a BAR or a Thompson, they start shooting back and I die, then they die right after they kill me.
  5. You never been shot before and RTB only to see you have actually been killed by someone? I have "traded" with people and still have been able to *walk* around, fight and cap, but the whole time someone had a kill credit on me. It does seem to happen more with SMG cause it does take a couple hits most of the time to actually put someone down. Also happened the other way where I shot someone and they are "dead" but they are still able to fight and kill. This is no different than double tracking a tank. The unit is "dead" but is able to get kills.
  6. CE, until the ticket and supply situation is straightened out, we can't attack like we used to.
  7. I've got an elaborate but plausible idea.... how about a special "command truck" that only someone Lt.Col or above can spawn, so typically HC or a vet at the very least. A high-risk high-reward unit. -Two per *GROUND* HQ flag (Beddy, Laff, Opel) could even make it a special version carrying a cap point flag in the bed of the truck and unable to tow or carry troops to make it fair (laff has better towing options than the others). If possible give it a special EWS signal. -Cannot spawn from FB since it's HQ. You also lose a ground flag from the FB due to the way HQ spawning works, i suppose you could have a HQ unit from another div show up though. I am not a map guy, so I dunno how bad you could game this system. -Uses entire HQ spawn list on a depot style trickle. Limited inf, but tons of other gear that finally has a legit chance to see attack action, usually the flag is reserved for last stand defense ive noticed. -Builds a "command" FMS that is twice the size with a cp flag on top, directly behind it like 15 meters are 3 functional truck style ammo cans with no collision that is the veh spawn point. It does not come with walls or any sort of protection and the ammo cans will block any attempt at further fortications or sandbag grief. Also it will have to be on somewhat flat ground due to size. (so no forests with berms, but you could deploy it in say... an enemy Army Base.) -Must have AO on the town to deploy (but not to spawn). You cannot build it out at an FB or some such beforehand and giggle. -Must be within 1k of an enemy controlled building or FB to build, so the REVERSE of current rules and it will for sure set off EWS and you will really have to hustle that thing outta there to get RTB or Res. -Joule value makes it immortal to bombs, but vulnerable to satchel charges, like an FB. Keep the same 4 satchel rule so you always have a shot at beating one even without engy. Idea behind it is to give a hardened FB style option that is limited but could be super evil at the same time. Imagine attacking antwerp/aachen and you can just straight up claim an army base essentially with an armor and bofors etc spawn. I dunno, just a thought. Go ahead and flame me plzkthx.
  8. Presenting the great wall of gridiron.
  9. Right, and not disputing that. I am simply saying that "being organized" is not easy to sustain under demoralizing circumstances. When it comes to the low-pop solution, the only solution is more people on at all times.
  10. Xoom, I will give you that we capped a few towns despite some pretty stiff resistance, and yes it was fun. However, we were overpop, and more importantly 3 hours later our flags were drained, surrounded, and sent back to training. That one town it took so long for us to get control of our spawn area we lost nearly half an inf bde trying to hold it. Didn't help that someone on the axis side was basically John Wick in the CP no matter how many people we had shooting at him. I give you massive credit for 3 successful attacking OPs, the hardest thing to do in the game basically. Yet it handed 2 of our flags to them on a silver platter once the low-pop superheroes hit their stride. Then yesterday more or less the same thing happened, the low-pop cut off led to a successful Antwerp attack which is basically gg. Not blaming you for trying, or blaming you for anything really... just sharing with you to see the big picture here. It's hard to "get organized" day after day when this stuff happens on the regular from what I am hearing. Same old story.
  11. Woogie.
  12. I feel unforeseen problems with a major patch that hasn't truly been tested is a legitimate concern, esp when said patch is supposed to fix things. I guess it's not valid one in your opinion. If they were just adding models or something to the game, thats one thing... this is changing a lot of the bowels of the system, bugs and problems that have existed in the core code for years. Sorry you feel that way. I merely was pointing out a jacked up pre-mature 1.35 that people are waiting for and were told it would be a fix could do vastly more harm than 2 more months of 1.34
  13. OK, lets take your analogy and tweak it..the 1.34 house I am currently in is mechanically sound but has a bad criminal element in the area where it is patently dangerous to go outside. I have a 1.35 house bought and paid for going up *right now* brand new out in the country that doesn't have electricity, water, sewer, or walls... but has no criminal element. It might be cool for me and you to stay in that 1.35 unfinished house, cause we are adults... but think of the newborn baby riflemen wandering around in it. You have a past with the game, as do I and many others... people who have never played the game, people we desperately need... have near zero tolerance for CTD's and stupid crap in 2016. I can hang-on for a couple more months in a place I have lived for years, or I can roll the dice and go to an unfinished house which will be done in 2 months. Then I can go outside all I want without fear of invisible EI. You are assuming 1.35 isn't coming for a long time, It will be here before you know it in the scope of the WW2OL timeline. 1.34 needs to be put out to pasture for sure, but not before that new house is ready for the little baby noob naders.
  14. I am going to go on a bit of a rant, and it's not directed at you Irish, although your post inspired it. Well my thoughts on that are "No." 1.34 for all its flaws that progressively seem to be getting worse somehow... is still very reliable for both the server and client. Hundreds of hours playing this game version and maybe 2 or 3 CTD's caused by it. The server side of things has been relatively rock solid (except for camp 115... le sigh) and the occasional ToE hiccup. Now compare that to 1.35. I had a CTD literally the first thing I clicked, the squad tab, not even in game, not 1 frame rendered. I wanted to make sure AEF wasn't Axis without me, and boom... CTD. As far as the gameplay with 30 or so people being on yeah it seemed better... but there are times 1.34 seems fine too, just not in close quarters battles, and def seems to get worse the more stuff going on. With 1.34 the problems and issues are known. 1.35 is still an unknown without a much larger test, and a live server is a horrible environment to dev on... that's like changing the serpentine belt on a running car. It took them quite a while to get 1.35 beta up in the first place, and that's part of the drill... more unknowns. What if 1.35 has some catastrophic bug or exploit and presents a problem 10x worse than the offset bug and it's something they can't fix in a timely manner. The game is essentially dead in the water at that point unless they roll back the server and all the clients, talk about a pain. Some of the minor patches already have had issues, m1 garand sight getting hosed, blackout beddy bug not being "included," the progressively worse offset and lag crap... it's like the more they try to fix it the madder it gets. I also cannot imagine a major patch like this is gonna be exactly like updating your browser, or even comparable to what this group have already done to 1.34 since the new hardware. 1.35 is supposed to be a stability patch, CRS and the players both are relying on it to come through. The last thing CRS needs is any more black eyes from the court of public opinion, and a fumble 1 yard before the goal-line of the "stability patch" is gonna turn them into "Cornered Racoon Software" their eyes would be so blackened. They have surely worked their ass off on this as I know the ".report DERIDE SHOT ME THROUGH THE WALL" or ".report DERIDE WAS INVISIBLE" 4000 times a month has to be getting old. The amount of time they will save on the the GM side of things not having to deal with the offset wank will be like someone just found money on the street. As bad as it is for us, think about how bad it is for them knowing their own game build hates them and is like actively plotting against them. I can cool off, take a break, walk away. They can't. I bet ol XoomXoom has launched a keyboard or 6 off the roof after he had to calmly explain in a professional manner some BS for the 10,000th time. I am sure I speak not only for myself, but a lot of the unwashed masses when I say this is basically a golden moment to save face and prove this is going in the right direction.
  15. I use shadowplay to death. Zeke is right, you must use the desktop capture thing, which means while it's active you are basically permanently going to have an overlay unless you turn it off. Pros: You can choose to save only those moments you need, like if something strange happens in-game you don't have to have a 5TB scratch drive capturing every second you have to go through. With that same sentiment, editing is easy because its a 10 minute clip or whatever as opposed to 5 hours. Near ZERO performance hit. Cons: Gotta have a recent-like high end nvidia card. the stream thing sorta sucks, I mean it works... but it's not nearly as nice as some others. You are limited to 60fps. Not usually a big deal, but on some games it is annoyingly noticeable. For whatever reason, the microphone capture is slipped into the audio of the game, making it nearly impossible to decouple it from a video... I just never select it, or rarely use PTT when I am using a video to demonstrate something... otherwise i can spoil footage easily. Supposedly there is a work-around for this, but it has never worked for me, also supposedly they are fixing this in the future. I have used all of them, and by far the nicest feature of this is that it always runs and if/when something happens you can just cap it on the spot as opposed to remember to capture it, or just leaving it on forever.