piercer

Registered Users
  • Content count

    546
  • Joined

  • Last visited

Everything posted by piercer

  1. I agree with this 100%, the problem isn't the Rifleman unit. Like Xanthus, I play it nearly 99% of the time. It IS the most versatile unit in the game, and if you master it, it offers the most rewarding sense of accomplishment. Are there refinements to the rifle I'd like to see? Sure, but it's also a zero-sum game. I think the main issues on rifle are more concealment related, and that most people think it's a close-combat unit, when it takes a ton of skill to use it effectively that way. My take is that we are over-focused on the Rifleman being the F2P unit, when in my opinion it should be the SMG or some other close-range combat unit. I mean don't we want more players? Don't we want there first experiences to be FUN?!?! and then they graduate to wanting to play more units, more versatility, etc...? Becoming more strategic in their play style? Graduate to a longer term sustainable user base. I remember when I first played originally in 2002/2003 and I used a rifle, if it wasn't for the 91st helping me out I probably would have quit the game out of frustration. There's so many other game experience and usage dynamics that work against a new player. Geeze even after all these years I bang my head every time I try to setup a mission.
  2. I've always been a bit torn on the white skull piece. It provides real-world data that overcomes the comms issue, as well as general SA challenges posed by a computer screen and not always positionally accurate audio. In the real world, given your hearing is intact you'd have a better sense of gun fire direction and distance, not so much in game. I like the idea of clipping it off after a certain rank, another idea is shorten their existence life span as a function of rank. P-
  3. As a real world (more relatable) example, if anyone plays hockey you know it's an anaerobic sport, similar to sprinting. I haven't played anything else that's similar in that regard. Of 2m on ice, you probably are full-out about < 40s and that's not with heavy gear, but the ATP build-up is fast, which is why teams cycle short-shifts -- even standing still is hard once it kicks in, which is why you see a lot of players bend-over when they're gassed (runners as well). You need up to 2m of bench time to rest, or slow-walk. If I was going to change regen it would be to implement a staged model, a stage that gives like 2-3s of sprint that recharges quickly after lying down, and a secondary stage that regens at a slowed pace over a longer set of time. Right now, it's linear, which feels unrealistic. You can sprint again after a few seconds of catching your breath, just for a very short distance. The way it is now you have to wait before regen even starts, it's like regen feels inverse to reality. slow- > quick vs. quick -> slow P-
  4. Wow... Not to pop this to top of queue, but this was posted after I had left the game. I'm honored to have such a great story written about an engagement. I had a lot of RL changes in the last few years that pulled me away, though honestly this is one game that I can seem to completely shed, and I always wonder how the community is doing. I just recently picked up my k98 for the first time in probably 3+ years. Game mechanics feel a bit alien to me right now, but have had a few good sorties - ran into Stankyus the other day. Maybe it's time for my return Thanks again for the call out pfmosquito!! !S Piercer
  5. I get them but it's been pretty sporadic lately. Seems more like once a month, rather than the weekly it was for awhile. I'd rather them be monthly, keep the rats focused on the game, fixing bugs, etc... I've done newsletters in the past for companies, can be a time sink even though they provide a lot of value.. have to find the balance. P-
  6. But, supporting business is what keeps people employed, fed, etc... money that goes to CRS goes to salaries, pays the bills that result in other people keeping their jobs and supports other companies that are in partnership with them. I'm waiting for the diamond encrusted special deluxe box edition....
  7. If the objects aren't rendered how do you detect surface collisions? If they're not 'visibly' rendered there is still a need to know where all surfaces are to detect the collision. If I shoot over a hill the client still needs to know where impact is registered - That's what I thought KFS1's diagram was indicating. P-
  8. IIRC Best way to think about a normal map is think of a small square mirror lying on a table. When light hits it from a certain angle the light then bounces off the mirror at an angle complimentary to the incoming angle. The normal for this surface would be a straight line extending from the center of the mirror and perpendicular to the surface (line would basically be straight through the middle of the mirror surface) For computer graphics though everything is drawn in triangles or polygons. And so that you don't see every single polygon and triangle independently slight adjustments to this line (normal) can be made so that incoming and outgoing light reflects just a little bit differently than normal. The result of these minor modifications is a smoothing effect that blends the triangles or polygons together more naturally - its why a sphere looks like a sphere and not a bunch of polygons or triangles stiched together. As well, you can also use adjustments to normals to exaggerate the surfaces of a texture to give it more realistic depth. A normal map is what is applied to the surface so the graphics card can calculate these surfaces to appear more seamless and freeflowing - similar to a texture map in some ways. I'd only expect performance impact on older cards, YMMV.
  9. Hmmmm... Didn't think of that, I should try it out - haven't even thought of using FRAPS since I got the SSDs. I'm also waiting for Intel to come out with RAID drivers that support TRIM... patience.... patience.... like waiting for 1.31 P-
  10. Just timed it, 28 secs to load Persona Screen. P-
  11. I have it on 2x 160GB Intel X-25 SSDs in RAID 0. It loads fast that's for sure But I haven't noticed any improvement in FPS or anything like that, nor did I expect it to. P-
  12. 10th on the High End
  13. Look in the "Live Game Bug Reporting" part of the forums. P-
  14. Best squad EVER!
  15. Yea, make sure you have SLI off. I was just in Dinant and was getting around 40 FPS it seemed. P-
  16. So far using the new beta 257.15 drivers and the settings I've found work best for me, I tested them using the .benchremagen test in offline mode: Ambient Occlusion: OFF Ansiotropic: 8x (Seems to have minimal if any frame impact) Antialiasing - Gamma: Off Antialiasing - Mode: Override Antialiasing - Setting: 2x * seems to have the least impact, each step up drops about 10-15 fps Antialiasing - Transparency: Off CUDA: None Extension Limit: Off Max pre-rendered frames: 3 Multi display: Single Power Management: Max performance Texture Filtering - Negative LOD: Clamp Texture Filtering - Quality: Quality Threaded Optimization: OFF * I've noticed this in previous versions and it seems to still impact fps though now its very nominal maybe like 5 fps max. When it's set to Auto you'll loose fps slightly. Triple Buffering: Off Vertical Sync: Application Controlled (I have it off in app also) For my system using .benchremagen I can sustain between 72-78 fps with these settings. Antialiasing seems to have the largest impact with 8xQ dropping me down to 47-50 fps. YMMV - Hope this helps. Oh, I turned post-rendering off in-game I just don't like the haziness it creates. P-
  17. I haven't tried it with the sniper rifle but I have been noticing some skipping with the standard rifle and I'm not sure if I need to tweak my mouse settings or what. But it's usually happening when I aim at objects in the distance slight movement jumps a few pixels rather than being smooth. I have a logitech g500 mouse with very high resolution so there shouldn't be any issues like I'm experiencing. P-
  18. I advise you read the proper method to overclock on your board - just google it, there are plenty of forums dedicated to overclocking. As indo mentioned you really need to pay attention to temperatures. That said, here is the typical methodology: 1) Download LinX for stress testing your CPU 2) Google around and find out the max core temp of your CPU 3) Backup your system 4) First, remove the memory from the overclock equation. That is increase the ratio so that the memory speed is much lower than spec, it usually doesn't matter how low you set it as long as the speed is under-spec you'll be fine. 5) Increase the FSB speed so that it increases the CPU clock up 50Mhz (usually when you first start overclocking from the CPU base you have about 100Mhz/200Mhz or more of headroom before you have to do anything else). 6) Run LinX, click on 'All' next to the 'Memory to use:' section on the main window. Run it for 5 iterations. Make sure you note how HOT your CPU is running (download speedfan or similar temp monitoring software RealTemp is another). 7) If it runs for 5 iterations with no errors and your computer doesn't lock up or crash, and your well within operating temperature range go back to step #4 and do it again. 8) At some point your system is going to lock, or Linx will give you an error. If you're still within reasonable operating temps you can throw a tiny .25v increment to the CPU voltage and try again. Granted though I consider this more serious overclocking territory. Otherwise, back-off about 100Mhz and then run Linx for 30 iterations. If it passes all 30 iterations then you're PROBABLY pretty stable. I say probably because there's a lot of variables, ambient temp being one of them. 9) Go back and change the ratio to put the memory back into spec range. YMMV - These are the steps I've taken in the past on these types of system. And your doing this at your own risk, these are just guidelines that have worked in the past. P-
  19. Maybe it's a YMMV and system dependent - I didn't notice any difference on my system. P-
  20. I've heard, though I haven't tried it some folks have experienced better performance with hyperthreading off on the i7 - Though I leave it on because I'm running Windows 7/64. P-
  21. Actually made a huge difference for me. Not sure I follow your logic above, the game actually runs on a single core. If you have single core, dual core, or quad doesn't make a difference but how fast a single core clocks does. This game has always been very CPU intensive in my experience no matter how much RAM or GPU power I've thrown at it, the single biggest difference I've experienced was from overclocking.... My system: RAM : 6GB (Game relies on single thread w/ max 2GB of memory) CPU : i7 920 overclocked to 4.0Ghz HDD : 2 160GB Intel X-25 SSDs in RAID0 GPU : Nvidia 280GTX Of the above the CPU overclock made the single biggest difference in FPS game performance. The SSDs only on load time. On your comment regarding CTDs -- If you're CTD'ing because of an overclock it's because you have an unstable overclock. I rarely if ever have CTDs in the game - I've been running at 4.0Ghz stable for over a year. P-
  22. Game Settings: * Logitech G35 * Hardware * 128 Sounds Yes, full surround sound for me - I've tried a lot of different headsets, these by-far have been the best for this game. P-