Custom Train Tracks - Revision history

Qaisjp: fix typo

2016-10-03T22:12:13Z

fix typo

← Older revision		Revision as of 22:12, 3 October 2016
Line 7:		Line 7:
	\|-		\|-
	\|'''Branch'''		\|'''Branch'''
	\|[https://github.com/multitheftauto/mtasa-blue/tree/feature/custom-train-tracks custom-train-tracks]		\|[https://github.com/multitheftauto/mtasa-blue/tree/feature/custom-train-tracks feature/custom-train-tracks]
	\|-		\|-
	\|'''Branch version'''		\|'''Branch version'''

2016-10-03T22:11:58Z

change branch url!

← Older revision		Revision as of 22:11, 3 October 2016
Line 7:		Line 7:
	\|-		\|-
	\|'''Branch'''		\|'''Branch'''
	\|[https://github.com/multitheftauto/mtasa-blue/tree/custom-train-tracks custom-train-tracks]		\|[https://github.com/multitheftauto/mtasa-blue/tree/feature/custom-train-tracks custom-train-tracks]
	\|-		\|-
	\|'''Branch version'''		\|'''Branch version'''
	\|1.6		\|1.5.3
	\|}		\|}

2016-07-22T22:22:06Z

API: add getNodes again

← Older revision		Revision as of 22:22, 22 July 2016
Line 31:		Line 31:
	track = TrainTrack(...nodes) -- createTrack(node1, node2, node3, ...)		track = TrainTrack(...nodes) -- createTrack(node1, node2, node3, ...)
	track:getNodes() returns a table of Vector3s		track:getNodes() returns a table of Vector3s
			track:getLength() -- getTrainTrack(track)
	-- Default track functions		-- Default track functions
	TrainTrack.removeDefault(int trackID)		TrainTrack.removeDefault(int trackID)
Line 36:		Line 37:

	-- These functions already exist, but I'm not sure how these lengths are used or what they are for		-- These functions already exist, but I'm not sure how these lengths are used or what they are for
	~~float track:getLength() -- getTrainTrack(track)~~
	~~bool track:setLength(float length) -- setTrackLength(track, float length)~~
	</syntaxhighlight>		</syntaxhighlight>

2016-07-22T20:47:42Z

API: add getNodes

← Older revision		Revision as of 20:47, 22 July 2016
Line 30:		Line 30:

	track = TrainTrack(...nodes) -- createTrack(node1, node2, node3, ...)		track = TrainTrack(...nodes) -- createTrack(node1, node2, node3, ...)
			track:getNodes() returns a table of Vector3s
	-- Default track functions		-- Default track functions
	TrainTrack.removeDefault(int trackID)		TrainTrack.removeDefault(int trackID)

2016-07-22T20:15:25Z

m_OriginalTrainTrackData

