GRFResourceManagement - Revision history

FooBar: /* Description of GRM-ops */ note on not splitting blocks for OpenTTD

2012-02-13T13:45:42Z

Description of GRM-ops: note on not splitting blocks for OpenTTD

← Older revision		Revision as of 13:45, 13 February 2012
Line 82:		Line 82:
	Action D returns its result (if any) in the given <target> parameter. If the result is marked as "(none)" in the above table, the <target> parameter is not modified.		Action D returns its result (if any) in the given <target> parameter. If the result is marked as "(none)" in the above table, the <target> parameter is not modified.

	The "reserve" and "find" operations will try to find a contiguous block of <count> entries, and store the first number in the target parameter of the action D. If not enough entries can be found, the grf file is deactivated.		The "reserve" and "find" operations will try to find a contiguous block of <count> entries, and store the first number in the target parameter of the action D. If not enough entries can be found, the grf file is deactivated. For OpenTTD it's not useful to split large blocks into multiple smaller blocks, as it is unlikely that even a large block can't be found in the 16777216 allocatable sprites.

	The "check" and "mark" operations use the value stored in the ''target'' parameter of the action D, and check/mark the block of <count> entries starting from that number. If not all entries are available, the grf file is deactivated.		The "check" and "mark" operations use the value stored in the ''target'' parameter of the action D, and check/mark the block of <count> entries starting from that number. If not all entries are available, the grf file is deactivated.

Pm-bot: use GRFID consistently

2011-06-15T16:06:09Z

use GRFID consistently

← Older revision		Revision as of 16:06, 15 June 2011
Line 77:		Line 77:

	\|-		\|-
	\|06\|\|\DO\|\|Get Owner\|\|GRF-ID of owner\|\|Retrieve ~~grfID~~ that has reserved the given ID (or 0 if not reserved)		\|06\|\|\DO\|\|Get Owner\|\|GRF-ID of owner\|\|Retrieve GRFID that has reserved the given ID (or 0 if not reserved)
	\|}		\|}

Pm-bot: use grfID consistently

2011-06-15T16:04:32Z

use grfID consistently

← Older revision		Revision as of 16:04, 15 June 2011
Line 77:		Line 77:

	\|-		\|-
	\|06\|\|\DO\|\|Get Owner\|\|GRF-ID of owner\|\|Retrieve ~~GRFID~~ that has reserved the given ID (or 0 if not reserved)		\|06\|\|\DO\|\|Get Owner\|\|GRF-ID of owner\|\|Retrieve grfID that has reserved the given ID (or 0 if not reserved)
	\|}		\|}

Pm-bot: Beautify wiki markup

2011-06-15T14:48:38Z

Beautify wiki markup

← Older revision		Revision as of 14:48, 15 June 2011
Line 1:		Line 1:

	== Introduction ==		== Introduction ==

Line 16:		Line 15:
	'''Please note:''' This resource management is cooperative. That means that grf files that do not use it can still access all IDs, and the patch will never know about it. Only those grf files that use this resource management will "know" of each other and can be sure not to use conflicting resources. If another grf file then uses a "reserved" ID without telling the patch via an action D, there is nothing that will prevent it from doing so.		'''Please note:''' This resource management is cooperative. That means that grf files that do not use it can still access all IDs, and the patch will never know about it. Only those grf files that use this resource management will "know" of each other and can be sure not to use conflicting resources. If another grf file then uses a "reserved" ID without telling the patch via an action D, there is nothing that will prevent it from doing so.

	==Syntax==		== Syntax ==

	<Sprite-number> * <Length> 0D <target> 00 <GRM-op> FE FF <feature> <count>		<Sprite-number> * <Length> 0D <target> 00 <GRM-op> FE FF <feature> <count>
