Maximum number of zones.
Moderators: Moderator, DM
-
Blackman D
- Retired Staff
- Posts: 4818
- Joined: Sat Sep 12, 2009 5:43 am
- Location: IL
Re: Maximum number of zones.
not sure what you mean? placeables and environmental objects are one thing and special effects are something else
everyone is evil till proven otherwise
-
Aspect of Sorrow
- Custom Content
- Posts: 2702
- Joined: Fri Mar 28, 2014 7:11 pm
- Location: Reliquary
Re: Maximum number of zones.
Fortunately BICs are generally the least of the resource concerns, though mule characters have a larger impact, especially with items containing descriptions that is rarely utilized, but they are prone to write corruption and ideally should be backed up every fifteen minutes using differential software.Storm Munin wrote:I should cut down on the numbers in my server vault.
Just 1 under the Int32 limit. If the nwserver process could take advantage of 64bit memory widths this becomes generally a moot point, but players on systems without an SSD would abhor the project. NWN2 in general would benefit from extra memory.DM Pun Pun wrote:There is no limit to how many areas you can have in a module. However, every area makes the module size bigger, and when you hit a certain size, performance will suffer.
A blank canvas of both interior and exterior is generally marginal in resource to the server, the interior limitation of space I imagine is the biggest contributor to a designer's output which in turn lends to significantly smaller requirements by the time when both are considered production ready. Foilage and texture information is a mess. Some kind of minifying effect applied will relieve a lot of wasted memory commits.LISA100595 wrote:Also Exterior Areas take up a Ton of more resources than Interiors.
A SEF with a model has fewer lines of information for it's property whereas a model without C2/C3 converted as an environmental object contains 22 properties. A placeable can contain 84 properties, excluding nested (inventory).Maximvs wrote:Very interesting information... While we're at it, what's the least taxing on a server host, between a placeable converted as environmental and a special effect that looks exactly the same?
-
Maximvs
- Posts: 281
- Joined: Sun May 17, 2009 3:45 pm
Re: Maximum number of zones.
Where can I find information on all the 2da files and what they all do? I used to visit that gameofthrones persistent world website because they had it all explained there but the website is now down... the nwn2 wiki info is far from complete and I can't find a tutorial either on nwn vault.
MmmmMMMMmmm, tasty humanz, hmmmmMMM!!!
-
Blackman D
- Retired Staff
- Posts: 4818
- Joined: Sat Sep 12, 2009 5:43 am
- Location: IL
Re: Maximum number of zones.
2DA is short hand for nightmare
pain in the butt to edit and you can mess up stuff if you do it wrong, but yea no idea where to find info, im sure AoS, ras or D47 might know
pain in the butt to edit and you can mess up stuff if you do it wrong, but yea no idea where to find info, im sure AoS, ras or D47 might know
everyone is evil till proven otherwise
-
Aspect of Sorrow
- Custom Content
- Posts: 2702
- Joined: Fri Mar 28, 2014 7:11 pm
- Location: Reliquary
Re: Maximum number of zones.
The resources you're probably requesting are listed here. You can search for them via google cache using the following query
Feat 2da
Classes
Skills
An editor based similarly to the NWN1 2DA tools can be obtained here. Be mindful of the v2 rendition, and not NWN1's.
Alternatively you can use Wikia's entries.
If you need any specific information certainly let me know. I've begun a parser that takes the contents of each for BG to start replicating nwn2db but always up to date with custom content.
Code: Select all
game of thrones nwn2 2da pdfClasses
Skills
An editor based similarly to the NWN1 2DA tools can be obtained here. Be mindful of the v2 rendition, and not NWN1's.
Alternatively you can use Wikia's entries.
If you need any specific information certainly let me know. I've begun a parser that takes the contents of each for BG to start replicating nwn2db but always up to date with custom content.
-
Maximvs
- Posts: 281
- Joined: Sun May 17, 2009 3:45 pm
Re: Maximum number of zones.
Holy mother f---- christ thank you wow google cache didnt know that existed >.>
... Aaaand it's not as good as I thought. How do you use google cache anyways? I type in your cache thing on top of my browser but it redirects to standard google. Anyways I guess this is forever lost as I can't access the extra info it had over the Wiki. Thanks though. Damn.
... Aaaand it's not as good as I thought. How do you use google cache anyways? I type in your cache thing on top of my browser but it redirects to standard google. Anyways I guess this is forever lost as I can't access the extra info it had over the Wiki. Thanks though. Damn.
MmmmMMMMmmm, tasty humanz, hmmmmMMM!!!
-
ComeAndSee
- Posts: 18
- Joined: Wed Oct 21, 2015 8:50 pm
Re: Maximum number of zones.
Each time the server module starts it copies the module folder and everything in it (maps, blueprints, etc) to a temporary folder and then loads all the files into memory. If you have 255 areas (let's say evenly split interior/exterior) you're talking over a gigabyte that have to be loaded each time the module starts up. The server then has to emulate and manage the resources in each area.
From first-hand experience; more maps doesn't necessarily mean more lag or instability. Player count and the amount of people on a specific map and what they're doing has a bigger impact. A map with a huge amount of placeables for example puts a lot of work on the server processor because it's constantly communicating with clients telling them what they can see on their screen.
Exterior maps are much heavier on resources because of the way walkmesh and terrain molding is handled. An interior map usually falls between 50KB-1MB depending on how many tiles you have (lets say 32x32). An exterior map with the same dimensions 32x32 may be well over 50 MBs.
2da files can be edited with programs like TLKedit. It's more or less a spreadsheet that contains information that your client reads from to determine things ingame like classes, races, model information, etc.
From first-hand experience; more maps doesn't necessarily mean more lag or instability. Player count and the amount of people on a specific map and what they're doing has a bigger impact. A map with a huge amount of placeables for example puts a lot of work on the server processor because it's constantly communicating with clients telling them what they can see on their screen.
Exterior maps are much heavier on resources because of the way walkmesh and terrain molding is handled. An interior map usually falls between 50KB-1MB depending on how many tiles you have (lets say 32x32). An exterior map with the same dimensions 32x32 may be well over 50 MBs.
2da files can be edited with programs like TLKedit. It's more or less a spreadsheet that contains information that your client reads from to determine things ingame like classes, races, model information, etc.
-
Aspect of Sorrow
- Custom Content
- Posts: 2702
- Joined: Fri Mar 28, 2014 7:11 pm
- Location: Reliquary
Re: Maximum number of zones.
NWNX4's xp_fastboot creates hardlinks rather than the default action of file copies, shortening the time drastically for larger modules. Realistically, all static files (mod, hak, tlk, etc) should be copied to and reside on a software ramdisk if enough memory in the system is available to lessen binary IO throughput. BICs as well if periodically writing out the differentials to disk. 500Mbps SSDs versus 7500Mbps ramdisks is an order of magnitude faster (15x).ComeAndSee wrote:Each time the server module starts it copies the module folder and everything in it (maps, blueprints, etc) to a temporary folder and then loads all the files into memory. If you have 255 areas (let's say evenly split interior/exterior) you're talking over a gigabyte that have to be loaded each time the module starts up. The server then has to emulate and manage the resources in each area.
Agreed, though it's more network throughput that takes a hit in these scenarios unless combat picks up.ComeAndSee wrote:From first-hand experience; more maps doesn't necessarily mean more lag or instability. Player count and the amount of people on a specific map and what they're doing has a bigger impact. A map with a huge amount of placeables for example puts a lot of work on the server processor because it's constantly communicating with clients telling them what they can see on their screen.
While the resource is heavier on disk, terrain data calculated for both interior and exteriors remain computationally similar to nwserver regarding pathfinding. Adjusted Z will still always apply.ComeAndSee wrote:Exterior maps are much heavier on resources because of the way walkmesh and terrain molding is handled. An interior map usually falls between 50KB-1MB depending on how many tiles you have (lets say 32x32). An exterior map with the same dimensions 32x32 may be well over 50 MBs.
-
Cubicle
- Retired Staff
- Posts: 540
- Joined: Tue Jun 12, 2012 6:44 am
Re: Maximum number of zones.
AoS, if we were to add 10 exterior areas instead of 10 interior areas, how much of a difference would adding the exteriors actually have on the server IG?Aspect of Sorrow wrote:While the resource is heavier on disk, terrain data calculated for both interior and exteriors remain computationally similar to nwserver regarding pathfinding. Adjusted Z will still always apply.
-
Aspect of Sorrow
- Custom Content
- Posts: 2702
- Joined: Fri Mar 28, 2014 7:11 pm
- Location: Reliquary
Re: Maximum number of zones.
To consider just terrain alone.
Flat unedited exterior TRX (optimized walkmesh and form attribution for clients) has negligible size differences than an interior. The more complex the terrain, the more representation is necessary. Walk/nowalk having fewer impacts than walkmesh cutters will help keeping that data to a minimum, but if you were to heightmap generate using perlin filter fractal software, the terrain TRX is significantly larger, albeit giving a more natural aesthetic to view. An impact largely to disk first, pathfinding calculations second. Additional texturing, water, grass, increase the TRX in size. The TRN generated is only needed for the toolset.
The interior TRX is smaller in part due to defining absolutes of the tile it represents, but can consist of the tile attributes for that particular cell. The more complex tiles have their boundaries represented and unoptimized tiles will create a complicated pathfinding option as seen in the Batari caves. Interior will always trump exterior in efficiency when it comes to server resources consumed, though exceptions to the rule exist, such as creating an entire area's representation with a single model on the same Z.
Both increase equally for each placeable and environmental object represented thereafter.
Unpatched, nwserver only accesses approximately 2GB of memory even on a 64bit machine, WoW64 will allow under certain conditions for 32bit applications to take advantage of higher capacities (4GB in many cases) with tools like memalloc, which would ease this scenario, benefiting additional areas, as well as the NWNX4 NSS->MSIL Script Accelerator. And, oddly enough, desktop Intel CPUs with unlocked overclocking modifier options such as the Intel i7-6950X which operate single threaded processes extremely quickly are better providers of horsepower to nwserver than their Xeon server counterparts.
We can always play the "throw more hardware at it game" but realistically refactoring and optimizing what's existing, both in nwscript and area design, is immediately beneficial to the project.
Flat unedited exterior TRX (optimized walkmesh and form attribution for clients) has negligible size differences than an interior. The more complex the terrain, the more representation is necessary. Walk/nowalk having fewer impacts than walkmesh cutters will help keeping that data to a minimum, but if you were to heightmap generate using perlin filter fractal software, the terrain TRX is significantly larger, albeit giving a more natural aesthetic to view. An impact largely to disk first, pathfinding calculations second. Additional texturing, water, grass, increase the TRX in size. The TRN generated is only needed for the toolset.
The interior TRX is smaller in part due to defining absolutes of the tile it represents, but can consist of the tile attributes for that particular cell. The more complex tiles have their boundaries represented and unoptimized tiles will create a complicated pathfinding option as seen in the Batari caves. Interior will always trump exterior in efficiency when it comes to server resources consumed, though exceptions to the rule exist, such as creating an entire area's representation with a single model on the same Z.
Both increase equally for each placeable and environmental object represented thereafter.
Unpatched, nwserver only accesses approximately 2GB of memory even on a 64bit machine, WoW64 will allow under certain conditions for 32bit applications to take advantage of higher capacities (4GB in many cases) with tools like memalloc, which would ease this scenario, benefiting additional areas, as well as the NWNX4 NSS->MSIL Script Accelerator. And, oddly enough, desktop Intel CPUs with unlocked overclocking modifier options such as the Intel i7-6950X which operate single threaded processes extremely quickly are better providers of horsepower to nwserver than their Xeon server counterparts.
We can always play the "throw more hardware at it game" but realistically refactoring and optimizing what's existing, both in nwscript and area design, is immediately beneficial to the project.
-
Cubicle
- Retired Staff
- Posts: 540
- Joined: Tue Jun 12, 2012 6:44 am
Re: Maximum number of zones.
Much appreciated, AoS! Some good information right there.
-
Maximvs
- Posts: 281
- Joined: Sun May 17, 2009 3:45 pm
Re: Maximum number of zones.
Do objects converted as environmental ones still have 22 properties when they are on an unwalkable walkmesh, in a walkmesh cutter or outside the zone?
MmmmMMMMmmm, tasty humanz, hmmmmMMM!!!
-
Aspect of Sorrow
- Custom Content
- Posts: 2702
- Joined: Fri Mar 28, 2014 7:11 pm
- Location: Reliquary
-
Maximvs
- Posts: 281
- Joined: Sun May 17, 2009 3:45 pm
Re: Maximum number of zones.
Interesting... forgive me for pushing the same subject with yet another question at a different angle... lol.
Do three small placeable mushroom create more, an equal amount or less lag than one huge mushroom?
Do three small placeable mushroom create more, an equal amount or less lag than one huge mushroom?
MmmmMMMMmmm, tasty humanz, hmmmmMMM!!!
-
Aspect of Sorrow
- Custom Content
- Posts: 2702
- Joined: Fri Mar 28, 2014 7:11 pm
- Location: Reliquary
Re: Maximum number of zones.
This impact has different points.
To the toolset and onto the module, irrespective of the model, it is still represented by the same context as any other object whether placeable or env, the only difference is the length of the string of the represented model name.
To the player client, the model's impact on disk and in the renderer depends on the complexity of the model's polycount and the texture therein. A single mushroom model could have 1,000 polygons to render for every frame, while a group of mushrooms of a different model could have 2,000 combined. The addition of polygons rendered for every frame impacts the client FPS being drawn on screen. This is where LOD (level of detail) comes in. Game designers take advantage of this for higher performance as objects that are far away at an arbitrary distance are reduced in their polycount, but NWN2 appears to be hit and miss with LOD in general. Scaling in NWN2 does not adjust the polycount. A 0.1,0.1,0.1 scaled object at 1K poly is still a 1K poly rendered on screen, even if it appears as a single pixel.
TheLier had pointed out in game once that it did not matter that the game was created in 2006, that it is still an unoptimized renderer. While true regarding the renderer, the point missed is that newer GPUs are exponentially faster at calculating the tris/poly, even those in the budget echelon of the nV 900 series than the 6800 / 7800 model cards that existed in that timeframe, 7 entirely new architectures have since come and gone.
To the toolset and onto the module, irrespective of the model, it is still represented by the same context as any other object whether placeable or env, the only difference is the length of the string of the represented model name.
To the player client, the model's impact on disk and in the renderer depends on the complexity of the model's polycount and the texture therein. A single mushroom model could have 1,000 polygons to render for every frame, while a group of mushrooms of a different model could have 2,000 combined. The addition of polygons rendered for every frame impacts the client FPS being drawn on screen. This is where LOD (level of detail) comes in. Game designers take advantage of this for higher performance as objects that are far away at an arbitrary distance are reduced in their polycount, but NWN2 appears to be hit and miss with LOD in general. Scaling in NWN2 does not adjust the polycount. A 0.1,0.1,0.1 scaled object at 1K poly is still a 1K poly rendered on screen, even if it appears as a single pixel.
TheLier had pointed out in game once that it did not matter that the game was created in 2006, that it is still an unoptimized renderer. While true regarding the renderer, the point missed is that newer GPUs are exponentially faster at calculating the tris/poly, even those in the budget echelon of the nV 900 series than the 6800 / 7800 model cards that existed in that timeframe, 7 entirely new architectures have since come and gone.