You cannot select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

scrawl 29556a1802 More consistent wording of errors/warnings ... A Warning indicates a potential problem in the content file(s) that the user told OpenMW to load. E.g. this might cause an object to not display at all or as intended, however the rest of the game will run fine. An Error, however, is more likely to be a bug with the engine itself - it means that basic assumptions have been violated and the engine might not run correctly anymore. The above mostly applies to errors/warnings during game-play; startup issues are handled differently: when a file is completely invalid/corrupted to the point that the engine can not start, that might cause messages that are worded as Error due to the severity of the issue but are not necessarily the engine's fault. Hopefully, being a little more consistent here will alleviate confusion among users as to when a log message should be reported and to whom.		8 years ago
..
controller.cpp	Use ref_ptr	9 years ago
controller.hpp	Remove debug output	9 years ago
nifloader.cpp	More consistent wording of errors/warnings	8 years ago
nifloader.hpp	More renaming of TextureManager -> ImageManager	9 years ago
particle.cpp	More consistent wording of errors/warnings	8 years ago
particle.hpp	Add explicit handling of most commonly used nodes to NodeVisitors to avoid excessive virtual function calls	8 years ago
userdata.hpp	Update comment, osgAnimation::RigGeometry is no longer used	8 years ago