XML talk:BINA/PAR3 - Revision history

Iritscen: /* The Scarlett case */ marked dead link

2025-12-30T23:08:52Z

The Scarlett case: marked dead link

← Older revision		Revision as of 23:08, 30 December 2025
Line 110:		Line 110:

	===The Scarlett case===		===The Scarlett case===
	Scarlett bound [http://oni.bungie.org/forum/viewtopic.php?id=2991 ~~mad_x01 to a character animation]~~ which spawns the particle at global 0; 0; 0.		Scarlett bound mad_x01 to a character animation (<nowiki>http://oni.bungie.org/forum/viewtopic.php?id=2991</nowiki>, dead link) which spawns the particle at global 0; 0; 0.

	I don't know yet what's wrong with the spawning but obviously its supposed to work differently.		I don't know yet what's wrong with the spawning but obviously its supposed to work differently.
Line 119:		Line 119:

	Creating and renaming particle clones would be ideal to introduce the actual changes so that the originals aren't affected. However, over here, the new explosion file isn't recognized which leads to new questions and investigations. But for now, ... not now.		Creating and renaming particle clones would be ideal to introduce the actual changes so that the originals aren't affected. However, over here, the new explosion file isn't recognized which leads to new questions and investigations. But for now, ... not now.


	==Discussion on <StopIfBreakable />==		==Discussion on <StopIfBreakable />==

Paradox-01 at 20:25, 28 January 2024

2024-01-28T20:25:52Z

← Older revision		Revision as of 20:25, 28 January 2024
Line 2:		Line 2:

	==Particle statistics==		==Particle statistics==
	http://paradox.oni2.net/~~galore~~/particle_statistics.txt		http://paradox.oni2.net/wiki/particle_statistics.txt

	==Particle subtype investigation==		==Particle subtype investigation==

Iritscen: marking dead link

2020-08-21T13:44:16Z

marking dead link

← Older revision		Revision as of 13:44, 21 August 2020
Line 114:		Line 114:
	I don't know yet what's wrong with the spawning but obviously its supposed to work differently.		I don't know yet what's wrong with the spawning but obviously its supposed to work differently.

	That bug (or new "feature") can be avoided by introducing a new root emitter. For tests I used [https://dl.dropboxusercontent.com/u/139715/OniGalore/BINA3RAP_Talk/BINA3RAPh2h_powerup_e01a.xml ~~h2h_powerup_e01a]~~ (Syndicate compound level, daodan blast).		That bug (or new "feature") can be avoided by introducing a new root emitter. For tests I used h2h_powerup_e01a (<nowiki>https://dl.dropboxusercontent.com/u/139715/OniGalore/BINA3RAP_Talk/BINA3RAPh2h_powerup_e01a.xml</nowiki>, dead link) (Syndicate compound level, daodan blast).

	For <SelfImmune>1 to take effect, x01 <HasDamageOwner> must be set to "true". (h2h_powerup_e01a has that already. A complete ''chain of ownage'' is essential.)		For <SelfImmune>1 to take effect, x01 <HasDamageOwner> must be set to "true". (h2h_powerup_e01a has that already. A complete ''chain of ownage'' is essential.)

Paradox-01 at 07:54, 3 September 2017

2017-09-03T07:54:43Z

← Older revision		Revision as of 07:54, 3 September 2017
Line 1:		Line 1:
	__TOC__		__TOC__

			==Particle statistics==
			http://paradox.oni2.net/galore/particle_statistics.txt

	==Particle subtype investigation==		==Particle subtype investigation==

Paradox-01: removing dead links and code longer relevant as links are dead and the issue has been solved and documentated on XML:BINA/PAR3

2017-09-02T09:46:39Z

removing dead links and code longer relevant as links are dead and the issue has been solved and documentated on XML:BINA/PAR3

← Older revision		Revision as of 09:46, 2 September 2017
Line 123:		Line 123:
	: ''Within the HitWall PAR3 event, ''[<StopIfBreakable />]'' stops the exection of all PAR3 actions listed BELOW this PAR3 action if the HitWall was called against a breakable material (in vanilla Oni, the only breakable material is glass).''		: ''Within the HitWall PAR3 event, ''[<StopIfBreakable />]'' stops the exection of all PAR3 actions listed BELOW this PAR3 action if the HitWall was called against a breakable material (in vanilla Oni, the only breakable material is glass).''


	~~'''Example of <StopIfBreakable /> not stopping a later action:'''~~

	~~modified BINA3RAPw8_mbo_p01~~

	~~<HitWall>~~
	~~'''<StopIfBreakable />'''~~
	~~<ImpactEffect>~~
	~~<ImpactType>w8_mbo</ImpactType>~~
	~~<ImpactModifier>2</ImpactModifier>~~
	~~</ImpactEffect>~~
	~~<Die />~~
	~~</HitWall>~~
	~~https://dl.dropboxusercontent.com/u/139715/OniGalore/StopIfBreakable_used.wmv~~


	~~<HitWall>~~
	~~<ImpactEffect>~~
	~~<ImpactType>w8_mbo</ImpactType>~~
	~~<ImpactModifier>2</ImpactModifier>~~
	~~</ImpactEffect>~~
	~~<Die />~~
	~~</HitWall>~~
	~~https://dl.dropboxusercontent.com/u/139715/OniGalore/StopIfBreakable_not_used.wmv~~
	~~: Side note: There's no visible effect (like decal) on the breakable glass because of ONIE.~~

	~~For better visibility we can also repeat the two tests with a plasma effect.~~


	~~<HitWall>~~
	~~'''<StopIfBreakable />'''~~
	~~<ImpactEffect>~~
	~~<ImpactType>w3_phr</ImpactType>~~
	~~<ImpactModifier>0</ImpactModifier>~~
	~~</ImpactEffect>~~
	~~<Die />~~
	~~</HitWall>~~
	~~https://dl.dropboxusercontent.com/u/139715/OniGalore/StopIfBreakable_used_phr3_alt.wmv~~


	~~<HitWall>~~
	~~<ImpactEffect>~~
	~~<ImpactType>w3_phr</ImpactType>~~
	~~<ImpactModifier>0</ImpactModifier>~~
	~~</ImpactEffect>~~
	~~<Die />~~
	~~</HitWall>~~
	~~https://dl.dropboxusercontent.com/u/139715/OniGalore/StopIfBreakable_not_used_phr3_alt.wmv~~

Paradox-01 at 09:30, 2 September 2017

2017-09-02T09:30:25Z

← Older revision		Revision as of 09:30, 2 September 2017
Line 6:		Line 6:
	Due to their huge number a statistic approach might be suitable.		Due to their huge number a statistic approach might be suitable.

	This would be best to be carried out with an programmed tool.		This would be best to be carried out with a programmed tool.

	We could look for common ~~trait~~ (tags and tag values).		We could look for common traits (tags and tag values).

	Expected types		Expected types

Paradox-01: mad_p04 seems to be an artefact

2017-09-02T09:28:44Z

mad_p04 seems to be an artefact

← Older revision		Revision as of 09:28, 2 September 2017
Line 87:		Line 87:
	* Each "count" textured particle comes with its own timer sound		* Each "count" textured particle comes with its own timer sound
	* "x" particle holds an sbg sound		* "x" particle holds an sbg sound
	* "e3" seems to provide a safety distance towards level geometry: <WallOffset>0.2</WallOffset>		* "e03" seems to provide a safety distance towards level geometry: <WallOffset>0.2</WallOffset>
	* ~~...~~		* "p04" seems obsolete, main content seems to be a "Sprite" texture but it's invisible, same texture is used by "p03"

Paradox-01 at 09:17, 2 September 2017

2017-09-02T09:17:22Z

← Older revision		Revision as of 09:17, 2 September 2017
Line 65:		Line 65:
	+-- mad_x01 from <Events><Lifetime><CollisionEffect><Effect>, self: <TexGeom>lensflare01 (really visible?)		+-- mad_x01 from <Events><Lifetime><CollisionEffect><Effect>, self: <TexGeom>lensflare01 (really visible?)
	\|		\|
	+-- mad_f01 from <Emitters><Emitter><Class>, self: <TexGeom>lensflare01 (~~rally~~ visible?)		+-- mad_f01 from <Emitters><Emitter><Class>, self: <TexGeom>lensflare01 (really visible?)
	+-- mad_f02 from <Emitters><Emitter><Class>, self: <TexGeom>smoke		+-- mad_f02 from <Emitters><Emitter><Class>, self: <TexGeom>smoke
	+-- mad_f03 from <Emitters><Emitter><Class>, self: <TexGeom>bloodyfoot		+-- mad_f03 from <Emitters><Emitter><Class>, self: <TexGeom>bloodyfoot

Paradox-01: new section: particle subtype investigation

2017-09-02T09:05:59Z

new section: particle subtype investigation

← Older revision		Revision as of 09:05, 2 September 2017
Line 1:		Line 1:
	__TOC__		__TOC__

			==Particle subtype investigation==
			TXMP was shown to have 3 types. Similar can be expected from particle.

			Due to their huge number a statistic approach might be suitable.

			This would be best to be carried out with an programmed tool.

			We could look for common trait (tags and tag values).

			Expected types
			* decal
			* lensflare
			* 3d object
			* contrail
			* damage dealer
			* General purpose particle (helper particle for location, orientation, attractor, emitter, event, used as emitter or in between a chain)

			Beside that there are optional features like "owning damage" which requires the property to be set in each file of the particle chain.

			So particles are best to be seen as "teams" not "individuals".

			===Decals===
			For example files with <HasDecalState>True could be investigated for shared structure and values.

			The result will be probably that Attractors, Emitters, Events aren't not only used for them but disabled (proof by testing).

			So only appearance and maybe variables apply for them.

			Seems to be always the same with decals:

			<Properties>
			<HasDecalState>true

			<Appearance>
			<DisplayType>Decal

			Properties based on observation:
			* hosting 3d surface must be in tolerance range (10 units)
			* <CollideWithChars> .. is ignored by decals
			* <TexGeom> .. links to TXMP file
			* <Alpha> .. alpha level is ignored when TXMP has adaptiveAlpha flag
			* <Tint> .. is ignored by decals


	==Exploring Mad Bomber particle==		==Exploring Mad Bomber particle==

Paradox-01: workaround: add a new root particle

2016-06-07T20:36:18Z

workaround: add a new root particle

@@ Line 1: / Line 1: @@
-===Exploring Mad Bomber particle===
+__TOC__
 What triggers Mad Bomber's explosion?
@@ Line 60: / Line 62: @@
-===Discussion on <StopIfBreakable />===
+===The Scarlett case===
 '''Controversial phrase:'''