Ascent LD's!!!!!! who else is getting these!

[Ragnayor]

been runniing for a while now and go LD now and again at the video part after placing the shard.  Is this happening to other servers too?  I missed out on an update  today  petitioned and some how its my fault for going LD to an SOE bug....even though 1-6 people go link dead on Oasis at this spot since I've been runing it......  Is this a known bug? 

[Warrden_defilez]

I am also getting this....I keep going LD the Cut sceen... reason why i hate doing this zone

[physco]

same

[TSR-JoshuaM]

I can't say it's a known bug as I've never heard of it before.  I do that zone a few times a week and haven't run in to that problem.  Let's go over a few things and see what we can find.

Can you submit your DXDIAG information here?  Just need the top 3 sections, system display and sound devices.

[Enchandress]

I've only experience once but I have a teammate who has experienced the LD issue many many times.  We actually now wait until loot has been passed out before clicking the shard.

[Ragnayor]

System Information------------------Time of this report: 4/6/2011, 16:29:33       Machine name: GEORGIE-PC   Operating System: Windows 7 Home Premium 64-bit (6.1, Build 7601) Service Pack 1 (7601.win7sp1_rtm.101119-1850)           Language: English (Regional Setting: English)System Manufacturer: Gateway       System Model: DX4300               BIOS: Default System BIOS          Processor: AMD Phenom(tm) II X4 805 Processor (4 CPUs), ~2.5GHz             Memory: 8192MB RAMAvailable OS Memory: 8192MB RAM          Page File: 3173MB used, 13206MB available        Windows Dir: C:Windows    DirectX Version: DirectX 11DX 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.      Display Tab 2: 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 460       Manufacturer: NVIDIA          Chip type: GeForce GTX 460           DAC type: Integrated RAMDAC         Device Key: EnumPCIVEN_10DE&DEV_0E22&SUBSYS_23211462&REV_A1     Display Memory: 4066 MB   Dedicated Memory: 738 MB      Shared Memory: 3327 MB       Current Mode: 1600 x 900 (32 bit) (60Hz)       Monitor Name: Generic PnP Monitor      Monitor Model: W2061         Monitor Id: GSM4EA1        Native Mode: 1600 x 900(p) (60.000Hz)        Output Type: HD15        Driver Name: nvd3dumx.dll,nvwgf2umx.dll,nvwgf2umx.dll,nvd3dum,n vwgf2um,nvwgf2umDriver File Version: 8.17.0012.6658 (English)     Driver Version: 8.17.12.6658        DDI Version: 11       Driver Model: WDDM 1.1  Driver Attributes: Final Retail   Driver Date/Size: 1/7/2011 21:27:00, 12859496 bytes        WHQL Logo'd: Yes    WHQL Date Stamp:   Device Identifier: {D7B71E3E-4D62-11CF-D06D-2D031FC2C535}          Vendor ID: 0x10DE          Device ID: 0x0E22          SubSys ID: 0x23211462        Revision ID: 0x00A1 Driver Strong Name: oem16.inf:NVIDIA_SetA_Devices.NTamd64.6.1:Section0 05:8.17.12.6658:pciven_10de&dev_0e22     Rank Of Driver: 00E62001                   

[TSR-JoshuaM]

Can you give this update a try?  I managed to crash a test computer but it was running a very old revision of DirectX 9 and this update did resolve the issue.  I cannot say with certainty that it is the same issue you have but the symptoms are identical.

[DX9] June 2010

[Ragnayor]

Nope did not work still froze at the cut seen

[Raheal]

I have the same issue type of issue since I swapped my video card from a gforce 6600 to a radeon 6850. What happens is when the cut sceen starts, my entire screen goes black. Voice chat still works just fine. Then, the cut sceen eventually starts after about a minute. I then catch just the end of the cut sceen. My screen then goes black again, except for the mouse cursor can now be seen. Voice chat still works. After about another minute, my display returns to normal, and everyone else is waiting for me.

something similar I've noticed is that at the same time I swapped my graphics card, switching from full-screen mode to windowed-mode with alt-enter takes a LONG LONG time. I was wondering if this was related. I did some searching online and someone stated that changing my Windows 7 display from using Aero to instead just use Basic would resolve the issue. I did this switch and now going from full-screen to windowed-mode is a little quicker, but nowhere near as fast it was with my previous card.

I then tested the Ascent cut screen again, and this time instead of just getting a black screen, my entire Everquest window minimized to the taskbar, but I couldn't interact with anything. Then, the window popped back up to full-screen and I saw the cut sceen. When the cut sceen was done, my window minimized itself again, until about a minute later and then the Everquest window returned to normal. I don't believe that my voice chat was working as people couldn't hear me, but I could hear them just fine.

[TSR-JoshuaM]

We're starting some testing to reproduce this with ATI specific cards.  Will keep you all updated.

[gimme]

TSR-JoshuaM wrote:

We're starting some testing to reproduce this with ATI specific cards.  Will keep you all updated.

I wouldn't mind an update myself as I have NEVER been able to do this zone without crashing at that mythical cutscene. Group members go through it with no problems apart from a slight delay and black screen but no cutscene. Mine just hangs.

4870x2 here.

Yes I know dragging out old posts isnt considered the best but surely its better than starting another with the same subject when there doesnt appear to have been ANY update.

Thanks

[harleygjc]

the one trick you can try to avoid the video scene is to target yourself and then click auto attack, if you do that then the video won't play and you'll avoid going LD!

[Jrral]

TSR-JoshuaM wrote:

We're starting some testing to reproduce this with ATI specific cards.  Will keep you all updated.

I do notice a lot of variability in how long the scene runs. Sometimes it runs almost immediately, sometimes it takes a very long time for the scene itself to start playing. Maybe it's not video-related, but related to a stall or delay in getting everything set up, and if it delays long enough something sees the lack of network traffic as an indication the client's gone dead?

[TSR-JoshuaM]

Jrral@Unrest wrote:

TSR-JoshuaM wrote:

We're starting some testing to reproduce this with ATI specific cards.  Will keep you all updated.

I do notice a lot of variability in how long the scene runs. Sometimes it runs almost immediately, sometimes it takes a very long time for the scene itself to start playing. Maybe it's not video-related, but related to a stall or delay in getting everything set up, and if it delays long enough something sees the lack of network traffic as an indication the client's gone dead?

We've gathered much more info since April on the issue as well.  We should already be on the path to a fix in the near future.