Aurora D Light

• The name of the light can be important if you're creating tiles, as you have to follow certain naming conventions then. If you're not following these naming conventions, the lights will be exported and work, but they won't be accessable in the tolset. To get the correct naming for tilelights, name them the same as the modelbase (eg ttr01_a01_01) and add the following...
  • ml1 - Mainlight 1 - (eg ttr01_a01_01ml1)
  • ml2 - Mainlight 2 - (eg ttr01_a01_01ml2)
  • sl1 - Sourcelight 1 - (eg ttr01_a01_01sl1) - this doesn't HAVE to be a light, but can be a simple helper instead
  • sl2 - Sourcelight 2 - (eg ttr01_a01_01sl2) - this doesn't HAVE to be a light, but can be a simple helper instead

[edit] Light Parameters

• The radius of the light is the effective radius (in cm) of the light.
• The multiplier can be used to enlarge the inner radius of the light, as well as create negative lighting.
• Priority The NWN engine has a light manager to prevent the engine from counting too many lights that affect dynamic objects. This relates to the light count setting in the game. The priority order is like this...
  • 1 - Highest - Sun/Moon
  • 2 - High... - Torches / Light spells
  • 3 - Medium. - Spells, general lights
  • 4 - Low.... - High-Priority Tile Lights
  • 5 - Lowest. - Magic Weapon Lights, Tile Lights
• Fading Light - Enable this to make lights turn on smoothly, instead of instantly turning to full brightness. As lights only get processed when they are on-screen, this helps with the general feel of tilesets for example - you don't want to have flickering ambient lights there.
• Color - you can set the color of the light here. Either use the color box and choose a color or enter RGB values in the fields. Note that the color is ignored on tile mainlights and sourcelights as this parameter gets controlled by the setting in the toolset.
• Negative Light - make this a negative light, make sure to up the multiplier value for best effect.
• Ambient - turn this on to create an ambient light, when off the light will affect diffuse colors.
• Is Dynamic Light , Affect Dynamic Objects - lights can have one of three dynamic states in NWN. Based on the setting the light will be more or less performance hungry. These two checkboxes control this.
  • Static - off/off - This setting will only affect static meshes, which basically is only TileGeometry. You can use this to shade certain areas on tiles for example.
  • Dynamic - on/on - This will affect all geom, dynamic and static, and should be turned on for animated lights. This is the most hungry setting - use sparingly.
  • Hybrid - off/on - The engine will determine if the light should be considered Static or Dynamic based on the situation. Sounds like the other two are useless, but the engine isn't always sure about your lighting motives :)
• Shadow - if the light should make objects cast a shadow based on this light.

• Tilelight Presets is a quick way to set the the standard settings for tile mainlights. When you select either Mainlight 1 or Mainlight 2 the light will be renamed, based on it's parent to fulfill the naming convention for tile mainlights (MODELNAMEml1 for example) and standard settings will be applied. The settings are based on Bioware suggestions in the Tile Creation Tutorial. The only difference between ml1 and ml2 is the name and the lightradius.

[edit] Lens Flares

[edit] Troubleshooting

Here are a few problems I've run into while bugtesting a tileset:

• Problem: If I set the tileset to torchlit only, I get individual tiles that are brightly lit. The light from these tiles spill over onto adjacent tiles or is contained within the tile but the transition from bright to dark is soft.
• Problem: If I set the tileset to torchlit only, some walls are dimly lit but others are dark.
  • Possible Solution: Check your light naming. I've found that if your naming is incorrect (ie you forget to add ml1, ml2) the toolset interprets the light as being on full brightness, all the time, and much larger than normal. These lights may have a wide enough range to affect lighting on every other tile in the same map.

• Problem: If I set the tileset to torchlit only, I get individual tiles that are brightly lit. The light from these tiles DO NOT spill over onto adjacent tiles and the transition from light to dark surfaces is very distinct.
• Problem: If I set the tileset to torchlit only, I get individual objects/meshes/faces that are brightly lit.
  • Possible Solution: This is most likely a texturing problem. If you extract the texture from that mesh in max, you may notice that although there is a map applied to the texture, the base ambient and diffuse colors are set to something other than grey. These colors aren't visible on the tile itself but they appear to control the self illumination level of the mesh. ex: a white background color will cause the mesh to be fully self-illuminated. The default should have an RGB value of 150/150/150. Try resetting the base back to grey and re-exporting the model.

• Problem: No matter what I put the tileset lighting settings at, all of the tiles are brightly lit.
  • Possible Solution: This is a more widespread version of the two problems above. Either there are many misnamed lights in the tileset that together serve to wash everything out or every texture was created with a white base color or both. In one case, I had broken lights in the default "wall" tile of an interiors tileset which washed everything out. In another case I had a tileset where all the base colors were white. If all the base colors are wrong, but wrong in the same way (ie all white) it may be easier to use a text file find & replace tool to just change the setting in all the models at once.

Back to NWmax_Documentation

phentermine buy phentermine cheap phentermine phentermine 37 5 phentermine diet pills phentermine online phentermine order phentermine sale