SM3 Map Format - Revision history

Flozi: recat to deprecated

2013-10-27T19:28:15Z

recat to deprecated

← Older revision		Revision as of 20:28, 27 October 2013
Line 1:		Line 1:
	{{~~Delete~~}}[[Engine_Development\|Development]] < [[Map_development\|Map Development]] < {{FULLPAGENAME}}		{{Deprecated}}[[Engine_Development\|Development]] < [[Map_development\|Map Development]] < {{FULLPAGENAME}}


Line 254:		Line 254:

	* fix bugs		* fix bugs

	~~[[Category:Map making]]~~

2013-08-10T02:41:49Z

sm3 has been removed from the engine

← Older revision		Revision as of 03:41, 10 August 2013
Line 1:		Line 1:
	[[Engine_Development\|Development]] < [[Map_development\|Map Development]] < {{FULLPAGENAME}}		{{Delete}}[[Engine_Development\|Development]] < [[Map_development\|Map Development]] < {{FULLPAGENAME}}

2013-03-21T08:23:46Z

1cat

2012-02-15T22:22:24Z

Introduction

← Older revision		Revision as of 23:22, 15 February 2012
Line 6:		Line 6:
	As opposed to the original SMF renderer, the SM3 map renderer allows multiple texture layers rendered on the terrain. This allows for higher texture resolutions and improved lighting such as bumpmapping/specular mapping.		As opposed to the original SMF renderer, the SM3 map renderer allows multiple texture layers rendered on the terrain. This allows for higher texture resolutions and improved lighting such as bumpmapping/specular mapping.

	Hugh Perkins has been working on a SM3 map editor:		Hugh Perkins has been working on a [[Maps:Map_Designer\|SM3 map editor]]
	~~http://springrts.com/phpbb/viewtopic.php?t=8094~~

	~~see~~
	~~https://github.com/hughperkins/SpringMapDesigner/~~
	~~for the source-code.~~

	== Map specification ==		== Map specification ==

2012-02-15T22:20:03Z

Introduction

← Older revision		Revision as of 23:20, 15 February 2012
Line 7:		Line 7:

	Hugh Perkins has been working on a SM3 map editor:		Hugh Perkins has been working on a SM3 map editor:
	http://~~taspring.clan-sy~~.com/phpbb/viewtopic.php?t=8094		http://springrts.com/phpbb/viewtopic.php?t=8094

			see
			https://github.com/hughperkins/SpringMapDesigner/
			for the source-code.

	== Map specification ==		== Map specification ==

2009-08-31T17:39:58Z

← Older revision		Revision as of 18:39, 31 August 2009
Line 1:		Line 1:
			[[Engine_Development\|Development]] < [[Map_development\|Map Development]] < {{FULLPAGENAME}}


	== Introduction ==		== Introduction ==

2007-03-01T07:44:33Z

Cleaned up the SM3 code bits to have consistent indenting and comments and stuff

2007-01-20T16:17:13Z

@@ Line 240: / Line 240: @@
        ..  other map tags ...
+  }
 == TODO ==

2007-01-12T22:17:23Z

← Older revision		Revision as of 23:17, 12 January 2007
Line 2:		Line 2:

	As opposed to the original SMF renderer, the SM3 map renderer allows multiple texture layers rendered on the terrain. This allows for higher texture resolutions and improved lighting such as bumpmapping/specular mapping.		As opposed to the original SMF renderer, the SM3 map renderer allows multiple texture layers rendered on the terrain. This allows for higher texture resolutions and improved lighting such as bumpmapping/specular mapping.

			Hugh Perkins has been working on a SM3 map editor:
			http://taspring.clan-sy.com/phpbb/viewtopic.php?t=8094

	== Map specification ==		== Map specification ==
Line 240:		Line 243:
	== TODO ==		== TODO ==

	* ~~dynamic shadow mapping support~~		* fix bugs
	* shadowmap storage, so the resolution can be increased

	[[Category:Map making]]		[[Category:Map making]]
	[[Category:SM3 map format]]		[[Category:SM3 map format]]

2006-12-05T02:43:26Z

Feature placement

← Older revision		Revision as of 03:43, 5 December 2006
Line 208:		Line 208:
	== Feature placement ==		== Feature placement ==

	The feature specification is done with a list of feature type names in the SM3 itself, and with an binary datafile that contains all the feature positions, orientations.		The feature specification is done with a list of feature type names in the SM3 itself, and with a binary datafile that contains all the feature positions, orientations.
	Feature types are specified like this:		Feature types are specified like this: