Permissive Field of View

From RogueBasin
(Difference between revisions)
Jump to: navigation, search
(Moved the Roguelike-lib-for-java and permissive-fov-in-python links down to the libraries section. Tabified the libraries section.)
m (link to ruby impl.)
Line 42: Line 42:
 
| [[Permissive Field of View in Python]]
 
| [[Permissive Field of View in Python]]
 
| Python
 
| Python
| [[Precise Permissive Field of View]]
+
|rowspan=4| [[Precise Permissive Field of View]]
 
|-
 
|-
 
| [[permissive-fov]]
 
| [[permissive-fov]]
 
| C/C++
 
| C/C++
| [[Precise Permissive Field of View]]
 
 
|-
 
|-
 
| [[Roguelike Library For Java]]
 
| [[Roguelike Library For Java]]
 
| Java
 
| Java
| [[Precise Permissive Field of View]]
+
|-
 +
| [[Ruby precise permissive FOV implementation|Ruby implementation]]
 +
| Ruby
 
|}
 
|}

Revision as of 00:19, 30 August 2008

Contents

What is Permissive Field of View?

Permissive field of view defines visibility more loosely than other Field of Vision methods. A destination square is visible from a source square if there is any unobstructed line from some point in the source square to some point in the destination square. This means that players and monsters will automatically 'peek' around corners, for example. It also means that field of view is symmetric. That is to say that if a destination square is visible from a source square, then that source square is also visible from the destination square. Some approximation algorithms might lose the property of guaranteed symmetry.

One tricky corner case are literally the corners. There are two questions that must be answered. Are corners of squares valid points in the source and destination squares for determining visibility? And do corners of walls obstruct line of sight? Different algorithms may answer these questions in different ways.

Advantages

  • Symmetry of field of view may make ranged combat more sensible.
  • Monsters cannot sneak up on the player as easily.
  • Reduced player exploitation of line of sight artifacts.
  • There is an existing library implementing it.
  • May make certain aspects of the game easier (realistic lighting).

Disadvantages

  • The most complicated method to understand and implement (and therefore debug).
  • The player cannot sneak up on monsters more easily.
  • May ruin play balance of current games.
  • It is more difficult for the player to withdraw from ranged combat.

How do I implement it?

There are a number of articles describing different methods:

  • Isaac_s_fast_beamcasting_LOS -- An approximate algorithm using 'wide beams' sent out at fixed slopes. The larger the radius, the more beams must be sent out to avoid artifacts.
  • Mutual_Visibility_Field_Of_View -- Uses the corners of squares to determine visibility. In some cases, it does not precisely capture Permissive Field of View. However, the algorithm guarantees symmetry in the field of view.
  • A fast algorithm using pre-cached dependencies is described in the source code for Dungeon Crawl Stone Soup
  • Precise Permissive Field of View -- A fast and, in theory, artifact free variation.

What games use it?

What libraries implement it?

Library Language(s) Algorithm(s)
Permissive Field of View in Python Python Precise Permissive Field of View
permissive-fov C/C++
Roguelike Library For Java Java
Ruby implementation Ruby
Personal tools