← Older revision		Revision as of 20:15, 22 July 2016
Line 86:		Line 86:
	We need to make sense of the following things:		We need to make sense of the following things:

	* Why is padding an argument here?		* Why is padding an argument here? (It doesn't do anything, and when Init() is called, real values are provided)
	* Why are values repeated several times?		* Why are values repeated several times?
	* Why does the last repeat have slightly different values?		* Why does the last repeat have slightly different values?

2016-07-21T02:51:55Z

Re-merge: archive section

← Older revision		Revision as of 02:51, 21 July 2016
Line 99:		Line 99:

	=== Re-merge ===		=== Re-merge ===
			<section name="This section has been archived" collapse="true">
	{\| class="wikitable" style="width: auto; table-layout: fixed;"		{\| class="wikitable" style="width: auto; table-layout: fixed;"
	\|-		\|-
Line 129:		Line 130:
	* ... Merged revision(s) 6092-6137 from trunk [https://github.com/multitheftauto/mtasa-blue/commit/61976a30a1edda6150d1840833ab8ac2d22ae59a 61976a30a1edda6150d1840833ab8ac2d22ae59a]		* ... Merged revision(s) 6092-6137 from trunk [https://github.com/multitheftauto/mtasa-blue/commit/61976a30a1edda6150d1840833ab8ac2d22ae59a 61976a30a1edda6150d1840833ab8ac2d22ae59a]

	This means that there are only four commits that need to be merged into the new branch. There is currently a packet issue introduced by the merge that needs to be fixed.		This means that there are only four commits that need to be merged into the new branch. <strike>There is currently a packet issue introduced by the merge that needs to be fixed.</strike>
			</section>
	[[Category: Development]]		[[Category: Development]]

2016-07-21T02:50:38Z

Findings: remove sections

← Older revision		Revision as of 02:50, 21 July 2016
Line 43:		Line 43:
	All information related custom train tracks are stored here.		All information related custom train tracks are stored here.

	~~<section name~~="Files~~" show~~=~~"true">~~		==== Files ====
	<syntaxhighlight lang="lua">		<syntaxhighlight lang="lua">
	MTA10/game_sa		MTA10/game_sa
Line 62:		Line 62:
	** luadefs/CLuaTrainTrackDefs.{cpp,h} -- contain definitions for the Lua API		** luadefs/CLuaTrainTrackDefs.{cpp,h} -- contain definitions for the Lua API
	</syntaxhighlight>		</syntaxhighlight>
	~~</section>~~

	~~<section name~~="m_OriginalTrainTrackData~~" show~~=~~"false">~~		==== m_OriginalTrainTrackData ====
	The [https://pastebin.mtasa.com/748483851 m_OriginalTrainTrackData array] contains the same values in CTrainTrackManager.cpp and CTrainTrackManagerSA.cpp.		The [https://pastebin.mtasa.com/748483851 m_OriginalTrainTrackData array] contains the same values in CTrainTrackManager.cpp and CTrainTrackManagerSA.cpp.

Line 90:		Line 89:
	* Why are values repeated several times?		* Why are values repeated several times?
	* Why does the last repeat have slightly different values?		* Why does the last repeat have slightly different values?
	~~</section>~~

	=== Issues ===		=== Issues ===

2016-07-21T02:49:30Z

Findings: notes about the manager

@@ Line 62: / Line 62: @@
 ** luadefs/CLuaTrainTrackDefs.{cpp,h} -- contain definitions for the Lua API
 </syntaxhighlight>
 </section>

2016-07-21T01:23:38Z

Issues: add issues

← Older revision		Revision as of 01:23, 21 July 2016
Line 68:		Line 68:
	** Infinite loop occurs at 006f8fda, see [http://i.imgur.com/HvBWAFm.png call stack]. Occurs when a track of two nodes have same x/y, but different z. Only occurs for tracks that ONLY consist of nodes atop each other.		** Infinite loop occurs at 006f8fda, see [http://i.imgur.com/HvBWAFm.png call stack]. Occurs when a track of two nodes have same x/y, but different z. Only occurs for tracks that ONLY consist of nodes atop each other.
	*** Possible solution: when creation tracks, ensure that atleast one of the nodes has a different x/y to any other node.		*** Possible solution: when creation tracks, ensure that atleast one of the nodes has a different x/y to any other node.
	* Tracks may not be cleaned up		* Tracks may not be cleaned up -> See CTrainTrackManager::ResetTracks
			* See CTrainTrackManager and CTrainTrackManagerSA - why is this file so big? Why are coordinates provided multiple times for the same track? Which ones are right?
	* <strike>int CWorldSA::FindClosestRailTrackNode needs updating. It needs to use MAX_TOTAL_TRACKS and the train manager.</strike> [https://github.com/multitheftauto/mtasa-blue/commit/09e3ee8f25810c17742728f038786b6a223c5296 See 09e3ee8f25810c17742]		* <strike>int CWorldSA::FindClosestRailTrackNode needs updating. It needs to use MAX_TOTAL_TRACKS and the train manager.</strike> [https://github.com/multitheftauto/mtasa-blue/commit/09e3ee8f25810c17742728f038786b6a223c5296 See 09e3ee8f25810c17742]

2016-07-15T15:25:01Z

add category

← Older revision		Revision as of 15:25, 15 July 2016
Line 103:		Line 103:

	This means that there are only four commits that need to be merged into the new branch. There is currently a packet issue introduced by the merge that needs to be fixed.		This means that there are only four commits that need to be merged into the new branch. There is currently a packet issue introduced by the merge that needs to be fixed.

			[[Category: Development]]