8,144
edits
XML talk:BINA/PAR3: Difference between revisions
new section: particle subtype investigation
Paradox-01 (talk | contribs) m (workaround: add a new root particle) |
Paradox-01 (talk | contribs) (new section: particle subtype investigation) |
||
| 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== | ||