Whenever a Union is called up it seems to be that the areas intended for the flowfield combinations are blank?
At least that's what it seems like with me; but I'm going thru a manual callup rather than letting autopilot do its thing.
If I see another example I'll ytry to upload an instance.
Re: FlowField Unions...Has ANyone Noticed?
Moderators: BTT, andy55, b.dwall, juxtiphi
-
JayPro
- Posts: 738
- Joined: Sat May 01, 2004 10:51 pm
- Location: Huntington Station, Long Island, New York
Re: FlowField Unions...Has ANyone Noticed?
"God is syntax."
to be honest, I have little, to no, experience here... The first thing I usually do is turn 'FlowField Unions' OFF ... this setting obviously, isn't saved. When I forget however, I think I know what you are talking about, BUT ASSUMED that is what the effect was all about... turning the current flowfield on/off per the defined union pattern... am I wrong here? I certainly could be!
Just checked out http://www.soundspectrum.com/g-force/fl ... nions.html ... I THINK I am very wrong, and AGREE with what YOU observed.
About two months ago (pre-GF4), I tried my hand at scripting, and the scripts I wrote no longer work under GF4. I have some confusion with the calling format of 'SetNextFlowField()' ... which by the way, allows you to specify the 'inUnionName', which is why I bring this up. 'Script Command Reference.txt' documents a 5 parameter convention, but 'CTRL 3.txt', which is SUPPOSE to be an example, uses a 4 parameter format... also, it MAY NOT be obvious, but the ''SetNextFlowField()' won't fire off UNLESS SetSlideShow( CONFIG_FLOWFIELD, true ); ... which DIDN'T USE TO BE TRUE. To further complicate the matter, the 'Starburst.txt' reference doesn't exist.
I know I kinda hijacked your original topic, but it MAY be all related. What exactly did you mean by "I'm going thru a manual callup" ? Are you writing a script?
PS: I rewote/cleanedup 'CTRL 3.txt', that pretty much confirms the above assertion, if you want to look at it...
Just checked out http://www.soundspectrum.com/g-force/fl ... nions.html ... I THINK I am very wrong, and AGREE with what YOU observed.
About two months ago (pre-GF4), I tried my hand at scripting, and the scripts I wrote no longer work under GF4. I have some confusion with the calling format of 'SetNextFlowField()' ... which by the way, allows you to specify the 'inUnionName', which is why I bring this up. 'Script Command Reference.txt' documents a 5 parameter convention, but 'CTRL 3.txt', which is SUPPOSE to be an example, uses a 4 parameter format... also, it MAY NOT be obvious, but the ''SetNextFlowField()' won't fire off UNLESS SetSlideShow( CONFIG_FLOWFIELD, true ); ... which DIDN'T USE TO BE TRUE. To further complicate the matter, the 'Starburst.txt' reference doesn't exist.
I know I kinda hijacked your original topic, but it MAY be all related. What exactly did you mean by "I'm going thru a manual callup" ? Are you writing a script?
PS: I rewote/cleanedup 'CTRL 3.txt', that pretty much confirms the above assertion, if you want to look at it...
-
JayPro
- Posts: 738
- Joined: Sat May 01, 2004 10:51 pm
- Location: Huntington Station, Long Island, New York
Manual callup is just my amateurish jargon for using keys (Q W E A S D Z X C) to run thru configs.
BTW I almost never write scripts. My specialty is config authoring itself. That could be why I looked at your observations re scripting and kind tilted my head a bit like a confused dog.
I doubt that anything is out of date with GF in my machine right now, as each subsequent DL, whether beta or release version, overwrites the one before it. SO there's no question that everything's current.
Also, any errors would (85-95% of the time) be flagged and displayed thru the Console in Verbose Mode (e.g. "Error Loading "XYZ") and there was nothing that indicated this as far as Unions are concerned. The pending union callup in auto mode was all I had to go by.
BTW, I'm using the latest beta (b5).
BTW I almost never write scripts. My specialty is config authoring itself. That could be why I looked at your observations re scripting and kind tilted my head a bit like a confused dog.
I doubt that anything is out of date with GF in my machine right now, as each subsequent DL, whether beta or release version, overwrites the one before it. SO there's no question that everything's current.
Also, any errors would (85-95% of the time) be flagged and displayed thru the Console in Verbose Mode (e.g. "Error Loading "XYZ") and there was nothing that indicated this as far as Unions are concerned. The pending union callup in auto mode was all I had to go by.
BTW, I'm using the latest beta (b5).
"God is syntax."