Vortec effect.
-
Hi m8,
FL also uses cone emitter and a host of others but cone cube sphere are the most common.
Most of the lines in ALE are read in -time , action or in the case of colours
time , R, G, B
some lines read time, action, time, action etc etc meaning at a certain time in the effect, the size will be blah, then at time x the effect will be bigger/smaller etc.
frequency is how many particles come out of the emitter.
pressure is how far those particles go away from the emitter
initial_particles is how many particles the effect starts within general (but not with all effects) each effect has a “general” basic appearence section and a specific appearence section(cone/cube etc)
Best way to find out what each one does is to change it and test it so trial and error as with most things. hope this helps a little.
Ice
-
Do people really still prefer ALE Editor over XML Project, or is it just not familiar?
-
Personally I’m just way too used to it to change to anything else. I’ve been working with ALEs for so long I’ve come to associate these pseudo-INIs with them.
-
Sorry Adoxa, mot really familiar with it. Been messing around a bit this morning with the info Ice and FF gave me. Understanding a little bit more but there are 2 areas I’m really after. These 2 :
Node_Name = gf_jumpgate_tunnel.app
BasicApp_Rotate = {
Entry = 0.0000000000000000
EFlag = 4
SubEntry = 0.0000000000000000, 0.0000000000000000
SubFlag = 4
}And……
Node_Name = gf_jumpgate_tunnel_Cone.emt
ConeEmitter_MinRadius = {
Entry = 0.0000000000000000, 0.0000000000000000
SubEntry = 0.0000000000000000, 130.0000000000000000, 0.0000000000000000, 0.0000000000000000
}ConeEmitter_MaxRadius = {
Entry = 0.0000000000000000, 1.0000000000000000
SubEntry = -0.0034849999938160, 130.0000000000000000, 0.0000000000000000, 0.0000000000000000
}ConeEmitter_MinSpread = {
Entry = 0.0000000000000000, 0.0000000000000000
SubEntry = -0.0034852474927902, 90.0000000000000000, 0.0000000000000000, 0.0000000000000000
}ConeEmitter_MaxSpread = {
Flag = 4
Entry = 0.0000000000000000, 0.0000000000000000
EFlag = 0
SubFlag = 1
SubEntry = 0.0126010002568364, 90.0000000000000000, 0.0000000000000000, 0.0000000000000000
}The rotate app. seems to do nothing at all when changed. Was trying to get the app to rotate on z axis like LS’s tradelane vid.
Now the radius and spead I can changein see a difference when changing the second values. But what I’m trying to do is make it small at the start and large at the end. So using Iceman’s tip: time action time action :nothing happens, like FF said about the last two values seem to to do nothing. I’ll make a post shortly on which does height and lenght.
-
BasicApp_Rotate only rotates the particle itself, not the emitter, anyway, and it doesn’t work half the time.
-
adoxa wrote:
Do people really still prefer ALE Editor over XML Project, or is it just not familiar?FriendlyFire wrote:
Personally I’m just way too used to it to change to anything else. I’ve been working with ALEs for so long I’ve come to associate these pseudo-INIs with them.This isn’t the first time I’ve seen this referenced. I don’t really understand what it is or what it’s for either. I’m with FriendlyFire in that I’ve been editing ALEs with the Editor tool thing the entire time as well, partly because I didn’t even know there was an alternative.
-
the alternative is a good bit younger than the initial ALE editor. although i do not work that much with ale’s, i also am kinda used to the editor’s output format. i came to work with ale’s after i already knew a bit of thn’s.
besides, the format of <parameter>= <values_array>is imo simplier and therefore easier to read than the xml tag-based script. however, i thought of trying out the xml project for this purpose.</values_array></parameter> -
Here is the tradelane ALE you saw used in the video. It is built from the original. From what I remember I simply flipped one on the fx by -90 degrees, adjusted scaling and speed to fit within the tradelane entrance.
The original fx was from gf_tradeinnerring.ale
