Having same problem. On Win 8 here, was working fine before the patch. Has anyone tried running game without on demand patching?
I've changed pc regions to US from UK and re-patching now.
Never use on demand patching, it's the cause of so many bugs and lag issues, always use full patch, keep pc on at night, and patch the game, and then u'll never have those kind of problens.
Been with cryptic thru 3 betas, 4 games, and this is by and large the worst response from them EVER. At this point even a "We know we FUBARed you guys good, and no one can respond cause we're trying to fix it" would be nice (see, that took all of 30 seconds for me to post...come on DEVS)
RANT over, arc off, hopefully NEXT week i can play :[
It would be good customer support to write any type of comment from the devs or anybody else in this thread. The lack of response shows a big disrespect for the customers.
0
idontwinitskkMember, NW M9 PlaytestPosts: 43Arc User
It would be good customer support to write any type of comment from the devs or anybody else in this thread. The lack of response shows a big disrespect for the customers.
I'm just happy none of the *smart* mods have come here yet to explain how you need to disable cores,update video drives or something dumb like that.
Also apparently one of the answers to a support ticket regarding the issue was *Your graphics card is no longer compatible with our game*. Says alot now doesn't it?Screw up then tell people they need to change their systems lol k
I would say according to their written minimum system requirements i still fulfill them. And i can get it to work but have to use a workaround so they blame us when they have tested it correctly. My problem is that when the character screen should load the game crashes.
If i start the game in a small window and enter thr game with one char and change to fullscreen the game works. I have then no problem changing to another char after entered the world once.
That would mean that something is broken when the game starts.
0
idontwinitskkMember, NW M9 PlaytestPosts: 43Arc User
edited August 2014
Well it's obviously your fault the game isn't running properly.
I mean this wasn't an issue reported over a month ago so clearly you need to figure it out for yourself why you are suddenly experiencing problems after the new patch.
Hard release dates - such an easy excuse for lazy programming.
And the Game knows what Graphics card we use if not supported why not tell us?
Nja they don't know what they have messed up and therefore do not answer. There are many other problems ppl have with menus, windows and stuff all related to graphics.
Trying again to get any kind of answer, what do we need to fulfill because the Graphics requirements is: 3D video chipset with pixel and vertex shader model 1.3 supported. GeForce 4 Ti4200 64MB or ATI Radeon 8500 64MB or newer for Windows XP. For Windows Vista and 7, a GeForce FX 5200 128MB or ATI Radeon 9500 128MB or newer is needed.
And that is not hard to do because the cards mention is about 10 years old so why are we having these graphical problems?
Please do us a favor, devs: when you call GetRawInputDeviceList() and get either an error code or zero devices returned, BELIEVE IT and just fall back to DirectInput8. Please.
I've spent the last two days crawling through the assembly in win32k.sys to try to add raw-device support. Now, I can spend another week at it and *maybe* get it working, or you could realize that DirectInput8 != win32 raw-input support and not assume that supporting one guarantees supporting the other. Further, not every WINE implementation and/or user might fully support raw-input (which involves a tunnel to kernel code via user32.dll <--> win32k.sys), and the slightest bug will crash the kernel. A switch to force using DirectInput8 instead of raw-input might be warranted, ya think?
(to give you an idea of how much of a PITA this is for me, I have to...)
- get definitions of PROCESSINFO and THREADINFO structures for XP (thank the Heavens for ReactOS!)
- reverse-engineer PROCESSINFO and THREADINFO for Win2k (they *are* different!)
- reverse-engineer the internal raw-input structures in XP
- reverse-engineer the raw-input logic (because I have to...see below)
- determine the parts of the raw-input logic that apply to keyboard and mouse (which 2k has support for in win32k) and which apply to non-keyboard-mouse USB HID devices (which win2k win32k.sys doesn't suport)
- port raw-input routines from XP to 2k, modifying each as necessary to:
a. drop all HID support (which the code calls non-legacy)
b. adapt to 2k PROCESSINFO and THREADINFO structures (by the way, I had to mod 2k to allocate a larger PROCESSINFO to support the raw-input request linked-lists that all of this logic needs)
c. modify all existing pertinent routines in 2k win32k to include raw-input support (otherwise NW won't get any data). This includes making sure to add code to clean up the new linked-lists!
d. expand win32k's internal dispatch table (move data after it out of the way so it can grow first!) I've done this once before in an earlier patch -- I know how to do it, but it's a real pain.
e. modify user32.dll to add the new API routines that call win32k (actually, the easiest part)
f. modify 2k's existing DEVICEINFO logic to support returning a handle to a device-info object when a client requests a list of registered raw-input devices (done, finished that today)
g. be on the lookout for references to fields in structures that differ between 2k and XP (e.g. there's a reference to a field in PWND, and 2k has the field in a different place). This requires *really* being on my toes.
.
.
.
z. periodically test changes in a VM (easy to do, just time-consuming -- I have to do this for every 2k patch I release)
And probably a bunch of other things that I haven't even discovered yet. Or, you could just check the results of some function calls and act appropriately...
Harper Chronicles: Cap Snatchers (RELEASED) - NW-DPUTABC6X Blood Magic (RELEASED) - NW-DUU2P7HCO Children of the Fey (RELEASED) - NW-DKSSAPFPF Buried Under Blacklake (WIP) - NW-DEDV2PAEP The Redcap Rebels (WIP) - NW-DO23AFHFH
My Foundry playthrough channel: https://www.youtube.com/user/Ruskaga/featured
I wonder if they ever going to fix this... I think they will not ,since noone has the decency to inform us about what is wrong or how long will it take...:(
I guess we all have to start looking for new games to play.....
explain ? I loaded game in safe mode option in the game, no difference. Still crashes immediately. Or do you mean actually running your Pc in safe mode? This bug going on for this long affecting this many people with no response or fix is F'N BS.
Any word from the devs? I'm gratified to see that a fix is in the pipeline for the Linux problem so perhaps there is hope
I've been conducting major surgery on my win32k.sys and *might* be able to get mice working ingame in a couple of days, if I haven't just jinxed it. Just expanding the internal mouse message buffer and all of the involved routines took all day, and I still have a few more routines to work on (the worst of the mouse-related changes are over, though, I hope...). A fix from your end would be much more desirable; I'm cringing at the changes I'd have to make to get the keyboard working.
Harper Chronicles: Cap Snatchers (RELEASED) - NW-DPUTABC6X Blood Magic (RELEASED) - NW-DUU2P7HCO Children of the Fey (RELEASED) - NW-DKSSAPFPF Buried Under Blacklake (WIP) - NW-DEDV2PAEP The Redcap Rebels (WIP) - NW-DO23AFHFH
My Foundry playthrough channel: https://www.youtube.com/user/Ruskaga/featured
after spending the week end going through the forums, and emailing back and forth with tech support....i think they just dont have a clue what they did or how to fix it
explain ? I loaded game in safe mode option in the game, no difference. Still crashes immediately. Or do you mean actually running your Pc in safe mode? This bug going on for this long affecting this many people with no response or fix is F'N BS.
This on all counts
But I have to admit, I already care a lot less than I did over the weekend - I think going live with this bug is really going to cost in the long run.
0
adernathMember, Neverwinter Knight of the Feywild UsersPosts: 0Arc User
edited August 2014
I have dualboot but it would be weird to install the game on my linux system just because it doesnt work on the windows system ....
Suggestions to improve NW:
- Dualspec
- Better rewarding foundry and foundry pvp maps
- Custom PvP leagues with leaderboards instead of the current 'matchmaking'.
- Armory
- make jumping cost stamina (to reduce hopping in pvp)
0
koolywampusMember, NW M9 PlaytestPosts: 52Arc User
edited August 2014
I fail to understand why we are trying to fix this problem on our end. Making changes to you system may or may not allow you to play the game, and how will these changes affect your other programs. I was online when the 10 min. warning went out. I logged off and went about my day. A few hours later I opened the launcher and let the patch run. When it was done I hit "PLAY". Since that time it has crashed at the Neverwinter load screen, and I get error #32926681. I had my computer off between logging off and patching. So please tell me why I need to "fix" my computer to run the game again?
Oppohere draconem est preherndere vitam.
0
boghy89Member, Neverwinter Beta UsersPosts: 26Arc User
edited August 2014
Well the DD chest bugg made like 20+ pages and was active for 1 month so as the bugg, if they didnt add mod 4 i doubt it would be fixed, so now there is this problem that also affects me but i think its gonna take atleast 1 month for something to start happening.
Posting on this forum is pointless learned it the hardway no matter the severity of the bugg or the ppl affected they just slack, and the more u post or look into it the more frustrated u get, even garbage collectors have more respect for their work then Pw has for its own and the ppl who play/pay the game.
explain ? I loaded game in safe mode option in the game, no difference. Still crashes immediately. Or do you mean actually running your Pc in safe mode? This bug going on for this long affecting this many people with no response or fix is F'N BS.
I fail to understand why we are trying to fix this problem on our end. Making changes to you system may or may not allow you to play the game, and how will these changes affect your other programs. I was online when the 10 min. warning went out. I logged off and went about my day. A few hours later I opened the launcher and let the patch run. When it was done I hit "PLAY". Since that time it has crashed at the Neverwinter load screen, and I get error #32926681. I had my computer off between logging off and patching. So please tell me why I need to "fix" my computer to run the game again?
Normally you wouldn't have to; after all, it's their product, not ours.
However...
Since I'm running Windows 2000 (and, unless more people are aware of the post-EOL patch thread on MSFN than I think), I just might be the only one on 2k. There's always the possibility that Crypric could come back and say, "well, we didn't require raw-input API support before, but since XP has it, we are now." That would leave me stuck, so just in case I've started porting the API over. I've lost count of all the API's and security patches I've backported over the last four years, so it's worth a try, though the changes are so intrusive that I'd really much rather not.
At least I don't have to do anything to IE6. I gave up on backporting patches to that. Mshtml.dll is complicated beyond imagining.
Harper Chronicles: Cap Snatchers (RELEASED) - NW-DPUTABC6X Blood Magic (RELEASED) - NW-DUU2P7HCO Children of the Fey (RELEASED) - NW-DKSSAPFPF Buried Under Blacklake (WIP) - NW-DEDV2PAEP The Redcap Rebels (WIP) - NW-DO23AFHFH
My Foundry playthrough channel: https://www.youtube.com/user/Ruskaga/featured
I think we have identified at least a portion of these issues and have a fix going out to Preview today at 5pm.
0
koolywampusMember, NW M9 PlaytestPosts: 52Arc User
edited August 2014
Thank you Panderus. No offence but this is the first acknowledgement that there even is a problem. Can you mention that to everybody/ Silence leads to frustration. Keep up the good work, I'm a big fan.
I can't report a bug in-game because I can't even get in the game. I've even tried re-installing the whole thing, let it patch and all and still nothing. After I hit Play, it loads the Cryptic page and once that's done it just crashes. After that it wants me to verify all the files so it could just crash again. I really like the game and would like to play it, but when can I? I'm not a computer-wizard, just a simple working mom who likes to kill some stuff before bedtime :P Please let me have my fun back, pretty please!
After a ton of changes, a few gotchas, and some surprises, I have mouse raw-input working in Windows 2000. The game client no longer crashes and I can get ingame. I even just invoked so I won't lose my coins on my main character.
The bad news:
Keyboard keys don't work ingame, presumably because I haven't implemented raw-input support for the keyboard yet. Keyboard support might be a bit tougher than mouse support, but now that all of the common infrastructure works the scope of the problem is a lot narrower.
And, of course, the Summer Festival starts tomorrow, so it's a race against time for me. I'm starting to dream in assembly
Harper Chronicles: Cap Snatchers (RELEASED) - NW-DPUTABC6X Blood Magic (RELEASED) - NW-DUU2P7HCO Children of the Fey (RELEASED) - NW-DKSSAPFPF Buried Under Blacklake (WIP) - NW-DEDV2PAEP The Redcap Rebels (WIP) - NW-DO23AFHFH
My Foundry playthrough channel: https://www.youtube.com/user/Ruskaga/featured
Does anyone know if they will fix this today on maintenance? It's been a week....:(
0
skandlumMember, Neverwinter Beta UsersPosts: 0Arc User
edited August 2014
This time i can get in the preview server, and i got the same bug like you guys. Works wonderfull, i hope they will implement it for the live server too:) thx dev team
Comments
Never use on demand patching, it's the cause of so many bugs and lag issues, always use full patch, keep pc on at night, and patch the game, and then u'll never have those kind of problens.
RANT over, arc off, hopefully NEXT week i can play :[
I'm just happy none of the *smart* mods have come here yet to explain how you need to disable cores,update video drives or something dumb like that.
Also apparently one of the answers to a support ticket regarding the issue was *Your graphics card is no longer compatible with our game*. Says alot now doesn't it?Screw up then tell people they need to change their systems lol k
If i start the game in a small window and enter thr game with one char and change to fullscreen the game works. I have then no problem changing to another char after entered the world once.
That would mean that something is broken when the game starts.
I mean this wasn't an issue reported over a month ago so clearly you need to figure it out for yourself why you are suddenly experiencing problems after the new patch.
Hard release dates - such an easy excuse for lazy programming.
Nja they don't know what they have messed up and therefore do not answer. There are many other problems ppl have with menus, windows and stuff all related to graphics.
And that is not hard to do because the cards mention is about 10 years old so why are we having these graphical problems?
I've spent the last two days crawling through the assembly in win32k.sys to try to add raw-device support. Now, I can spend another week at it and *maybe* get it working, or you could realize that DirectInput8 != win32 raw-input support and not assume that supporting one guarantees supporting the other. Further, not every WINE implementation and/or user might fully support raw-input (which involves a tunnel to kernel code via user32.dll <--> win32k.sys), and the slightest bug will crash the kernel. A switch to force using DirectInput8 instead of raw-input might be warranted, ya think?
(to give you an idea of how much of a PITA this is for me, I have to...)
- get definitions of PROCESSINFO and THREADINFO structures for XP (thank the Heavens for ReactOS!)
- reverse-engineer PROCESSINFO and THREADINFO for Win2k (they *are* different!)
- reverse-engineer the internal raw-input structures in XP
- reverse-engineer the raw-input logic (because I have to...see below)
- determine the parts of the raw-input logic that apply to keyboard and mouse (which 2k has support for in win32k) and which apply to non-keyboard-mouse USB HID devices (which win2k win32k.sys doesn't suport)
- port raw-input routines from XP to 2k, modifying each as necessary to:
a. drop all HID support (which the code calls non-legacy)
b. adapt to 2k PROCESSINFO and THREADINFO structures (by the way, I had to mod 2k to allocate a larger PROCESSINFO to support the raw-input request linked-lists that all of this logic needs)
c. modify all existing pertinent routines in 2k win32k to include raw-input support (otherwise NW won't get any data). This includes making sure to add code to clean up the new linked-lists!
d. expand win32k's internal dispatch table (move data after it out of the way so it can grow first!) I've done this once before in an earlier patch -- I know how to do it, but it's a real pain.
e. modify user32.dll to add the new API routines that call win32k (actually, the easiest part)
f. modify 2k's existing DEVICEINFO logic to support returning a handle to a device-info object when a client requests a list of registered raw-input devices (done, finished that today)
g. be on the lookout for references to fields in structures that differ between 2k and XP (e.g. there's a reference to a field in PWND, and 2k has the field in a different place). This requires *really* being on my toes.
.
.
.
z. periodically test changes in a VM (easy to do, just time-consuming -- I have to do this for every 2k patch I release)
And probably a bunch of other things that I haven't even discovered yet. Or, you could just check the results of some function calls and act appropriately...
Blood Magic (RELEASED) - NW-DUU2P7HCO
Children of the Fey (RELEASED) - NW-DKSSAPFPF
Buried Under Blacklake (WIP) - NW-DEDV2PAEP
The Redcap Rebels (WIP) - NW-DO23AFHFH
My Foundry playthrough channel: https://www.youtube.com/user/Ruskaga/featured
oh and error id: 32926681
preceded by "materials reloading" at the NEVERWINTER splash
I guess we all have to start looking for new games to play.....
SAMOTHRACE
Trickster Rogue
────────────────────────────
I've been conducting major surgery on my win32k.sys and *might* be able to get mice working ingame in a couple of days, if I haven't just jinxed it. Just expanding the internal mouse message buffer and all of the involved routines took all day, and I still have a few more routines to work on (the worst of the mouse-related changes are over, though, I hope...). A fix from your end would be much more desirable; I'm cringing at the changes I'd have to make to get the keyboard working.
Blood Magic (RELEASED) - NW-DUU2P7HCO
Children of the Fey (RELEASED) - NW-DKSSAPFPF
Buried Under Blacklake (WIP) - NW-DEDV2PAEP
The Redcap Rebels (WIP) - NW-DO23AFHFH
My Foundry playthrough channel: https://www.youtube.com/user/Ruskaga/featured
This on all counts
But I have to admit, I already care a lot less than I did over the weekend - I think going live with this bug is really going to cost in the long run.
- Dualspec
- Better rewarding foundry and foundry pvp maps
- Custom PvP leagues with leaderboards instead of the current 'matchmaking'.
- Armory
- make jumping cost stamina (to reduce hopping in pvp)
Posting on this forum is pointless learned it the hardway no matter the severity of the bugg or the ppl affected they just slack, and the more u post or look into it the more frustrated u get, even garbage collectors have more respect for their work then Pw has for its own and the ppl who play/pay the game.
as stated in this sticky thread: http://nw-forum.perfectworld.com/showthread.php?620951-Read-Before-Posting-getting-the-most-out-of-the-bug-reports-forum
devs are likely not going to reply in bug reports unless they are asking for more information.
patch days are thursday unless it's an emergency patch.
i can understand the frustration here but that doesn't give license to ignore the forum rules of conduct. please be mindful. thanks.
do not reply to this mod note. instead, send us a PM if you'd like to discuss it.
Normally you wouldn't have to; after all, it's their product, not ours.
However...
Since I'm running Windows 2000 (and, unless more people are aware of the post-EOL patch thread on MSFN than I think), I just might be the only one on 2k. There's always the possibility that Crypric could come back and say, "well, we didn't require raw-input API support before, but since XP has it, we are now." That would leave me stuck, so just in case I've started porting the API over. I've lost count of all the API's and security patches I've backported over the last four years, so it's worth a try, though the changes are so intrusive that I'd really much rather not.
At least I don't have to do anything to IE6. I gave up on backporting patches to that. Mshtml.dll is complicated beyond imagining.
Blood Magic (RELEASED) - NW-DUU2P7HCO
Children of the Fey (RELEASED) - NW-DKSSAPFPF
Buried Under Blacklake (WIP) - NW-DEDV2PAEP
The Redcap Rebels (WIP) - NW-DO23AFHFH
My Foundry playthrough channel: https://www.youtube.com/user/Ruskaga/featured
Thanks!
Will the preview patch also correct the newly added delay in professions?
Blood Magic (RELEASED) - NW-DUU2P7HCO
Children of the Fey (RELEASED) - NW-DKSSAPFPF
Buried Under Blacklake (WIP) - NW-DEDV2PAEP
The Redcap Rebels (WIP) - NW-DO23AFHFH
My Foundry playthrough channel: https://www.youtube.com/user/Ruskaga/featured
The good news:
After a ton of changes, a few gotchas, and some surprises, I have mouse raw-input working in Windows 2000. The game client no longer crashes and I can get ingame. I even just invoked so I won't lose my coins on my main character.
The bad news:
Keyboard keys don't work ingame, presumably because I haven't implemented raw-input support for the keyboard yet. Keyboard support might be a bit tougher than mouse support, but now that all of the common infrastructure works the scope of the problem is a lot narrower.
And, of course, the Summer Festival starts tomorrow, so it's a race against time for me. I'm starting to dream in assembly
Blood Magic (RELEASED) - NW-DUU2P7HCO
Children of the Fey (RELEASED) - NW-DKSSAPFPF
Buried Under Blacklake (WIP) - NW-DEDV2PAEP
The Redcap Rebels (WIP) - NW-DO23AFHFH
My Foundry playthrough channel: https://www.youtube.com/user/Ruskaga/featured