Jump to content

Really Bad Performance On New System. Heat Blur Choppy!!!


Recommended Posts

Hi Everyone,

 

I upgraded both my cpu and graphics card and FC2 runs a lot worse than before.

 

I went from my dual core 2.4 / 8800 GTX to a quad core 2.66 (q9400) / 465 GTX to be expecting a little performance boost.

 

I'm running a nice clean copy of windows 7 64bit with the latest nvidia drivers and updated directx. I notice something was wrong right from the moment I was sitting on the runway in F15 missile practice mission. The heat blur was really choppy, I remember it being nice and smooth before. one of my favorite effects that I cant live without. Then I noticed really bad frame rate in the cockpit, looking at the airport where most of the planes are really chopped it up. like 12 fps. when i look behind it gets a bit better and sure when i'm up in the air its much better but still shutters big time when i switch to other planes or look at external fly by.

 

Can someone help me, what am I doing wrong? Is there a bug with nvidia's latest drivers ? using 258.96. Again what I noticed right away was the heat blur looking like crap, I hope it's not because i have a new directx 11 card. other games run fine and better than before.

 

Thanks in advance.

 

quad core q9400 2.66

nvidia 465 GTX

8 gigs of ram ddr2

xfx 750i sli motherboard


Edited by capsilus
Link to comment
Share on other sites

Hi, welcome to the forum.

 

Could you please havea a quick read-through this thread? It contains a lot of tips on how to easily get enough information to help us out in assisting you, and also several tips on how to maintain and verify system health: TROUBLESHOOTING - Help us helping you (FC2 edition)

 

Also, in the beginning of that thread there are directions on how to supply a DxDiag. Could you please do so? This should help verify what the driver situation is like without you having to go through each and every one.

 

My own suspicion is either a driver issue, or a heat issue. Have you verified that the temperature of your CPU and MCP (the XFX driver suite CD should have some nVidia software that allows you to monitor this - at least mine did) isn't spiking? The MCP should be fine, but on the CPU it is very easy to make a small mistake with the standard fans that results in ineficcient cooling. The heat situation then causes the processor tho throttle itself as it gets hot (it reduces it's clock frequency and/or "skips" clock cycles), which would make the whole system suddenly start to slow down.

[sIGPIC][/sIGPIC]

Daniel "EtherealN" Agorander | Даниэль "эфирныйн" Агорандер

Intel i7 2600K @ 4.4GHz, ASUS Sabertooth P67, 8GB Corsair Vengeance @ 1600MHz, ASUS GTX 560Ti DirectCU II 1GB, Samsung 830series 512GB SSD, Corsair AX850w, two BENQ screens and TM HOTAS Warthog

DCS: A-10C Warthog FAQ | DCS: P-51D FAQ | Remember to read the Forum Rules |

|
| Life of a Game Tester
Link to comment
Share on other sites

Hi, welcome to the forum.

 

Could you please havea a quick read-through this thread? It contains a lot of tips on how to easily get enough information to help us out in assisting you, and also several tips on how to maintain and verify system health: TROUBLESHOOTING - Help us helping you (FC2 edition)

 

Also, in the beginning of that thread there are directions on how to supply a DxDiag. Could you please do so? This should help verify what the driver situation is like without you having to go through each and every one.

 

My own suspicion is either a driver issue, or a heat issue. Have you verified that the temperature of your CPU and MCP (the XFX driver suite CD should have some nVidia software that allows you to monitor this - at least mine did) isn't spiking? The MCP should be fine, but on the CPU it is very easy to make a small mistake with the standard fans that results in ineficcient cooling. The heat situation then causes the processor tho throttle itself as it gets hot (it reduces it's clock frequency and/or "skips" clock cycles), which would make the whole system suddenly start to slow down.

 

Hi Ethereal,

 

Thanks again for the quick reply. Let me start by saying I love the game and have been playing it for a while, I just reinstalled it and getting these problems and now even on my other system that has 2x 8800 GTX SLI.

 

I'm good with systems so I can tell you that it's not running hot at all. using CPUID HWMonitor and reporting very low heat on all my hardware even under load, I have a really nice case with good cooling so it's not it. I tried rolling back some of the NVIDIA drivers but without any luck. Only tried a few versions back so far and want to test something more from last year. Again all I remember that running FC2 and Black Shark last year was a lot faster on my system than now.

 

I did get some better frame rates when changing some settings under NVIDIA control panel, under 3D settings I put "Select a PhysX processor" back to "CPU" instead of 465 GTX. Also under "Manage 3D settings" I set Texture Filtering Negative LOD bias to "Clamp" These 2 changes did give me much better frame rates however it still seams to lag for a second any time I view an external flyby where by the terrain flickers for a frame and loads with 3 to 4 frame shutter. Most noticeable is still at startup, sitting in cockpit when looking at the horizon where ever the parked aircraft are it slows down to like 12 frames a second. very choppy, but as soon as I look down in the cockpit or look straight up into the sky or even external view of the aircraft but looking down at it it's blazing fast. Again when I'm in the air it gets better. but as soon as there are other models it chopps. I have also tried all the graphics options under FC2 nothing makes a change. The heat blur now loosk good with the Clamp on LOD bias, which I'm not sure what it does yet but will investigate.

 

Anyway , here is my dxdiag. I want to make sure I have good system to run LOMAC as I'm really looking forward to A-10c Warthog. If I have to buy more hardware I will, just tell me what I need to get to run FC2 and A-10c at high frame rates and I will get it.

 

Considering that I also tested it on my brothers system also a quad core but this time with 2x 8800 GTX running in sli gave me the same results the problem must be with CPU or NVIDIA. Unless I'm doing something wrong at install, I just run LOMAC digital version download from ubisoft online store, than install FC2 followed by the 1.2.1 patch and run. Should i let it install directx? but I even when to ms site and got latest version after install.

 

Thanks


Edited by capsilus
Link to comment
Share on other sites

------------------

System Information

------------------

Time of this report: 8/17/2010, 23:08:07

Machine name: CAPSILUS-PC

Operating System: Windows 7 Ultimate 64-bit (6.1, Build 7600) (7600.win7_gdr.100618-1621)

Language: English (Regional Setting: English)

System Manufacturer: XFX

System Model: MB-750I-72P9

BIOS: Default System BIOS

Processor: Intel® Core2 Quad CPU Q9400 @ 2.66GHz (4 CPUs), ~2.7GHz

Memory: 8192MB RAM

Available OS Memory: 8192MB RAM

Page File: 1602MB used, 14778MB 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.

Sound Tab 3: 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 465

Manufacturer: NVIDIA

Chip type: GeForce GTX 465

DAC type: Integrated RAMDAC

Device Key: Enum\PCI\VEN_10DE&DEV_06C4&SUBSYS_14673842&REV_A3

Display Memory: 4065 MB

Dedicated Memory: 993 MB

Shared Memory: 3071 MB

Current Mode: 1680 x 1050 (32 bit) (60Hz)

Monitor Name: Generic PnP Monitor

Monitor Model: W2242

Monitor Id: GSM5678

Native Mode: 1680 x 1050(p) (59.883Hz)

Output Type: DVI

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

Driver File Version: 8.17.0012.5896 (English)

Driver Version: 8.17.12.5896

DDI Version: 10.1

Driver Model: WDDM 1.1

Driver Attributes: Final Retail

Driver Date/Size: 7/9/2010 18:38:00, 12471400 bytes

WHQL Logo'd: n/a

WHQL Date Stamp: n/a

Device Identifier: {D7B71E3E-4584-11CF-FA4C-6B341DC2C535}

Vendor ID: 0x10DE

Device ID: 0x06C4

SubSys ID: 0x14673842

Revision ID: 0x00A3

Driver Strong Name: oem14.inf:NVIDIA_SetA_Devices.NTamd64.6.1:Section012:8.17.12.5896:pci\ven_10de&dev_06c4

Rank Of Driver: 00E62001

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

 

-------------

Sound Devices

-------------

Description: Speakers (Realtek High Definition Audio)

Default Sound Playback: Yes

Default Voice Playback: Yes

Hardware ID: HDAUDIO\FUNC_01&VEN_10EC&DEV_0888&SUBSYS_14627567&REV_1001

Manufacturer ID: 1

Product ID: 100

Type: WDM

Driver Name: RTKVHD64.sys

Driver Version: 6.00.0001.6167 (English)

Driver Attributes: Final Retail

WHQL Logo'd: n/a

Date and Size: 7/28/2010 18:26:00, 2445672 bytes

Other Files:

Driver Provider: Realtek Semiconductor Corp.

HW Accel Level: Basic

Cap Flags: 0x0

Min/Max Sample Rate: 0, 0

Static/Strm HW Mix Bufs: 0, 0

Static/Strm HW 3D Bufs: 0, 0

HW Memory: 0

Voice Management: No

EAX 2.0 Listen/Src: No, No

I3DL2 Listen/Src: No, No

Sensaura ZoomFX: No

 

Description: Realtek Digital Output (Realtek High Definition Audio)

