Detail Up = Warp?

[Sincraft]

Not sure but I've played with this.  Seems like the more detail, the more warping.  Or am I incorrect?

I'm having issues landing kills while watching my hits LAND with sparks on planes, then suddenly the plane ZIPS forward about 100m in warp speed, and I'm in too steep of an angle to EVER hope to get back on him in that pass again, making me wonder did I really hit him according to the servers?

I have a pretty decent system.  I have a 3200+ amd single core, 7600 gt vid card, 2 gigs o ram and 2 sata 3 hard drives in raid (for speed).

Maybe I suck but, I notice I can spray a pretty quick couple o squirts if the plane is flying level for a bit, but during a turnfight, although I am landing hits when they are straigthening out, I'm not getting kills

HECK , one time I unloaded almost all my ammo from my yak, I watched AT LEAST 20 rounds sparking off of his plane (spit), and then someone came in and killed him.  I didn't even get an assist, as in, I didn't land ONE shot according to the system.

Maybe it's just me but something doesn't 'feel' right in comparison to other sims I've played with landing shots.  

I'm having a blast playing this game, I must say.  And I took several recommendations for Conv on planes.  One guy told me that other planes should be set to 300, planes with 50mm (all) should be set to about 350, and the p38 should be set to 650.  I killed two planes EASILY with a p38 on straight on shots, never got a chance to really 'turn fight' with it though.

Like I said, it seems as if the issue is whenever they are straight for a moment then turn.  I can land hits but then they turn as if 'I really didn't hit them' although I DO SEE SPARKS flying, which means the system is registering the hits on my end.  Is it on theirs too?  If so then I am just the suck...if the sparks flying means NOTHING then there is a real issue here and I'm not just dreaming.  

Anyway - any advice anyone could give would be great.  Someone told me to synch my monitor with my refresh but I am not sure where in game I should do this, or should I do this within my control panel of my monitor/vid card?

Thanks gents.

S

[Sincraft]

btw here is my dxdiag, maybe some of you vets may see some red flags here but I didn't see anything.  I think my nvidia drivers are 'ok' due to the newer ones causing fubars in other games I reverted back to these ones.

------------------
System Information
------------------
Time of this report: 2/13/2007, 00:37:42
       Machine name: KOMPUTER001
   Operating System: Windows XP Professional (5.1, Build 2600) Service Pack 2 (2600.xpsp_sp2_gdr.050301-1519)
           Language: English (Regional Setting: English)
System Manufacturer: System manufacturer
       System Model: System Product Name
               BIOS: Phoenix - AwardBIOS v6.00PG
          Processor: AMD Athlon(tm) 64 Processor 3200+,  MMX,  3DNow, ~2.0GHz
             Memory: 2048MB RAM
          Page File: 389MB used, 3550MB 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 7600 GT
     Manufacturer: NVIDIA
        Chip type: GeForce 7600 GT
         DAC type: Integrated RAMDAC
       Device Key: Enum\PCI\VEN_10DE&DEV_0391&SUBSYS_22201682&REV_A1
   Display Memory: 256.0 MB
     Current Mode: 1280 x 1024 (32 bit) (85Hz)
          Monitor: Default Monitor
  Monitor Max Res:
      Driver Name: nv4_disp.dll
   Driver Version: 6.14.0010.8391 (English)
      DDI Version: 9 (or higher)
Driver Attributes: Final Retail
 Driver Date/Size: 3/10/2006 00:38:38, 3960064 bytes
      WHQL Logo'd: Yes
  WHQL Date Stamp: n/a
              VDD: n/a
         Mini VDD: nv4_mini.sys
    Mini VDD Date: 3/10/2006 00:38:40, 3642784 bytes
