Free Play Account
  • Content count

  • Joined

  • Last visited

Posts posted by jon8798

  1. The problem with a PvP game like this is the possibility of overwhelming numbers advantage for one side or the other. It all depends on what the players want to do today. There's no hard and fast rule, occasionally a campaign will see one side almost always overpopulated, other times it will be more even. Regardless, the losing side tends to have fewer players right at the end of a campaign as a percentage of players will swap sides to enjoy "winning" or some give the game a rest for a week or so because they don't want to be there when defeat is confirmed.

    When imbalance is really bad, spawn delays kick in to try and even it up a bit, although they also upset a lot of people. I understand CRS are working on an update that will make it more rewarding and fun to play on the underpopulated side. Expect a long wait for that though.

    I used to get really wound up by it, now it doesn't bother me. I like being slightly under populated because then it gives me a chance to set up cunning defensive positions and inflict death on over confident attackers trying to zerg. If it's really bad, don't go to the big attack where it's a super camp. Go somewhere quieter or drive from a distant town and surprise the lazy attackers with death from behind whilst they're fixated on camping.

  2. The combat training mission basically gives an area for people to spawn in and try out the game. It relies on there being more than one person trying it at a time. If you're the only one doing the combat training mission then you'll be the only one there. If you want to practice against other players, you need to get others to spawn in on the combat training mission.

    To be honest, it's not very well explained in the game and it's not that useful. Most people don't bother with it and go straight into the campaign game so it's always empty.

  3. Thank you very much for the pointers fellas. I had indeed just been using the windows driver updater to keep my system up to date. I had naively assumed that Windows was looking after me and sorting everything out.

    I'll get all the newest drivers from the manufacturers this weekend and should hopefully be able to get a couple of hours play worked in too (around my wife's demands that I sort out the garden).

    If I get another crash the same as before then I'll post here again with the new DxDiag text file.

    Thanks again,


  4. Hi,

    I'm wondering if anyone is having or has had any issues with older architecture NVIDIA cards.

    My laptop had a 8600M card and used to crash regularly. The screen would freeze mid-game at random times and a loud buzzing noise came from the speakers. The only solution was to turn off the power. NVIDIA customer support said that the card was faulty, but refused to replace it as the warranty had expired.

    I've just got a new desktop machine which (sadly) came with another NVIDIA card, the GT320. I've only had it a week but I've had the exact same crash twice now. I understand that the GT320 is based on the old 9-series cards and so is not that new in terms of its architecture. I have heard that NVIDIA used a fairly substandard manufacturing process on these older cards that caused a higher than expected failure rate and wonder if that might also apply to the 'new' GT320, 330 and 340 cards.

    The only other thing I can think of that might be relevant is that DXDiag claims DirectX 11 is running, despite the fact that I'm pretty sure there aren't any NVIDIA cards supporting DirectX 11 yet.

    Anyway, the first bit of the DXDiag file is below, should I post the rest of it? It's pages long and mostly looks like gibberish to me...

    This problem isn't going to end my life, it's not that regular at the moment and I'm not playing a huge amount right now. But my biggest worry is that this is exactly how it began on my laptop and after 8 months it was completely unusable.

    If anyone's got any bright ideas or can see that I'm missing something obvious, I'd be very grateful for your help.




    System Information


    Time of this report: 7/22/2010, 10:00:52

    Machine name: JON-PC

    Operating System: Windows 7 Home Premium 64-bit (6.1, Build 7600) (7600.win7_gdr.100226-1909)

    Language: English (Regional Setting: English)

    System Manufacturer: Packard Bell

    System Model: ixtreme M3730

    BIOS: Default System BIOS

    Processor: Intel® Core2 Quad CPU Q8300 @ 2.50GHz (4 CPUs), ~2.5GHz

    Memory: 4096MB RAM

    Available OS Memory: 4096MB RAM

    Page File: 1393MB used, 6795MB available

    Windows Dir: C:\Windows

    DirectX Version: DirectX 11

    DX Setup Parameters: Not found

    User DPI Setting: Using System DPI

    System DPI Setting: 96 DPI (100 percent)

    DWM DPI Scaling: Disabled

    DxDiag Version: 6.01.7600.16385 64bit Unicode


    DxDiag Notes


    Display Tab 1: No problems found.

    Sound Tab 1: No problems found.

    Sound Tab 2: No problems found.

    Input Tab: No problems found.


    DirectX Debug Levels


    Direct3D: 0/4 (retail)

    DirectDraw: 0/4 (retail)

    DirectInput: 0/5 (retail)

    DirectMusic: 0/5 (retail)

    DirectPlay: 0/9 (retail)

    DirectSound: 0/5 (retail)

    DirectShow: 0/6 (retail)


    Display Devices


    Card name: NVIDIA GeForce GT 320

    Manufacturer: NVIDIA

    Chip type: GeForce GT 320

    DAC type: Integrated RAMDAC

    Device Key: Enum\PCI\VEN_10DE&DEV_0CA2&SUBSYS_2150174B&REV_A2

    Display Memory: 2778 MB

    Dedicated Memory: 986 MB

    Shared Memory: 1791 MB

    Current Mode: 1360 x 768 (32 bit) (60Hz)

    Monitor Name: Generic PnP Monitor

    Monitor Model: TOSHIBA-TV

    Monitor Id: TSB0105

    Native Mode: 1360 x 768(p) (60.015Hz)

    Output Type: HD15

    Driver Name: nvd3dumx.dll,nvwgf2umx.dll,nvwgf2umx.dll,nvd3dum,nvwgf2um,nvwgf2um

    Driver File Version: 8.17.0011.9745 (English)

    Driver Version:

    DDI Version: 10.1

    Driver Model: WDDM 1.1

    Driver Attributes: Final Retail

    Driver Date/Size: 4/3/2010 22:55:32, 11906664 bytes

    WHQL Logo'd: Yes

    WHQL Date Stamp:

    Device Identifier: {D7B71E3E-4FE2-11CF-EA52-5B011CC2C535}

    Vendor ID: 0x10DE

    Device ID: 0x0CA2

    SubSys ID: 0x2150174B

    Revision ID: 0x00A2

    Driver Strong Name: oem29.inf:NVIDIA_SetA_Devices.NTamd64.6.1:Section011:\ven_10de&dev_0ca2&subsys_2150174b

    Rank Of Driver: 00E60001

    Video Accel: ModeMPEG2_A ModeMPEG2_C ModeVC1_C ModeWMV9_C