Default Sound Playback: No

Default Voice Playback: No

Hardware ID: HDAUDIO\FUNC_01&VEN_10EC&DEV_0888&SUBSYS_14627567&REV_1001

Manufacturer ID: 1

Product ID: 100

Type: WDM

Driver Name: RTKVHD64.sys

Driver Version: 6.00.0001.6167 (English)

Driver Attributes: Final Retail

WHQL Logo'd: n/a

Date and Size: 7/28/2010 18:26:00, 2445672 bytes

Other Files:

Driver Provider: Realtek Semiconductor Corp.

HW Accel Level: Basic

Cap Flags: 0x0

Min/Max Sample Rate: 0, 0

Static/Strm HW Mix Bufs: 0, 0

Static/Strm HW 3D Bufs: 0, 0

HW Memory: 0

Voice Management: No

EAX 2.0 Listen/Src: No, No

I3DL2 Listen/Src: No, No

Sensaura ZoomFX: No

 

Description: Realtek Digital Output(RCA) (Realtek High Definition Audio)

Default Sound Playback: No

Default Voice Playback: No

Hardware ID: HDAUDIO\FUNC_01&VEN_10EC&DEV_0888&SUBSYS_14627567&REV_1001

Manufacturer ID: 1

Product ID: 100

Type: WDM

Driver Name: RTKVHD64.sys

Driver Version: 6.00.0001.6167 (English)

Driver Attributes: Final Retail

WHQL Logo'd: n/a

Date and Size: 7/28/2010 18:26:00, 2445672 bytes

Other Files:

Driver Provider: Realtek Semiconductor Corp.

HW Accel Level: Basic

Cap Flags: 0x0

Min/Max Sample Rate: 0, 0

Static/Strm HW Mix Bufs: 0, 0

Static/Strm HW 3D Bufs: 0, 0

HW Memory: 0

Voice Management: No

EAX 2.0 Listen/Src: No, No

I3DL2 Listen/Src: No, No

Sensaura ZoomFX: No

Link to comment
Share on other sites

---------------------

Sound Capture Devices

---------------------

Description: Microphone (Realtek High Definition Audio)

Default Sound Capture: Yes

Default Voice Capture: Yes

Driver Name: RTKVHD64.sys

Driver Version: 6.00.0001.6167 (English)

Driver Attributes: Final Retail

Date and Size: 7/28/2010 18:26:00, 2445672 bytes

Cap Flags: 0x0

Format Flags: 0x0

 

-------------------

DirectInput Devices

-------------------

Device Name: Mouse

Attached: 1

Controller ID: n/a

Vendor/Product ID: n/a

FF Driver: n/a

 

Device Name: Keyboard

Attached: 1

Controller ID: n/a

Vendor/Product ID: n/a

FF Driver: n/a

 

Device Name: Razer Gaming Device

Attached: 1

Controller ID: 0x0

Vendor/Product ID: 0xBEEF, 0x0EED

FF Driver: n/a

 

Device Name: Logitech Attack 3

Attached: 1

Controller ID: 0x0

Vendor/Product ID: 0x046D, 0xC214

FF Driver: n/a

 

Device Name: Razer Lycosa

Attached: 1

Controller ID: 0x0

Vendor/Product ID: 0x1532, 0x0109

FF Driver: n/a

 

Device Name: Razer Lycosa

Attached: 1

Controller ID: 0x0

Vendor/Product ID: 0x1532, 0x0109

FF Driver: n/a

 

Poll w/ Interrupt: No

 

-----------

USB Devices

-----------

+ USB Root Hub

| Vendor/Product ID: 0x10DE, 0x026D

| Matching Device ID: usb\root_hub

| Service: usbhub

| Driver: usbhub.sys, 10/24/2009 00:28:24, 343040 bytes

| Driver: usbd.sys, 7/13/2009 20:06:23, 7936 bytes

|

+-+ DeathAdder Mouse

| | Vendor/Product ID: 0x1532, 0x0016

| | Location: Port_#0004.Hub_#0001

| | Matching Device ID: usb\vid_1532&pid_0016

| | Lower Filters: danewFltr

| | Service: HidUsb

| | Driver: danew.sys, 3/23/2010 16:37:34, 12032 bytes

| | Driver: hidusb.sys, 7/13/2009 20:06:22, 30208 bytes

| | Driver: hidclass.sys, 7/13/2009 20:06:21, 76288 bytes

| | Driver: hidparse.sys, 7/13/2009 20:06:17, 32896 bytes

| |

| +-+ HID-compliant mouse

| | | Vendor/Product ID: 0x1532, 0x0016

| | | Matching Device ID: hid_device_system_mouse

| | | Service: mouhid

| | | Driver: mouhid.sys, 7/13/2009 20:00:20, 31232 bytes

| | | Driver: mouclass.sys, 7/13/2009 21:48:27, 49216 bytes

| |

+-+ USB Input Device

| | Vendor/Product ID: 0x046D, 0xC214

| | Location: Port_#0008.Hub_#0001

| | Matching Device ID: generic_hid_device

| | Service: HidUsb

| | OEMData: 01 00 00 10 0B 00 00 00

| | Driver: hidusb.sys, 7/13/2009 20:06:22, 30208 bytes

| | Driver: hidclass.sys, 7/13/2009 20:06:21, 76288 bytes

| | Driver: hidparse.sys, 7/13/2009 20:06:17, 32896 bytes

| |

| +-+ HID-compliant game controller

| | | Vendor/Product ID: 0x046D, 0xC214

| | | Matching Device ID: hid_device_system_game

| | | OEMData: 01 00 00 10 0B 00 00 00

 

----------------

Gameport Devices

----------------

 

------------

PS/2 Devices

------------

+ HID Keyboard Device

| Matching Device ID: hid_device_system_keyboard

| Service: kbdhid

| Driver: kbdhid.sys, 7/13/2009 20:00:20, 33280 bytes

| Driver: kbdclass.sys, 7/13/2009 21:48:04, 50768 bytes

|

+ HID Keyboard Device

| Vendor/Product ID: 0x1532, 0x0109

| Matching Device ID: hid_device_system_keyboard

| Service: kbdhid

| Driver: kbdhid.sys, 7/13/2009 20:00:20, 33280 bytes

| Driver: kbdclass.sys, 7/13/2009 21:48:04, 50768 bytes

|

+ Terminal Server Keyboard Driver

| Matching Device ID: root\rdp_kbd

| Upper Filters: kbdclass

| Service: TermDD

| Driver: i8042prt.sys, 7/13/2009 19:19:57, 105472 bytes

| Driver: kbdclass.sys, 7/13/2009 21:48:04, 50768 bytes

|

+ HID-compliant mouse

| Matching Device ID: hid_device_system_mouse

| Service: mouhid

| Driver: mouhid.sys, 7/13/2009 20:00:20, 31232 bytes

| Driver: mouclass.sys, 7/13/2009 21:48:27, 49216 bytes

|

+ Terminal Server Mouse Driver

| Matching Device ID: root\rdp_mou

| Upper Filters: mouclass

| Service: TermDD

| Driver: termdd.sys, 7/13/2009 21:45:55, 62544 bytes

| Driver: sermouse.sys, 7/13/2009 20:00:20, 26624 bytes

| Driver: mouclass.sys, 7/13/2009 21:48:27, 49216 bytes

Link to comment
Share on other sites

------------------

DirectShow Filters

------------------

 

DirectShow Filters:

WMAudio Decoder DMO,0x00800800,1,1,WMADMOD.DLL,6.01.7600.16385

WMAPro over S/PDIF DMO,0x00600800,1,1,WMADMOD.DLL,6.01.7600.16385

WMSpeech Decoder DMO,0x00600800,1,1,WMSPDMOD.DLL,6.01.7600.16385

MP3 Decoder DMO,0x00600800,1,1,mp3dmod.dll,6.01.7600.16385

Mpeg4s Decoder DMO,0x00800001,1,1,mp4sdecd.dll,6.01.7600.16385

WMV Screen decoder DMO,0x00600800,1,1,wmvsdecd.dll,6.01.7600.16385

WMVideo Decoder DMO,0x00800001,1,1,wmvdecod.dll,6.01.7600.16385

Mpeg43 Decoder DMO,0x00800001,1,1,mp43decd.dll,6.01.7600.16385

Mpeg4 Decoder DMO,0x00800001,1,1,mpg4decd.dll,6.01.7600.16385

DV Muxer,0x00400000,0,0,qdv.dll,6.06.7600.16385

Color Space Converter,0x00400001,1,1,quartz.dll,6.06.7600.16490

WM ASF Reader,0x00400000,0,0,qasf.dll,12.00.7600.16385

Screen Capture filter,0x00200000,0,1,wmpsrcwp.dll,12.00.7600.16385

AVI Splitter,0x00600000,1,1,quartz.dll,6.06.7600.16490

VGA 16 Color Ditherer,0x00400000,1,1,quartz.dll,6.06.7600.16490

