PDA

View Full Version : Very Strange New Graphics Issue


Traenkuri
03-12-2011, 12:15 PM
<p>Hello!</p><p>Just as a little background, I had a hard drive die on my, and was forced to reinstall EQ2 on the new Hard Drive for the first time in years. Everything was OK for a while but that new drive was bad and had to be replaced by WD, so I had to reinstall everything /again/.</p><p>Ever since this new installation, which uses a different patcher than I used to have, when I zone into some places like Lavastorm, Loping Plains, Pillars of Flame, Frosfang Sea and many other zones, parts of the ground or mountains seem to be missing. That happened to me in Outer Kael, the floor appeared to be missing, but it was still solid. Well, in these other zones, the ground just doesn't appear to be missing, it is /really/ not there. I took my Griffon into Somborn Village, and the entire ground was missing except for one mound of dirt. In Frostfang Sea, I can fly through an entire mountain as if it wasn't even there. Same in Lavastorm, except part of the beach is missing and if I try to walk on any of these missing areas, I fall through the world.</p><p>There used to be a way to delete the offending zone files and have the patcher redownload them, but I'm not seeing a way to do that now. How can I do that?</p><p>Sincerely,</p><p>Traenkuri</p>

sneakerz
03-21-2011, 11:24 PM
<p>I'm having the same issue. ever since the new expansion alot of the older zones like, lavastorm, everfrost, loping planes etc.... the graphics are not rendering at all. I been trying all sorts of things like updated my graphics driver, redownloaded the game, cleared the game cache and still same thing. I'm not sure what is causing this but any help is greatly appreciated. gonna try a few more things and see if it helps. i will post any findings.</p>

sneakerz
03-23-2011, 12:29 AM
<p>so i fixed the graphic rendering issue. So i was looking at some other post in here and took some of their advice and it seems that maybe some files may have corrupted. I have windows 7 64 bit home edition. i uninstalled the game using the control panel and i also went to c:program datasony online entertainement and deleted the folder. Then i just downloaded the launcher from the website and reinstalled the game, but before i deleted the folder i copied my toons UIsettings that also indicates the server your on and copied those files and saved in a seperate folder. I did this so i didnt have to redo my toolbars and such. its such a pain to set your toolbars all over again. Also if you use profit UI save those files too so you dont have to redo those tool bars and settings. once the game was installed just copy those files into the directory folder. I launched the game and everything is back to normal. Graphics rendering and able to go to all zones. Hope this helps.</p>

Rangy Bear
03-28-2011, 03:25 PM
<p>I've encounterd the same problem up on the Dreadnever Crash site.  Not on any of the other islands  just DCS.  I had configured my Windows 7 (64bit) system on a AMD Phenom II Quad Core to use the shader 3.0 stuff.  I changed back to shader 1.0 and the problem cleared up.  OH, I'm using an ATI 4770 video card.</p><p>I filed a couple of bug reports, but never heard anything back.</p><p>Looks like SOE may still need to do some work to the 3.0 drivers.  Not surprising as they appears to be new to SOE's tool box.  Hopefully, they'll get a bit more experience and get us some new drivers.</p>

Rangy Bear
03-28-2011, 03:29 PM
<p>OH, I almost forgot: Since the new expac, and running the shader 3.0 stuff, I had been encountering major lag in zoning.  Several times I got kicked back to character select while zoning.  So far, only 2 day, since I switched back to shader 1.0, I have not encounterd the lag in zoning nor been kicked to character select.</p>

