Update 8176
raz651
Member Posts: 175
Anyone else having diffuculties with 8176? Such as no chat window and not being able to select any race but human in the character creation menu?
1
Comments
It's in ovr/ in the development download. Only updated ones are racialtypes.2da and portrait.2da
As for the chat window, thing I did not encounter this during testing. Also beamdog client develop branch has not been update to 8176 it still at 8175. Steam version has been updated.
A friend told me how to split the chat window. (never had to do that before so something must have defaulted the multiplayer to a single window.)
True, the gripe about races lacks legs. No new races have been added to the game. Developers now have the ability to add new races via .2da; however, that's restricted exclusively to custom content. It's a nice new feature. I won't ever use it. But it's nice.
But here's the rub.
For developers, the new patch has taken great strides toward helping EE to catch up to 1.69 -- but it offers nothing new to players. For players, it's arguably a direct downgrade.
After less than an hour on this patch, I'd discovered:
- Chatbar settings now save, but aren't loaded. Rendering this feature pointless. Settings also no longer default based on singleplayer/multiplayer gameplay, making this a direct downgrade.
- All doors now have transition VFX--even if the door has no transition attached. I assume this is a bug. It looks odd and it's confusing.
- Sounds now sometimes play from the client even when volume is muted. Obviously unintended.
As a developer, I appreciate the new toys, but I do hope the next patch offers more to players and is released in a more polished state. Players are the lifeline of any community, afterall.
As always it's a mixed bag, optional things, not quite full featured, but generally steps in moving the game forward.
As for sounds playing while muted I've had that happen before randomly on the last stable patch. I'm just going to expect a lot of bugs and instabilities until a much later date.
As above, I also feel the door transition VFX is a bug, I really really really want to disable it. I have a lot of areas where I use walls crossing with gates like say a walled in town, all of these gates are very difficult to traverse without either rotating the view 180 degrees or using WASD movement which I only use in FPS games
Do you want BD to make new base races in the game? If Yes then unlocking the race screen make it a lot easier them to provide you new races. Do you play on PW with any hak paks? Yes, then this will make though pw have a easier time adding races for you to play with. Do you plan to play new single player modules with hak pak? Yes, then the module creator can have new races options easier and tell the stories around them. Just because you not going to use a feature does not mean the playerbase will not use it or benefit from it.
Three minor bugs that will get patched (Bioware had one patch that destroyed all multi-player and numerous patch that caused minor to big issues (including the 1.69 patch that messed with DM possessed creature losing abilities) So if you did not understand when you bought this game there going to be hic-up along the way that will mostly minor, then I sorry you miss-read about it.
Thing the game and patch offer to new players that 1.69 does not.
Core master server: Now you can connect to PW again in one unified system. There are other options for 1.69 to connect but they are not as unified. Minor improvement.
Steam: Weather you love/hate/indifferent to it the steam setup let you direct connect to friends playing and let you subscribe to module to play by downloading the hak/tlk/module to you so you can get in and play right away. Great for PW/group/single play and this feature will be added to BD client soon. This is a big improvement over 1.69.
Improved models that are on steam and will come to the core game.
Side note: A bunch of these improvements help PW servers. With at least 50% (you can debate the numbers in another topic) playing NWN for PW servers that is a big chunk of the playerbase of nwn and when you talk about direct benefit to the playerbase you have to keep that in mind.
This patch:
I already mention the race information.
SetObjectVisualTransform
If you did not see the thread on this new function you missed big one. This will allow PW to do all sorts of fun thing in PW weather they use hak or not. LINK
SetHiddenWhenEquipped
Which allow true open face helmets.
Player event
Fixes to bug that were in 1.69
Improved compiler
Improvement to toolset.
I sorry if I'm of the mind-set that by improving all areas of the game will improve the game for the players. The same thinking that bioware had and BD have.
Here hoping we have many more patches that are awesome even if a few things get missed.
- door VFX
- random sound
- lan play multiplayer server list not displaying columns correct
- annoying chat bar change that cant changed w/default save
I remember watching the stream the week before when it was RC and the CEO *asked* people to please download the dev build and test and report issues. I know I reported two of the above and it sits in redmine bug reports, unresponded, and guess what, the patch was pushed out anyhow. I find that annoying and think to myself "why test when you ask me to" when stuff clearly isn't taken in anyhow. I also read on steam all the multiplayer issues and note those, too. That's just my .02.
Otherwise I'm very happy with the game, they just need to work on their release cycle. I cringe to think if I have to wait a month for regression bug fixes.
http://blog.beamdog.com/2018/06/neverwinter-nights-darkness-over.html
As far as testing, I work on my PW every day, and would have loved to add/test a lot of these new features. That being said it's entirely reliant on nwnx-lite and there hasn't been support for the betas or I'd have found and reported all of these issues like the other bugs I've reported. It's no ones fault, people are busy and I would never put pressure on anyone to release something that wasn't ready but I think the main people who would find the bugs are PW devs and without nwnx they just aren't going spend time on something they can't use.
Thanks a lot for your feedback. The team are currently working on a dev build to address all the hot issues, with regressions being the most important bugs to fix.
We'd appreciate a lot if you could report all the problems mentioned in this thread on our bug tracker (support.baldursgate.com) - just search for existing reports first.
@FreshLemonBun I think the flickering is still not on the public tracker. Can you please file it?
Forgive me if this Quote is a mess... I've never gotten a solid handle on how to do it.
But I noticed this from ShadowM and it bothered me... I don't use Steam, and I'm a tad saddened that the good stuff is going to folks that bought the game from Steam and not those of us who spent our dollars with the good folks who are build this game for us. Maybe my skin is too thin, but I'm just not happy that Steam is getting all the fancy looking stuff, and I have a deal with a herky jerky game.
As stated during livestreams, the plan is to slowly roll out visual updates, and when the team is happy with the state of all those models and stuff, to include them into the base game.
Again thank you @JuliusBorisov
https://steamcommunity.com/games/704450/announcements/detail/2779165948478533583