SBE2MediaTypeProfile,0x00200000,0,0,sbe.dll,6.06.7600.16385

Microsoft DTV-DVD Video Decoder,0x005fffff,2,4,msmpeg2vdec.dll,6.01.7140.0000

AC3 Parser Filter,0x00600000,1,1,mpg2splt.ax,6.06.7600.16590

StreamBufferSink,0x00200000,0,0,sbe.dll,6.06.7600.16385

Microsoft TV Captions Decoder,0x00200001,1,0,MSTVCapn.dll,6.01.7600.16385

MJPEG Decompressor,0x00600000,1,1,quartz.dll,6.06.7600.16490

CBVA DMO wrapper filter,0x00200000,1,1,cbva.dll,6.01.7600.16385

MPEG-I Stream Splitter,0x00600000,1,2,quartz.dll,6.06.7600.16490

SAMI (CC) Parser,0x00400000,1,1,quartz.dll,6.06.7600.16490

VBI Codec,0x00600000,1,4,VBICodec.ax,6.06.7600.16385

MPEG-2 Splitter,0x005fffff,1,0,mpg2splt.ax,6.06.7600.16590

Closed Captions Analysis Filter,0x00200000,2,5,cca.dll,6.06.7600.16385

SBE2FileScan,0x00200000,0,0,sbe.dll,6.06.7600.16385

Microsoft MPEG-2 Video Encoder,0x00200000,1,1,msmpeg2enc.dll,6.01.7600.16385

Internal Script Command Renderer,0x00800001,1,0,quartz.dll,6.06.7600.16490

MPEG Audio Decoder,0x03680001,1,1,quartz.dll,6.06.7600.16490

DV Splitter,0x00600000,1,2,qdv.dll,6.06.7600.16385

Video Mixing Renderer 9,0x00200000,1,0,quartz.dll,6.06.7600.16490

Microsoft MPEG-2 Encoder,0x00200000,2,1,msmpeg2enc.dll,6.01.7600.16385

ACM Wrapper,0x00600000,1,1,quartz.dll,6.06.7600.16490

Video Renderer,0x00800001,1,0,quartz.dll,6.06.7600.16490

MPEG-2 Video Stream Analyzer,0x00200000,0,0,sbe.dll,6.06.7600.16385

Line 21 Decoder,0x00600000,1,1,,

Video Port Manager,0x00600000,2,1,quartz.dll,6.06.7600.16490

Video Renderer,0x00400000,1,0,quartz.dll,6.06.7600.16490

VPS Decoder,0x00200000,0,0,WSTPager.ax,6.06.7600.16385

WM ASF Writer,0x00400000,0,0,qasf.dll,12.00.7600.16385

VBI Surface Allocator,0x00600000,1,1,vbisurf.ax,6.01.7600.16385

File writer,0x00200000,1,0,qcap.dll,6.06.7600.16385

iTV Data Sink,0x00600000,1,0,itvdata.dll,6.06.7600.16385

iTV Data Capture filter,0x00600000,1,1,itvdata.dll,6.06.7600.16385

DVD Navigator,0x00200000,0,3,qdvd.dll,6.06.7600.16385

Microsoft TV Subtitles Decoder,0x00200001,1,0,MSTVCapn.dll,6.01.7600.16385

Overlay Mixer2,0x00200000,1,1,,

RDP DShow Redirection Filter,0xffffffff,1,0,DShowRdpFilter.dll,

Microsoft MPEG-2 Audio Encoder,0x00200000,1,1,msmpeg2enc.dll,6.01.7600.16385

WST Pager,0x00200000,1,1,WSTPager.ax,6.06.7600.16385

MPEG-2 Demultiplexer,0x00600000,1,1,mpg2splt.ax,6.06.7600.16590

DV Video Decoder,0x00800000,1,1,qdv.dll,6.06.7600.16385

SampleGrabber,0x00200000,1,1,qedit.dll,6.06.7600.16385

Null Renderer,0x00200000,1,0,qedit.dll,6.06.7600.16385

MPEG-2 Sections and Tables,0x005fffff,1,0,Mpeg2------------------------

Disk & DVD/CD-ROM Drives

------------------------

Drive: C:

Free Space: 179.3 GB

Total Space: 305.1 GB

File System: NTFS

Model: ST332062 0AS SCSI Disk Device

 

Drive: D:

Free Space: 131.9 GB

Total Space: 305.2 GB

File System: NTFS

Model: ST332062 0AS SCSI Disk Device

 

Drive: E:

Free Space: 59.3 GB

Total Space: 410.9 GB

File System: NTFS

Model: ST350032 0AS SCSI Disk Device

 

Drive: G:

Free Space: 0.1 GB

Total Space: 0.1 GB

File System: NTFS

Model: ST332062 0AS SCSI Disk Device

 

Drive: T:

Free Space: 449.4 GB

Total Space: 953.6 GB

File System: FAT32

Model: WD 10EADS External USB Device

 

Drive: F:

Model: PBDS DVD+-RW DH-16W1S SCSI CdRom Device

Driver: c:\windows\system32\drivers\cdrom.sys, 6.01.7600.16385 (English), 7/13/2009 19:19:54, 147456 bytes

 

--------------

System Devices

--------------

Name: PCI standard PCI-to-PCI bridge

Device ID: PCI\VEN_10DE&DEV_05B1&SUBSYS_00000000&REV_A2\5&35D05A08&0&180018

Driver: C:\Windows\system32\DRIVERS\pci.sys, 6.01.7600.16385 (English), 7/13/2009 21:45:45, 183872 bytes

 

Name: PCI standard RAM Controller

Device ID: PCI\VEN_10DE&DEV_03B6&SUBSYS_00000000&REV_A1\3&267A616A&0&10

Driver: n/a

 

Name: PCI standard RAM Controller

Device ID: PCI\VEN_10DE&DEV_03AE&SUBSYS_00000000&REV_A1\3&267A616A&0&09

Driver: n/a

 

Name: PCI standard RAM Controller

Device ID: PCI\VEN_10DE&DEV_0272&SUBSYS_75671462&REV_A3\3&267A616A&0&52

Driver: n/a

 

Name: NVIDIA nForce Serial ATA Controller

Device ID: PCI\VEN_10DE&DEV_0266&SUBSYS_75671462&REV_A1\3&267A616A&0&70

Driver: C:\Windows\system32\DRIVERS\nvstor64.sys, 11.01.0000.0033 (English), 8/4/2009 17:45:32, 241696 bytes

Driver: C:\Windows\system32\nvraidco.dll, 11.01.0000.0033 (English), 8/4/2009 17:45:32, 402976 bytes

Driver: C:\Windows\system32\nvraiins.dll, 11.01.0000.0033 (English), 8/4/2009 17:45:32, 402976 bytes

Driver: C:\Windows\system32\NvRCoDa.dll, 11.01.0000.0033 (Danish), 8/4/2009 17:45:34, 18464 bytes

Driver: C:\Windows\system32\NvRCoDe.dll, 11.01.0000.0033 (German), 8/4/2009 17:45:34, 18976 bytes

Driver: C:\Windows\system32\NvRCoEng.dll, 11.01.0000.0033 (English), 8/4/2009 17:45:34, 17952 bytes

Driver: C:\Windows\system32\NvRCoENU.dll, 11.01.0000.0033 (English), 8/4/2009 17:45:36, 17952 bytes

Driver: C:\Windows\system32\NvRCoEs.dll, 11.01.0000.0033 (Spanish), 8/4/2009 17:45:36, 18976 bytes

Driver: C:\Windows\system32\NvRCoEsm.dll, 11.01.0000.0033 (Spanish), 8/4/2009 17:45:38, 18976 bytes

Driver: C:\Windows\system32\NvRCoFi.dll, 11.01.0000.0033 (Finnish), 8/4/2009 17:45:38, 18464 bytes

Driver: C:\Windows\system32\NvRCoFr.dll, 11.01.0000.0033 (French), 8/4/2009 17:45:40, 18976 bytes

Driver: C:\Windows\system32\NvRCoIt.dll, 11.01.0000.0033 (Italian), 8/4/2009 17:45:40, 18976 bytes

Driver: C:\Windows\system32\NvRCoJa.dll, 11.01.0000.0033 (Japanese), 8/4/2009 17:45:42, 16416 bytes

Driver: C:\Windows\system32\NvRCoKo.dll, 11.01.0000.0033 (Korean), 8/4/2009 17:45:42, 16416 bytes

Driver: C:\Windows\system32\NvRCoNl.dll, 11.01.0000.0033 (Dutch), 8/4/2009 17:45:44, 18464 bytes

Driver: C:\Windows\system32\NvRCoNo.dll, 11.01.0000.0033 (Norwegian (Bokmål)), 8/4/2009 17:45:48, 18464 bytes

Driver: C:\Windows\system32\NvRCoPtb.dll, 11.01.0000.0033 (Portuguese), 8/4/2009 17:45:50, 18976 bytes

Driver: C:\Windows\system32\NvRCoRu.dll, 11.01.0000.0033 (Russian), 8/4/2009 17:45:50, 18464 bytes

