Deleted
Deleted Member
Posts: 0
|
Post by Deleted on Jun 11, 2018 8:38:11 GMT -5
FRC will soon be the only populated english-languaged RP server to stay in the old version.
Hey not so negative huh?? How about some positive spin on that!
"FRC will be #1!"
Woot!
|
|
|
Post by Animayhem on Jun 11, 2018 14:31:46 GMT -5
I think once intel snafu gets fixed more will move over. I would still buy the EE it is a good price as you can actually run the game on 64 setting rather than 16. I have visited a few EE servers and I did not the feel the hospitality I did and do here.
|
|
|
Post by sergeil on Jun 11, 2018 15:21:16 GMT -5
I have visited a few EE servers and I did not the feel the hospitality I did and do here. Soul of any server is DM team. Which game or which type of server is secondary...
|
|
|
Post by Razgriz on Jun 11, 2018 18:54:02 GMT -5
I have visited a few EE servers and I did not the feel the hospitality I did and do here. Soul of any server is DM team. Which game or which type of server is secondary... Actually, it is the players. DMs themselves are players here too.
|
|
|
Post by sergeil on Jun 11, 2018 22:49:06 GMT -5
Actually, it is the players. DMs themselves are players here too. Players everywhere are like the same. DM are not players, because must work to support us instead of play. And it is serious, permanent and enough boring work.
|
|
|
Post by Dobian on Jun 12, 2018 8:46:03 GMT -5
Sure, I left Ravenloft because it was a server full of assholes, both players and DMs. I ran one of the guilds over there at one point so it wasn't like it was a light decision to ditch the place. They could move the server to the graphic equivalent of ESO and I wouldn't go back.
|
|
|
Post by DM Hawk on Jun 12, 2018 14:00:39 GMT -5
Hi, Short question. Will I be able to play on FRC in NWN EE? I'm planning to buy it. Hi Joze, FRC will migrate to NWN EE in due course. It is my understanding that there are technical limitations right now preventing an upgrade of FRC to NWN:EE. Basically, some add-ons of NWNX that FRC relies on are not available in NWN:EE yet. I have no doubt that will change sooner than later.
|
|
|
Post by sergeil on Jun 13, 2018 0:20:36 GMT -5
Basically, some add-ons of NWNX that FRC relies on are not available in NWN:EE yet. NWNX is not part of server and, in much part, is just monitoring tool. <del> But I do not see any reason to hurry, because EE is still in intensive bugfixing and FRC is enough good even "as is". Now windows user, who play legacy nwn1, have issue because win10. After migration to EE they will have issues because win10 and EE. I do not have much issues with legacy nwn1, because Linux. </del> Maybe, it is not bad idea to create pure EE server (without extra packs). It allow anybody, who want go ahead so much, test it. Without monitoring, only limited support and bugzilla. I would take part in testing too. Gatered info could be (or not) useful for DM to have fresh information from first hands. As I remember, there are stable and develop versions. I do not know which is better. It should be DM decision. Update of server should be made as soon as new version is announced.
|
|
|
Post by Animayhem on Jun 13, 2018 9:46:06 GMT -5
The NWNX and the intel graphic driver two main sticky points. Custom haks work fine with EE as I have seen on some servers. I have no problem with ee and win10 myself. There are higer end settings which if reduced or shut off will make ee run better
Right now window based worlds have to run NWNX in a docker format which emulates Linux. Also EE is still, in my opinion not totally out of beta as their are updates to correct problems (steam does this automatically), which if worlds who are ee not on top of it causes problems with players who have the updates but not the world they play on.
|
|
|
Post by sergeil on Jun 13, 2018 12:00:07 GMT -5
Right now window based worlds have to run NWNX in a docker format which emulates Linux Can you explain me why do you use windows for nwn server? As I remember, OS and hardware have to be selected and tuned according to application server. As for me, it means, Linux should be better for nwn.
|
|
Nicoen
Proven Member
Posts: 225
|
Post by Nicoen on Jun 13, 2018 17:04:14 GMT -5
Also EE is still, in my opinion not totally out of beta as their are updates to correct problems (steam does this automatically), which if worlds who are ee not on top of it causes problems with players who have the updates but not the world they play on. This is not true. You can just select the older version on steam and play with that.
|
|
|
Post by sergeil on Jun 13, 2018 23:41:24 GMT -5
Also EE is still, in my opinion not totally out of beta ... This is not true. You can just select the older version on steam and play with that. Older version is beta too, but has different collection of bugs. EE is still in intensive bugfixing... In fact, EE is released, because it was not possible to wait any more. It was released with a lot of bugs and regressions. Now I can consider EE as early beta.
|
|
|
Post by sergeil on Jun 13, 2018 23:46:02 GMT -5
Is horseback realised in pure EE as basic element or DM team have to develope it again and implement to EE like it is already done for legacy FRC?
|
|
|
Post by sergeil on Jun 14, 2018 0:11:52 GMT -5
Sure, I left Ravenloft because it was a server full of assholes, both players and DMs. Players are the same everywhere. Everything is dependent of DM. If DM are right, players will be good too, but if DM are assholes, layers will be the assholes too. It is like the same as in any company. If management is correct and effective, company becoming leader of market. If management is bad, company becoming insignificant player and bankrupt in future.
|
|
Fenix
~
Sleepless Golem, aka Kenny
If you read this, send me a love note.
Posts: 2,183
|
Post by Fenix on Jun 14, 2018 12:10:56 GMT -5
This is not true. You can just select the older version on steam and play with that. Older version is beta too, but has different collection of bugs. EE is still in intensive bugfixing... In fact, EE is released, because it was not possible to wait any more. It was released with a lot of bugs and regressions. Now I can consider EE as early beta. Detail the bugs.
|
|
|
Post by lucid on Jun 14, 2018 12:30:07 GMT -5
My only problem with EE so far is the lack of Gamma control, so everything is dark AF, and for whatever reason it makes things in the distance blurry, which is killing my eyes.
Pro: sticky modes, Expertise won't turn off now!
Otherwise I'm finding them largely indistinguishable.
|
|
|
Post by malclave on Jun 14, 2018 13:04:49 GMT -5
for whatever reason it makes things in the distance blurry, which is killing my eyes. Do you have Depth of Field enabled (in nwn.ini, I think)? If so, try turning it off.
|
|
Deleted
Deleted Member
Posts: 0
|
Post by Deleted on Jun 14, 2018 13:46:50 GMT -5
for whatever reason it makes things in the distance blurry, which is killing my eyes. Do you have Depth of Field enabled (in nwn.ini, I think)? If so, try turning it off. You can edit the .ini file directly if you want to, but it's not necessary because this setting, along with all the new video effects, are settable in the video options dialog window.
From the release notes document:
• Advanced Frame-Buffer Effect (Depth of Field).
Causes more distant pixels to be blurred. This effect only becomes visible as the camera zooms in close to the player character.
|
|
|
Post by sergeil on Jun 14, 2018 15:50:46 GMT -5
Today I have connected to public nwn-EE server and was able to play in full screen mode without big issues (key combinations Ctrl-F2,Ctrl-F3,Ctrl-F4,Ctrl-F12 still do not work), client is crashed on game exit.
In case if game is started by beamdogClient-2.1.3-x86_64.AppImage, sound do not work, but, thanks to forums, I found, that it is launcher issue. If game is started directly by nwmain-linux, sound work
Some interesting details:
As I see, all executable files, except launcher, are 32 bit. Surprise :-)
[sergeil@homedesk Beamdog Library]$ file beamdogClient-2.1.3-x86_64.AppImage beamdogClient-2.1.3-x86_64.AppImage: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux 2.6.24, BuildID[sha1]=c271a1d61198e53b90595d8bf0a7d50a57e0a53e, stripped
[sergeil@homedesk linux-x86]$ file nwserver-linux nwserver-linux: ELF 32-bit LSB shared object, Intel 80386, version 1 (SYSV), dynamically linked, interpreter /lib/ld-linux.so.2, for GNU/Linux 2.6.32, BuildID[sha1]=f03a0e4306f9df5c6d733e2f5d99a2f27bd82cd3, stripped
[sergeil@homedesk linux-x86]$ file nwmain-linux nwmain-linux: ELF 32-bit LSB shared object, Intel 80386, version 1 (GNU/Linux), dynamically linked, interpreter /lib/ld-linux.so.2, for GNU/Linux 2.6.32, BuildID[sha1]=5741c21e69bffcdb3289a19481a6ca8f695d2dff, stripped
[sergeil@homedesk win32]$ file nwmain.exe nwmain.exe: PE32 executable (GUI) Intel 80386, for MS Windows
As for me, it is not big issue for client, but server... Server should be 64-bit.
|
|
|
Post by sergeil on Jun 14, 2018 15:54:53 GMT -5
Older version is beta too, but has different collection of bugs. EE is still in intensive bugfixing... In fact, EE is released, because it was not possible to wait any more. It was released with a lot of bugs and regressions. Now I can consider EE as early beta. Detail the bugs. Even for today, list of opened bugs is still enough big...
|
|
|
Post by Fluffy the Mad on Jun 14, 2018 16:15:44 GMT -5
Today I have connected to public nwn-EE server and was able to play in full screen mode without big issues (key combinations Ctrl-F2,Ctrl-F3,Ctrl-F4,Ctrl-F12 still do not work), client is crashed on game exit. In case if game is started by beamdogClient-2.1.3-x86_64.AppImage, sound do not work, but, thanks to forums, I found, that it is launcher issue. If game is started directly by nwmain-linux, sound work Some interesting details: As I see, all executable files, except launcher, are 32 bit. Surprise :-) [sergeil@homedesk Beamdog Library]$ file beamdogClient-2.1.3-x86_64.AppImage beamdogClient-2.1.3-x86_64.AppImage: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux 2.6.24, BuildID[sha1]=c271a1d61198e53b90595d8bf0a7d50a57e0a53e, stripped [sergeil@homedesk linux-x86]$ file nwserver-linux nwserver-linux: ELF 32-bit LSB shared object, Intel 80386, version 1 (SYSV), dynamically linked, interpreter /lib/ld-linux.so.2, for GNU/Linux 2.6.32, BuildID[sha1]=f03a0e4306f9df5c6d733e2f5d99a2f27bd82cd3, stripped [sergeil@homedesk linux-x86]$ file nwmain-linux nwmain-linux: ELF 32-bit LSB shared object, Intel 80386, version 1 (GNU/Linux), dynamically linked, interpreter /lib/ld-linux.so.2, for GNU/Linux 2.6.32, BuildID[sha1]=5741c21e69bffcdb3289a19481a6ca8f695d2dff, stripped [sergeil@homedesk win32]$ file nwmain.exe nwmain.exe: PE32 executable (GUI) Intel 80386, for MS Windows As for me, it is not big issue for client, but server... Server should be 64-bit. Gee, it's almost like the base game was designed in 2002 when the main operating system the game was built for was still 32-bit and it hasn't had a complete rewrite. Who would have guessed it? By the way, the entire game was built originally for an older Windows platform. It only got Linux support in the 1.69 update; there's zero basis to assume your personal distro of Linux is going to work best with this game, either the original or EE. No one here generally cares about your command line dialog. If you want to offer constructive criticism, go do it on the Beamdog forums.
|
|
|
Post by sergeil on Jun 14, 2018 22:53:32 GMT -5
there's zero basis to assume your personal distro of Linux is going to work best with this game, either the original or EE. No one here generally cares about your command line dialog. If you want to offer constructive criticism, go do it on the Beamdog forums. Both nwn are not from my distributive, but official versions from vendors. Command line is added only to confirm type of executables. It is technical topic and everybody should understand details. Sorry, if I upset you. I hope my info is useful for somebody. I do not want offer any criticism. Everything, what is necessary, I already posted into Beamdog bugzilla. PS: Can you inform what type of process (32 or 64) is running under windowd?
|
|
|
Post by sergeil on Jun 14, 2018 23:21:13 GMT -5
Dear DM team,
Is it planned to setup test EE server FRC or it is better to investigate in different place?
If it is planned, please announce when exactly.
|
|
|
Post by sergeil on Jun 14, 2018 23:54:28 GMT -5
As I found, EE client for Linux in full screen mode use only 50% of one CPU core. Nwn1 legacy use 100% of one core.
So, both versions for linux are not able to use more as one core, but EE client use twice less CPU resources.
Can anybody check if the same for windows?
|
|
|
Post by sergeil on Jun 15, 2018 0:30:46 GMT -5
base game was designed in 2002 when the main operating system the game was built for was still 32-bit and it hasn't had a complete rewrite. Who would have guessed it? By the way, the entire game was built originally for an older Windows platform. It only got Linux support in the 1.69 update en.m.wikipedia.org/wiki/Neverwinter_NightsIt means, code base for all main platforms is common a lot of time. Patch 1.69 is released much later, Jun 2014. neverwintervault.org/project/nwn1/other/patch/169-critical-rebuild-englishBy this reason I can assume, that Linux, Windows abd Mac OS version of legacy nwn1 have to work very similar.
|
|
|
Post by jozeftaktyka on Jun 15, 2018 1:47:17 GMT -5
Damn, looking at those bugs I think I'm going to wait with the purchase...
|
|
|
Post by FlyingMidget on Jun 15, 2018 1:55:44 GMT -5
base game was designed in 2002 when the main operating system the game was built for was still 32-bit and it hasn't had a complete rewrite. Who would have guessed it? By the way, the entire game was built originally for an older Windows platform. It only got Linux support in the 1.69 update en.m.wikipedia.org/wiki/Neverwinter_NightsIt means, code base for all main platforms is common a lot of time. Patch 1.69 is released much later, Jun 2014. neverwintervault.org/project/nwn1/other/patch/169-critical-rebuild-englishBy this reason I can assume, that Linux, Windows abd Mac OS version of legacy nwn1 have to work very similar.
You're very much mistaken, alot of NWN1 is using library's that have been unsupported since windows XP and have been a bit hit and miss with workaround in later editions of windows being released to make them "somewhat" functional, one of radeons fixes for various graphics issues is a custom hidden and unchangable profile for the NWmain.exe file which includes quite a few features turned off as they break the game and got alot of complaints about it. There's a very good reason NWN:EE has redone the way they handle movies, sound and the graphics engine before even the head start was announced.
1.69 was released on 9 July 2008, a bit rushed at that as Bioware were aware they were no longer going to be supporting the game and the developers tried to push as much content into the patch as possible. The page you linked for such was a NWN vault page and the date on it showed the date that was uploaded to that particular vault, the vault which wasn't created until quite a few years after 1.69 because the IGNNWvault was taken offline.
64 bit support for both the server and the client is something Beamdog want to do in time, I believe they've mentioned they've been investigating it, but it's not a light weight change, it'll be quite an undertaking, regardless, while this is a topic about NWN:EE the majority of players are likely to play on Windows and most aren't really concerned about your personal technical read outs and if you desire anything to come of such it would be far more likely to reach someone that would care to see it on the Beamdog NWN:EE forum.
Likewise, referring to the issue tracker as bugzilla really isn't helpful, while there are a number of bugs (the biggest ones currently being Intel issues which are actually a Intel iGPU driver issue and not a beamdog issue and some minor issues with doors that were introduced with the latest patch) alot of the posts on their issue tracker include things like someone isn't using up to date drivers, crashes due to other programs, crashes due to broken custom tilesets (from haks), server specific bugs from scripts written, user mistakes and a fair number of 1.69 issues that are being reported to get fixed up as well.
Also please try and avoid claiming that FRC doesn't need NWNx support as it's just a monitoring program, it isn't, NWNx allows plugin injection into the NWNserver itself to add further functionality that isn't part of the base game (including scripting hooks, plugins that can help with stability and performance, plugins can change the way the game handles combat, the dynamic loading of maps and summons, variables being stored on items that are sold which would break any newly sold tent, summon theme, spell changing book/ring/token and a whole host of other things).
FM.
|
|
Templar
Old School
A female dwarf?! No really! What do you play?
Posts: 585
|
Post by Templar on Jun 15, 2018 2:52:36 GMT -5
I don't really see the point of EE.... so far the only upgrades i've heard are: 1. minor graphical ones (which are buggy with gamma, camera and other stuff people are mentioning) 2. the fact you can sticky things like expertise... which honestly can be done here with some dev command lines. the sticky thing came up a long time ago and I remember someone pointing out that it wouldn't be too hard to make it sticky but would just need someone with the time and know how to do it. 3. server lists actually working again.
Honestly only 3 is the tempting one but when websites that show server lists, it isn't really needed. It just means after spending $20 from gog, people now are being required to give another $20 to beamdog to play a game that is 16 years old because the final handful of servers still alive made the move.
FRC should market itself a bit as the only one NOT moved and you will probably get people coming in for that reason alone. Throw it up on redit, mention on facebook, some of the gaming sites that still talk about nwn, etc.
|
|
|
Post by Dobian on Jun 15, 2018 8:42:49 GMT -5
People are mostly jumping to EE because of Shiny New Car syndrome.
|
|
|
Post by Dimitri on Jun 15, 2018 9:09:10 GMT -5
... Also the sheer amount of fixes and ease of use? Like, I haven't had any of the bugs that are being complained about. I would absolutely *LOVE* Dimitri having EE, because then he wouldn't lose charisma every time I shapeshift. EE is a great step, and non-EE is very much over time going to lose popularity as the list of fixes and improvements grow.
|
|