Line 50:		Line 49:
	For the check, mark, no-fail check, and get-owner operations, <target> must contain the first ID to be operated on.		For the check, mark, no-fail check, and get-owner operations, <target> must contain the first ID to be operated on.

	==Description of GRM-ops==		== Description of GRM-ops ==

	The following operations are available:		The following operations are available:

	Each operation also has a corresponding escape sequence, as listed. See [[GRFActionsDetailed#~~Byte_order~~\|the discussion of escape sequences]] for further information on escape sequences in general.		Each operation also has a corresponding escape sequence, as listed. See [[GRFActionsDetailed#Byte order\|the discussion of escape sequences]] for further information on escape sequences in general.

	{\|		{\|
Line 93:		Line 92:
	For each feature, multiple "find" operations will check for different size blocks, but will always return the same base entry number, so "find" should only be called once for each feature.		For each feature, multiple "find" operations will check for different size blocks, but will always return the same base entry number, so "find" should only be called once for each feature.

	==Support for features==		== Support for features ==

	The following features and feature/GRM-op combinations are supported:		The following features and feature/GRM-op combinations are supported:

Pm-bot: /* Support for features */ suddenly the tag makes sense

2011-06-14T23:28:00Z

Support for features: suddenly the <nowiki> tag makes sense

← Older revision		Revision as of 23:28, 14 June 2011
Line 123:		Line 123:
	X = safe to use		X = safe to use

	* = safe but useless		<nowiki>*</nowiki> = safe but useless

	- = do not use		- = do not use

Pm-bot: /* Feature */ section heading

2011-06-14T23:27:08Z

Feature: section heading

← Older revision		Revision as of 23:27, 14 June 2011
Line 93:		Line 93:
	For each feature, multiple "find" operations will check for different size blocks, but will always return the same base entry number, so "find" should only be called once for each feature.		For each feature, multiple "find" operations will check for different size blocks, but will always return the same base entry number, so "find" should only be called once for each feature.

			==Support for features==
	==Feature==

	The following features and feature/GRM-op combinations are supported:		The following features and feature/GRM-op combinations are supported:

Pm-bot: /* GRM-op */ section title

2011-06-14T23:26:35Z

GRM-op: section title

← Older revision		Revision as of 23:26, 14 June 2011
Line 50:		Line 50:
	For the check, mark, no-fail check, and get-owner operations, <target> must contain the first ID to be operated on.		For the check, mark, no-fail check, and get-owner operations, <target> must contain the first ID to be operated on.

	==GRM-op==		==Description of GRM-ops==

	The following operations are available:		The following operations are available:

Pm-bot: /* GRF Resource Management */ remove unneded heading

2011-06-14T23:25:54Z

GRF Resource Management: remove unneded heading

← Older revision		Revision as of 23:25, 14 June 2011
Line 1:		Line 1:

	== Introduction ==		== Introduction ==

	=GRF Resource Management=

	Preventing conflicts with limited resources		Preventing conflicts with limited resources
Line 8:		Line 6:


	Since 2.0.1 alpha 51, it has been possible to use action D to participate in cooperative resource management.		Since TTDPatch 2.0.1 alpha 51, it has been possible to use action D to participate in cooperative resource management.

	This feature is useful for avoiding resource conflicts between grf files. A file may query the available resources, check whether certain IDs are available, and/or mark them as reserved. Then, an action 6 will enter the actual values in the appropriate action entries, for example action 0 or 3 for vehicles, and action A for sprites. Alternatively, one can use another action D to set variable 99 and have it adjust the IDs of the relevant actions appropriately.		This feature is useful for avoiding resource conflicts between grf files. A file may query the available resources, check whether certain IDs are available, and/or mark them as reserved. Then, an action 6 will enter the actual values in the appropriate action entries, for example action 0 or 3 for vehicles, and action A for sprites. Alternatively, one can use another action D to set variable 99 and have it adjust the IDs of the relevant actions appropriately.

Pm-bot: Bot: Automated text replacement (--= +==)

2011-06-14T23:25:11Z

Bot: Automated text replacement (--= +==)

Show changes

Orudge: 2 revisions

2011-06-12T19:23:30Z

2 revisions

← Older revision	Revision as of 19:23, 12 June 2011
(No difference)