Driver: C:\Windows\system32\NvRCoSv.dll, 11.01.0000.0033 (Swedish), 8/4/2009 17:45:52, 18464 bytes

Driver: C:\Windows\system32\NvRCoZhc.dll, 11.01.0000.0033 (Chinese (Simplified)), 8/4/2009 17:45:52, 15904 bytes

Driver: C:\Windows\system32\NvRCoZht.dll, 11.01.0000.0033 (Chinese (Traditional)), 8/4/2009 17:45:54, 15904 bytes

 

Name: PCI standard PCI-to-PCI bridge

Device ID: PCI\VEN_10DE&DEV_05B1&SUBSYS_00000000&REV_A2\5&35D05A08&0&100018

Driver: C:\Windows\system32\DRIVERS\pci.sys, 6.01.7600.16385 (English), 7/13/2009 21:45:45, 183872 bytes

 

Name: PCI standard RAM Controller

Device ID: PCI\VEN_10DE&DEV_03B5&SUBSYS_00000000&REV_A1\3&267A616A&0&06

Driver: n/a

 

Name: PCI standard RAM Controller

Device ID: PCI\VEN_10DE&DEV_03AD&SUBSYS_00000000&REV_A1\3&267A616A&0&08

Driver: n/a

 

Name: PCI standard RAM Controller

Device ID: PCI\VEN_10DE&DEV_0270&SUBSYS_75671462&REV_A2\3&267A616A&0&48

Driver: n/a

 

Name: Standard Dual Channel PCI IDE Controller

Device ID: PCI\VEN_10DE&DEV_0265&SUBSYS_75671462&REV_A1\3&267A616A&0&68

Driver: C:\Windows\system32\DRIVERS\pciide.sys, 6.01.7600.16385 (English), 7/13/2009 21:45:45, 12352 bytes

Driver: C:\Windows\system32\DRIVERS\pciidex.sys, 6.01.7600.16385 (English), 7/13/2009 21:45:46, 48720 bytes

Driver: C:\Windows\system32\DRIVERS\atapi.sys, 6.01.7600.16385 (English), 7/13/2009 21:52:21, 24128 bytes

Driver: C:\Windows\system32\DRIVERS\ataport.sys, 6.01.7600.16385 (English), 7/13/2009 21:52:21, 155728 bytes

 

Name: PCI standard PCI-to-PCI bridge

Device ID: PCI\VEN_10DE&DEV_05B1&SUBSYS_00000000&REV_A2\5&35D05A08&0&000018

Driver: C:\Windows\system32\DRIVERS\pci.sys, 6.01.7600.16385 (English), 7/13/2009 21:45:45, 183872 bytes

 

Name: PCI standard RAM Controller

Device ID: PCI\VEN_10DE&DEV_03B4&SUBSYS_00000000&REV_A1\3&267A616A&0&07

Driver: n/a

 

Name: PCI standard RAM Controller

Device ID: PCI\VEN_10DE&DEV_03AC&SUBSYS_00000000&REV_A1\3&267A616A&0&01

Driver: n/a

 

Name: PCI standard PCI-to-PCI bridge

Device ID: PCI\VEN_10DE&DEV_026F&SUBSYS_CB8410DE&REV_A2\3&267A616A&0&80

Driver: C:\Windows\system32\DRIVERS\pci.sys, 6.01.7600.16385 (English), 7/13/2009 21:45:45, 183872 bytes

 

Name: NVIDIA nForce PCI System Management

Device ID: PCI\VEN_10DE&DEV_0264&SUBSYS_75671462&REV_A3\3&267A616A&0&51

Driver: n/a

Link to comment
Share on other sites

Name: Standard Dual Channel PCI IDE Controller

Device ID: PCI\VEN_197B&DEV_2363&SUBSYS_75671462&REV_03\4&26F59549&0&0030

Driver: C:\Windows\system32\DRIVERS\pciide.sys, 6.01.7600.16385 (English), 7/13/2009 21:45:45, 12352 bytes

Driver: C:\Windows\system32\DRIVERS\pciidex.sys, 6.01.7600.16385 (English), 7/13/2009 21:45:46, 48720 bytes

Driver: C:\Windows\system32\DRIVERS\atapi.sys, 6.01.7600.16385 (English), 7/13/2009 21:52:21, 24128 bytes

Driver: C:\Windows\system32\DRIVERS\ataport.sys, 6.01.7600.16385 (English), 7/13/2009 21:52:21, 155728 bytes

 

Name: PCI standard RAM Controller

Device ID: PCI\VEN_10DE&DEV_03BC&SUBSYS_00000000&REV_A1\3&267A616A&0&11

Driver: n/a

 

Name: PCI standard RAM Controller

Device ID: PCI\VEN_10DE&DEV_03B3&SUBSYS_00000000&REV_A1\3&267A616A&0&0E

Driver: n/a

 

Name: PCI standard RAM Controller

Device ID: PCI\VEN_10DE&DEV_03AB&SUBSYS_00000000&REV_A1\3&267A616A&0&04

Driver: n/a

 

Name: Standard Enhanced PCI to USB Host Controller

Device ID: PCI\VEN_10DE&DEV_026E&SUBSYS_75671462&REV_A3\3&267A616A&0&59

Driver: C:\Windows\system32\drivers\usbehci.sys, 6.01.7600.16445 (English), 10/24/2009 00:27:33, 51712 bytes

Driver: C:\Windows\system32\drivers\usbport.sys, 6.01.7600.16385 (English), 7/13/2009 20:06:31, 324608 bytes

Driver: C:\Windows\system32\drivers\usbhub.sys, 6.01.7600.16445 (English), 10/24/2009 00:28:24, 343040 bytes

 

Name: PCI standard ISA bridge

Device ID: PCI\VEN_10DE&DEV_0260&SUBSYS_75671462&REV_A3\3&267A616A&0&50

Driver: C:\Windows\system32\DRIVERS\msisadrv.sys, 6.01.7600.16385 (English), 7/13/2009 21:48:27, 15424 bytes

 

Name: PCI standard PCI-to-PCI bridge

Device ID: PCI\VEN_10DE&DEV_03BB&SUBSYS_0C5510DE&REV_A1\3&267A616A&0&38

Driver: C:\Windows\system32\DRIVERS\pci.sys, 6.01.7600.16385 (English), 7/13/2009 21:45:45, 183872 bytes

 

Name: PCI standard RAM Controller

Device ID: PCI\VEN_10DE&DEV_03B2&SUBSYS_00000000&REV_A1\3&267A616A&0&0D

Driver: n/a

 

Name: PCI standard RAM Controller

Device ID: PCI\VEN_10DE&DEV_03AA&SUBSYS_00000000&REV_A1\3&267A616A&0&02

Driver: n/a

 

Name: Standard OpenHCD USB Host Controller

Device ID: PCI\VEN_10DE&DEV_026D&SUBSYS_75671462&REV_A3\3&267A616A&0&58

Driver: C:\Windows\system32\drivers\usbohci.sys, 6.01.7600.16385 (English), 7/13/2009 20:06:30, 25600 bytes

Driver: C:\Windows\system32\drivers\usbport.sys, 6.01.7600.16385 (English), 7/13/2009 20:06:31, 324608 bytes

Driver: C:\Windows\system32\drivers\usbhub.sys, 6.01.7600.16445 (English), 10/24/2009 00:28:24, 343040 bytes

 

Name: High Definition Audio Controller

Device ID: PCI\VEN_10DE&DEV_0BE5&SUBSYS_14673842&REV_A1\6&25811459&0&01100018

Driver: C:\Windows\system32\DRIVERS\hdaudbus.sys, 6.01.7600.16385 (English), 7/13/2009 20:06:13, 122368 bytes

 

Name: PCI standard RAM Controller

Device ID: PCI\VEN_10DE&DEV_03BA&SUBSYS_00000000&REV_A1\3&267A616A&0&12

Driver: n/a

 

Name: PCI standard RAM Controller

Device ID: PCI\VEN_10DE&DEV_03B1&SUBSYS_00000000&REV_A1\3&267A616A&0&0C

Driver: n/a

 

Name: PCI standard RAM Controller

Device ID: PCI\VEN_10DE&DEV_03A9&SUBSYS_00000000&REV_A1\3&267A616A&0&03

Driver: n/a

 

Name: High Definition Audio Controller

Device ID: PCI\VEN_10DE&DEV_026C&SUBSYS_75671462&REV_A2\3&267A616A&0&81

Driver: C:\Windows\system32\DRIVERS\hdaudbus.sys, 6.01.7600.16385 (English), 7/13/2009 20:06:13, 122368 bytes

 

Name: NVIDIA GeForce GTX 465

Device ID: PCI\VEN_10DE&DEV_06C4&SUBSYS_14673842&REV_A3\6&25811459&0&00100018

Driver: C:\Program Files\NVIDIA Corporation\Drs\dbInstaller.exe, 8.17.0012.5896 (English), 7/9/2010 18:38:00, 189032 bytes

