Fury of the Feywild
Sharandar. Once the heart of the moon and wood elf kingdom of Iliyanbruen, it was nearly destroyed by invading hordes of orcs long ago. Though the war was won, the Iliyanbruen people were scattered. A few wood elf communities survived in what is now known as Neverwinter Wood. Meanwhile, many of the moon elves used powerful magic to transport much of what remained of Sharandar to their ancient homeland in the Feywild.
But now the forces of the Feydark have returned. Led by King Malabog, the fomorians seek to destroy New Sharandar and seize control of the fey crossing into Neverwinter Wood. The Iliyanbruen elves are besieged, and need allies in their fight against Malabog. Will you answer the call to battle?
Application Details:
| Version: | 5.x |
| License: | Free to use |
| URL: | http://games.arcgames.com/en/p... |
| Votes: | Marked as obsolete |
| Latest Rating: | Gold |
| Latest Wine Version Tested: | 1.7.1 |
Maintainers: About Maintainership
What works
Everything in the actual game.
What does not
There are some quirks with installer (Arc):
Workarounds
What was not tested
Hardware tested
Graphics:
Additional Comments
I had some issues with the "Arc" installer. When trying to install Neverwinter, it kept giving me errors. From looking at Arcs log files, it turned out, that it wants to make a folder in the root of the windows drive, that you are installing to. So you need to either install inside the actual profix, or make sure you've mapped a drive in a way that Arc will have write permissions in the root folder. Because the Arc installer launches the "old" Neverwinter installer, you still need a 32 bit prefix with ie8 installed, or that part will not be working properly. Personally, I got better performance out of putting in "-enablerawinputsupport 0" as "Advanced command line" in options, and checking "Disable on-demand patching". I had to reduce the graphics details to close to the lowest possible, but kept the "render scale" at the top. This was tested on a AMD Radeon HD 6800 series graphics card. That could possibly be part of the explanation for bad performance.
| Operating system | Test date | Wine version | Installs? | Runs? | Used Workaround? | Rating | Submitter | ||
| Show | Ubuntu 13.04 "Raring" amd64 (+ variants like Kubuntu) | Sep 07 2013 | 1.7.1 | N/A | Yes | Gold | Dan (Strit) Johansen | ||
| Show | Ubuntu 13.04 "Raring" amd64 (+ variants like Kubuntu) | Sep 06 2013 | 1.7.1 | Yes | No | Garbage | Dennis William Johansen | ||
| Show | Linux Mint Debian | Sep 17 2013 | 1.6 | Yes | Yes | Bronze | Eric N | ||
| Show | Ubuntu 13.10 "Saucy" amd64 (+ variants like Kubuntu) | Sep 16 2013 | 1.6 | Yes | Yes | Gold | Dennis William Johansen | ||
| Current | Ubuntu 13.04 "Raring" amd64 (+ variants like Kubuntu) | Aug 28 2013 | 1.6 | Yes | Yes | Gold | Dennis William Johansen |
Installing Arc
Standing where you have downloaded the Arc installer enter this comand: (Alter the prefix and filename as needed)WINEPREFIX=/wineprefixes/Neverwinter wine ArcInstall_v20131010a.exeLaunching Arc When installing Arc, you should have gotten an option for a desktop shortcut, but the manual way of launching Arc would be: (Standing in the folder you installed Arc into. Alter the prefix path as needed)
WINEPREFIX=/wineprefixes/Neverwinter wine ArcLauncher.exeFrom there you can download and start Neverwinters launcher - Which will update the game and start the actual game.
Windowed mode crashes
Some users have experienced crashes when running in windowed mode. Should that happen for you, try running in full screen mode instead.
Mouse input lagging
If you experience lag when using the mouse, try going to the options panel of the Neverwinter launcher, and add "-enablerawinputsupport 0" in the "Advanced command line" editbox.
Disabling on-demand patching
This is mostly a matter of preference - If you want to force the launcher to update the entire game before you play, head into the options panel of the Neverwinter launcher and check "Disable on-demand patching".
Freezes while on loading screen
There has been problems, with Neverwinter freezing on the loading screen, with a combination of fglrx drivers and wine 1.7 - It isn't quite clear, what exactly triggers that, but downgrading wine, and/or changing fglrx driver versions apparently helps.
To be sure everything worked fine , i'll completely reinstalled the game, i had a crash at first loading screen after reinstall, seems it corrected itself when using full screen in virtual mode ( in my case 1600x900 ) its specific to mac os , tried on a mac mini and imac 27" both are corrected this way.
the game run smoothly , appart few glitch during loading screen between zone, nothing unpleasant.
The following comments are owned by whoever posted them. WineHQ is not responsible for what they say.
by Sergej on Saturday January 11th 2014, 6:10
[quot]
There has been problems, with Neverwinter freezing on the loading screen, with a combination of fglrx drivers and wine 1.7 - It isn't quite clear, what exactly triggers that, but downgrading wine, and/or changing fglrx driver versions apparently helps.
[/quot]
I have he same issue with one detail - I'm using
NVIDIA Corporation GF108 [GeForce GT 630] (rev a1)
I've tried both nvidia 331.* and nouveau drivers, wine versions 1.6, 1.5.20, 1.5.25 - same freeze after "Material files reloaded" with no tips. So it's not fglrx/wine17 error at least for me.
by Amin Kh. on Thursday February 6th 2014, 7:28
it's work fine, but first time "Material files reloaded" take long time to load, for me, it was about 10min !!
by Dennis William Johansen on Thursday February 6th 2014, 9:01
(Specifically Software-->Wine-->Direct3D-->VideoMemorySize)
It might help to set the VideoPciDeviceID and VideoPciVendorID too, but try with the memory size alone first.
by Dennis William Johansen on Thursday February 6th 2014, 8:55
The bug you quoted is a specific wine commit, that breaks the fglrx drivers. But as the bug is only present in some fglrx drivers, and neither AMD/Nvidia open source drivers or nVidias proprietary drivers, odds are that commit will stay in Wine ;)
by Sergej on Thursday February 6th 2014, 21:41
(yes, I can use my system on rest cores while loading) and VOILA!
I'm in. So yes, this bug does not affect my nvidia card.
Sorry for panic.
And after I've set vendor card(VMS was already) in regedit loading time droped to ~7 minutes next time.
It's like old good days - you spend some hours/days to run a game in wine just to satisfy with this victory and delete a game.
Thanks!
by Ian on Thursday October 31st 2013, 17:23
by Dennis William Johansen on Friday November 1st 2013, 8:32
Do you have any sort of proxy, or anything else, that might interfere with http traffic?
Regarding ArcLauncher.exe and Arc.exe: They both exist, and just running Arc.exe worked fine - I assume they launch each other as needed ;-)
by Ian on Friday November 1st 2013, 19:49
i.imgur.com/oItK3HN.png
by Dennis William Johansen on Saturday November 2nd 2013, 4:02
I tried again, and Arc.exe isn't there indeed - It only arrives after the initial updating of Arc. I didn't notice that, as the installer offers to start Arc the first time, resulting in Arc.exe being there afterwards.
Is it a clean prefix you've tried with? Without any winetricks added?
If it isn't a clean prefix, could you try running the installer in a clean one?
I do wonder why you run wine with sudo though. That only gives wine far too much access to your system. But isn't related to this problem as such ;)
Perhaps check if there is any problems on the way to the server:
traceroute cc-ns.perfectworld.com
by Ian on Sunday November 3rd 2013, 13:22
The only thing this prefix has, is ie8.
by Ian on Sunday November 3rd 2013, 13:23
by Dennis William Johansen on Sunday November 3rd 2013, 13:46
If I understand you right, you have ie8, d3d9x, vcrun2008, vcrun2005 and vcrun2010 in your prefix?
If so, could you try to make a clean prefix and test it there, as I asked before?. None of the above are required, and only add to the odds of things breaking.
Normally wine would default to creating a ".wine" directory in your home directory - Not the root.
By setting WINEPREFIX, you can have that directory where you want.
There shouldn't be any reason to use sudo to run wine.
by Adam Tommasi on Wednesday September 11th 2013, 8:53
Another computer i own also has a g500 and I am experiencing the same exact issue. This computer has a 2nd wireless optical mouse that works just fine.
In order to play the game I have to switch to using the crappy optical mice instead of the G500. Again, this issue was not present before the feywild patch.
If i'm not mistaken, that patch introduced directx11 support. Could this be part of the problem?
by Dennis William Johansen on Wednesday September 11th 2013, 12:31
Have you tried putting in "-enablerawinputsupport 0" in the options panel under "Advanced command line"?
If you already have it there, could you try removing it - To see if that helps you?
by Adam Tommasi on Thursday September 12th 2013, 10:30
by Lukáš Hermann on Sunday February 8th 2015, 15:45
Problem is mouse polling rate. I'v had that problem too with my Speedlink Decus gaming mouse. My Polling rate was 1000Hz. And that was the problem. If you want it working, you need polling rate 125Hz.
If you have any drivers to you mouse, try look there. In my case, I had to reboot to windows, and install special software for my mouse to change it.
Good luck!