TSR-JoshuaM
03-28-2011, 03:39 PM
<p>Few initial steps we need to cover before we move on with more troubleshooting.</p><p>Update video card drivers to latest available from the manufacturers website (www.ati.com or <a href="http://www.nvidia.com" target="_blank" rel="nofollow">www.nvidia.com</a>)</p><p>Update to the June 2010 revision of DirectX 9.0c</p><p><span style="font-family: Arial; font-size: x-small;"><a href="http://launch.soe.com/eq2 " target="_blank">[EQII] LaunchPad</a></span></p><p>And finally, clear the cache/settings for your EQ2.</p><p><p>You may want to make backups and then delete the following files and folders:</p><p>cache folder</p><p>eq2_recent.ini</p><p>eq2_default.ini</p><p>EverQuest2.exe</p><p>eq2.ini</p><p>As well as the character specific files, these will appear as such:</p><p>Servername_CharacterName_EQ2_uisettings.ini</p><p>Stationname_characters.ini</p><p>To do this, please follow these directions:</p><p>1. First look for your EverQuest II directory. You can find the default directory in (for Windows XP): C:Program FilesSonyEverQuest II (for Windows Vista/7): C:Program DataSony Online EntertainmentInstalled GamesEverQuest II</p><p>2. Click on MY COMPUTER and then proceed into local disk C:</p><p>3. Navigate your way to the default directory, or your chosen installation directory.</p><p>4. Next look for any files explained above and delete them. </p><p>5. Afterwards, please start EverQuest II to have these files re-downloaded by the patcher.</p><p>If deleting these files does not resolve your issue, you can restore your backed up files and folders and retain your hotkeys, contact lists, and display settings.</p></p>

Rangy Bear
03-31-2011, 04:12 PM
<p>Over the course of the last 6 or 7 years I've encounterd various graphic problems with EQ2.  Not really a big deal, just annoying.  Anyway, I'm familar with the procedured that Joshua Outlined and had already done these.  I was still having the strange graphics issues with the ground missing and some other strange issues.  Once I disabled the shade3.0 stuff my problems pretty well resolved themselves. </p><p>Like I said earlier, I suspect that there may be some more tunning required on the new shader stuff.  Not a big deal, it just take a little time for the devs to get a better grasp on the new tools and learn some of the hidden ins and outs and how to better tune the procedures to do what they want them to do.  Not to mentions what hidden bugs, or is that features, they may uncover in the libraries that they are using.</p>

TSR-JoshuaM
03-31-2011, 04:24 PM
<p><div><p>I cannot reproduce the issue with any setting so I want to look in to it deeper.  Those areas with Shader 3 work for me and I have tried many different configurations and systems.  </p><p>Are you using the multi-game Station Launcher or the latest streaming LaunchPad?  If you are using the LaunchPad, did you happen to migrate to it from a Station Launcher installation or was it a fresh LaunchPad stand-alone install? </p></div></p>

Rangy Bear
03-31-2011, 04:43 PM
<p>When I purchased this system last fall, I did a fresh install of SF using installiation CDs so I'm using whatever launchpad comes with the standard version of SF.  I hope to upgrade to the DoV expac sometime after the first whne I get paid.</p><p>I'm going to try and re-enable the Shader 3.0 options this evening and see what happens.</p><p>THere use to be a complete scan option on the older launcher, but I've been unable to find one on the current newer laundcher. Just wondering if doing a complete scan might help.</p><p>Thanks,</p><p>John</p>

TSR-JoshuaM
03-31-2011, 05:22 PM
<p>Our current LaunchPad does have a scan feature and installing a fresh copy using the streaming launcher may be able to resolve this issue for you if it exists in the assets themselves.</p><p><a href="http://launch.soe.com/eq2" target="_blank">[EQII] LaunchPad</a></p>

Rangy Bear
03-31-2011, 05:50 PM
<p>I just checked and there is a new video driver for my card. It looks like it came out yesterday. Finished downloading and installed it.  I'll be testing shortly</p><p>Also, I was under the impression that Shader 3.0 needed a minimum of DirectX 10.1 to work correctly.  I have DirectX 11 installed.</p><p>Thanks,</p><p>John</p>

TSR-JoshuaM
03-31-2011, 05:57 PM
<p>Chances are you have DX9, 10, and 11 installed.  That's just how it works, they co-exist.  Let me know how the test turns out.</p>

