Jump to content

silverliu

Members
  • Posts

    17
  • Joined

  • Last visited

Everything posted by silverliu

  1. Yes, the video card need update.
  2. Thanks buddy! I guess i need more economy resource to buy new PC.:thumbup:
  3. Is it so Hi-Fi to PC or is it so low efficient code both net code and 3D model code and calc code ?
  4. ridiculous, BuGs, leak responsible.
  5. If the whole problem is my system and internet connection condition,why while play with the IL2 1946,the error ever happen? I would mention the lock on's competitor which also have gorgeous image and wonderful multiplayer experience. Thanks everyone help me find the truth!:thumbup: Perhaps lock on suitable for 2020 year 's my Sys to play!:(
  6. Yes! The install interface also use the 1.12A with the 1.12 B !
  7. Great ED 's 1.12B patch could download , But the interface also with 1.12A :thumbup: :helpsmilie: :joystick: MY Alam MY God MY ED!
  8. Thanks ALL, the total problem is if I can afford it. every years the high-end Pc will be sell on market with $3000 or $ 4000 price level.:music_whistling: but in the 2007, u also can't play the max setting with Lock on. :( economy resource, FS2004, FSX.
  9. Ok, $3500 'pc, high-end PC.
  10. Thanks for U advise!:)
  11. $1000 ' Pc or $1500' PC , envy U! But every year there alway High-end PC, Lock on should consider from which year ,i mean the lower PC 's system.
  12. May i know U system ?
  13. the whole Dxdiag.txt Jumping A-10 during internet game. A-10 could be dancing,but the IL2 never happen. Dear diveplane Thank your for understand my feeling,cause i spent lots of time in Flanker &Lock on, i expect ED could be the king of market. If the ED 's software need the high_end pc require,the sales would not make people satisfly. I mean the Blizzard 's product could run smoothly in lot of people 'pc, stable & high FPS & wonderfull image with the time! I dont' have enough resource to use high-end PC, perhaps after 10 year that want i use computer could run 2007' lock on better....... DxDiag.txt
  14. ------------------ System Information ------------------ Time of this report: 4/30/2007, 10:55:07 Machine name: ## Operating System: Windows XP Professional (5.1, Build 2600) Service Pack 2 (2600.xpsp_sp2_gdr.070227-2254) Language: Chinese (Regional Setting: Chinese) System Manufacturer: MICRO-STAR INTERNATIONAL CO., LTD System Model: MS-7102 BIOS: Phoenix - AwardBIOS v6.00PG Processor: AMD Sempron Processor 2600+, MMX, 3DNow, ~1.6GHz Memory: 512MB RAM Page File: 329MB used, 1174MB available Windows Dir: C:\WINDOWS DirectX Version: DirectX 9.0c (4.09.0000.0904) DX Setup Parameters: Not found DxDiag Version: 5.03.2600.2180 32bit Unicode ------------ DxDiag Notes ------------ DirectX Files Tab: No problems found. Display Tab 1: No problems found. Sound Tab 1: No problems found. Music Tab: No problems found. Input Tab: No problems found. Network Tab: No problems found. -------------------- DirectX Debug Levels -------------------- Direct3D: 0/4 (n/a) DirectDraw: 0/4 (retail) DirectInput: 0/5 (n/a) DirectMusic: 0/5 (n/a) DirectPlay: 0/9 (retail) DirectSound: 0/5 (retail) DirectShow: 0/6 (retail) --------------- Display Devices --------------- Card name: NVIDIA GeForce FX 5200 Manufacturer: NVIDIA Chip type: GeForce FX 5200 DAC type: Integrated RAMDAC Device Key: Enum\PCI\VEN_10DE&DEV_0322&SUBSYS_33601642&REV_A1 Display Memory: 128.0 MB Current Mode: 1024 x 768 (32 bit) (85Hz) Monitor: Monitor Max Res: 1600,1200 Driver Name: nv4_disp.dll Driver Version: 6.14.0010.9147 (English) DDI Version: 9 (or higher) Driver Attributes: Final Retail Driver Date/Size: 8/11/2006 21:42:52, 4496128 bytes WHQL Logo'd: Yes WHQL Date Stamp: n/a VDD: Mini VDD: nv4_mini.sys Mini VDD Date: 8/11/2006 21:42:42, 3958496 bytes Device Identifier: {D7B71E3E-4062-11CF-4956-6A1300C2CB35} Vendor ID: 0x10DE Device ID: 0x0322 SubSys ID: 0x33601642 Revision ID: 0x00A1 Revision ID: 0x00A1 Video Accel: ModeMPEG2_A ModeMPEG2_B ModeMPEG2_C ModeMPEG2_D Deinterlace Caps: {212DC722-3235-44A4-BD29-E1652BBCC71C}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,2) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive {212DC723-3235-44A4-BD29-E1652BBCC71C}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_MedianFiltering {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 {212DC722-3235-44A4-BD29-E1652BBCC71C}: Format(In/Out)=(UYVY,UYVY) Frames(Prev/Fwd/Back)=(0,0,2) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive {212DC723-3235-44A4-BD29-E1652BBCC71C}: Format(In/Out)=(UYVY,UYVY) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_MedianFiltering {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 {212DC722-3235-44A4-BD29-E1652BBCC71C}: Format(In/Out)=(YV12,0x32315659) Frames(Prev/Fwd/Back)=(0,0,2) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive {212DC723-3235-44A4-BD29-E1652BBCC71C}: Format(In/Out)=(YV12,0x32315659) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_MedianFiltering {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 {212DC722-3235-44A4-BD29-E1652BBCC71C}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,2) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive {212DC723-3235-44A4-BD29-E1652BBCC71C}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_MedianFiltering {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 Registry: OK DDraw Status: Enabled D3D Status: Enabled AGP Status: Enabled DDraw Test Result: Not run D3D7 Test Result: Not run D3D8 Test Result: Not run D3D9 Test Result: Not run ------------- Sound Devices ------------- Description: Realtek AC97 Audio Default Sound Playback: Yes Default Voice Playback: Yes Hardware ID: PCI\VEN_1106&DEV_3059&SUBSYS_66661462&REV_60 Manufacturer ID: 65535 Product ID: 65535 Type: WDM Driver Name: ALCXWDM.SYS Driver Version: 5.10.0000.5580 (English) Driver Attributes: Final Retail WHQL Logo'd: Yes Date and Size: 5/14/2004 23:24:10, 622172 bytes Other Files: Driver Provider: Realtek Semiconductor Corp. HW Accel Level: Full Cap Flags: 0xF5F Min/Max Sample Rate: 100, 192000 Static/Strm HW Mix Bufs: 33, 32 Static/Strm HW 3D Bufs: 33, 32 HW Memory: 0 Voice Management: Yes EAX 2.0 Listen/Src: Yes, Yes I3DL2 Listen/Src: Yes, Yes Sensaura ZoomFX: No Registry: OK Sound Test Result: Not run --------------------- Sound Capture Devices --------------------- Description: Realtek AC97 Audio Default Sound Capture: Yes Default Voice Capture: Yes Driver Name: ALCXWDM.SYS Driver Version: 5.10.0000.5580 (English) Driver Attributes: Final Retail Date and Size: 5/14/2004 23:24:10, 622172 bytes Cap Flags: 0x41 Format Flags: 0xFFF ----------- DirectMusic ----------- DLS Path: C:\WINDOWS\SYSTEM32\drivers\GM.DLS DLS Version: 1.00.0016.0002 Acceleration: n/a Ports: Microsoft Synthesizer, Software (Not Kernel Mode), Output, DLS, Internal, Default Port Realtek AC97 Audio, Software (Kernel Mode), Output, DLS, Internal Microsoft MIDI Microsoft GS Registry: OK Test Result: Not run ------------------- DirectInput Devices ------------------- Device Name: Attached: 1 Controller ID: n/a Vendor/Product ID: n/a FF Driver: n/a Device Name: Attached: 1 Controller ID: n/a Vendor/Product ID: n/a FF Driver: n/a Device Name: Saitek Cyborg 3D Stick USB Attached: 1 Controller ID: 0x0 Vendor/Product ID: 0x06A3, 0x0006 FF Driver: n/a Poll w/ Interrupt: No Registry: OK ----------- USB Devices ----------- + USB Root Hub | Vendor/Product ID: 0x1106, 0x3038 | Matching Device ID: usb\root_hub | Service: usbhub | Driver: usbhub.sys, 8/3/2004 23:08:44, 57600 bytes | Driver: usbd.sys, 8/17/2004 12:00:00, 4736 bytes | +-+ USB Optical WheelMouse | | Vendor/Product ID: 0x046D, 0xC016 | | Location: Optical USB Mouse | | Matching Device ID: usb\vid_046d&pid_c016 | | Service: LHidUsb | | Driver: LHidUsb.sys, 6/30/2003 17:50:00, 37884 bytes | | | +-+ HID-compliant Wheel Mouse | | | Vendor/Product ID: 0x046D, 0xC016 | | | Matching Device ID: hid\vid_046d&pid_c016 | | | Upper Filters: LMouFlt2 | | | Lower Filters: LHidFlt2 | | | Service: mouhid | | | Driver: mouhid.sys, 8/31/2001 15:31:08, 12160 bytes | | | Driver: mouclass.sys, 8/16/2004 16:23:52, 21760 bytes | | | Driver: LHidFlt2.Sys, 6/30/2003 17:50:00, 25214 bytes | | | Driver: LMouFlt2.Sys, 6/30/2003 17:50:00, 72894 bytes | | | Driver: Logi_MwX.Exe, 6/30/2003 17:50:00, 19968 bytes | | +-+ Saitek Cyborg 3D Stick USB | | Vendor/Product ID: 0x06A3, 0x0006 | | Location: CYBORG 3D USB | | Matching Device ID: usb\vid_06a3&pid_0006 | | Service: HidUsb | | OEMData: 03 00 08 10 0E 00 00 00 | | Driver: hidusb.sys, 8/17/2001 14:02:20, 9600 bytes | | Driver: hidclass.sys, 8/3/2004 23:08:20, 36224 bytes | | Driver: hidparse.sys, 8/3/2004 23:08:18, 24960 bytes | | Driver: hid.dll, 8/17/2004 12:00:00, 20992 bytes | | Driver: sai0006.dll, 7/26/2004 13:06:26, 798720 bytes | | | +-+ Saitek Cyborg 3D Stick USB (HID) | | | Vendor/Product ID: 0x06A3, 0x0006 | | | Matching Device ID: hid\vid_06a3&pid_0006 | | | Service: SaiH0006 | | | OEMData: 03 00 08 10 0E 00 00 00 | | | Driver: SaiH0006.sys, 7/26/2004 12:54:48, 56576 bytes
  15. Yes, i know what i am talk about, but all i want is let the product more and more better!
  16. Infact, my friend my AMD 3600+ 2GB mem and 256MB video card ,The FPS also low!
  17. I am the fans of fighter combat,so i play the lock on. As we know the Lock on had terrible perforcemence,what is on earth what kind of Pc could be Server or client play it well? A.Terrible client FPS, & bad mutiplayer, as we know, there always lots of UFO in sky, the target could be any of speed and hegiht could me 30,XXXX m,and the craft could jumping dancing in the sky. While I use the same PC and net condition play IL2 1946,the FPS make me feel smoothly. B.Terrible Perforcemence of Padlock, as we know ,the sim need Padlock,and padlock already several year 'old! While I use padlock with target,then if i POV some direction, what shall happen? The Padlock will not track with target,but the view angle will not chang! By the way, if Padlock miss with bandit, the view could not return to default like Flanker2.5. C. Terrible Perforcemence of Image, like what the FPS alway low,and also big mistake.Strange line and clour block often in the CRT, the cockipt also miss sth. D.If U fly F-15, but in the VSD and HUD the fronts type is two small to read! AS we know the Blizzard and IL 1946,there product sales well in the world,cause lot of PC could play it with good experience! What on earth the System the Lock on need? U can check the system require,but U will get Terrible Perforcemence Of Lock on! AMD 2600+ 512MB FX5200 128 Video card, in the background the NIS2006 Perhaps lock on work very well 's PC which could play FSX could got high score ,but the PC will be 5 years later could be popularity! let me drew the conclusion,why in the Hyperlobby the whole world people play IL2 1946 not the Lock on? Cause there is only few people 's have the Highend PC and could bear such awfull Bug!
×
×
  • Create New...