chevalier
Mon, 15th Jan '07, 8:54pm
Here are today's Neverwinter Nights 2 forum highlights, collected by NWVault (http://nwvault.ign.com). Please take into account that these are only single parts of various threads and should not be taken out of context. Bear in mind also that the posts presented here are copied as-is, and that any bad spelling and grammar does not get corrected on our end.
<font size="3" face="Verdana, Arial" color="#cc6600">Feargus Urquhart, CEO</font>
Monk Weapons and Two-Weapon Fighting (http://nwn2forums.bioware.com/forums/viewpost.html?topic=539352&post=4732990&forum=110&highlight=)
I had the QA staff here check Khelgar and they are pretty sure that he is working correctly with the number of attacks and BAB that he has after becoming a monk. Was there something specific that anyone noticed that was wrong?
<font size="3" face="Verdana, Arial" color="#cc6600">Rob McGinnis</font>
Say Hello to Your Community Representatives! (http://nwn2forums.bioware.com/forums/viewpost.html?topic=541480&post=4732304&forum=109&highlight=)
We're looking into that. They may not get an icon by the threads, but they might be able to have a logo by their names.
More: <hr />Is it wise for DLA to have a monopoly on CC stuff?<hr />I have no problem with them both being from DLA. They are reporting back to me what the CC people have posted. Their suggestions and recomendations will be backed up by the threads in the forums.
We have the Community Rep system structured so that one person or organization cannot monopolize on what gets fixed/implemented. All the reps have a say in the suggestions, and I listen to all the reps before I finalize how and what I present internally.
The Community Rep program is not about Obsidian or DLA or any other organization. It is about the Community as a whole. Your voice is what will drive change.
We are just getting started but, after some time of working with the Rep system, if anyone feels they are not being represented properly or fairly, I invite you to send me a PM and explain your side to me. All messages will be kept confidential.
Can't log in via NWN2 (http://nwn2forums.bioware.com/forums/viewpost.html?topic=539265&post=4732340&forum=116&highlight=)
Try putting a copy of your NWCDKey.ini file in your My DocumentsNeverwinter Nights 2 folder.
I think I had this same problem before and this fixed it.
Can't see terrain in toolset... (http://nwn2forums.bioware.com/forums/viewpost.html?topic=540526&post=4732998&forum=113&highlight=)
Hang on to those corrupted areas. I think I may have you guys FTP them to me if I can't seem to get this issue to happen for me.
Darkvision Adjustments (http://nwn2forums.bioware.com/forums/viewpost.html?topic=533911&post=4733211&forum=115&highlight=)
We are actually working on something to consolidate all the Questions and answers in one place where you can look things up by category and comment to ask for further clarification or give opinions.
<font size="3" face="Verdana, Arial" color="#cc6600">J.E. Sawyer, Lead Designer</font>
e-mail bugs reports?? What's wrong with talking about in forums? Is the list too long? (http://nwn2forums.bioware.com/forums/viewpost.html?topic=541669&post=4733533&forum=109&highlight=)
E-mailing bugs to a centralized list means that there's one place for us to look at all bugs reported by endusers.
More: <hr />You can read those lists in forums too,but we can't read the e-mails you get...<hr />This is the General Discussion forum, which happens to also contain threads about bugs. Some people also talk about bugs in threads that are not specifically about bugs. Threads in this forum about bugs are not, as a rule, closed/deleted/moved, so feel free to talk about them here. Just don't expect that we will catch everything that's mentioned.
E-mailing them to the addresses listed in the stickied post helps assure that they go to a centralized location for QA and development.
<font size="3" face="Verdana, Arial" color="#cc6600">Rich Taylor, Programmer</font>
Top missing features and bugs from PW standpoint. (http://nwn2forums.bioware.com/forums/viewpost.html?topic=539943&post=4732241&forum=118&highlight=)
Thanks for this thread, everyone. I will address some of the great points weby has made in the initial post. Some things I can update everyone on, other things I can only say that we're still working on a solution for.
1 - Indication of required files and where to get them. I agree that this is a severe problem. The method(s) of distributing custom content needs improvement as the current methods for integrating custom information into a user's build are very inconvenient. We're still working on ways to improve this. While I wish I could go into specifics on this, I can't right now.
2 - Automatic updating of custom content is another thing where all I can say is we're working on it. Since PWC files compress down to about the size of a mp3 in many cases, it might become viable to update them directly from the server hosting the game with the option of providing alternative download locations for them if uploading directly from the server strains bandwidth. More information about what we're doing with this stuff will come out when we've made some more decisions on our end.
3 - Module sizes. The dynamic area loading/unloading is something that I have been thinking about for a long time. There are a number of problems with trying to get a change of that scale into the engine, but we'll see what happens. Also, it is my understanding that portal support is currently broken which would prevent even the multi-server approach from being an option. We are working on that as well.
4 - DM Client Crashing the Server. We have resolved as many of these crashes as we could fine with regards to the DM client. These fixes should be coming in the 1.04 patch. If there are still any remaining crashes caused by the DM Client after 1.04, we will definitely look into them.
5 - No command line loading of directory-style modules via the dedicated server. I wasn't aware of this problem. I'll have it added to our issue tracking lists.
6 - There will be an increased focus on server stability for the 1.05 patch. We are aware of a number of the crash issues and memory leaks you are running into and will be working on resolving them.
7 - Linux Dedicated Server. I wish I had good news here, but I don't. You don't need to sell me on the importance of a Linux dedicated server. I felt it was important to have one from the beginning. Unfortunately, there were major systems decisions made along the way of developing NWN2 that make it borderline impossible to create a Linux dedicated server port at this time. By the time I learned of these changes and what it would mean about the possability of a Linux Server, it was too late to reverse the changes. While I won't say that there will never be a Linux dedicated server, I will say that it is unlikely. :/
8 - Language Version Patches. Yeah, sorry about the huge delay on the language version patches for 1.03. This was mostly caused by the staggered -releases- of the different languages, which we had no control over at Obsidian. Since the different languages were released at different days, it threw off the patching for the other language versions as well. For example, while we were working on the 1.02 patch for English, we were also still working on getting the Release version of Russian and Polish done. This meant that when we moved to working on 1.03, some of the language versions were already way behind. There is also a problem in that we can't test the localized versions internally and have to rely on Atari's external QA departments to test them. This slows things down a bit as well. The good news is that the gap between patch releases should get more narrow as we refine the patching process and everything gets synched up better.
9. Script functions needed. As soon as we get past fixing the more major issues (Updating PWCs, version validation, etc) we will be able to put more time into addressing specific scripting requests.
10. Same as 9.
11. Toolset stablity. This is something we will always be working on as crashes are reported. Hopefully improvements are seen in future patches.
12. Limited info in the dedicated server. I agree that there needs to be a lot more 'administrative' type information exposed in the dedicated server UI and the servermonitor UI. Once we have more major issues resolved, we can start looking into those kinds of less severe issues.
<font size="3" face="Verdana, Arial" color="#cc6600">Feargus Urquhart, CEO</font>
Monk Weapons and Two-Weapon Fighting (http://nwn2forums.bioware.com/forums/viewpost.html?topic=539352&post=4732990&forum=110&highlight=)
I had the QA staff here check Khelgar and they are pretty sure that he is working correctly with the number of attacks and BAB that he has after becoming a monk. Was there something specific that anyone noticed that was wrong?
<font size="3" face="Verdana, Arial" color="#cc6600">Rob McGinnis</font>
Say Hello to Your Community Representatives! (http://nwn2forums.bioware.com/forums/viewpost.html?topic=541480&post=4732304&forum=109&highlight=)
We're looking into that. They may not get an icon by the threads, but they might be able to have a logo by their names.
More: <hr />Is it wise for DLA to have a monopoly on CC stuff?<hr />I have no problem with them both being from DLA. They are reporting back to me what the CC people have posted. Their suggestions and recomendations will be backed up by the threads in the forums.
We have the Community Rep system structured so that one person or organization cannot monopolize on what gets fixed/implemented. All the reps have a say in the suggestions, and I listen to all the reps before I finalize how and what I present internally.
The Community Rep program is not about Obsidian or DLA or any other organization. It is about the Community as a whole. Your voice is what will drive change.
We are just getting started but, after some time of working with the Rep system, if anyone feels they are not being represented properly or fairly, I invite you to send me a PM and explain your side to me. All messages will be kept confidential.
Can't log in via NWN2 (http://nwn2forums.bioware.com/forums/viewpost.html?topic=539265&post=4732340&forum=116&highlight=)
Try putting a copy of your NWCDKey.ini file in your My DocumentsNeverwinter Nights 2 folder.
I think I had this same problem before and this fixed it.
Can't see terrain in toolset... (http://nwn2forums.bioware.com/forums/viewpost.html?topic=540526&post=4732998&forum=113&highlight=)
Hang on to those corrupted areas. I think I may have you guys FTP them to me if I can't seem to get this issue to happen for me.
Darkvision Adjustments (http://nwn2forums.bioware.com/forums/viewpost.html?topic=533911&post=4733211&forum=115&highlight=)
We are actually working on something to consolidate all the Questions and answers in one place where you can look things up by category and comment to ask for further clarification or give opinions.
<font size="3" face="Verdana, Arial" color="#cc6600">J.E. Sawyer, Lead Designer</font>
e-mail bugs reports?? What's wrong with talking about in forums? Is the list too long? (http://nwn2forums.bioware.com/forums/viewpost.html?topic=541669&post=4733533&forum=109&highlight=)
E-mailing bugs to a centralized list means that there's one place for us to look at all bugs reported by endusers.
More: <hr />You can read those lists in forums too,but we can't read the e-mails you get...<hr />This is the General Discussion forum, which happens to also contain threads about bugs. Some people also talk about bugs in threads that are not specifically about bugs. Threads in this forum about bugs are not, as a rule, closed/deleted/moved, so feel free to talk about them here. Just don't expect that we will catch everything that's mentioned.
E-mailing them to the addresses listed in the stickied post helps assure that they go to a centralized location for QA and development.
<font size="3" face="Verdana, Arial" color="#cc6600">Rich Taylor, Programmer</font>
Top missing features and bugs from PW standpoint. (http://nwn2forums.bioware.com/forums/viewpost.html?topic=539943&post=4732241&forum=118&highlight=)
Thanks for this thread, everyone. I will address some of the great points weby has made in the initial post. Some things I can update everyone on, other things I can only say that we're still working on a solution for.
1 - Indication of required files and where to get them. I agree that this is a severe problem. The method(s) of distributing custom content needs improvement as the current methods for integrating custom information into a user's build are very inconvenient. We're still working on ways to improve this. While I wish I could go into specifics on this, I can't right now.
2 - Automatic updating of custom content is another thing where all I can say is we're working on it. Since PWC files compress down to about the size of a mp3 in many cases, it might become viable to update them directly from the server hosting the game with the option of providing alternative download locations for them if uploading directly from the server strains bandwidth. More information about what we're doing with this stuff will come out when we've made some more decisions on our end.
3 - Module sizes. The dynamic area loading/unloading is something that I have been thinking about for a long time. There are a number of problems with trying to get a change of that scale into the engine, but we'll see what happens. Also, it is my understanding that portal support is currently broken which would prevent even the multi-server approach from being an option. We are working on that as well.
4 - DM Client Crashing the Server. We have resolved as many of these crashes as we could fine with regards to the DM client. These fixes should be coming in the 1.04 patch. If there are still any remaining crashes caused by the DM Client after 1.04, we will definitely look into them.
5 - No command line loading of directory-style modules via the dedicated server. I wasn't aware of this problem. I'll have it added to our issue tracking lists.
6 - There will be an increased focus on server stability for the 1.05 patch. We are aware of a number of the crash issues and memory leaks you are running into and will be working on resolving them.
7 - Linux Dedicated Server. I wish I had good news here, but I don't. You don't need to sell me on the importance of a Linux dedicated server. I felt it was important to have one from the beginning. Unfortunately, there were major systems decisions made along the way of developing NWN2 that make it borderline impossible to create a Linux dedicated server port at this time. By the time I learned of these changes and what it would mean about the possability of a Linux Server, it was too late to reverse the changes. While I won't say that there will never be a Linux dedicated server, I will say that it is unlikely. :/
8 - Language Version Patches. Yeah, sorry about the huge delay on the language version patches for 1.03. This was mostly caused by the staggered -releases- of the different languages, which we had no control over at Obsidian. Since the different languages were released at different days, it threw off the patching for the other language versions as well. For example, while we were working on the 1.02 patch for English, we were also still working on getting the Release version of Russian and Polish done. This meant that when we moved to working on 1.03, some of the language versions were already way behind. There is also a problem in that we can't test the localized versions internally and have to rely on Atari's external QA departments to test them. This slows things down a bit as well. The good news is that the gap between patch releases should get more narrow as we refine the patching process and everything gets synched up better.
9. Script functions needed. As soon as we get past fixing the more major issues (Updating PWCs, version validation, etc) we will be able to put more time into addressing specific scripting requests.
10. Same as 9.
11. Toolset stablity. This is something we will always be working on as crashes are reported. Hopefully improvements are seen in future patches.
12. Limited info in the dedicated server. I agree that there needs to be a lot more 'administrative' type information exposed in the dedicated server UI and the servermonitor UI. Once we have more major issues resolved, we can start looking into those kinds of less severe issues.