Free Play Account
  • Content count

  • Joined

  • Last visited

Community Reputation

0 Green Tag

About mako26

  • Rank
  • Birthday
  1. I always like going for the AB's during any attack, its usually a low probability of success, but sometimes things go your way and nobody decides to check the bunker....... I joined a small attack taking place at Antwerp AF, early in the assault the probability of striking quickly and capping the ab looked likely. After a few initial infantry skirmishes the ab erupted with allied activity and our small assault force lost its grip on the perimeter. During the fight I held tight to the AB perimeter and somehow didn't get spotted or incidentally mowed down in the fighting despite an ei running within .5m of me while I hid under the AB tents. While the AB was still hot with mostly tanks driving in all directions I decided that before the AI respawned I should make a break for the bunker. I stood up to check which way the many commanders and gun barrels were pointed then made my suicide dash to the bunker, which somehow went unseen. More surprising was the lack of bunker security despite the flurry of equipment activity around the AB. As I peaked out of the murder holes I got to watch most of the Allied arsenal in action, until a lone lmg located me from the infantry spawn and started firing at my little view port. Though he did get a scratch on my lmg commando, I dodged in time to avoid death and held ready until he had to reload.....but that never happened. After 30seconds I'm thinking 'okay what....the...hell...' so I peak out another viewport to see Mr. Rambo is still firing away from the same position, a ctd maybe? As the clock ticked by and the fighting around the perimeter continued I took the above picture. I REALLY wanted to mow those guys down too. Once the cap occurred I did get my chance to mop up Bloke in his AAA gun before the bunker started getting repeatedly hit by armor fire. After that I kept taking peaks out of the view port to locate the armor and update marks until ironfist42 got my commando in the noggin with his stuart mg. Save for the ctd'ing lmg guy I was never challenged in the bunker by infantry, much to my boredom, but the flurry of equipment activity around me did make this a rather humorous capture, and worth writing about
  2. Question for CRS: When looking at video card reviews and the list of games that are generally used as benchmarks, which game should we look at as the closest marker to BGE? Generally speaking, I know it wouldn't be possible to have an absolute direct comparable.
  3. welp process of elimination via $, buy a new video card then. Whats your preferred price range?
  4. I've noticed the frame rate versus actual record hits connection also, not just in this game either because its very apparent when I play BFBC2 too. I'd suggest trying to latest trial version of playclaw. The Cpu cores setting in playclaw selects how many cores you want the program to use during compression, I haven't alternatively toyed with the core affinity in Task Manager. My current Playclaw settings are: Compression/low Frame size/Full Frame Rate/30 Cores/2 Frame size/Half generates low quality videos, but the FPS hit during play is nil. For some reason Frame Rate/60 causes stutters in the recorded video, 30 results in the smoothest video's for me. Side note on the compression settings, high compression uses a special codec m-jpeg, which required some scouring on the net to find.
  5. I'm assuming you've tried various settings in playclaw? Here's their most recent settings tutorial: I had to play around with the Compression/Frame size/Frame rate/Cores settings until I found a satisfactory balance between in game fps hit and video quality. I suggest adjusting the settings until you get the least FPS hit, check the video quality, if it isn't satisfactory then work backwards with the settings from there until you find a good balance.
  6. What resolution? Not sure why Playclaw would be killing it that bad considering your system specs. Either there is a driver issue or there's a hardware bottleneck at the vidcard. I've a budget system: i5 750 intel 2gig ddr3 1333 Biostar T5xe mobo ATI 4860 single 300gig sata drive 1680x1050 with most settings on high I can still run playclaw and hold over 30 fps around contested towns.
  7. Looks like AMD holds the single card performance crown for now. The new dual gpu 6990 has some awesome performance numbers, but the price gasp +$700, and power consumption is huge. Nvidia 590 dual gpu is on its way though. Here's a 6990 review:
  8. after all of this CyborgX nonsense and getting my standard x52 back and running I notice that something just ain't right. Game response to stick input is a little twitchy such as the view hat switch not holding input direction and jittering. Well after my trial by fire experience with device manager earlier in the week, I open up the USB hub directories and see most of the input devices are stacked on the one hub. I plug/unplug usb devices between all the ports till I get the x52 on its own hub with just the rudder pedals and stack the other with the mouse, keyboard, etc. Low and behold my input control in BGE is far better than it ever has been, not only is the hat switch operating smoothly but the main X-Y axis input while flying seemed noticeably smoother. i.e. I found the rather borked 109 fm's in 1.32 to be easier to handle. Since 1.32 109E4 FM love vs. hate has been consistently divided between x52 users and other joystick users, maybe I stumbled on a potential x52 fix?
  9. I'm having some shat luck this week with the comp. Had another issue come up yesterday and initially thought I roasted the cpu. - initiate TOverclocker and turn cpu up to V12 setting, rather minor OC. Load up BFBC2 and comp freezes. *fugggggggggggggggggggggg. - restart comp, windows loads then slows to a crawl, can't start any programs nada. - load safemode, event viewer showing all kinds of errors from the previous boot, all were startup files. - Try to load TOverclocker, no luck, uninstall/install still nada. Google search, find one topic where poster says cpu damaged. *spins in chair* - After couple hours of futzing I decide to start uninstalling sht, starting with Zone Alarm and Avast. Sure nuff comp runs fine. - Okay so I install fresh Avast 6 free version. Comp runs fine. I switch to Online Armor free version firewall. Load it, comps fine, restart. lock up *more spinning in chair* Wtf I can't run a 3rd party firewall now? - Uninstall both then install firewall only. Comp runs smooth. Install Avast and check permissions between both. Restart, Frozen comp. *spinning circles on floor now* - Uninstall both then go to Avast and OA forums, see there are about 10 settings I gotta check off on Avast 6. I then come to the summation Avast auto-updated to version 6 thus causing the initial crash outta nowhere, cuz it has new *features* - Install Avast, restart, install OA and check off all 100 permission points. System runs good now. Don't wanna say how long all that took *bangs head on wall*
  10. While trying various fixes I found through google search one of them brought me to viewing Device Manager with 'show hidden devices' checked. Coincidentally I found MCSTRM in there with a yellow ! next to it so I disabled it, which got rid of the MCSTRM at start up, though it didn't get rid of the BSOD. It generate some consistency with the BSOD report though. Here is what I'm consistently getting from the dmp now: Saik0836.sys is part of the CyborgX driver set. After some testing the CyborgX is only causing BSOD when combo'd with the x52 throttle. For a second time I tried a thorough delete of all the saitek drivers and software then reloading, but that didn't help at all. Sent the dmp report off to Saitek, guess I'll just be using the x52 for now. Thank you for the assistance and suggestions.
  11. Noticed the real player connection also after some searching. I uninstalled it months ago, I don't see it in admin tools/services. Checking through log, looks like this happens at every startup so I don't believe this is my system crash culprit because its been there much longer than the present crash problem. ----------------- heatsink, I replaced it with a basick Rocketfish heatsink/fan combo, fine now at 30c stable. ------------------ So I installed the Windows debugger too. Here's what it keeps spitting out: Microsoft ® Windows Debugger Version 6.12.0002.633 X86 Copyright © Microsoft Corporation. All rights reserved. Loading Dump File [C:\WINDOWS\Minidump\Mini030211-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*c:\symbol* Executable search path is: Windows XP Kernel Version 2600 (Service Pack 3) MP (4 procs) Free x86 compatible Product: WinNt, suite: TerminalServer SingleUserTS Built by: 2600.xpsp_sp3_gdr.101209-1647 Machine Name: Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720 Debug session time: Wed Mar 2 04:11:25.875 2011 (UTC - 8:00) System Uptime: 0 days 2:51:21.842 Loading Kernel Symbols ............................................................... ................................................................ ..................... Loading User Symbols Loading unloaded module list .......... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 19, {20, 89067958, 89068690, ba713d0} Probably caused by : HIDCLASS.SYS ( HIDCLASS!HidpDistributeInterruptReport+ae ) Followup: MachineOwner ---------
  12. Alright unchecked now. Will see what happens While cleaning pc I hit power supply with lot of air and vacuum, but I will pull it apart and check. Going to try reverting to original x52 joystick setup first. Event Viewer? Event Type: Information Event Source: Save Dump Event Category: None Event ID: 1001 Date: 3/2/2011 Time: 4:12:47 AM User: N/A Computer: MATT Description: The computer has rebooted from a bugcheck. The bugcheck was: 0x00000019 (0x00000020, 0x89067958, 0x89068690, 0x0ba713d0). A dump was saved in: C:\WINDOWS\Minidump\Mini030211-01.dmp. followed by: Event Type: Error Event Source: Service Control Manager Event Category: None Event ID: 7000 Date: 3/2/2011 Time: 4:13:34 AM User: N/A Computer: MATT Description: The MCSTRM service failed to start due to the following error: The system cannot find the file specified.
  13. grr. Thought I had this kicked last night, but it came back again. So shortly after making my second post I loaded up Aces High, soon as I spawned in a plane *poof* comp reset. Now this is odd because I'd fly a 2hr scenario on Saturday shortly after installing the Cyborgx without a hitch. next steps: - I load up speed fan and start checking temps. cpu is spiking up to 70-80c - Open up computer and dust it out, all fans and power supply. - Notice the cpu fan is loose, one of the mount posts has backed off of the mobo and wont secure - Junk oem fan, install new fan. cpu running cool at 30c - Load BGE, fly around - instant reboot. try aces high same thing - Search on net for info regarding error files. find potential solution - Try AH, fly for hour without problem, try BGE no problem ------------- - Today I load BGE and play for quite awhile. lots of ground, several bomber sorties, then I fly a 109E4 and after 40min comp locks up, no restart. - manual reboot, get back in game and play ground for 1hr. get in a tank, drive tank around for 10min *poof* comp restarts. ARGGGGGGGGGGGGGGGGGGGGGGGGGG
  14. ruled out the temperature thing, cpu and vcard are good. Could it be the joystick combo is using more juice thus pushing the limits of the power supply? Comps working fine in every other game though
  15. During flight I'm getting a full system lockup or full auto reboot when I get near active towns. This started occurring after I swapped my x52 joystick for a Cyborgx while retaining the x52 throttle. If the computer completely reboots I get a 'system has recovered from a serious error' pop up once windows reloads. Error Report Contents: C:\DOCUME~1\cocacola\LOCALS~1\Temp\WERf453.dir00\Mini022811-01.dmp C:\DOCUME~1\cocacola\LOCALS~1\Temp\WERf453.dir00\sysdata.xml