Jump to content

Fps Drops?


25 replies to this topic

#1 DeusL0Vult

    Member

  • Pip
  • Survivor
  • Survivor
  • 12 posts

Posted 12 October 2013 - 07:35 PM

My build is not the best, but it's not the worst. I should be able to at least run this game on medium at solid FPS, but for some reason that does not happen. I have tried the new Nvidia beta drivers that supposedly increase FPS in Mechwarrior, and that did nothing. I do not know what the problem is.

DirectX is as follows:

------------------
System Information
------------------
Operating System: Windows 7 Home Premium 64-bit (6.1, Build 7601) Service Pack 1 (7601.win7sp1_rtm.101119-1850)
Language: English (Regional Setting: English)
System Manufacturer: Gigabyte Technology Co., Ltd.
System Model: GA-78LMT-S2
BIOS: Award Modular BIOS v6.00PG
Processor: AMD FX™-4100 Quad-Core Processor (4 CPUs), ~3.6GHz
Memory: 8192MB RAM
Available OS Memory: 8174MB RAM
Page File: 3933MB used, 9866MB available
Windows Dir: C:\Windows
DirectX Version: DirectX 11
DX Setup Parameters: Not found
User DPI Setting: 120 DPI (125 percent)
System DPI Setting: 96 DPI (100 percent)
DWM DPI Scaling: Disabled
DxDiag Version: 6.01.7601.17514 32bit 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 GTX 660
Manufacturer: NVIDIA
Chip type: GeForce GTX 660
DAC type: Integrated RAMDAC
Device Key: Enum\PCI\VEN_10DE&DEV_11C0&SUBSYS_26603842&REV_A1
Display Memory: 4038 MB
Dedicated Memory: 1990 MB
Shared Memory: 2048 MB
Current Mode: 1600 x 900 (32 bit) (60Hz)
Monitor Name: Generic PnP Monitor
Monitor Model: Acer S200HL
Monitor Id: ACR02D5
Native Mode: 1600 x 900(p) (60.000Hz)
Output Type: HD15
Driver Name: nvd3dumx.dll,nvwgf2umx.dll,nvwgf2umx.dll,nvd3dum,nvwgf2um,nvwgf2um
Driver File Version: 9.18.0013.3140 (English)
Driver Version: 9.18.13.3140
DDI Version: 11
Driver Model: WDDM 1.1
Driver Attributes: Final Retail
Driver Date/Size: 9/27/2013 02:57:55, 18229224 bytes
WHQL Logo'd: n/a
WHQL Date Stamp: n/a
Device Identifier: {D7B71E3E-5280-11CF-B657-6D061CC2C435}
Vendor ID: 0x10DE
Device ID: 0x11C0
SubSys ID: 0x26603842
Revision ID: 0x00A1
Driver Strong Name: oem64.inf:NVIDIA_SetA_Devices.NTamd64.6.1:Section089:9.18.13.3140:pci\ven_10de&dev_11c0
Rank Of Driver: 00E02001
Video Accel: ModeMPEG2_A ModeMPEG2_C ModeVC1_C ModeWMV9_C
Deinterlace Caps: {6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
{F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch
{6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(UYVY,UYVY) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
{F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(UYVY,UYVY) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(UYVY,UYVY) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(UYVY,UYVY) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch
{6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(YV12,0x32315659) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
{F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(YV12,0x32315659) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(YV12,0x32315659) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(YV12,0x32315659) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch
{6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
{F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch
{6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(IMC1,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(IMC1,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC1,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(IMC1,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(IMC2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(IMC2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(IMC2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(IMC3,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(IMC3,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC3,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(IMC3,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(IMC4,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(IMC4,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC4,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(IMC4,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(S340,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(S340,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(S340,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(S340,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(S342,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(S342,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(S342,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(S342,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
D3D9 Overlay: Supported
DXVA-HD: Supported
DDraw Status: Enabled
D3D Status: Enabled
AGP Status: Enabled

Edited by GlaDOSisaPotato, 12 October 2013 - 07:38 PM.


#2 Thunder Lips Express

    Member

  • PipPipPipPipPipPipPip
  • Liquid Metal
  • Liquid Metal
  • 905 posts
  • LocationFrom parts unknown

Posted 12 October 2013 - 07:48 PM

yeah me too! i can run for weeks on ultra high, but then say one night i have to run on low. i'm assuming its something on my end though

#3 StainlessSR

    Member

  • PipPipPipPipPipPip
  • Philanthropist
  • Philanthropist
  • 443 posts
  • LocationSunShine State

Posted 13 October 2013 - 12:22 PM

Operating System: Windows 7 Home Premium 64-bit (6.1, Build 7601) Service Pack 1 (7601.win7sp1_rtm.101119-1850)
Language: English (Regional Setting: English)
System Manufacturer: Gigabyte Technology Co., Ltd.
System Model: GA-78LMT-S2
BIOS: Award Modular BIOS v6.00PG
Processor: AMD FX™-4100 Quad-Core Processor (4 CPUs), ~3.6GHz
Memory: 8192MB RAM
Available OS Memory: 8174MB RAM
Page File: 3933MB used, 9866MB available
---------------
Display Devices
---------------
Card name: NVIDIA GeForce GTX 660
Display Memory: 4038 MB
Dedicated Memory: 1990 MB
Shared Memory: 2048 MB
Current Mode: 1600 x 900 (32 bit) (60Hz)
Monitor Model: Acer S200HL
Native Mode: 1600 x 900(p) (60.000Hz)
Driver Date/Size: 9/27/2013 02:57:55, 18229224 bytes

Video card is good
memory is good
OS is great
CPU is iffy.

Most articals you will find of AMD processors on the low end will all show that to get better performance you will need to overclock. With the gpu you have you would get better performance by overclocking. Even Intel chips which are running under 4GHtz benefit from overclocking if available. If your game performance starts good but then tanks run a program which would monitor max cpu temps and see if it is spiking and causing the cpu to throttle down. (there is a thread that has a link to a few good programs for this). Also, read some of the other threads about amd in support workarounds.

#4 Durant Carlyle

    Member

  • PipPipPipPipPipPipPipPipPip
  • Survivor
  • Survivor
  • 3,877 posts
  • LocationClose enough to poke you with a stick.

Posted 13 October 2013 - 01:28 PM

AMD CPUs are somewhat weak for gaming in general, and this game depends far more on the CPU than the GPU. Plus, the game isn't optimized at all. So that adds up to poor performance compared to other games on the same hardware.

#5 New Day

    Member

  • PipPipPipPipPipPipPipPip
  • Veteran Founder
  • Veteran Founder
  • 1,394 posts
  • LocationEye of Terror

Posted 13 October 2013 - 02:23 PM

View PostDurant Carlyle, on 13 October 2013 - 01:28 PM, said:

AMD CPUs are somewhat weak for gaming in general, and this game depends far more on the CPU than the GPU. Plus, the game isn't optimized at all. So that adds up to poor performance compared to other games on the same hardware.

This game has serious problems. I get the SAME (~5) FPS at low and ultra high.

#6 DeusL0Vult

    Member

  • Pip
  • Survivor
  • Survivor
  • 12 posts

Posted 14 October 2013 - 04:58 PM

View PostNamesAreStupid, on 13 October 2013 - 02:23 PM, said:

This game has serious problems. I get the SAME (~5) FPS at low and ultra high.

Same,

And my FPS gets better the long the game goes on, as the the more mechs die. I think it's a problem with my shaders, as they glitch out when I get close.

#7 New Day

    Member

  • PipPipPipPipPipPipPipPip
  • Veteran Founder
  • Veteran Founder
  • 1,394 posts
  • LocationEye of Terror

Posted 15 October 2013 - 12:21 AM

View PostGlaDOSisaPotato, on 14 October 2013 - 04:58 PM, said:

Same,

And my FPS gets better the long the game goes on, as the the more mechs die. I think it's a problem with my shaders, as they glitch out when I get close.

Maybe. I get 50FPS in testing grounds.

#8 Sen

    Member

  • PipPipPipPipPipPipPip
  • 757 posts
  • LocationTexas

Posted 15 October 2013 - 06:58 AM

Quote

This game has serious problems. I get the SAME (~5) FPS at low and ultra high.


Which suggests that you are being limited by your CPU.

Which suggests the game (while resource heavy and unoptimized) is NOT the problem.

Edited by Sen, 15 October 2013 - 06:59 AM.


#9 Oderint dum Metuant

    Member

  • PipPipPipPipPipPipPipPipPip
  • Ace Of Spades
  • Ace Of Spades
  • 4,758 posts
  • LocationUnited Kingdom

Posted 15 October 2013 - 08:52 AM

View PostSen, on 15 October 2013 - 06:58 AM, said:


Which suggests that you are being limited by your CPU.

Which suggests the game (while resource heavy and unoptimized) is NOT the problem.



True and not true.

CPU is the biggest limiting factor, and the 4100 is {Scrap} which is correct.

The games current state of poor optimization is a problem and one that needs to be rectified if you have new generation quad cores that have issues...that's a problem when those same quad cores perform ok in other games based on the same engine.

#10 Sen

    Member

  • PipPipPipPipPipPipPip
  • 757 posts
  • LocationTexas

Posted 15 October 2013 - 10:53 AM

Quote

The games current state of poor optimization is a problem and one that needs to be rectified if you have new generation quad cores that have issues...that's a problem when those same quad cores perform ok in other games based on the same engine.


This assumes that any given user's computer is running optimally, free of viruses, malware, horrible paid antivirus programs, latest drivers installed, computer is free of massive TSRs sucking up memory and CPU cycles, whether you have an INTEL quad core or AMD quad core. . . I could do this for an hour.

Not to say that MwO isn't a horribly unoptimized mess: it is. But there are so many other individual variables to look at when considering performance issues. Of course it could never be anything the USER did :)

Edited by Sen, 15 October 2013 - 10:54 AM.


#11 MavRCK

    Member

  • PipPipPipPipPipPipPipPip
  • Bad Company
  • Bad Company
  • 1,375 posts
  • Google+: Link
  • LocationMontreal - Vancouver

Posted 16 October 2013 - 12:28 AM

Amd processors don't appear to be well-optimized for Cryengine 3. Lethalrose talks about this in my latest tier list video.

#12 Oderint dum Metuant

    Member

  • PipPipPipPipPipPipPipPipPip
  • Ace Of Spades
  • Ace Of Spades
  • 4,758 posts
  • LocationUnited Kingdom

Posted 16 October 2013 - 08:58 AM

View PostSen, on 15 October 2013 - 10:53 AM, said:


This assumes that any given user's computer is running optimally, free of viruses, malware, horrible paid antivirus programs, latest drivers installed, computer is free of massive TSRs sucking up memory and CPU cycles, whether you have an INTEL quad core or AMD quad core. . . I could do this for an hour.

Not to say that MwO isn't a horribly unoptimized mess: it is. But there are so many other individual variables to look at when considering performance issues. Of course it could never be anything the USER did :)


And your assuming PGI codes correctly, efficiently and has sufficient Q&A process in place to address such issues, and/or has the technical ability and knowledge of the engine.

As someone who does have knowledge of computers as you do, i can tell you that this game runs poorly on systems that should have no problem and i can guarantee are free of serious user generated issues because i've serviced them :huh:

#13 Sen

    Member

  • PipPipPipPipPipPipPip
  • 757 posts
  • LocationTexas

Posted 16 October 2013 - 01:09 PM

Quote

And your assuming PGI codes correctly, efficiently and has sufficient Q&A process in place to address such issues, and/or has the technical ability and knowledge of the engine.


Did not: and you even quoted me on it:


Quote

Posted Today, 11:58 AM
Posted ImageSen, on 15 October 2013 - 01:53 PM, said:



This assumes that any given user's computer is running optimally, free of viruses, malware, horrible paid antivirus programs, latest drivers installed, computer is free of massive TSRs sucking up memory and CPU cycles, whether you have an INTEL quad core or AMD quad core. . . I could do this for an hour.

Not to say that MwO isn't a horribly unoptimized mess: it is. But there are so many other individual variables to look at when considering performance issues. Of course it could never be anything the USER did :D





I'm not arguing that the game isn't completely unoptimized. I'm not saying that it couldn't run MUCH BETTER on computers with lower end hardware. What I *AM* saying is: before you start sharpening your pitchforks and lighting your torches to burn the devs in effigy, look to your own O/S optimizations first. A lot of what I deal with on a daily basis are computer ignorant people confused as heck as to why their computer is running slow, and then angry when they find out that any kind of knowledge or routine maintenance/upkeep is involved. General neglect/ignorance is the number 1 cause of poor performance [in general computing circles]

I won't even get into regular driver updates.

Yes, the game is a mess. No, there is no reason for it to run as badly as it does. There are, however, many OTHER things that can factor into the issue. A lot of performance issues can be resolved by maintenance/tweaking windows. MOST of the rest can be solved by overclocking.

Or buying intel i5/i7

and a high end air/water cooler

and then overclocking

. . . and possibly dry ice :ph34r:

Edited by Sen, 16 October 2013 - 01:11 PM.


#14 VikingN1nja

    Member

  • PipPipPipPipPipPipPip
  • Bad Company
  • Bad Company
  • 607 posts
  • LocationIreland

Posted 27 October 2013 - 04:09 AM

What is it in game that makes fps go from 60 to sub 30?

#15 Sen

    Member

  • PipPipPipPipPipPipPip
  • 757 posts
  • LocationTexas

Posted 27 October 2013 - 05:45 AM

Quote

What is it in game that makes fps go from 60 to sub 30?


The amount of data the CPU/GPU has to process/render.

Is there any way of tracking/recording CPU usage while in game? Something like % of CPU used. . .if you can get your hands on that data, it'd show if any given CPU was maxed at 100%

Edited by Sen, 27 October 2013 - 05:45 AM.


#16 JustJoshing

    Rookie

  • 1 posts

Posted 27 October 2013 - 05:26 PM

Crossfire isn't even supported? Wow... No wonder im getting 30-40 fps. I'd lower the settings, but that doesn't even really change my performance at all.

#17 The Argie

    Rookie

  • Bad Company
  • 5 posts

Posted 05 April 2014 - 01:10 AM

I really tired to try thing but my FPS never gets better, I tryied all, settings Low, etc. Change drivers, change Video Card, reset modem and nothing since the last 2 patches in the Hangar I have 26 FPS (usually I have there 50) and in the game 18FPS my nvidia GT240 its bad but can handle a good game in 40FPS, now, its almost impossible.
I think they scrub the game in some way but just for some configs. the strange thing is I didnt find any good tutorial or well explained to modify things like *.cfg files, just a few words of some dev.
I guess the uninstall its the last resort...
I played this game for long time but in the last 7 patches game experience is going down...
Cheers from the south...

#18 PeeWrinkle

    Member

  • PipPipPipPipPipPip
  • Ace Of Spades
  • Ace Of Spades
  • 384 posts

Posted 13 June 2014 - 04:23 PM

If I would not have just purchases a clan package a few weeks ago I would quit the game because of this issue. I have an i5, 12GB memory, and a GTX 760 (2GB, 256Bit), win 8 64x. I play every other game on ultra high graphics and most are very graphic intensive. I play this game on low and medium and I get FPS in the teens. I would say it was my internet speeds, but I consistently test out over 25mbps.

Based on that I cannot believe it would be on my end, but you never know. I started a support ticket and haven't really gotten anywhere, but I can say I will not drop more money to upgrade my system considering other high end games play fine.

Let me be honest. I am above 60 until I start to move and fire, then I am in the teens. Sometimes the 20's. If I thought PGI would give me my money back for the Clan package I bought I would ask for it and stop playing the game.

#19 Goose

    Member

  • PipPipPipPipPipPipPipPipPip
  • Civil Servant
  • Civil Servant
  • 3,463 posts
  • Twitch: Link
  • LocationThat flattop, up the well, overhead

Posted 13 June 2014 - 05:36 PM

… Necro much?

There are other threads, Ace.

#20 PeeWrinkle

    Member

  • PipPipPipPipPipPip
  • Ace Of Spades
  • Ace Of Spades
  • 384 posts

Posted 14 June 2014 - 03:57 AM

Not much, actually I would say very rarely. So it just goes to show my current level of frustration. Mostly because I keep dumping money into suggested upgrades made by support that don't make much difference at all. That said, this seems like the appropriate thread to post in because it is about FPS dropping in game. Which is my exact problem.

Hopefully my experience will help others, or maybe there's can help me with something to try.

Don't miss understand me either. I support PGI, that is why I spent more than I should have on packages they offer. Although that could also be because the BattleTech universe is one of my favorites and I have been playing table top since the late 80's. So I want to support them. I'd just be much happier doing so if I could prevent that dreaded drop in FPS. There is nothing like having your target lined up and when you fire the target has blinked away.





1 user(s) are reading this topic

0 members, 1 guests, 0 anonymous users