Driver: C:\Program Files\NVIDIA Corporation\Drs\nvdrsdb.bin, 7/9/2010 18:38:00, 261268 bytes

Driver: C:\Windows\System32\DriverStore\FileRepository\nv_disp.inf_amd64_neutral_e3981c6eee5931b7\NvCplSetupEng.exe, 14.00.0000.0162 (English), 7/9/2010 18:38:00, 23969016 bytes

Driver: C:\Windows\system32\DRIVERS\nvBridge.kmd, 8.17.0012.5896 (English), 7/9/2010 18:38:00, 11240 bytes

Driver: C:\Windows\system32\DRIVERS\nvlddmkm.sys, 8.17.0012.5896 (English), 7/9/2010 18:38:00, 13187176 bytes

Driver: C:\Windows\system32\OpenCL.dll, 1.00.0000.0000 (English), 7/9/2010 18:38:00, 65128 bytes

Driver: C:\Windows\system32\dpinst.exe, 2.00.0001.0000 (English), 7/30/2009 10:29:58, 845736 bytes

Driver: C:\Windows\system32\nvapi64.dll, 8.17.0012.5896 (English), 7/9/2010 18:38:00, 2037864 bytes

Driver: C:\Windows\system32\nvcompiler.dll, 6.14.0012.5896 (English), 7/9/2010 18:38:00, 14513768 bytes

Driver: C:\Windows\system32\nvcuda.dll, 8.17.0012.5896 (English), 7/9/2010 18:38:00, 6116968 bytes

Driver: C:\Windows\system32\nvcuvenc.dll, 6.14.0012.5896 (English), 7/9/2010 18:38:00, 2761832 bytes

Driver: C:\Windows\system32\nvcuvid.dll, 8.17.0012.5896 (English), 7/9/2010 18:38:00, 3089512 bytes

Driver: C:\Windows\system32\nvd3dumx.dll, 8.17.0012.5896 (English), 7/9/2010 18:38:00, 12471400 bytes

Driver: C:\Windows\system32\nvdecodemft.dll, 8.17.0012.5896 (English), 7/9/2010 18:38:00, 382568 bytes

Driver: C:\Windows\system32\nvinfo.pb, 7/9/2010 18:38:00, 12264 bytes

Driver: C:\Windows\system32\nvoglv64.dll, 8.17.0012.5896 (English), 7/9/2010 18:38:00, 19114088 bytes

Driver: C:\Windows\system32\nvwgf2umx.dll, 8.17.0012.5896 (English), 7/9/2010 18:38:00, 7002216 bytes

Driver: C:\Windows\SysWow64\OpenCL.dll, 1.00.0000.0000 (English), 7/9/2010 18:38:00, 56936 bytes

Driver: C:\Windows\SysWow64\nvapi.dll, 8.17.0012.5896 (English), 7/9/2010 18:38:00, 1625192 bytes

Driver: C:\Windows\SysWow64\nvcompiler.dll, 6.14.0012.5896 (English), 7/9/2010 18:38:00, 10267240 bytes

Driver: C:\Windows\SysWow64\nvcuda.dll, 8.17.0012.5896 (English), 7/9/2010 18:38:00, 4553832 bytes

Driver: C:\Windows\SysWow64\nvcuvenc.dll, 6.14.0012.5896 (English), 7/9/2010 18:38:00, 2506344 bytes

Driver: C:\Windows\SysWow64\nvcuvid.dll, 8.17.0012.5896 (English), 7/9/2010 18:38:00, 2892904 bytes

Driver: C:\Windows\SysWow64\nvd3dum.dll, 8.17.0012.5896 (English), 7/9/2010 18:38:00, 9818728 bytes

Driver: C:\Windows\SysWow64\nvdecodemft.dll, 8.17.0012.5896 (English), 7/9/2010 18:38:00, 314984 bytes

Driver: C:\Windows\SysWow64\nvoglv32.dll, 8.17.0012.5896 (English), 7/9/2010 18:38:00, 14092904 bytes

Driver: C:\Windows\SysWow64\nvwgf2um.dll, 8.17.0012.5896 (English), 7/9/2010 18:38:00, 5107816 bytes

Driver: C:\Program Files\NVIDIA Corporation\Uninstall\nvdisp.nvu, 7/9/2010 18:38:00, 24011 bytes

Driver: C:\Program Files\NVIDIA Corporation\Uninstall\nvudisp.exe, 1.10.0062.0040 (English), 7/9/2010 18:38:00, 660072 bytes

Driver: C:\Windows\system32\nvcod.dll, 1.09.0022.0107 (English), 7/9/2010 18:38:00, 260712 bytes

Driver: C:\Windows\system32\nvcod1922.dll, 1.09.0022.0107 (English), 7/9/2010 18:38:00, 260712 bytes

 

Name: PCI standard PCI-to-PCI bridge

Device ID: PCI\VEN_10DE&DEV_03B9&SUBSYS_0C5510DE&REV_A1\3&267A616A&0&30

Driver: C:\Windows\system32\DRIVERS\pci.sys, 6.01.7600.16385 (English), 7/13/2009 21:45:45, 183872 bytes

 

Name: PCI standard RAM Controller

Device ID: PCI\VEN_10DE&DEV_03B0&SUBSYS_00000000&REV_A1\3&267A616A&0&0B

Driver: n/a

 

Name: PCI standard RAM Controller

Device ID: PCI\VEN_10DE&DEV_03A8&SUBSYS_00000000&REV_A2\3&267A616A&0&05

Driver: n/a

 

Name: NVIDIA nForce 10/100/1000 Mbps Ethernet

Device ID: PCI\VEN_10DE&DEV_0269&SUBSYS_567C1462&REV_A3\3&267A616A&0&A0

Driver: n/a

 

Name: PCI standard PCI-to-PCI bridge

Device ID: PCI\VEN_10DE&DEV_05B1&SUBSYS_75671462&REV_A2\4&334D9995&0&0018

Driver: C:\Windows\system32\DRIVERS\pci.sys, 6.01.7600.16385 (English), 7/13/2009 21:45:45, 183872 bytes

 

Name: PCI standard PCI-to-PCI bridge

Device ID: PCI\VEN_10DE&DEV_03B7&SUBSYS_0C5510DE&REV_A1\3&267A616A&0&18

Driver: C:\Windows\system32\DRIVERS\pci.sys, 6.01.7600.16385 (English), 7/13/2009 21:45:45, 183872 bytes

 

Name: PCI standard RAM Controller

Device ID: PCI\VEN_10DE&DEV_03AF&SUBSYS_00000000&REV_A1\3&267A616A&0&0A

Driver: n/a

Link to comment
Share on other sites

Name: PCI standard host CPU bridge

Device ID: PCI\VEN_10DE&DEV_03A3&SUBSYS_00000000&REV_A2\3&267A616A&0&00

Driver: n/a

 

Name: NVIDIA nForce Serial ATA Controller

Device ID: PCI\VEN_10DE&DEV_0267&SUBSYS_75671462&REV_A1\3&267A616A&0&78

Driver: C:\Windows\system32\DRIVERS\nvstor64.sys, 11.01.0000.0033 (English), 8/4/2009 17:45:32, 241696 bytes

Driver: C:\Windows\system32\nvraidco.dll, 11.01.0000.0033 (English), 8/4/2009 17:45:32, 402976 bytes

Driver: C:\Windows\system32\nvraiins.dll, 11.01.0000.0033 (English), 8/4/2009 17:45:32, 402976 bytes

Driver: C:\Windows\system32\NvRCoDa.dll, 11.01.0000.0033 (Danish), 8/4/2009 17:45:34, 18464 bytes

Driver: C:\Windows\system32\NvRCoDe.dll, 11.01.0000.0033 (German), 8/4/2009 17:45:34, 18976 bytes

Driver: C:\Windows\system32\NvRCoEng.dll, 11.01.0000.0033 (English), 8/4/2009 17:45:34, 17952 bytes

Driver: C:\Windows\system32\NvRCoENU.dll, 11.01.0000.0033 (English), 8/4/2009 17:45:36, 17952 bytes

Driver: C:\Windows\system32\NvRCoEs.dll, 11.01.0000.0033 (Spanish), 8/4/2009 17:45:36, 18976 bytes

Driver: C:\Windows\system32\NvRCoEsm.dll, 11.01.0000.0033 (Spanish), 8/4/2009 17:45:38, 18976 bytes

Driver: C:\Windows\system32\NvRCoFi.dll, 11.01.0000.0033 (Finnish), 8/4/2009 17:45:38, 18464 bytes

Driver: C:\Windows\system32\NvRCoFr.dll, 11.01.0000.0033 (French), 8/4/2009 17:45:40, 18976 bytes

Driver: C:\Windows\system32\NvRCoIt.dll, 11.01.0000.0033 (Italian), 8/4/2009 17:45:40, 18976 bytes

Driver: C:\Windows\system32\NvRCoJa.dll, 11.01.0000.0033 (Japanese), 8/4/2009 17:45:42, 16416 bytes