Device Identifier: {D7B71E3E-40D1-11CF-F555-2A0200C2CB35}
        Vendor ID: 0x10DE
        Device ID: 0x0391
        SubSys ID: 0x22201682
      Revision ID: 0x00A1
      Revision ID: 0x00A1
      Video Accel: ModeMPEG2_A ModeMPEG2_B ModeMPEG2_C ModeMPEG2_D ModeWMV9_B ModeWMV9_A
 Deinterlace Caps: {212DC724-3235-44A4-BD29-E1652BBCC71C}: 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
                   {212DC724-3235-44A4-BD29-E1652BBCC71C}: 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
                   {212DC724-3235-44A4-BD29-E1652BBCC71C}: Format(In/Out)=(YV12,0x32315659) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
                   {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_BOBVerticalSt retch
                   {212DC724-3235-44A4-BD29-E1652BBCC71C}: 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
         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: SB Audigy 2 ZS Audio [A000]
 Default Sound Playback: Yes
 Default Voice Playback: Yes
            Hardware ID: PCI\VEN_1102&DEV_0004&SUBSYS_20021102&REV_04
        Manufacturer ID: 1
             Product ID: 100
                   Type: WDM
            Driver Name: ctaud2k.sys
         Driver Version: 5.12.0001.1164 (English)
      Driver Attributes: Final Retail
            WHQL Logo'd: Yes
          Date and Size: 12/8/2005 13:55:46, 439296 bytes
            Other Files:
        Driver Provider: Creative
         HW Accel Level: Full
              Cap Flags: 0xF5F
    Min/Max Sample Rate: 4000, 192000
Static/Strm HW Mix Bufs: 64, 62
 Static/Strm HW 3D Bufs: 64, 62
              HW Memory: 0
       Voice Management: Yes
 EAX(tm) 2.0 Listen/Src: Yes, Yes
   I3DL2(tm) Listen/Src: No, No
Sensaura(tm) ZoomFX(tm): No
               Registry: OK
      Sound Test Result: Not run

---------------------
Sound Capture Devices
---------------------
            Description: SB Audigy 2 ZS Audio [A000]
  Default Sound Capture: Yes
  Default Voice Capture: Yes
            Driver Name: ctaud2k.sys
         Driver Version: 5.12.0001.1164 (English)
      Driver Attributes: Final Retail
          Date and Size: 12/8/2005 13:55:46, 439296 bytes
              Cap Flags: 0x41
           Format Flags: 0xFFF

[Sincraft]

-----------
DirectMusic
-----------
        DLS Path: C:\WINDOWS\SYSTEM32\drivers\GM.DLS
     DLS Version: 1.00.0016.0002
    Acceleration: Enabled
           Ports: SB Audigy 2 ZS DirectMusic Synthesizer [A000], Hardware (Kernel Mode), Output, DLS, Internal, Default Port
                  MPU-401, Hardware (Kernel Mode), Input, No DLS, External
                  MPU-401, Hardware (Kernel Mode), Output, No DLS, External
                  SB Audigy 2 ZS Audio [A000], Software (Kernel Mode), Output, DLS, Internal
                  Microsoft MIDI Mapper [Emulated], Hardware (Not Kernel Mode), Output, No DLS, Internal
                  SB Audigy 2 ZS Synth A [A000] [Emulated], Hardware (Not Kernel Mode), Output, No DLS, Internal
                  MPU-401 [Emulated], Hardware (Not Kernel Mode), Output, No DLS, External
                  SB Audigy 2 ZS Sw Synth [A000] [Emulated], Hardware (Not Kernel Mode), Output, No DLS, Internal
                  SB Audigy 2 ZS Synth B [A000] [Emulated], Hardware (Not Kernel Mode), Output, No DLS, Internal
                  SB Audigy 2 ZS MIDI IO [A000] [Emulated], Hardware (Not Kernel Mode), Output, No DLS, External
                  Microsoft GS Wavetable SW Synth [Emulated], Hardware (Not Kernel Mode), Output, No DLS, Internal
                  MPU-401 [Emulated], Hardware (Not Kernel Mode), Input, No DLS, External
                  SB Audigy 2 ZS MIDI IO [A000] [Emulated], Hardware (Not Kernel Mode), Input, No DLS, External
                  Microsoft Synthesizer, Software (Not Kernel Mode), Output, DLS, Internal
        Registry: OK
     Test Result: Not run

-------------------
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: Saitek AV8R Joystick
         Attached: 1
    Controller ID: 0x0
Vendor/Product ID: 0x06A3, 0x0461
        FF Driver: n/a

Poll w/ Interrupt: No
         Registry: OK

-----------
USB Devices
-----------
+ USB Root Hub
| Vendor/Product ID: 0x10DE, 0x005A
| Matching Device ID: usb\root_hub
| Service: usbhub
| Driver: usbhub.sys, 8/4/2004 07:00:00, 57600 bytes
| Driver: usbd.sys, 8/4/2004 07:00:00, 4736 bytes
|
+-+ USB Human Interface Device
| | Vendor/Product ID: 0x06A3, 0x0461
| | Location: Saitek AV8R Joystick
| | Matching Device ID: usb\class_03
| | Service: HidUsb
| | OEMData: 03 00 88 10 0E 00 00 00
| | Driver: hidclass.sys, 8/4/2004 07:00:00, 36224 bytes
| | Driver: hidparse.sys, 8/4/2004 07:00:00, 24960 bytes
| | Driver: hid.dll, 8/4/2004 07:00:00, 20992 bytes
| | Driver: hidusb.sys, 8/4/2004 07:00:00, 9600 bytes
| |
| +-+ HID-compliant game controller
| | | Vendor/Product ID: 0x06A3, 0x0461
| | | Matching Device ID: hid_device_system_game
| | | OEMData: 03 00 88 10 0E 00 00 00

----------------
Gameport Devices
----------------
+ PCI bus
| Matching Device ID: *pnp0a03
| Service: pci
| Driver: pci.sys, 8/4/2004 07:00:00, 68224 bytes
|
+-+ Standard Game Port
| | Matching Device ID: *pnpb02f
| | Service: gameenum
| | Driver: gameenum.sys, 8/4/2004 01:08:22, 10624 bytes
|
+ PCI standard PCI-to-PCI bridge
| Location: PCI bus 0, device 9, function 0
| Matching Device ID: pci\cc_0604
| Service: pci
| Driver: pci.sys, 8/4/2004 07:00:00, 68224 bytes
|
+-+ Creative Game Port
| | Location: PCI bus 5, device 7, function 1
| | Matching Device ID: pci\ven_1102&dev_7003&subsys_00401102
| | Service: gameenum
| | Driver: gameenum.sys, 8/4/2004 01:08:22, 10624 bytes

------------
PS/2 Devices
------------
+ Standard 101/102-Key or Microsoft Natural PS/2 Keyboard
| Matching Device ID: *pnp0303
| Service: i8042prt
| Driver: i8042prt.sys, 8/4/2004 07:00:00, 52736 bytes
| Driver: kbdclass.sys, 8/4/2004 07:00:00, 24576 bytes
|
+ Terminal Server Keyboard Driver
| Matching Device ID: root\rdp_kbd
| Upper Filters: kbdclass
| Service: TermDD
| Driver: termdd.sys, 8/4/2004 03:01:08, 40840 bytes
| Driver: kbdclass.sys, 8/4/2004 07:00:00, 24576 bytes
|
+ PS/2 Compatible Mouse
| Matching Device ID: *pnp0f13
| Service: i8042prt
| Driver: i8042prt.sys, 8/4/2004 07:00:00, 52736 bytes
| Driver: mouclass.sys, 8/4/2004 07:00:00, 23040 bytes
|
+ Terminal Server Mouse Driver
| Matching Device ID: root\rdp_mou
| Upper Filters: mouclass
| Service: TermDD
| Driver: termdd.sys, 8/4/2004 03:01:08, 40840 bytes
| Driver: mouclass.sys, 8/4/2004 07:00:00, 23040 bytes

----------------------------
DirectPlay Service Providers
----------------------------
DirectPlay8 Modem Service Provider - Registry: OK, File: dpnet.dll (5.03.2600.2180)
DirectPlay8 Serial Service Provider - Registry: OK, File: dpnet.dll (5.03.2600.2180)
DirectPlay8 IPX Service Provider - Registry: OK, File: dpnet.dll (5.03.2600.2180)
DirectPlay8 TCP/IP Service Provider - Registry: OK, File: dpnet.dll (5.03.2600.2180)
Internet TCP/IP Connection For DirectPlay - Registry: OK, File: dpwsockx.dll (5.03.2600.2180)
IPX Connection For DirectPlay - Registry: OK, File: dpwsockx.dll (5.03.2600.2180)
Modem Connection For DirectPlay - Registry: OK, File: dpmodemx.dll (5.03.2600.2180)
Serial Connection For DirectPlay - Registry: OK, File: dpmodemx.dll (5.03.2600.2180)

DirectPlay Voice Wizard Tests: Full Duplex: Passed, Half Duplex: Passed, Mic: Passed
DirectPlay Test Result: Not run
Registry: OK

-------------------
DirectPlay Adapters
-------------------
DirectPlay8 Serial Service Provider: COM1
DirectPlay8 TCP/IP Service Provider: Local Area Connection - IPv4 -

-----------------------
DirectPlay Voice Codecs
-----------------------
Voxware VR12 1.4kbit/s
Voxware SC06 6.4kbit/s
Voxware SC03 3.2kbit/s
MS-PCM 64 kbit/s
MS-ADPCM 32.8 kbit/s
Microsoft GSM 6.10 13 kbit/s
TrueSpeech(TM) 8.6 kbit/s

-------------------------
DirectPlay Lobbyable Apps
-------------------------

------------------------
Disk & DVD/CD-ROM Drives
------------------------
      Drive: C:
 Free Space: 5.0 GB
Total Space: 50.0 GB
File System: NTFS
      Model: NVIDIA  STRIPE   149.06G

      Drive: D:
 Free Space: 66.8 GB
Total Space: 102.6 GB
File System: NTFS
      Model: NVIDIA  STRIPE   149.06G

      Drive: E:
      Model: LITE-ON DVDRW SHM-165H6S
     Driver: c:\windows\system32\drivers\cdrom.sys, 5.01.2600.2180 (English), 8/4/2004 07:00:00, 49536 bytes

[Skuzzy]

You certainly can create warping issues if you are running out of resources.

What video settings are you using in the game?
Have you installed the high resolution texture package?
Do you have skins enabled?
Are you using any anti-aliasing in the video card?
Do you have any custom sound packs loaded?
What settings do you have in the graphic details panel of the game?
How many background processes are running on the computer?

All the above effect resource usage.  Youy can quite easily use up all 2GB of your RAM, and then some, depending on the settings you are using.

You can also run out of video RAM as well, again, depending on what settingsyou are using.

[airspro]

control panel of my monitor/vid card?

Vertical sync is located in the Performace and Quality settings under "advanced" in Disply properties .

Turn that on you don't want to have more fps than the monitor can refresh .

Plus I would turn down every option there to "Best Proformace" at least till you get things working right for once .

I don't run any extra skins or anything but the basic game on 1024 by 768 with 256 textures . I have mostly the same but a little lower PC than you do .

3.0 Barton , 7600GT 256 mb card , 2 512's DDR 3200 running dual channel , etc , game does run good for me and don't get what you have at all .

=====

I do have a steady connection , if your "net status" in the game is spikeing alot you gonna have problem . That would most likely be on your end as AH runs pretty smooth most all the time IMO .

AH runs even more smooth for me on dialup , this game plays very well from Michigan connected at 21.6 , without any problem at all . But I don't use that much as it ties up the phone line so I use my high speed connection .

gl
spro

[bj229r]

When I log into game, windows shows about 47 processes running (1 gig ram)--after clicking away for quite some time, I can pare that down to 33 or so (could mebbe do a few more, but I really havent any idea what some of them do) My machine is far less than yours (3200 256 meg fx 5700 card, mb has either 400 or 800 fsb) and im dialup, and its smooth 95% the time (near ground drops frames from 59 down to low 20's/teens sometimes, and puffy ack sounds are a frightful resource grabber, as i use onboard audio)--and I have every video setting in AH maxed--theres gotta be somethin in your box thats not set right.
Also was gonna mention, how do you know whether the cannons are landing, or is it the bullets? Always had that problem in 190's, until I just stopped firing the bullets

[Sincraft]

I have minimal processes running.  I built a custom XP build for gaming with minimal resources being used although some of my resources DO use some ram.

Although, with this game I am not barely touching the CPU or the ram.  Honestly.

The questions asked above are answered (for the most part) in my dxdiag file.

Everything else is set to middle of the road.  Detail vs fastest.

No I haven't installed any hi-res packs or anything.

Like I said, I installed the game, and ran it.

That's all.

[Krusty]

But what about vid card settings? And AH settings? Are you running AH at 1600+ resolution with 16x FSAA and 18x anisotropic filtering? Might run detail settings in AH at "X" fine, but starts choking at "3 x X", for example (just a wild thought).

[Sincraft]

I run at 1024 x 768.
Textures , both boxes unchecked (Preload in sys mem and preload skins)
Max Textures are what the system selected at 1024
Max frames = unlimited.
Hardware Vertex Processing is CHECKED
Optimize objects and Optimize Terrain is CHECKED

My video card is set to APPLICATION CONTROLLED with the exception of the Vsync.

I was hit and miss tonight.  

BIG example here.  I sprayed at one bomber, didn't get that great of shots ...mostly on the wings a bit, then pulled off while spraying a bit toward the other two.

As I am turning toward them for another run, #2 and #3 bombers implode and drop in pieces for some reason.

I then turned on bomber 1 and flamed both engines and then left him to his demise.

I got 3 kills somehow on what I consider some of my worst gunnery.

I then get behind a f4u, spraying and nailing him for my entire load of fresh ammo.  He turns like I am not even there toward another enemy.  It was like he didn't even hear me hitting him as he let me unload everything on him.

Then 5 minutes later, I sprayed into another f4 and he exploded into a million pieces as if I launched an A2A missle at him.

Strange.

[NHawk]

Dumb question...how far away are you when you shoot?

The term "spray" sounds like you're +600 or farther. And the 100 yd jump tends to point toward the same thing since at those distances the distance meter changes in 100yd increments. So far as convergence, if you have it set at 300 and you're shooting at 600 I can guarantee you're not getting enough punch in your hits to take out a tin can.

Hold fire until 400 (or your longest convergence setting) or less. Anything farther and you're in pretty much spray and pray mode.

[doc1kelley]

Originally posted by Sincraft
I run at 1024 x 768.
Textures , both boxes unchecked (Preload in sys mem and preload skins)
Max Textures are what the system selected at 1024
Max frames = unlimited.
Hardware Vertex Processing is CHECKED
Optimize objects and Optimize Terrain is CHECKED

My video card is set to APPLICATION CONTROLLED with the exception of the Vsync.

I was hit and miss tonight.  

BIG example here.  I sprayed at one bomber, didn't get that great of shots ...mostly on the wings a bit, then pulled off while spraying a bit toward the other two.

As I am turning toward them for another run, #2 and #3 bombers implode and drop in pieces for some reason.

I then turned on bomber 1 and flamed both engines and then left him to his demise.

I got 3 kills somehow on what I consider some of my worst gunnery.

I then get behind a f4u, spraying and nailing him for my entire load of fresh ammo.  He turns like I am not even there toward another enemy.  It was like he didn't even hear me hitting him as he let me unload everything on him.

Then 5 minutes later, I sprayed into another f4 and he exploded into a million pieces as if I launched an A2A missle at him.

Strange.

I don't believe you have enough vid mem to preload skins.  You should have VSYNC forced to the ON position or else you are gonna see lots of rubber bullets (your Front End shows hits but it's not registered on the server or the victim's front end).  I lock my refresh rate at 60 in AH.

All the Best...
Jay
awDoc1

[Sincraft]

I'm pretty sure, actually 100% sure that my rig is more than adequate for this game.  Video memory is not an issue.  Monitor refresh rate, possibly I don't know but I vsynced recently.  I havent seen many warping planes but I do see some strange behavior now and then.  There is definetely a high delay in this game round trip imo.