Rangy Bear
03-31-2011, 06:19 PM
<p>Well, as soon as I turn on the shader 3.0 options, the ground disappeared on the Dreadnever Crash Site. I have a screen shot and it does look interesting.  Just can't see the ground.  I'll turn the Shader 3.0 off to verify that the ground returns. This is amusing.  It'd be kind of fun if it were not so  hazadours to the toons health.</p><p>To bad I can't attach an image.  THe insert image option wants an URL.  No upload option.  Oh well.</p><p>Regards,</p><p>John</p><p>Update: As soon as I swithch the Shader 3 option off, the ground is visiable once again.  Interesting, verrrrry interesting.</p><p>John</p>

TSR-JoshuaM
03-31-2011, 06:49 PM
<p>Would you mind installing the streaming LaunchPad to a new folder and immediately logging in to that character and turning on Shader 3? You can jump in to game immediately while it downloads everything.  I suggest parking your character in the problematic area (so the first things the game is forced to download are those models).</p>

Zarkan
04-01-2011, 02:55 AM
<p>As mentioned in <a href="http://forums.station.sony.com/eq2/posts/list.m?topic_id=497557">another thread</a> i have the same problems with the Dreadnever Crash Site and Shader 3.0. I've tried what you suggested and went to another pc without Everquest 2, installed the streaming launcher and immediately logged in (without downloading the whole game). There's no ground with Shader 3.0. The PC's have both Windows 7 64 Bit and the AMD/ATI-Driver 11.02.</p>

TSR-JoshuaM
04-01-2011, 12:05 PM
<p>Zarkan, can you PM me the contents of your LaunchPad.log and LaunchPad.ini?</p>