Driver: C:\Windows\system32\NvRCoKo.dll, 11.01.0000.0033 (Korean), 8/4/2009 17:45:42, 16416 bytes

Driver: C:\Windows\system32\NvRCoNl.dll, 11.01.0000.0033 (Dutch), 8/4/2009 17:45:44, 18464 bytes

Driver: C:\Windows\system32\NvRCoNo.dll, 11.01.0000.0033 (Norwegian (Bokmål)), 8/4/2009 17:45:48, 18464 bytes

Driver: C:\Windows\system32\NvRCoPtb.dll, 11.01.0000.0033 (Portuguese), 8/4/2009 17:45:50, 18976 bytes

Driver: C:\Windows\system32\NvRCoRu.dll, 11.01.0000.0033 (Russian), 8/4/2009 17:45:50, 18464 bytes

Driver: C:\Windows\system32\NvRCoSv.dll, 11.01.0000.0033 (Swedish), 8/4/2009 17:45:52, 18464 bytes

Driver: C:\Windows\system32\NvRCoZhc.dll, 11.01.0000.0033 (Chinese (Simplified)), 8/4/2009 17:45:52, 15904 bytes

Driver: C:\Windows\system32\NvRCoZht.dll, 11.01.0000.0033 (Chinese (Traditional)), 8/4/2009 17:45:54, 15904 bytesData.ax,6.06.7600.16385

Microsoft AC3 Encoder,0x00200000,1,1,msac3enc.dll,6.01.7600.16385

StreamBufferSource,0x00200000,0,0,sbe.dll,6.06.7600.16385

Smart Tee,0x00200000,1,2,qcap.dll,6.06.7600.16385

Overlay Mixer,0x00200000,0,0,,

AVI Decompressor,0x00600000,1,1,quartz.dll,6.06.7600.16490

NetBridge,0x00200000,2,0,netbridge.dll,6.01.7600.16385

AVI/WAV File Source,0x00400000,0,2,quartz.dll,6.06.7600.16490

Wave Parser,0x00400000,1,1,quartz.dll,6.06.7600.16490

MIDI Parser,0x00400000,1,1,quartz.dll,6.06.7600.16490

Multi-file Parser,0x00400000,1,1,quartz.dll,6.06.7600.16490

File stream renderer,0x00400000,1,1,quartz.dll,6.06.7600.16490

Microsoft DTV-DVD Audio Decoder,0x005fffff,1,1,msmpeg2adec.dll,6.01.7140.0000

StreamBufferSink2,0x00200000,0,0,sbe.dll,6.06.7600.16385

AVI Mux,0x00200000,1,0,qcap.dll,6.06.7600.16385

Line 21 Decoder 2,0x00600002,1,1,quartz.dll,6.06.7600.16490

File Source (Async.),0x00400000,0,1,quartz.dll,6.06.7600.16490

File Source (URL),0x00400000,0,1,quartz.dll,6.06.7600.16490

Media Center Extender Encryption Filter,0x00200000,2,2,Mcx2Filter.dll,6.01.7600.16385

AudioRecorder WAV Dest,0x00200000,0,0,WavDest.dll,

AudioRecorder Wave Form,0x00200000,0,0,WavDest.dll,

SoundRecorder Null Renderer,0x00200000,0,0,WavDest.dll,

Infinite Pin Tee Filter,0x00200000,1,1,qcap.dll,6.06.7600.16385

Enhanced Video Renderer,0x00200000,1,0,evr.dll,6.01.7600.16385

BDA MPEG2 Transport Information Filter,0x00200000,2,0,psisrndr.ax,6.06.7600.16385

MPEG Video Decoder,0x40000001,1,1,quartz.dll,6.06.7600.16490

 

WDM Streaming Tee/Splitter Devices:

Tee/Sink-to-Sink Converter,0x00200000,1,1,ksproxy.ax,6.01.7600.16385

 

Video Compressors:

WMVideo8 Encoder DMO,0x00600800,1,1,wmvxencd.dll,6.01.7600.16385

WMVideo9 Encoder DMO,0x00600800,1,1,wmvencod.dll,6.01.7600.16385

MSScreen 9 encoder DMO,0x00600800,1,1,wmvsencd.dll,6.01.7600.16385

DV Video Encoder,0x00200000,0,0,qdv.dll,6.06.7600.16385

MJPEG Compressor,0x00200000,0,0,quartz.dll,6.06.7600.16490

 

Audio Compressors:

WM Speech Encoder DMO,0x00600800,1,1,WMSPDMOE.DLL,6.01.7600.16385

WMAudio Encoder DMO,0x00600800,1,1,WMADMOE.DLL,6.01.7600.16385

IMA ADPCM,0x00200000,1,1,quartz.dll,6.06.7600.16490

PCM,0x00200000,1,1,quartz.dll,6.06.7600.16490

Microsoft ADPCM,0x00200000,1,1,quartz.dll,6.06.7600.16490

GSM 6.10,0x00200000,1,1,quartz.dll,6.06.7600.16490

CCITT A-Law,0x00200000,1,1,quartz.dll,6.06.7600.16490

CCITT u-Law,0x00200000,1,1,quartz.dll,6.06.7600.16490

MPEG Layer-3,0x00200000,1,1,quartz.dll,6.06.7600.16490

 

Audio Capture Sources:

