Sending a celestial body to annihilate disconnects me from server.

Yesterday my brother called me to (mostly vent) that twice he was disconnected after confirming a target for a halley'd moon to smoosh. This evening I was able to duplicate the bug. I played a 2v2 (with my brother and two random players) on a randomly generated "Seven Gates" system. I built the required 4 Halley engines on the moon, clicked "Send to Annihilate", selected the enemy planet, selected the Enemy Commander, Confirmed *Disconnected from server!* Victory denied. The absolute very second I clicked Confirm the game disconnected. I've never seen PA exit a game so quickly (Serious). My brother also lost his connection at the same time. I don't know if the other team was disconnected. I was unable to rejoin the game. My brother and I are not on the same internet connection. PA.exe did not crash.

Sure, Nukes and SXX platforms are fun, but they're not the NAMESAKE! I don't think it's a drive issue, but I'm attaching a dxdiag anyway.

Hello,

I checked your Dxdiag, and it turns out you have an issue with outdated drivers:

Code:

Processor: Intel(R) Core(TM) i7-4700MQ CPU @ 2.40GHz (8 CPUs), ~2.4GHz
Card name: Intel(R) HD Graphics 4600
Dedicated Memory: 32 MB
Driver Version: 9.18.10.3165
Driver Date/Size: 5/7/2013 20:22:46, 8632320 bytes

Follow @SXX's instructions below to update your Intel graphics drivers:

Also, you have only 32 MB of dedicated graphics memory. That, plus the outdated drivers, could explain why you disconnected. The server/client possibly couldn't handle the load.

Just to point out that 32MB number is likely not accurate. Going from the dxdiag it would suggest he is likely using a laptop. And I know from experience with friends laptops and such that the dedicated memory allocated scales as software requires it.

This is a bug that happens to me as well (despite up to date drivers). It's on the bugtracker and could use more votes and confirmations.

I didn't have this bug the last time I launched a Halley. When I confirmed the launch, I didn't disconnect.

I don't know why I was able to smash the enemy commander without disconnecting.

This man speaks the truth

But, that number is technically correct. This is not the problem.

DVMT allocates memory based on system needs.

here, i found this for reference
http://www.tomshardware.com/answers/id-2069225/ideal-ram-intel-4600.html

This problem probably has to do with the drivers or servers. Although i do find it weird that it happened twice.

Actually I have 2 GB of GDDR5, and relatively up to date nVidia drivers. Optimus hides it from the dxdiag apparently. Quad core i7, 16GB RAM...32MB of graphics memory? Come on now!

I upvoted that, and submitted this last night: http://pa.lennardf1989.com/Tracker/index.php?do=details&task_id=3953

These are the last two minutes of my log before the games crashes back to the main menu. Current build, 2vs2 Team Armies.

Where do I find this log? I'll post mine too. I haven't played since there disconnect last night.

The same issue happens to me also quite often after updating the game to v 70289 (PA 64-bit): in 4-player games with 3 AI opponents, 1 sesond after hitting "confirm" I'm getting disconnected from the server; occurs 2/3 times.

Code:

------------------
System Information
------------------
Time of this report: 8/15/2014, 12:02:00
  Machine name: REACTOR
  Operating System: Windows 7 Professional 64-bit (6.1, Build 7601) Service Pack 1 (7601.win7sp1_gdr.140303-2144)
  Language: German (Regional Setting: German)
System Manufacturer: Gigabyte Technology Co., Ltd.
  System Model: P67A-UD3P-B3
  BIOS: Award Modular BIOS v6.00PG
  Processor: Intel(R) Core(TM) i7-2700K CPU @ 3.50GHz (8 CPUs), ~4.4GHz
  Memory: 8192MB RAM
Available OS Memory: 8176MB RAM
  Page File: 3475MB used, 21082MB 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 32bit 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 680
  Manufacturer: NVIDIA
  Chip type: GeForce GTX 680
  DAC type: Integrated RAMDAC
  Device Key: Enum\PCI\VEN_10DE&DEV_1180&SUBSYS_118010B0&REV_A1
  Display Memory: 4038 MB
  Dedicated Memory: 1990 MB
  Shared Memory: 2048 MB
  Current Mode: 1920 x 1200 (32 bit) (59Hz)
  Monitor Name: HP ZR24w Wide LCD Monitor
  Monitor Model: HP ZR24w
  Monitor Id: HWP2869
  Native Mode: 1920 x 1200(p) (59.950Hz)
  Output Type: Displayport External
  Driver Name: nvd3dumx.dll,nvwgf2umx.dll,nvwgf2umx.dll,nvd3dum,nvwgf2um,nvwgf2um
Driver File Version: 9.18.0013.4052 (English)
  Driver Version: 9.18.13.4052
  DDI Version: 11
  Driver Model: WDDM 1.1
  Driver Attributes: Final Retail
  Driver Date/Size: 7/2/2014 22:48:32, 17555104 bytes
  WHQL Logo'd: n/a
  WHQL Date Stamp: n/a
  Device Identifier: {D7B71E3E-52C0-11CF-D47C-8D311CC2C435}
  Vendor ID: 0x10DE
  Device ID: 0x1180
  SubSys ID: 0x118010B0
  Revision ID: 0x00A1
Driver Strong Name: oem177.inf:NVIDIA_SetA_Devices.NTamd64.6.1:Section093:9.18.13.4052:pci\ven_10de&dev_1180
  Rank Of Driver: 00E02001
  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: Lautsprecher (Realtek High Definition Audio)
Default Sound Playback: Yes
Default Voice Playback: Yes
  Hardware ID: HDAUDIO\FUNC_01&VEN_10EC&DEV_0889&SUBSYS_1458A022&REV_1000
  Manufacturer ID: 1
  Product ID: 100
  Type: WDM
  Driver Name: RTKVHD64.sys
  Driver Version: 6.00.0001.6662 (English)
  Driver Attributes: Final Retail
  WHQL Logo'd: n/a
  Date and Size: 6/19/2012 10:54:20, 4065296 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

Your DX Diag looks fine. When you get a disconnect that is usually a server crash, Uber have been doing lots of work on the server recently so looks like this is due to something they've changed their end.

If you could look at your replays and find the id for your game that would be helpful as they can look at the what was happening to cause the crash

How to do so?

You *should* be able to find the ID by going into the game- then go to 'replays' and setting to 'my games only'.

The ID is listed with each game I believe- just find the game that crashed and post the ID here.

Just a suggestion: The latested added feature about celestial was that now the orientation changes to reflect the position of the Halleys, might this be a reason for the disconnects because the server gets into trouble with this?

The thing is: Games crashing this way are nowhere to be found in the replay list. At least that's the case for me; I can find none of the matches I played which where "finished" by Halleys.

Yes quite possibly...

That's a pain, not sure what else to suggest apart from *set up a game for a planet smash, not the ID and hope it crashes*?

I was able to reproduce it again (4 Halleys ready, selected the planet and confirmed), this time I added the log.

To the ones which observed the same issue: which kind of screen resolution you are using?

I use the native resolution of my display. 1600x900 My replays with the crash are also not listed.

So the aspect ratio seems not to be involved.