Aces High Bulletin Board
General Forums => Hardware and Software => Topic started by: MaineX on March 20, 2017, 03:09:01 PM
-
So here I am again... Started flying AW back in DOS days. Also flew AW2 and AW3. Then
I stopped flying altogether and now after +10 years not flying i'm thinking of coming back.
My current system:
Ahtlon 5350 (Integrated graphics)
RAM: 8 GB
The rest of specs the usual.
I'm on a loooow budget and I'm thinking of getting the GTX 750 Ti 2GB. I know I have a sh**y CPU
for gaming (for the rest is decent) and I don't want to spend money on new CPU+MB. So, is that
combo (Athlon 5350 + GTX 750 Ti) any good? I'm not looking for 100 fps, just enough to play... :)
Anyone have a similar system? I've seen many videos on YouTube of that combo and it seems to work
OK for other games (CoD, Battlefield, etc) but haven't seen a thing AH3 related.
Thanks in advance!
My callsign back in the days was -MX- {Shillelagh} :airplane: :old:
<S>!
-
So here I am again... Started flying AW back in DOS days. Also flew AW2 and AW3. Then
I stopped flying altogether and now after +10 years not flying i'm thinking of coming back.
My current system:
Ahtlon 5350 (Integrated graphics)
RAM: 8 GB
The rest of specs the usual.
I'm on a loooow budget and I'm thinking of getting the GTX 750 Ti 2GB. I know I have a sh**y CPU
for gaming (for the rest is decent) and I don't want to spend money on new CPU+MB. So, is that
combo (Athlon 5350 + GTX 750 Ti) any good? I'm not looking for 100 fps, just enough to play... :)
Anyone have a similar system? I've seen many videos on YouTube of that combo and it seems to work
OK for other games (CoD, Battlefield, etc) but haven't seen a thing AH3 related.
Thanks in advance!
My callsign back in the days was -MX- {Shillelagh} :airplane: :old:
<S>!
Hi MaineX,
If you could post a dxdiag report of your computer that would help most folks in here to help you out as this report will give a listing of most of the installed components along w\ drivers in your system w\ exception of the size of the PSU being used in your system.
The PSU size will be the main determiner of the size of vid card upgrade your system can accept along w\ the rated power usage of the vid card upgrade so if you can give this info as well that would help.
:salute
-
I am running a 2gb 750ti (in an i5) and most of the time I am over 50fps. Very playable
-
Zardoz,
I was going to ask what CPU. I5 didnt see it. Doh... At what screen resolution? All settings to max?
-MX-
-
1080 and I have most settings at maximum. I think I have all the post lighting off.
-
Here are the results of my DxDiag report. It's kinda long...
------------------
System Information
------------------
Time of this report: 3/21/2017, 20:53:20
Machine name: RANDY
Operating System: Windows 7 Professional N 64-bit (6.1, Build 7601) Service Pack 1 (7601.win7sp1_gdr.150715-0600)
Language: Spanish (Regional Setting: Spanish)
System Manufacturer: ASUS
System Model: All Series
BIOS: BIOS Date: 03/13/14 10:13:33 Ver: 05.05
Processor: AMD Athlon(tm) 5350 APU with Radeon(tm) R3 (4 CPUs), ~2.0GHz
Memory: 8192MB RAM
Available OS Memory: 7616MB RAM
Page File: 1757MB used, 13475MB 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.7601.17514 64bit Unicode
------------
DxDiag Notes
------------
Display Tab 1: No problems found.
Sound Tab 1: 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: AMD Radeon HD 8400
Manufacturer: Advanced Micro Devices, Inc.
Chip type: AMD Radeon HD 8400 (0x9830)
DAC type: Internal DAC(400MHz)
Device Key: Enum\PCI\VEN_1002&DEV_9830&SUBSYS_86231043&REV_00
Display Memory: 4050 MB
Dedicated Memory: 497 MB
Shared Memory: 3552 MB
Current Mode: 1280 x 1024 (32 bit) (60Hz)
Monitor Name: Monitor PnP genérico
Monitor Model: L1718S
Monitor Id: GSM443C
Native Mode: 1280 x 1024(p) (60.020Hz)
Output Type: HD15
Driver Name: aticfx64.dll,aticfx64.dll,aticfx64.dll,aticfx32,aticfx32,aticfx32,atiumd64.dll,atidxx64.dll,atidxx64.dll,atiumdag,atidxx32,atidxx32,atiumdva,atiumd6a.cap,atitmm64.dll
Driver File Version: 8.17.0010.1267 (English)
Driver Version: 13.351.1001.0
DDI Version: 11
Driver Model: WDDM 1.1
Driver Attributes: Final Retail
Driver Date/Size: 2/15/2014 12:15:00, 1328328 bytes
WHQL Logo'd: n/a
WHQL Date Stamp: n/a
Device Identifier: {D7B71EE2-DB70-11CF-0077-29A6BEC2C535}
Vendor ID: 0x1002
Device ID: 0x9830
SubSys ID: 0x86231043
Revision ID: 0x0000
Driver Strong Name: oem2.inf:ATI.Mfg.NTamd64.6.1:ati2mtag_Kabini_Mobile:13.351.1001.0:pci\ven_1002&dev_9830
Rank Of Driver: 00E62001
Video Accel: ModeMPEG2_A ModeMPEG2_C ModeVC1_C ModeWMV9_C
Deinterlace Caps: {6E8329FF-B642-418B-BCF0-BCB6591E255F}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
{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_BOBVerticalSt retch
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY
{6E8329FF-B642-418B-BCF0-BCB6591E255F}: Format(In/Out)=(UYVY,UYVY) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
{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_BOBVerticalSt retch
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: 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)=(YV12,0x32315659) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{3C5323C1-6FB7-44F5-9081-056BF2EE449D}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,2) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
{552C0DAD-CCBC-420B-83C8-74943CF9F1A6}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,2) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
{6E8329FF-B642-418B-BCF0-BCB6591E255F}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
{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_BOBVerticalSt retch
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: 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)=(IMC1,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=
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC3,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=
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(S340,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=
D3D9 Overlay: Not Supported
DXVA-HD: Not Supported
DDraw Status: Enabled
D3D Status: Enabled
AGP Status: Enabled
---------------------------------------------------------------------------------------------------------------
It's a basic system: MB+CPU, 1 HDD, 8 GB 1600 Mhz DDR3 RAM, Windows 7 Pro 64 bits. No
graphics card as the graphics system goes within the CPU. An APU I think is called.
The PSU is 90W and yes, it runs and it does not crash! The case is an ANTEC ISK-110.
Most probably I'd also need to upgrade that as the GTX 750 Ti demands 60W. My current
CPU demands 25W. Would be running out of watts... LOL!
-MX-
-
--> 2nd part of dxdiag report
------------------------------------------------------------------------------------------
-------------
Sound Devices
-------------
Description: Altavoces (Realtek High Definition Audio)
Default Sound Playback: Yes
Default Voice Playback: Yes
Hardware ID: HDAUDIO\FUNC_01&VEN_10EC&DEV_0887&SUBSYS_10438576&REV_1003
Manufacturer ID: 1
Product ID: 100
Type: WDM
Driver Name: RTKVHD64.sys
Driver Version: 6.00.0001.7071 (English)
Driver Attributes: Final Retail
WHQL Logo'd: n/a
Date and Size: 10/22/2013 21:38:24, 3692632 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(tm) 2.0 Listen/Src: No, No
I3DL2(tm) Listen/Src: No, No
Sensaura(tm) ZoomFX(tm): No
---------------------
Sound Capture Devices
---------------------
-------------------
DirectInput Devices
-------------------
Device Name: Mouse
Attached: 1
Controller ID: n/a
Vendor/Product ID: n/a
FF Driver: n/a
Device Name: Teclado
Attached: 1
Controller ID: n/a
Vendor/Product ID: n/a
FF Driver: n/a
Poll w/ Interrupt: No
-----------
USB Devices
-----------
+ Concentrador raíz USB
| Vendor/Product ID: 0x1022, 0x7807
| Matching Device ID: usb\root_hub
| Service: usbhub
| Driver: usbhub.sys, 11/27/2013 02:41:37, 343040 bytes
| Driver: usbd.sys, 11/27/2013 02:41:03, 7808 bytes
----------------
Gameport Devices
----------------
------------
PS/2 Devices
------------
+ Teclado PS/2 estándar
| Matching Device ID: *pnp0303
| Service: i8042prt
| Driver: i8042prt.sys, 7/14/2009 00:19:57, 105472 bytes
| Driver: kbdclass.sys, 7/14/2009 02:48:04, 50768 bytes
|
+ Controlador de teclado de Terminal Server
| Matching Device ID: root\rdp_kbd
| Upper Filters: kbdclass
| Service: TermDD
| Driver: i8042prt.sys, 7/14/2009 00:19:57, 105472 bytes
| Driver: kbdclass.sys, 7/14/2009 02:48:04, 50768 bytes
|
+ Mouse PS/2 de Microsoft
| Matching Device ID: *pnp0f03
| Service: i8042prt
| Driver: i8042prt.sys, 7/14/2009 00:19:57, 105472 bytes
| Driver: mouclass.sys, 7/14/2009 02:48:27, 49216 bytes
|
+ Controlador de mouse de Terminal Server
| Matching Device ID: root\rdp_mou
| Upper Filters: mouclass
| Service: TermDD
| Driver: termdd.sys, 11/21/2010 04:24:15, 63360 bytes
| Driver: sermouse.sys, 7/14/2009 01:00:20, 26624 bytes
| Driver: mouclass.sys, 7/14/2009 02:48:27, 49216 bytes
------------------------
Disk & DVD/CD-ROM Drives
------------------------
Drive: C:
Free Space: 133.9 GB
Total Space: 476.8 GB
File System: NTFS
Model: WDC WD50 00BPKX-00HPJT0 SATA Disk Device
-
There is more stuff, but it's just too long. If you need that info I'll post it as well. What is left
is: System Devices (really long, exceeds the 12.000 characters) DirectShow Filters, and EVR
Power Information.
-MX-
-
Was that done after a fresh reboot before you ran any other applications?
-
Kinda. At the moment there was Excel and Android Studio open. Should repeat it after a
fresh boot?
-MX-
-
It would help, as the page file usage in this report is way too high.
-
Here it goes. It went down a bit but I must admit I'm surprised myself as well. The only things that
I'm aware of run at boot are the Catalyst Control Center, Java Update Scheduler, and I can see an
application Lenovo Service Bridge. It allows Android Studio install apps on a Lenovo tablet I have. Oh,
and the RealTek audio manager. The rest is the usual stuff: Windows Explorer, Task Manager, etc.
From what I know swap file is only used if the physical memory is all used up.
In the report says that 576 MB of the physical RAM are being used. How come
if there are still 7.616MB left, the swap file is being used (968MB)?
-MX-
-
------------------
System Information
------------------
Time of this report: 3/21/2017, 21:37:32
Machine name: RANDY
Operating System: Windows 7 Professional N 64-bit (6.1, Build 7601) Service Pack 1 (7601.win7sp1_gdr.150715-0600)
Language: Spanish (Regional Setting: Spanish)
System Manufacturer: ASUS
System Model: All Series
BIOS: BIOS Date: 03/13/14 10:13:33 Ver: 05.05
Processor: AMD Athlon(tm) 5350 APU with Radeon(tm) R3 (4 CPUs), ~2.0GHz
Memory: 8192MB RAM
Available OS Memory: 7616MB RAM
Page File: 968MB used, 14264MB 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.7601.17514 64bit Unicode
------------
DxDiag Notes
------------
Display Tab 1: No problems found.
Sound Tab 1: 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: AMD Radeon HD 8400
Manufacturer: Advanced Micro Devices, Inc.
Chip type: AMD Radeon HD 8400 (0x9830)
DAC type: Internal DAC(400MHz)
Device Key: Enum\PCI\VEN_1002&DEV_9830&SUBSYS_86231043&REV_00
Display Memory: 4050 MB
Dedicated Memory: 497 MB
Shared Memory: 3552 MB
Current Mode: 1280 x 1024 (32 bit) (60Hz)
Monitor Name: Monitor PnP genérico
Monitor Model: L1718S
Monitor Id: GSM443C
Native Mode: 1280 x 1024(p) (60.020Hz)
Output Type: HD15
Driver Name: aticfx64.dll,aticfx64.dll,aticfx64.dll,aticfx32,aticfx32,aticfx32,atiumd64.dll,atidxx64.dll,atidxx64.dll,atiumdag,atidxx32,atidxx32,atiumdva,atiumd6a.cap,atitmm64.dll
Driver File Version: 8.17.0010.1267 (English)
Driver Version: 13.351.1001.0
DDI Version: 11
Driver Model: WDDM 1.1
Driver Attributes: Final Retail
Driver Date/Size: 2/15/2014 12:15:00, 1328328 bytes
WHQL Logo'd: n/a
WHQL Date Stamp: n/a
Device Identifier: {D7B71EE2-DB70-11CF-0077-29A6BEC2C535}
Vendor ID: 0x1002
Device ID: 0x9830
SubSys ID: 0x86231043
Revision ID: 0x0000
Driver Strong Name: oem2.inf:ATI.Mfg.NTamd64.6.1:ati2mtag_Kabini_Mobile:13.351.1001.0:pci\ven_1002&dev_9830
Rank Of Driver: 00E62001
Video Accel: ModeMPEG2_A ModeMPEG2_C ModeVC1_C ModeWMV9_C
Deinterlace Caps: {6E8329FF-B642-418B-BCF0-BCB6591E255F}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
{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_BOBVerticalSt retch
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY
{6E8329FF-B642-418B-BCF0-BCB6591E255F}: Format(In/Out)=(UYVY,UYVY) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
{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_BOBVerticalSt retch
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: 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)=(YV12,0x32315659) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{3C5323C1-6FB7-44F5-9081-056BF2EE449D}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,2) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
{552C0DAD-CCBC-420B-83C8-74943CF9F1A6}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,2) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
{6E8329FF-B642-418B-BCF0-BCB6591E255F}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
{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_BOBVerticalSt retch
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: 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)=(IMC1,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=
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC3,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=
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(S340,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=
D3D9 Overlay: Not Supported
DXVA-HD: Not Supported
DDraw Status: Enabled
D3D Status: Enabled
AGP Status: Enabled
-------------
Sound Devices
-------------
Description: Altavoces (Realtek High Definition Audio)
Default Sound Playback: Yes
Default Voice Playback: Yes
Hardware ID: HDAUDIO\FUNC_01&VEN_10EC&DEV_0887&SUBSYS_10438576&REV_1003
Manufacturer ID: 1
Product ID: 100
Type: WDM
Driver Name: RTKVHD64.sys
Driver Version: 6.00.0001.7071 (English)
Driver Attributes: Final Retail
WHQL Logo'd: n/a
Date and Size: 10/22/2013 21:38:24, 3692632 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(tm) 2.0 Listen/Src: No, No
I3DL2(tm) Listen/Src: No, No
Sensaura(tm) ZoomFX(tm): No
---------------------
Sound Capture Devices
---------------------
-------------------
DirectInput Devices
-------------------
Device Name: Mouse
Attached: 1
Controller ID: n/a
Vendor/Product ID: n/a
FF Driver: n/a
Device Name: Teclado
Attached: 1
Controller ID: n/a
Vendor/Product ID: n/a
FF Driver: n/a
Poll w/ Interrupt: No
-----------
USB Devices
-----------
+ Concentrador raíz USB
| Vendor/Product ID: 0x1022, 0x7807
| Matching Device ID: usb\root_hub
| Service: usbhub
| Driver: usbhub.sys, 11/27/2013 02:41:37, 343040 bytes
| Driver: usbd.sys, 11/27/2013 02:41:03, 7808 bytes
----------------
Gameport Devices
----------------
------------
PS/2 Devices
------------
+ Teclado PS/2 estándar
| Matching Device ID: *pnp0303
| Service: i8042prt
| Driver: i8042prt.sys, 7/14/2009 00:19:57, 105472 bytes
| Driver: kbdclass.sys, 7/14/2009 02:48:04, 50768 bytes
|
+ Controlador de teclado de Terminal Server
| Matching Device ID: root\rdp_kbd
| Upper Filters: kbdclass
| Service: TermDD
| Driver: i8042prt.sys, 7/14/2009 00:19:57, 105472 bytes
| Driver: kbdclass.sys, 7/14/2009 02:48:04, 50768 bytes
|
+ Mouse PS/2 de Microsoft
| Matching Device ID: *pnp0f03
| Service: i8042prt
| Driver: i8042prt.sys, 7/14/2009 00:19:57, 105472 bytes
| Driver: mouclass.sys, 7/14/2009 02:48:27, 49216 bytes
|
+ Controlador de mouse de Terminal Server
| Matching Device ID: root\rdp_mou
| Upper Filters: mouclass
| Service: TermDD
| Driver: termdd.sys, 11/21/2010 04:24:15, 63360 bytes
| Driver: sermouse.sys, 7/14/2009 01:00:20, 26624 bytes
| Driver: mouclass.sys, 7/14/2009 02:48:27, 49216 bytes
------------------------
Disk & DVD/CD-ROM Drives
------------------------
Drive: C:
Free Space: 133.6 GB
Total Space: 476.8 GB
File System: NTFS
Model: WDC WD50 00BPKX-00HPJT0 SATA Disk Device
-
From what I know swap file is only used if the physical memory is all used up.
In the report says that 576 MB of the physical RAM are being used. How come
if there are still 7.616MB left, the swap file is being used (968MB)?
By default it's not actually so and changing that behaviour may cause instability issues. Now someone may jump up and say he's done it without any problems, but then again there's people who have successfully jumped out of a plane without a parachute...
Windows likes to keep the RAM relatively clean for future needs, so it puts less needed data into the swap file. Since you've just started your computer, the swapped data is most likely files that were used at startup but won't/shouldn't be active until next start. Windows is still keeping them at hand just in case.
-
If you run the "Superfetch" service it will fill system RAM with all the programs Windows thinks you are going to try and run. A lot of that ends up in the swap file, along with sleeping processes.
-
Pagefile use in dxdiag is actually virtual memory use, that is physical memory + the emulation in swapfile (AKA Page file).
To upgrade your system I'd look for a 1050 non-TI, although it's said to have 75W TDP it's often limited to 70W or below by driver.
The 750TI is know to exceed it's 60W TDP quite often, some are even so badly designed to take more than 75W despite having no additional power connector.
-
Still though, your pagefile used after a fresh re-boot is right near the sweet spot between 900 to 750 or so MBs used for Windows 7 64 bit install.... you could try and do some minor tweaks to get it lower...but I don't think it's bad....
In AH2 that CPU might of had a struggle, but AH3 is more GPU , so you probably will be okay, if not wanting Max fps isn't an issue...
Hope this helps
Welcome back ya Shill!
TC
-
Pagefile use in dxdiag is actually virtual memory use, that is physical memory + the emulation in swapfile (AKA Page file).<snip>
The total page file space available is the amount of disk space allocated for the physical page file/swap space, plus the total amount of free system RAM.
The amount used is how much of the disk space is being used in the page file/swap space. For Windows 10 it also includes any memory which has been compressed to save space in physical RAM.
You can use the terms "virtual memory" and "page file" interchangeably but I find it causes less confusion if you use "page file" for the virtual swap space on the disk.
-
There is more stuff, but it's just too long. If you need that info I'll post it as well. What is left
is: System Devices (really long, exceeds the 12.000 characters) DirectShow Filters, and EVR
Power Information.
-MX-
Hi MaineX,
I've looked up the APU that you have & it appears to be a FM2 socket APU, is this correct? Or is it a FM2+ socket?
If it is a FM2+ socket there is another avenue that you might consider to take.
If FM2+ socket mobo you might consider to upgrade the APU to an AMD A10 7870K APU for a little more than just a vid card upgrade and get a 2-for-1 upgrade by upgrading both the CPU\GPU.
This AMD APU has been tested & shown in reviews to be able to run the latest AAA titles at a decent frame rate around 25-35 FPS w\ fairly high graphics settings @ 1920 x 1080 res but when settings were lowered it got up to the low 40-50 FPS range.
This APU uses around 95W..............
Just another thought to throw in.........but it depends on the mobo having a FM2+ socket.
FYI..........................
:salute
-
Pudgie,
Athlon 5350 is an AM1 socket CPU. With that sockets all I can upgrade to is a 5370. I think that would represent a 7% increase in performance. Hot worth the price?
-
http://dealnews.com/c113/Computers/Upgrades-Components/Video-Cards/
-
--- I think that would represent a 7% increase in performance. Hot worth the price?
Studies reveal that a regular user won't notice changes in performance less than about 20%. An old rule of thumb tells to at least double the performance level for a truly enjoyable improvement.
-
thaT CPU is a short lived AM1 socket , only like 4 speeds where produced. 2.2ghz being the highest you can upgrade too, i actually have one i used for my daughters computer as its low power and does HD very well..
-
Ok,
So I'm back. I've tested the Athlon 5330, 8GB DDR3 RAM and GTX 750 Ti on a fresh Win7-64bits install.
All I had was and old sata 2 HDD, but oh well... Notice the ASUS AM1I-A is an ITX board with only 1 PCIe 2.0
4x slot.
I got 40 fps during offline flying. 1280x1024 with max texture size of 2048. I know that there are more
settings than can changed so to increase fps. 40 fps might be ok for offline flying but once in real air battle
my guess is those fps will go down considerably.
So my question is, What settings and in which order I should change them so as to test which configuration gives me
best fps.
Thanks,
-MX- :airplane: :old:
-
I have a 750 Ti. I get 60 fps most of the time with default settings except for the environment map slider set to none and reflections and shadows set off.
If that doesn't do it for you, try setting your texture size to 1024 or even 512.
-
Yes, the Environment Map is the biggest resource hogs. After that, disable post lighting effects like bloom and lens glare, they're mostly good for filming.
-
Shadows and reflections are also expensive graphic options.