Rangy Bear
04-01-2011, 04:25 PM
<p>Joshua,</p><p>Here is the DXDIAG list from my machine.  Still waiting for the streaming to finish.  this takes bloody forever!</p><p><p>------------------</p><p>System Information</p><p>------------------</p><p>Time of this report: 4/1/2011, 14:17:30</p><p>       Machine name: DESKTOP</p><p>   Operating System: Windows 7 Home Premium 64-bit (6.1, Build 7601) Service Pack 1 (7601.win7sp1_rtm.101119-1850)</p><p>           Language: English (Regional Setting: English)</p><p>System Manufacturer: HP-Pavilion</p><p>       System Model: NY553AA-ABA e9220y</p><p>               BIOS: BIOS Date: 08/31/09 13:56:34 Ver: 5.02</p><p>          Processor: AMD Phenom(tm) II X4 910 Processor (4 CPUs), ~2.6GHz</p><p>             Memory: 8192MB RAM</p><p>Available OS Memory: 8184MB RAM</p><p>          Page File: 3063MB used, 13302MB available</p><p>        Windows Dir: C:Windows</p><p>    DirectX Version: DirectX 11</p><p>DX Setup Parameters: Not found</p><p>   User DPI Setting: Using System DPI</p><p> System DPI Setting: 96 DPI (100 percent)</p><p>    DWM DPI Scaling: Disabled</p><p>     DxDiag Version: 6.01.7601.17514 32bit Unicode</p><p>------------</p><p>DxDiag Notes</p><p>------------</p><p>      Display Tab 1: No problems found.</p><p>        Sound Tab 1: No problems found.</p><p>        Sound Tab 2: No problems found.</p><p>          Input Tab: No problems found.</p><p>--------------------</p><p>DirectX Debug Levels</p><p>--------------------</p><p>Direct3D:    0/4 (retail)</p><p>DirectDraw:  0/4 (retail)</p><p>DirectInput: 0/5 (retail)</p><p>DirectMusic: 0/5 (retail)</p><p>DirectPlay:  0/9 (retail)</p><p>DirectSound: 0/5 (retail)</p><p>DirectShow:  0/6 (retail)</p><p>---------------</p><p>Display Devices</p><p>---------------</p><p>          Card name: ATI Radeon HD 4770</p><p>       Manufacturer: ATI Technologies Inc.</p><p>          Chip type: ATI display adapter (0x94B3)</p><p>           DAC type: Internal DAC(400MHz)</p><p>         Device Key: EnumPCIVEN_1002&DEV_94B3&SUBSYS_29001682&REV_00</p><p>     Display Memory: 240 MB</p><p>   Dedicated Memory: 500 MB</p><p>      Shared Memory: 3835 MB</p><p>       Current Mode: 1920 x 1080 (32 bit) (59Hz)</p><p>       Monitor Name: Generic PnP Monitor</p><p>      Monitor Model: W2361</p><p>         Monitor Id: GSM56FA</p><p>        Native Mode: 1920 x 1080(p) (59.934Hz)</p><p>        Output Type: DVI</p><p>        Driver Name: aticfx64.dll,aticfx64.dll,aticfx64.dll,aticfx32,at icfx32,aticfx32,atiumd64.dll,atidxx64.dll,atidxx64 .dll,atiumdag,atidxx32,atidxx32,atiumdva,atiumd6a. cap,atitmm64.dll</p><p>Driver File Version: 8.17.0010.1070 (English)</p><p>     Driver Version: 8.831.2.0</p><p>        DDI Version: 10.1</p><p>       Driver Model: WDDM 1.1</p><p>  Driver Attributes: Final Retail</p><p>   Driver Date/Size: 3/9/2011 00:55:52, 795136 bytes</p><p>        WHQL Logo'd: Yes</p><p>    WHQL Date Stamp: </p><p>  Device Identifier: {D7B71EE2-D7F3-11CF-1C71-0A09BEC2C535}</p><p>          Vendor ID: 0x1002</p><p>          Device ID: 0x94B3</p><p>          SubSys ID: 0x29001682</p><p>        Revision ID: 0x0000</p><p> Driver Strong Name: oem48.inf:ATI.Mfg.NTamd64.6.1:ati2mtag_RV7X:8.831. 2.0:pciven_1002&dev_94b3&subsys_29001682</p><p>     Rank Of Driver: 00E60001</p><p>        Video Accel: ModeMPEG2_A ModeMPEG2_C </p><p>   Deinterlace Caps: {6E8329FF-B642-418B-BCF0-BCB6591E255F}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive </p><p>                     {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 </p><p>                     {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY </p><p>                     {6E8329FF-B642-418B-BCF0-BCB6591E255F}: Format(In/Out)=(UYVY,UYVY) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive </p><p>                     {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 </p><p>                     {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(UYVY,UYVY) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY </p><p>                     {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(YV12,0x32315659) Frames(Prev/Fwd/Back)=(0,0,0) Caps=</p><p>                     {3C5323C1-6FB7-44F5-9081-056BF2EE449D}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,2) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive </p><p>                     {552C0DAD-CCBC-420B-83C8-74943CF9F1A6}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,2) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive </p><p>                     {6E8329FF-B642-418B-BCF0-BCB6591E255F}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive </p><p>                     {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 </p><p>                     {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY </p><p>                     {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC1,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=</p><p>                     {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=</p><p>                     {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC3,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=</p><p>                     {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC4,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=</p><p>                     {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(S340,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=</p><p>                     {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(S342,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=</p><p>       D3D9 Overlay: Not Supported</p><p>            DXVA-HD: Not Supported</p><p>       DDraw Status: Enabled</p><p>         D3D Status: Enabled</p><p>         AGP Status: Enabled</p><p>-------------</p><p>Sound Devices</p><p>-------------</p><p>            Description: Headphones (Realtek High Definition Audio)</p><p> Default Sound Playback: Yes</p><p> Default Voice Playback: Yes</p><p>            Hardware ID: HDAUDIOFUNC_01&VEN_10EC&DEV_0888&SUBSYS_103C2A92&REV_1002</p><p>        Manufacturer ID: 1</p><p>             Product ID: 100</p><p>                   Type: WDM</p><p>            Driver Name: RTKVHD64.sys</p><p>         Driver Version: 6.00.0001.6196 (English)</p><p>      Driver Attributes: Final Retail</p><p>            WHQL Logo'd: Yes</p><p>          Date and Size: 9/7/2010 12:27:34, 2484072 bytes</p><p>            Other Files: </p><p>        Driver Provider: Realtek Semiconductor Corp.</p><p>         HW Accel Level: Basic</p><p>              Cap Flags: 0xF1F</p><p>    Min/Max Sample Rate: 100, 200000</p><p>Static/Strm HW Mix Bufs: 1, 0</p><p> Static/Strm HW 3D Bufs: 0, 0</p><p>              HW Memory: 0</p><p>       Voice Management: No</p><p> EAX(tm) 2.0 Listen/Src: No, No</p><p>   I3DL2(tm) Listen/Src: No, No</p><p>Sensaura(tm) ZoomFX(tm): No</p><p>            Description: Realtek Digital Output (Realtek High Definition Audio)</p><p> Default Sound Playback: No</p><p> Default Voice Playback: No</p><p>            Hardware ID: HDAUDIOFUNC_01&VEN_10EC&DEV_0888&SUBSYS_103C2A92&REV_1002</p><p>        Manufacturer ID: 1</p><p>             Product ID: 100</p><p>                   Type: WDM</p><p>            Driver Name: RTKVHD64.sys</p><p>         Driver Version: 6.00.0001.6196 (English)</p><p>      Driver Attributes: Final Retail</p><p>            WHQL Logo'd: Yes</p><p>          Date and Size: 9/7/2010 12:27:34, 2484072 bytes</p><p>            Other Files: </p><p>        Driver Provider: Realtek Semiconductor Corp.</p><p>         HW Accel Level: Basic</p><p>              Cap Flags: 0xF1F</p><p>    Min/Max Sample Rate: 100, 200000</p><p>Static/Strm HW Mix Bufs: 1, 0</p><p> Static/Strm HW 3D Bufs: 0, 0</p><p>              HW Memory: 0</p><p>       Voice Management: No</p><p> EAX(tm) 2.0 Listen/Src: No, No</p><p>   I3DL2(tm) Listen/Src: No, No</p><p>Sensaura(tm) ZoomFX(tm): No</p><p>---------------------</p><p>Sound Capture Devices</p><p>---------------------</p><p>            Description: Microphone (Realtek High Definition Audio)</p><p>  Default Sound Capture: Yes</p><p>  Default Voice Capture: Yes</p><p>            Driver Name: RTKVHD64.sys</p><p>         Driver Version: 6.00.0001.6196 (English)</p><p>      Driver Attributes: Final Retail</p><p>          Date and Size: 9/7/2010 12:27:34, 2484072 bytes</p><p>              Cap Flags: 0x1</p><p>           Format Flags: 0xFFFFF</p><p>-------------------</p></p>

Rangy Bear
04-01-2011, 05:15 PM
<p>Well, after 4+ hours of downloading the streaming version, I ran the test.  As soon as I enabled the shader 3.0 option the ground disappeared.  Disabled Shader 3.0 and the ground shows up.  </p><p>Do you want the launder log and ini file from my system as well?</p><p>John</p>

TSR-JoshuaM
04-01-2011, 06:10 PM
<p>Yes please.</p>

Zarkan
04-01-2011, 09:49 PM
<p>.int and .log is send via pm. In three parts due to the pm size limit of 20k.</p>

Breanor
04-02-2011, 02:08 AM
<p>Not sure if they may be related but I am having a similarly strange graphics issue.  I will be playing for a few minutes and everything is fine, then my frame rate drops to 1 - 5 FPS and stays there for 30seconds to over a minute...  I have been monitoring with Resource monitor and other tools and am not seeing anything out of the ordinary... I am trying the steps mentioned in your earlier post about removing cache files and specific settings currently and will post as to how that works.</p>

TSR-JoshuaM
04-06-2011, 05:21 PM
<p>We're still tracking and working on a resolution for this issue.  I'm doing more testing here myself shortly.</p>