Aces High Bulletin Board
Help and Support Forums => Technical Support => Topic started by: Lusche on March 01, 2011, 03:15:30 PM
-
Since two days, I have increasing disco troubles. As of now I can't stay connected for longer than 30 minutes. In the last 2 hours, I'm losing UDP almost immediately after entering LW-OH.
Interestingly, a pingplot running at the same time doesn't show any packet loss (even when selecting UDP as packet type.
(http://img714.imageshack.us/img714/2703/whyn.gif)
I had changed no settings at my comp, it's not a firewall issue either. :headscratch:
-
Yesterday, on Titanic Tuesday map, I could play without problems.
Today, in offhours arena again, the same as two days before: Twice I lost UDP, and then connection, within a few moments after entering arena. Ping Plotter (running parallel) shows no UDP packet loss at all.
Right now, I can not stay connected for longer than 2-3 minutes.
:(
Update: I went to DA and was able to fly & fight there without problems. Went back to LWOH and lost UDP within a minute again, while I was sitting in Oclub of a remote field. Still, no packet loss indicated in Pingplotter.
-
More and more I'm beginning to suspect it's a resource issue, that is either limited to that particular map (mindanao) or greatly boosted by it.
Summing up some details:
- it only started to happen a few days ago, some time after the last patch. I did not have any of those problems before, on no map.
- I tried to duplicate the problem in other arenas (with same and differetn server), but so far failed.
- Even on TT map (orkansas) it didn't happen. Once I was back to LWOH it appeared again
- PingPlotter shows not packet loss
- 4 times out of 5 can induced a connection loss by alt tabbing out. When I get back in, I see "lost udp" (and usually crash).
- On TT, I was fighting in a big battle with lots of action around and could minimize and come back to AH without any problem.. In offpeak (mindanao), even when I do that far away from any action, it often provokes the disco. That's what's currently giving me the idea that it could be limited to that map, but again, it only started a few days again.
- Nothing in my computer/router configuration had changed, I still have the same number (and types) of processes running (and memory used) than I used to for a long time without problems
- This seems to be somewhat similar ot my problem:
after alt-tabbing my game use to crash. May i reinstall or something?
****************************
------------------
System Information
------------------
Time of this report: 3/3/2011, 12:43:13
Machine name: PANDY
Operating System: Windows XP Professional (5.1, Build 2600) Service Pack 3 (2600.xpsp_sp3_gdr.101209-1647)
Language: German (Regional Setting: German)
System Manufacturer: To Be Filled By O.E.M.
System Model: To Be Filled By O.E.M.
BIOS: Default System BIOS
Processor: AMD Athlon(tm) 64 X2 Dual Core Processor 4200+, MMX, 3DNow (2 CPUs), ~2.2GHz
Memory: 1920MB RAM
Page File: 333MB used, 3479MB available
Windows Dir: C:\WINDOWS
DirectX Version: DirectX 9.0c (4.09.0000.0904)
DX Setup Parameters: Not found
DxDiag Version: 5.03.2600.5512 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 9600 GT
Manufacturer: NVIDIA
Chip type: GeForce 9600 GT
DAC type: Integrated RAMDAC
Device Key: Enum\PCI\VEN_10DE&DEV_0622&SUBSYS_2AC5107D&REV_A1
Display Memory: 512.0 MB
Current Mode: 1920 x 1080 (32 bit) (60Hz)
Monitor: LG W2361(Digital)
Monitor Max Res: 1920,1080
Driver Name: nv4_disp.dll
Driver Version: 6.14.0011.9745 (English)
DDI Version: 9 (or higher)
Driver Attributes: Final Retail
Driver Date/Size: 4/3/2010 23:55:31, 6432128 bytes
WHQL Logo'd: n/a
WHQL Date Stamp: n/a
VDD: Nicht zutreffend
Mini VDD: nv4_mini.sys
Mini VDD Date: 4/3/2010 23:55:31, 10232128 bytes
Device Identifier: {D7B71E3E-4562-11CF-DC55-CE0A00C2CB35}
Vendor ID: 0x10DE
Device ID: 0x0622
SubSys ID: 0x2AC5107D
Revision ID: 0x00A1
Revision ID: 0x00A1
Video Accel: ModeMPEG2_C ModeMPEG2_D
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
{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
{6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(UYVY,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(UYVY,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalSt retch
{6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(YV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(YV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalSt retch
{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
{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 Live! 24-bit
Default Sound Playback: Yes
Default Voice Playback: Yes
Hardware ID: PCI\VEN_1102&DEV_0007&SUBSYS_100A1102&REV_00
Manufacturer ID: 1
Product ID: 100
Type: WDM
Driver Name: P17.sys
Driver Version: 5.12.0001.0514 (English)
Driver Attributes: Final Retail
WHQL Logo'd: n/a
Date and Size: 6/15/2007 09:47:26, 1127936 bytes
Other Files:
Driver Provider: CREATIVE
HW Accel Level: Full
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: 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 Live! 24-bit
Default Sound Capture: Yes
Default Voice Capture: Yes
Driver Name: P17.sys
Driver Version: 5.12.0001.0514 (English)
Driver Attributes: Final Retail
Date and Size: 6/15/2007 09:47:26, 1127936 bytes
Cap Flags: 0x0
Format Flags: 0x0
-----------
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
SB Live! 24-bit, Software (Kernel Mode), Output, DLS, Internal
Microsoft MIDI-Mapper [Emuliert], Hardware (Not Kernel Mode), Output, No DLS, Internal
Creative SoundFont Synth [Emuliert], Hardware (Not Kernel Mode), Output, No DLS, Internal
Microsoft GS Wavetable SW Synth [Emuliert], Hardware (Not Kernel Mode), Output, No DLS, Internal
Registry: OK
Test Result: Not run
-------------------
DirectInput Devices
-------------------
Device Name: Maus
Attached: 1
Controller ID: n/a
Vendor/Product ID: n/a
FF Driver: n/a
Device Name: Tastatur
Attached: 1
Controller ID: n/a
Vendor/Product ID: n/a
FF Driver: n/a
Device Name: Saitek Magic Hotkey Device
Attached: 1
Controller ID: 0x0
Vendor/Product ID: 0x06A3, 0x5081
FF Driver: n/a
Device Name: Saitek X52 Pro Flight Controller
Attached: 1
Controller ID: 0x0
Vendor/Product ID: 0x06A3, 0x0762
FF Driver: n/a
Poll w/ Interrupt: No
Registry: OK
-
I believe I am having the same problem. I am getting a high memory usage message though.
-
I believe I am having the same problem. I am getting a high memory usage message though.
Are you using high-res textures?
I did some further testing: So far, it seems to be the combination of high res-textures and the Mindanao map. I was running high-res on other maps (so far on Orkansas, Trinity, Grinder) without trouble, and I apparently can run 512 textures on Mindanao. Only this specific combination results in loss of UDP (& connection in 90% of those cases)
-
I run hi-res textures and haven't had a problem on Mindnao. I'm running Win7 and a dual core Intel CPU, plus different video card/maker, so I don't think we can draw a comparison or conclusion.
-
Turn the hardware acceleration down to 3/4 from Full.
-
Turn the hardware acceleration down to 3/4 from Full.
Did that, and set texture size to 1024 again for another test on Mindanao.
Didn't help. Still "Host stopped receiving UDP" and loss of connection when going back to the game with alt-tab.
-
When you alt-tab back into the game, the resources for the game have to be reallocated. If the CPU gets too tied up to respond to a network request, then UDP loss is inevitable.