So here we are again, used to be getting through a dungeon alive was a problem, now getting through a dungeon without crashing must be the new challenge. Not my computer, not my graphic cards running in crossfire, its the game. Whats odd is some days are better than others, but still crash on the good days.
Specs: Windows 10/64 MB Rampage Extreme Ram 64 Gigs HD 10 TBS Graphics watercooled by EK waterblocks on an independent radiator: 2 290x cu2 in crossfire processor 4790 watercooled by corsair independent power supply 1600 watt:
Its a mean system, that being said, fix the friggin game!!!
------------------ System Information ------------------ Time of this report: 5/16/2017, 06:17:24 Machine name: *****-PC Operating System: Windows 7 Home Premium 64-bit (6.1, Build 7601) Service Pack 1 (7601.win7sp1_ldr.170427-1518) Language: English (Regional Setting: English) System Manufacturer: Acer System Model: Aspire 5733Z BIOS: InsydeH2O Version V1.07 Processor: Intel(R) Pentium(R) CPU P6200 @ 2.13GHz (2 CPUs), ~2.1GHz Memory: 4096MB RAM Available OS Memory: 3766MB RAM Page File: 1171MB used, 6360MB 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 64bit Unicode
------------ DxDiag Notes ------------ Display Tab 1: No problems found. Sound Tab 1: No problems found. Input Tab: No problems found.
I can get into the game and as long as I'm just on to do jobs, pick up my key, do AH, everything is ok. I redid my DirectX since that's the error message I get and was even able to go out and fight. However as soon as I tried to party with someone for a quest the whole error problem came back even worse then what it was before. PLEASE HELP I tired of not being able to play and I haven't even been able to start the new expanse that came out.
stealth is survival skills (and not tanking skills, that is really different)
stealth is damage
stealth is mobility
stealth is everything
everything is stealth
Stealth make TR OP, but lack of stealth make TR useless.
I'll have a dig and see if I can find some of this information then. I'm no techie, but I'll put out what I can find. I plead ignorance if I post anything that's not relevant, though!
[... Trimmed ..]
Thank you for posting this information, and this does give this the developer an idea as to where to start looking. The only other Idea I have is to gather more information on the graphics card. I know that AMD includes a utility that makes it easy to find out about the current hardware and software, and the utility is fairly straight forward to use.
Right click on the desktop.
The list of options at this point should include "AMD Radeon Settings", click this option.
On the Main page of the "AMD Radeon Settings" utility click on the "System" tab.
The current tab under the "System" should be the "Overview" tab. This tab should contain some extra information that can help the developers. At this point click the "Copy All" button on the upper right.
post this information in the forum. For example, My current system says the following...
Radeon Software Version - 17.4.3 Radeon Software Edition - Crimson ReLive Graphics Chipset - AMD Radeon (TM) R9 Fury Series Memory Size - 4096 MB Memory Type - High Bandwidth Memory (HBM) Core Clock - 1050 MHz Windows Version - Windows 10 (64 bit) System Memory - 16 GB CPU Type - AMD FX-8320E Eight-Core Processor
Here you go. Did all that.
Radeon Software Version - 17.1.1 Radeon Software Edition - Crimson ReLive Graphics Chipset - AMD Radeon R9 200 Series Memory Size - 4096 MB Memory Type - GDDR5 Core Clock - 1000 MHz Windows Version - Windows 10 (64 bit) System Memory - 32 GB CPU Type - Intel(R) Core(TM) i5-4690K CPU @ 3.50GHz
I notice at least that my Radeon Software Version appears to be older than yours (.1 instead of .4), but the driver tells me it's up to date... so not sure.
Thanks for the reply. Hopefully that gives people a little more idea where I can poke next.
Radeon Software Version - 17.1.1 Radeon Software Edition - Crimson ReLive Graphics Chipset - AMD Radeon R9 200 Series Memory Size - 4096 MB Memory Type - GDDR5 Core Clock - 1000 MHz Windows Version - Windows 10 (64 bit) System Memory - 32 GB CPU Type - Intel(R) Core(TM) i5-4690K CPU @ 3.50GHz
I notice at least that my Radeon Software Version appears to be older than yours (.1 instead of .4), but the driver tells me it's up to date... so not sure.
Thanks for the reply. Hopefully that gives people a little more idea where I can poke next.
I believe it would be a really good idea to redownload the driver from AMD's Website( http://support.amd.com/en-us ). Windows update CAN AND WILL automatically downgrade your driver. I just had windows update forcibly downgrade the driver from what I was running (17.4.3) to the 17.1.1 driver version.
As far as driver version I recommend going with Crimson ReLive 17.4.4 seeing as how this is the latest WHQL version, however if you want the absolute latest driver you can use Crimson ReLive 17.5.1.
I'm really disappointed. VIP runs out tomorrow. Can't say I'm even going to log back in much to contribute to any "crash logging."
Based on how long this is taking, the issue is more likely eliminating itself though people quitting. I mean, who keeps hitting their head on a brick wall for 16-17-18+ days in a row?
Here are the facts. Things worked before May 2. Things have not worked since May 2. Also, major graphics changes were made on May 2, and major graphics issues have been preventing a significant amount of people from playing since May 2. Obviously there's a historical solution available.
Its incredible isn't it that this still isn't fixed?
Radeon Software Version - 17.1.1 Radeon Software Edition - Crimson ReLive Graphics Chipset - AMD Radeon R9 200 Series Memory Size - 4096 MB Memory Type - GDDR5 Core Clock - 1000 MHz Windows Version - Windows 10 (64 bit) System Memory - 32 GB CPU Type - Intel(R) Core(TM) i5-4690K CPU @ 3.50GHz
I notice at least that my Radeon Software Version appears to be older than yours (.1 instead of .4), but the driver tells me it's up to date... so not sure.
Thanks for the reply. Hopefully that gives people a little more idea where I can poke next.
I believe it would be a really good idea to redownload the driver from AMD's Website( http://support.amd.com/en-us ). Windows update CAN AND WILL automatically downgrade your driver. I just had windows update forcibly downgrade the driver from what I was running (17.4.3) to the 17.1.1 driver version.
As far as driver version I recommend going with Crimson ReLive 17.4.4 seeing as how this is the latest WHQL version, however if you want the absolute latest driver you can use Crimson ReLive 17.5.1.
Did that last night after the recent patch meant instant restarts three times in a row, and to be fair, it ran like a dream for the entire night and I only had one loading screen lock. I thought that was going great.
Tried this morning... I've had three device hung issues in the first twenty minutes and barely managed to get anywhere.
Seems now that the Safe Mode is even hit and miss and you try until something works and play it while you can once it does.
Any further ideas? I haven't changed anything on the machine except the graphics driver to the 17.4 version.
EDIT: It's... significantly worse than it has been for a week or so, now, following the mid May patch update. Something... is again more wrong than it was before. I'm getting Device Removed and Device Hung issues after maybe 10 minutes of play now if I'm lucky.
It's crazy.....I bought some zen before the upgrade and can't even spend it,you guys need to put in some effort to fix this!!!
I did the same; ended up rage-spending it on keys a few days after the bug had rendered it impossible to do anything other than stand there, comatose. Wouldn't you know; the Universe finally opened up, and after years of key purchases, I finally landed an Orange mount I'll probably never be able to use. Oh, the irony. To laugh or cry? Lolz
It would be nice to get an orange mount. I've been a customer for years and very little to show for it now lol. Congrats? I guess.
Relmyna - AC/DC Righteous + Haste| Nadine - CW MoF (working on it)|Buffy - GF SM Tact| Hrist - Justice Tankadin|Healadin (Wannabe Tank)| Lena -MI Sabo TR (Farmer) | Jeska - GWF SM Destroyer (Farmer) | Maggie - HR PF Trapper (Wannabe DPS)
--
I'll never retrace my steps.
I've been crashing every 10-15 minutes, mostly when either 1) changing characters - 8 total, 2) playing in small groups, 3) playing in large groups, 4) moving to SH - sometimes takes 2 or 3 tries, 5) moving to any other play area, or 6) just standing around or moving around. My system is current and stable with any other program. This problem has gotten worse all month. I keep sending in the Cryptic Error Reporting stuff that comes up after each crash. Can't the Devs see what's going on with that app? Anyway, this must get fixed or I simply won't be able to play.
20 days.. still no fix for the same issue I've been reporting over and over. It's really feeling hopeless.
I can't understand why they just don't get a similar Intel onboard system, it's old and cheap, few hundred dollars, and even that doubtfully. Usually in a software company with internal QA, the IT has old stuff laying around or can get / loan it. And just run the debug on it. Once it's established with enough confidence that it's a specific platform issue it's can be easily reproduced without crashing users on preview on weekly basis. Now each test is on a weekly basis: change something, wait a week for a preview push, get results, repeat. When it can be immediate with minimal investment and resolved in few hours.
The current build on Preview Server seems to have stopped my device removed error. I encourage anyone here who was having problems to check it out. It's possible that they fixed it.
Relmyna - AC/DC Righteous + Haste| Nadine - CW MoF (working on it)|Buffy - GF SM Tact| Hrist - Justice Tankadin|Healadin (Wannabe Tank)| Lena -MI Sabo TR (Farmer) | Jeska - GWF SM Destroyer (Farmer) | Maggie - HR PF Trapper (Wannabe DPS)
--
I'll never retrace my steps.
> @bitt3rnightmar3 said: > The current build on Preview Server seems to have stopped my device removed error. I encourage anyone here who was having problems to check it out. It's possible that they fixed it.
Really noob question, I'm sure but how do I get on to the preview shard to try it?
> The current build on Preview Server seems to have stopped my device removed error. I encourage anyone here who was having problems to check it out. It's possible that they fixed it.
Really noob question, I'm sure but how do I get on to the preview shard to try it?
I've quoted the important bits. Please note to test the build I was referring to you'll need to go to Mimic or Preview.
The NeverwinterPreview shard is a place to preview upcoming content, game and class balance changes, and other improvements to the game. By playing on Preview, you'll be able to provide invaluable feedback on what can be improved and changed before updates go to the Neverwinter live shards.
Getting set up on NeverwinterPreview (Mimic) or Owlbear* is easy! Simply follow these steps:
Click the "Sign Up!" button. This makes your account Preview enabled, and allows you to select "NeverwinterPreview" and "Owlbear" as a shard in the Neverwinter launcher. Now, you'll be able to make a new character and play on NeverwinterPreview and Owlbear, or...
On the next page, select one of your previously existing characters from the dropdown menu.
Select Mimic or Owlbear as the destination to copy the character in the following dropdown menu.
Press the Copy button.
Open your Neverwinter launcher, select the NeverwinterPreview shard or Owlbear shard, and wait for your client to patch.
Launch the game. If you copied your character over, you will now see it on NeverwinterPreview or Owlbear respectively.
Otherwise, you will have to make a new character.
Please note that copying a character to NeverwinterPreview and Owlbear will not affect your character on the Neverwinter live shards in any way, and certain account features (such as buying and spending Zen) are not available on NeverwinterPreview.
* What is the Difference beteween Mimic and Owlbear? When there is a New Module on Mimic, Owlbear is used instead for testing of patches that will be published to Dragon prior to the release of the Module in testing on Mimic. If Owlbearis available, you'll also have the option to patch that test server in the launcher, as well as be able to transfer characters there too. Mimic and Owlbear are two entirely separate testing environments and as such will each require their own patched installations.
Now go, have fun and don't forget to let us know what issues you find here in this Testing Forum! Be sure to remember to label your threads with either [Mimic] or [Owlbear] to show which Preview Shard the issue is on, or use any existing thread's specifically for them.
Relmyna - AC/DC Righteous + Haste| Nadine - CW MoF (working on it)|Buffy - GF SM Tact| Hrist - Justice Tankadin|Healadin (Wannabe Tank)| Lena -MI Sabo TR (Farmer) | Jeska - GWF SM Destroyer (Farmer) | Maggie - HR PF Trapper (Wannabe DPS)
--
I'll never retrace my steps.
Any idea when that may happen? Because I've yet to have a single day playing this game without a crash or device hung issue... and I really do enjoy it amongst the pauses and reloads and stuff.
Any idea when that may happen? Because I've yet to have a single day playing this game without a crash or device hung issue... and I really do enjoy it amongst the pauses and reloads and stuff.
Usually, the builds that are on preview to test are the same ones that go live the following week if they are in the same module we're in. In the patch notes for the current build it lists 'Shroud of Souls' so that would lead me to believe that on this coming Thursday, June 1st the build would patched to live. It might be worth checking to make sure the build on preview is working for you too if you haven't already.
Any idea when that may happen? Because I've yet to have a single day playing this game without a crash or device hung issue... and I really do enjoy it amongst the pauses and reloads and stuff.
Usually, the builds that are on preview to test are the same ones that go live the following week if they are in the same module we're in. In the patch notes for the current build it lists 'Shroud of Souls' so that would lead me to believe that on this coming Thursday, June 1st the build would patched to live. It might be worth checking to make sure the build on preview is working for you too if you haven't already.
No dice. Logged in well enough. Had the guitar in hand waiting because the loading bar was much longer than normal, which I assumed was normal for a first time on the preview screen, and then my character stood there for a few minutes and it all crashed out with Device Removed, Device Hung comments again.
Comments
Any news on a possible fix for this? It will be 2 weeks tomorrow since many people affected by this would have been able to play, myself included.
--
I'll never retrace my steps.
Some of my best friends are Imaginary.
Specs:
Windows 10/64
MB Rampage Extreme
Ram 64 Gigs
HD 10 TBS
Graphics watercooled by EK waterblocks on an independent radiator: 2 290x cu2 in crossfire
processor 4790 watercooled by corsair independent
power supply 1600 watt:
Its a mean system, that being said, fix the friggin game!!!
System Information
------------------
Time of this report: 5/16/2017, 06:17:24
Machine name: *****-PC
Operating System: Windows 7 Home Premium 64-bit (6.1, Build 7601) Service Pack 1 (7601.win7sp1_ldr.170427-1518)
Language: English (Regional Setting: English)
System Manufacturer: Acer
System Model: Aspire 5733Z
BIOS: InsydeH2O Version V1.07
Processor: Intel(R) Pentium(R) CPU P6200 @ 2.13GHz (2 CPUs), ~2.1GHz
Memory: 4096MB RAM
Available OS Memory: 3766MB RAM
Page File: 1171MB used, 6360MB 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 64bit Unicode
------------
DxDiag Notes
------------
Display Tab 1: No problems found.
Sound Tab 1: 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: Intel(R) HD Graphics
Manufacturer: Intel Corporation
Chip type: Intel(R) HD Graphics (Pentium)
DAC type: Internal
Device Key: Enum\PCI\VEN_8086&DEV_0046&SUBSYS_06011025&REV_02
Display Memory: 1755 MB
Dedicated Memory: 128 MB
Shared Memory: 1627 MB
Current Mode: 1280 x 768 (32 bit) (60Hz)
Monitor Name: Generic PnP Monitor
Monitor Model: unknown
Monitor Id: AUO26EC
Native Mode: 1366 x 768(p) (60.014Hz)
Output Type: Internal
Driver Name: igdumd64.dll,igd10umd64.dll,igdumdx32,igd10umd32
Driver File Version: 8.15.0010.2993 (English)
Driver Version: 8.15.10.2993
DDI Version: 10
Driver Model: WDDM 1.1
Driver Attributes: Final Retail
Driver Date/Size: 2/19/2013 14:44:10, 8314368 bytes
WHQL Logo'd: Yes
WHQL Date Stamp:
Device Identifier: {D7B78E66-4306-11CF-2478-0B26A2C2C535}
Vendor ID: 0x8086
Device ID: 0x0046
SubSys ID: 0x06011025
Revision ID: 0x0002
Driver Strong Name: oem14.inf:IntelGfx.NTamd64.6.0:iILKM0:8.15.10.2993:pci\ven_8086&dev_0046
Rank Of Driver: 00E62001
Video Accel: ModeMPEG2_A ModeMPEG2_C ModeWMV9_B ModeWMV9_C ModeVC1_B ModeVC1_C
Deinterlace Caps: {BF752EF6-8CC4-457A-BE1B-08BD1CAEEE9F}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_EdgeFiltering
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_BOBVerticalStretch
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend
{BF752EF6-8CC4-457A-BE1B-08BD1CAEEE9F}: Format(In/Out)=(UYVY,YUY2) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_EdgeFiltering
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(UYVY,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_BOBVerticalStretch
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(UYVY,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend
{BF752EF6-8CC4-457A-BE1B-08BD1CAEEE9F}: Format(In/Out)=(YV12,YUY2) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_EdgeFiltering
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(YV12,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_BOBVerticalStretch
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(YV12,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend
{BF752EF6-8CC4-457A-BE1B-08BD1CAEEE9F}: Format(In/Out)=(NV12,YUY2) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_EdgeFiltering
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(NV12,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_BOBVerticalStretch
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(NV12,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend
{BF752EF6-8CC4-457A-BE1B-08BD1CAEEE9F}: Format(In/Out)=(IMC1,YUY2) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_EdgeFiltering
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(IMC1,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_BOBVerticalStretch
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC1,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend
{BF752EF6-8CC4-457A-BE1B-08BD1CAEEE9F}: Format(In/Out)=(IMC2,YUY2) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_EdgeFiltering
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(IMC2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_BOBVerticalStretch
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend
{BF752EF6-8CC4-457A-BE1B-08BD1CAEEE9F}: Format(In/Out)=(IMC3,YUY2) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_EdgeFiltering
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(IMC3,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_BOBVerticalStretch
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC3,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend
{BF752EF6-8CC4-457A-BE1B-08BD1CAEEE9F}: Format(In/Out)=(IMC4,YUY2) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_EdgeFiltering
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(IMC4,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_BOBVerticalStretch
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC4,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend
D3D9 Overlay: Supported
DXVA-HD: Supported
DDraw Status: Enabled
D3D Status: Enabled
AGP Status: Enabled
stealth is damage
stealth is mobility
stealth is everything
everything is stealth
Stealth make TR OP, but lack of stealth make TR useless.
--
I'll never retrace my steps.
Some of my best friends are Imaginary.
Here you go. Did all that.
Radeon Software Version - 17.1.1
Radeon Software Edition - Crimson ReLive
Graphics Chipset - AMD Radeon R9 200 Series
Memory Size - 4096 MB
Memory Type - GDDR5
Core Clock - 1000 MHz
Windows Version - Windows 10 (64 bit)
System Memory - 32 GB
CPU Type - Intel(R) Core(TM) i5-4690K CPU @ 3.50GHz
I notice at least that my Radeon Software Version appears to be older than yours (.1 instead of .4), but the driver tells me it's up to date... so not sure.
Thanks for the reply. Hopefully that gives people a little more idea where I can poke next.
a) Takes more than 5 mins to load the game
b) The Neverwinter client is using 1.4gb of RAM memory
c) The fan goes ballistic just prior to crash
A computer WITHOUT the problem [a different Intel integrated video card]
a) Takes less than a minute to load the game
b) The Nevewinter client is only using c700mb of RAM memory
As far as driver version I recommend going with Crimson ReLive 17.4.4 seeing as how this is the latest WHQL version, however if you want the absolute latest driver you can use Crimson ReLive 17.5.1.
--
I'll never retrace my steps.
Some of my best friends are Imaginary.
Tried this morning... I've had three device hung issues in the first twenty minutes and barely managed to get anywhere.
Seems now that the Safe Mode is even hit and miss and you try until something works and play it while you can once it does.
Any further ideas? I haven't changed anything on the machine except the graphics driver to the 17.4 version.
EDIT: It's... significantly worse than it has been for a week or so, now, following the mid May patch update. Something... is again more wrong than it was before. I'm getting Device Removed and Device Hung issues after maybe 10 minutes of play now if I'm lucky.
It would be nice to get an orange mount. I've been a customer for years and very little to show for it now lol. Congrats? I guess.
--
I'll never retrace my steps.
Some of my best friends are Imaginary.
HP Pavillion i5 processor with Intel Iris 5100, 8GB ram
--
I'll never retrace my steps.
Some of my best friends are Imaginary.
--
I'll never retrace my steps.
Some of my best friends are Imaginary.
> The current build on Preview Server seems to have stopped my device removed error. I encourage anyone here who was having problems to check it out. It's possible that they fixed it.
Really noob question, I'm sure but how do I get on to the preview shard to try it?
TIA
https://www.arcgames.com/en/forums/neverwinter/#/discussion/1207208/welcome-to-neverwinterpreview-preview-testing-information
I've quoted the important bits. Please note to test the build I was referring to you'll need to go to Mimic or Preview.
- Go to http://www.arcgames.com/en/my/character/copy/nw
- Click the "Sign Up!" button. This makes your account Preview enabled, and allows you to select "NeverwinterPreview" and "Owlbear" as a shard in the Neverwinter launcher. Now, you'll be able to make a new character and play on NeverwinterPreview and Owlbear, or...
- On the next page, select one of your previously existing characters from the dropdown menu.
- Select Mimic or Owlbear as the destination to copy the character in the following dropdown menu.
- Press the Copy button.
- Open your Neverwinter launcher, select the NeverwinterPreview shard or Owlbear shard, and wait for your client to patch.
- Launch the game. If you copied your character over, you will now see it on NeverwinterPreview or Owlbear respectively.
- Otherwise, you will have to make a new character.
Please note that copying a character to NeverwinterPreview and Owlbear will not affect your character on the Neverwinter live shards in any way, and certain account features (such as buying and spending Zen) are not available on NeverwinterPreview.Getting set up on NeverwinterPreview (Mimic) or Owlbear* is easy! Simply follow these steps:
* What is the Difference beteween Mimic and Owlbear?
When there is a New Module on Mimic, Owlbear is used instead for testing of patches that will be published to Dragon prior to the release of the Module in testing on Mimic. If Owlbearis available, you'll also have the option to patch that test server in the launcher, as well as be able to transfer characters there too. Mimic and Owlbear are two entirely separate testing environments and as such will each require their own patched installations.
Now go, have fun and don't forget to let us know what issues you find here in this Testing Forum! Be sure to remember to label your threads with either [Mimic] or [Owlbear] to show which Preview Shard the issue is on, or use any existing thread's specifically for them.
--
I'll never retrace my steps.
Some of my best friends are Imaginary.
Just need them to put it on the actual server and looks like we're all back in business
https://www.arcgames.com/en/forums/neverwinter#/discussion/1231474/shroud-of-souls-preview-patch-notes-nw-80-20170515e-4/p1
--
I'll never retrace my steps.
Some of my best friends are Imaginary.
No luck yet.