Microphone (Realtek High Defini,0x00200000,0,0,qcap.dll,6.06.7600.16385

 

PBDA CP Filters:

PBDA DTFilter,0x00600000,1,1,CPFilters.dll,6.06.7600.16590

PBDA ETFilter,0x00200000,0,0,CPFilters.dll,6.06.7600.16590

PBDA PTFilter,0x00200000,0,0,CPFilters.dll,6.06.7600.16590

 

Midi Renderers:

Default MidiOut Device,0x00800000,1,0,quartz.dll,6.06.7600.16490

Microsoft GS Wavetable Synth,0x00200000,1,0,quartz.dll,6.06.7600.16490

 

WDM Streaming Capture Devices:

Realtek HD Audio CD input,0x00200000,1,1,ksproxy.ax,6.01.7600.16385

Realtek HD Audio Line input,0x00200000,1,1,ksproxy.ax,6.01.7600.16385

Realtek HD Audio Mic input,0x00200000,1,1,ksproxy.ax,6.01.7600.16385

Realtek HD Audio Stereo input,0x00200000,1,1,ksproxy.ax,6.01.7600.16385

 

WDM Streaming Rendering Devices:

Realtek HD Audio output,0x00200000,1,1,ksproxy.ax,6.01.7600.16385

Realtek HDA SPDIF RCA Out,0x00200000,1,1,ksproxy.ax,6.01.7600.16385

Realtek HDA SPDIF Out,0x00200000,1,1,ksproxy.ax,6.01.7600.16385

 

BDA Network Providers:

Microsoft ATSC Network Provider,0x00200000,0,1,MSDvbNP.ax,6.06.7600.16385

Microsoft DVBC Network Provider,0x00200000,0,1,MSDvbNP.ax,6.06.7600.16385

Microsoft DVBS Network Provider,0x00200000,0,1,MSDvbNP.ax,6.06.7600.16385

Microsoft DVBT Network Provider,0x00200000,0,1,MSDvbNP.ax,6.06.7600.16385

Microsoft Network Provider,0x00200000,0,1,MSNP.ax,6.06.7600.16590

 

Multi-Instance Capable VBI Codecs:

VBI Codec,0x00600000,1,4,VBICodec.ax,6.06.7600.16385

 

BDA Transport Information Renderers:

BDA MPEG2 Transport Information Filter,0x00600000,2,0,psisrndr.ax,6.06.7600.16385

MPEG-2 Sections and Tables,0x00600000,1,0,Mpeg2Data.ax,6.06.7600.16385

 

BDA CP/CA Filters:

Decrypt/Tag,0x00600000,1,1,EncDec.dll,6.06.7600.16385

Encrypt/Tag,0x00200000,0,0,EncDec.dll,6.06.7600.16385

PTFilter,0x00200000,0,0,EncDec.dll,6.06.7600.16385

XDS Codec,0x00200000,0,0,EncDec.dll,6.06.7600.16385

 

WDM Streaming Communication Transforms:

Tee/Sink-to-Sink Converter,0x00200000,1,1,ksproxy.ax,6.01.7600.16385

 

Audio Renderers:

Speakers (Realtek High Definiti,0x00200000,1,0,quartz.dll,6.06.7600.16490

Default DirectSound Device,0x00800000,1,0,quartz.dll,6.06.7600.16490

Default WaveOut Device,0x00200000,1,0,quartz.dll,6.06.7600.16490

DirectSound: Realtek Digital Output (Realtek High Definition Audio),0x00200000,1,0,quartz.dll,6.06.7600.16490

DirectSound: Realtek Digital Output(RCA) (Realtek High Definition Audio),0x00200000,1,0,quartz.dll,6.06.7600.16490

DirectSound: Speakers (Realtek High Definition Audio),0x00200000,1,0,quartz.dll,6.06.7600.16490

Realtek Digital Output (Realtek,0x00200000,1,0,quartz.dll,6.06.7600.16490

Realtek Digital Output(RCA) (Re,0x00200000,1,0,quartz.dll,6.06.7600.16490

 

---------------

EVR Power Information

---------------

Current Setting: {5C67A112-A4C9-483F-B4A7-1D473BECAFDC} (Quality)

Quality Flags: 2576

Enabled:

Force throttling

Allow half deinterlace

Allow scaling

Decode Power Usage: 100

Balanced Flags: 1424

Enabled:

Force throttling

Allow batching

Force half deinterlace

Force scaling

Decode Power Usage: 50

PowerFlags: 1424

Enabled:

Force throttling

Allow batching

Force half deinterlace

Force scaling

Decode Power Usage: 0

Link to comment
Share on other sites

What can happen is that if the CPU cannot feed pixels to the dual cards fast enough one will go to low power mode. The other card will do a lot of work and then once in a while the slow card will be tasked with drawing a frame, but since it takes a little bit to power up from power saving the frames take a little while to render. This means that things run a quite smooth and then the frame rate drops a for a second before climbing back up. This mostly affects dual ATI cards with recent version of the powersaving software in their drivers. Not likely to be your problem but something to keep at the back of your mind (just in case Nvidia has the same problem in SLI).

 

Progressive loading of a scene causes some stutter and initially low-res tectures etc when you're first in the cockpit. After a few seconds it should be ok though. Is your disk drive fast enough to stream the high-res textures when needed? Again, maybe not your problem but something to test and eliminate as a possible source of problems.

 

Are you rendering a lot of frames in advance? I forget the setting but some drivers anticipate scenes. At high frame rates humans perceive the smoothness more than any slight positional accuracy so this technique can be useful. However, it means you multiply the number of frames rendered by the card by a factor of 3 or 4.

 

Also, have you tried turning your anti-aliasing and anisotropic filtering down to the minimal level. These re-render the scene several times (although the real effort is usually determining which polygons in the world are visible scene and projecting them, while converting the polygons to pixels and lighting them is not usually as expensive, so this may not make much of a difference).

 

Note that LockOn can only use 1 core for the game and an additional core for sound. So having four cores only helps in that any other processes your have can run on cores 3 & 4 (maybe). Otherwise the quad core doesn't make any different to LockOn compared to a dual core. Arma2, however, will love all your cores (and hopefully DCS:A-10C might find some way of using another core, but then, maybe not).

 

This means your CPU upgrade is going from 2.4 GHz to 2.66 GHz, an 11% increase in clockspeed if we disregard any CPU architecture effects (which might bump it up a bit more). That might not be enough to fully utilize your pair of graphics cards with LockOn (although your other games will go faster).

 

Clearly something else is going on as even if you don't expect to get very much faster you certainly don't expect to get a lot slower (although perhaps you now have everything at 'max', which is expensive for clouds, water, and viewing distance).

 

What speed is your RAM running at? This can make a big difference to LockOn.

Link to comment
Share on other sites

What can happen is that if the CPU cannot feed pixels to the dual cards fast enough one will go to low power mode. The other card will do a lot of work and then once in a while the slow card will be tasked with drawing a frame, but since it takes a little bit to power up from power saving the frames take a little while to render. This means that things run a quite smooth and then the frame rate drops a for a second before climbing back up. This mostly affects dual ATI cards with recent version of the powersaving software in their drivers. Not likely to be your problem but something to keep at the back of your mind (just in case Nvidia has the same problem in SLI).

 

Progressive loading of a scene causes some stutter and initially low-res tectures etc when you're first in the cockpit. After a few seconds it should be ok though. Is your disk drive fast enough to stream the high-res textures when needed? Again, maybe not your problem but something to test and eliminate as a possible source of problems.

 

Are you rendering a lot of frames in advance? I forget the setting but some drivers anticipate scenes. At high frame rates humans perceive the smoothness more than any slight positional accuracy so this technique can be useful. However, it means you multiply the number of frames rendered by the card by a factor of 3 or 4.

 

Also, have you tried turning your anti-aliasing and anisotropic filtering down to the minimal level. These re-render the scene several times (although the real effort is usually determining which polygons in the world are visible scene and projecting them, while converting the polygons to pixels and lighting them is not usually as expensive, so this may not make much of a difference).

 

Note that LockOn can only use 1 core for the game and an additional core for sound. So having four cores only helps in that any other processes your have can run on cores 3 & 4 (maybe). Otherwise the quad core doesn't make any different to LockOn compared to a dual core. Arma2, however, will love all your cores (and hopefully DCS:A-10C might find some way of using another core, but then, maybe not).

 

This means your CPU upgrade is going from 2.4 GHz to 2.66 GHz, an 11% increase in clockspeed if we disregard any CPU architecture effects (which might bump it up a bit more). That might not be enough to fully utilize your pair of graphics cards with LockOn (although your other games will go faster).

 

Clearly something else is going on as even if you don't expect to get very much faster you certainly don't expect to get a lot slower (although perhaps you now have everything at 'max', which is expensive for clouds, water, and viewing distance).

 

What speed is your RAM running at? This can make a big difference to LockOn.

 

Thanks for all the great suggestions. I wil put them to test tonight. I do remember seeing the advanced frame rendering set to 3, should I change that to a lower number and if so what?

 

My hard drive is new and working great, but will test speed just in case. I will also look into fixing my FSB:DRAM ratio as it is currently an odd division, 10:11. currently using 2 sets of 4gigs of corsair but with different timing. one is 5-5-5-18 and other is 4-4-4-12. I will take one of the 4gig chips out for testing. you think that could be it?

 

Also enabled fps info in game, so take the F15 weapons and missile practice mission, when the game loads in I'm sitting in cockpit on runway with engine running to my left are a bunch of parked F15's and buildings/forest. So only when I look at that area I drop to 11 fps, when I'm looking any where else in cockpit I get 192 fps. When I'm flying I get between 110 to 42 fps, when I start landing and get close to the ground looking at it it can again drop to 18fps. I don't get it.

 

I even clocked my system up since i have good hardware to 3ghz and still the same thing with the fps drops.

 

I will try with new ram since u pointed that out. Ram can effect the game that much? will let you know after the next set of tests.

 

other than that I cant complain that much , game is very playable just like to have things perfect and without massive fps drop when only looking at a little bit of geometry in certain parts of the game.

Link to comment
Share on other sites

Personally I am a bit skeptical to RAM speed specifically being a culprit - in DCS:BS I ran some tests with my RAM clocked at 800MHz and then overclocked (and overvolted) to 1092MHz, and found no statistically certain change in performance. I haven't run this test in FC2 though but I would expect the situation to be similar.

 

However, having two sets of RAM with different timings installed looks weird. I've never tried that since my philosophy on RAM has always been to never use a dissimilar setup, in order to reduce the risk of issues. Last time I had a dissimlar RAM setup it did cause strange issues in the computer, but that was a long time ago and therefore might not translate to capabilities of newer chipsets. (A Pentium 75MHz that was upgraded from 8MB RAM to a blisteringly huge 24MB :D )

[sIGPIC][/sIGPIC]

Daniel "EtherealN" Agorander | Даниэль "эфирныйн" Агорандер

Intel i7 2600K @ 4.4GHz, ASUS Sabertooth P67, 8GB Corsair Vengeance @ 1600MHz, ASUS GTX 560Ti DirectCU II 1GB, Samsung 830series 512GB SSD, Corsair AX850w, two BENQ screens and TM HOTAS Warthog

DCS: A-10C Warthog FAQ | DCS: P-51D FAQ | Remember to read the Forum Rules |

|
| Life of a Game Tester
Link to comment
Share on other sites

to echo the last post, I have just updated my own system and the one thing that was looked hard at by the people who build my systems was to insure that I had identical sets of ram even to the point from the same company.So this may very well be your issue. cheers hope you get it sorted out.:thumbup:

Link to comment
Share on other sites

Personally I am a bit skeptical to RAM speed specifically being a culprit - in DCS:BS I ran some tests with my RAM clocked at 800MHz and then overclocked (and overvolted) to 1092MHz, and found no statistically certain change in performance. I haven't run this test in FC2 though but I would expect the situation to be similar.

 

However, having two sets of RAM with different timings installed looks weird. I've never tried that since my philosophy on RAM has always been to never use a dissimilar setup, in order to reduce the risk of issues. Last time I had a dissimlar RAM setup it did cause strange issues in the computer, but that was a long time ago and therefore might not translate to capabilities of newer chipsets. (A Pentium 75MHz that was upgraded from 8MB RAM to a blisteringly huge 24MB :D )

 

It's not the ram, I just checked, both sets are Corsair xms2 ddr2 800mhz and both with same timing 5-5-5-18 the only thing thats different is the version number, on set is 1.3 and the other is 1.4 but I dont see that being it. However I will try to run only using one set of 4gigs.

 

Still, would you say that its normal to have only 12fps sitting on runway looking out cockpit at other parked planes, while getting 90+fps flying or looking at other places with less geometry? Considering I have quad core now running at 3ghz with 8gigs of ram and a new 465 GTX with a gig of video memory that game should not dip to 12fps on the ground not moving but just looking out the cockpit?

Link to comment
Share on other sites

First of all, no, I wouldn't say that it's normal. I get several times better results from my machine when running at stock speeds (I always run at stock in testing scenarios, to eliminate such issues from my reporting). Do note however that quad-core is a bit beside the point, since the application runs in two threads only. (In fact, there are less games on the market than you may think that actually make full use of all cores in a 4-core machine - the engineering issues in this are quite huge, and while some games may claim to use all, they'll not saturate all of them.)

 

Basically, something is very weird here. I'll have to think about it for a bit to see if I can come up with something.

[sIGPIC][/sIGPIC]

Daniel "EtherealN" Agorander | Даниэль "эфирныйн" Агорандер

Intel i7 2600K @ 4.4GHz, ASUS Sabertooth P67, 8GB Corsair Vengeance @ 1600MHz, ASUS GTX 560Ti DirectCU II 1GB, Samsung 830series 512GB SSD, Corsair AX850w, two BENQ screens and TM HOTAS Warthog

DCS: A-10C Warthog FAQ | DCS: P-51D FAQ | Remember to read the Forum Rules |

|
| Life of a Game Tester
Link to comment
Share on other sites

Got the exact same issue on a ati 5770 system with a q6600 so its not nvidia spesific.

 

Eyefinity 3240x1920 or 1920x1080 yield the same frame rates

 

Has been tested on Stock and 3.4ghz .

 

Added Dxdiag

1080 ti, i7700k 5ghz, 16gb 3600 cl14 ddr4 oc

Link to comment
Share on other sites

First of all, no, I wouldn't say that it's normal. I get several times better results from my machine when running at stock speeds (I always run at stock in testing scenarios, to eliminate such issues from my reporting). Do note however that quad-core is a bit beside the point, since the application runs in two threads only. (In fact, there are less games on the market than you may think that actually make full use of all cores in a 4-core machine - the engineering issues in this are quite huge, and while some games may claim to use all, they'll not saturate all of them.)

 

Basically, something is very weird here. I'll have to think about it for a bit to see if I can come up with something.

 

That's the reason why I decided to purchase a E8500 instead of going Quad. I'm not sold on the platform yet and most of my games are older so Quad would not help those.

 

EtherealN, you made an interesting comment that you get better results running STOCK and not overclocking. Can you elaborate? I thought the opposite would be true.

Link to comment
Share on other sites

Well I will chime in a little here. If you guys a using WIN 7. The new updates on 7 ar killing ED games for some reason. So a few of the guys in the my groop have moved back to pree update and have regained performance lost. I have ben hitting 8FPS and didn't know why.

Home built PC Win 10 Pro 64bit, MB ASUS Z170 WS, 6700K, EVGA 1080Ti Hybrid, 32GB DDR4 3200, Thermaltake 120x360 RAD, Custom built A-10C sim pit, TM WARTHOG HOTAS, Cougar MFD's, 3D printed UFC and Saitek rudders. HTC VIVE VR.

 

https://digitalcombatmercenaries.enjin.com/

Link to comment
Share on other sites

Im a happy Q9550 user, so whatever the problem is I doubt its because of 4 cores.

[sigpic]http://forums.eagle.ru/signaturepics/sigpic4448_29.gif[/sigpic]

My PC specs below:

Case: Corsair 400C

PSU: SEASONIC SS-760XP2 760W Platinum

CPU: AMD RYZEN 3900X (12C/24T)

RAM: 32 GB 4266Mhz (two 2x8 kits) of trident Z RGB @3600Mhz CL 14 CR=1T

MOBO: ASUS CROSSHAIR HERO VI AM4

GFX: GTX 1080Ti MSI Gaming X

Cooler: NXZT Kraken X62 280mm AIO

Storage: Samsung 960 EVO 1TB M.2+6GB WD 6Gb red

HOTAS: Thrustmaster Warthog + CH pro pedals

Monitor: Gigabyte AORUS AD27QD Freesync HDR400 1440P

 

Link to comment
Share on other sites

EtherealN, you made an interesting comment that you get better results running STOCK and not overclocking. Can you elaborate? I thought the opposite would be true.

 

Sorry, I might have confused the language a bit in my post: what I meant was that I get several times better results than the OP even without my overclock. (I stated that so that he wouldn't look at my signature and deduce that it is caused by my overclock.)

 

Obviously, overclocking my machine does give almost linear improvements in my FPS, but even without overclock there are only very rare (and usually antivirus-induced :P ) circumstances where my FPS goes even close to what he has been experiencing.

[sIGPIC][/sIGPIC]

Daniel "EtherealN" Agorander | Даниэль "эфирныйн" Агорандер

Intel i7 2600K @ 4.4GHz, ASUS Sabertooth P67, 8GB Corsair Vengeance @ 1600MHz, ASUS GTX 560Ti DirectCU II 1GB, Samsung 830series 512GB SSD, Corsair AX850w, two BENQ screens and TM HOTAS Warthog

DCS: A-10C Warthog FAQ | DCS: P-51D FAQ | Remember to read the Forum Rules |

|
| Life of a Game Tester
Link to comment
Share on other sites

Well I will chime in a little here. If you guys a using WIN 7. The new updates on 7 ar killing ED games for some reason. So a few of the guys in the my groop have moved back to pree update and have regained performance lost. I have ben hitting 8FPS and didn't know why.

 

Wow, that sounds interesting because I usually hate updates and don't do them but with this rig and win 7 64 I have been keeping up with all updates.

 

I wouldn't be surprised if that caused this odd frame lag in certain view angles.

 

Will setup a new windows on a separate drive in the next few days and test this out CAT.

 

Anyone think it might even be a good idea to try say windows xp 64bit or 32bit. I was really happy to leave xp 64 behind as I was having lots of problems with opengl and photoshop CS4+ due to microsoft no longer supporting it on xp 64.

Link to comment
Share on other sites

1-Have you changed the motherboard? or just the cpu and graphic card?

 

2-Is this the same Win7 that you where running with the old hardware or a new clean/formated one?

 

3-Are you using the same settings in the nvidia control panel? presets or customized?

 

 

BTW Capsilus, Vista and W7 are like 30-50% faster than XP for DCS/FC2.

AMD Ryzen 1400 // 16 GB DDR4 2933Mhz // Nvidia 1060 6GB // W10 64bit // Microsoft Sidewinder Precision 2

Link to comment
Share on other sites

1-Have you changed the motherboard? or just the cpu and graphic card?

 

2-Is this the same Win7 that you where running with the old hardware or a new clean/formated one?

 

3-Are you using the same settings in the nvidia control panel? presets or customized?

 

 

BTW Capsilus, Vista and W7 are like 30-50% faster than XP for DCS/FC2.

 

Motherboard did not change. only cpu and video card. I did a fresh install on format.

 

Regarding Nvidia Setting in the control panel I'm not sure if I'm using the same settings. I did try just about every option in there a few days back, trying to find the culprit.

 

What are good settings under the nvidia control panel for LOMAC FC2?

 

Also have a 2ndd system with win 7 64 with another quad core, asus motherboard and 2x 8800 GTX's in sli, I had the same frame drop issue as on my main system. Both systems play other games well, and only have this isolated problem in FC2 when looking at a certain area. I was doing some more testing last night and I was getting better game play online both on the 104th server and a few others.

Link to comment
Share on other sites

  • 2 weeks later...

Ok, I have tried just about everything, even reinstalled directly to root as some people were suggesting. I tried all the graphic options and even installed the new win7 dtx11 booster patch from microsoft and nothing.

 

Even if I run the game with everything turned down it still falls to the 10fps when looking out the cockpit at airport with parked f15s.

 

If I run the graphics maxed I get really nice frame rates (60+) say when looking at the sky or in different direction other than the sweet spot where the fps drops to 10 or even below.

 

The one thing I did notice that as soon as I went online to multiplayer the game was perfect. Parked in cockpit view I got steady 80+ fps looking at anything without the shutter / fps drop that I get on single player missions. I really want to figure this out. I'm ready to buy an i7 960 with tri band memory but if it's still going to give me the same problem I'm not sure it's worth it.

Link to comment
Share on other sites

try change bios settings sometimes the cpu throttles so switch ths underlockin option off.

 

I am running e8400 on3,6ghz and its silky smooth on highet settings.

 

so maybe bios is the problem ,maybe temperature of cpu.

[sigpic][/sigpic]

MB MSI x570 Prestige Creation, RYzen 9 3900X, 32 Gb Ram 3333MHz, cooler Dark rock PRO 4, eVGA 1080Ti, 32 inch BenQ 32011pt, saitek X52Pro, HP Reverb, win 10 64bit

Link to comment
Share on other sites

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...