Another question
Moderators: BTT, andy55, b.dwall, juxtiphi
- markofkane
- Posts: 346
- Joined: Thu Feb 03, 2005 3:08 pm
Another question
Can you stop error messages in G-Force when a certain colormap, waveshape, and flowfield comes on?? It's annoying.
- JayPro
- Posts: 738
- Joined: Sat May 01, 2004 10:51 pm
- Location: Huntington Station, Long Island, New York
This is one of the reasons why I'm still on 3.0.1.
I've seen in these newer versions that VectorC spits back at you messages indicating some kind of code syntax error, yet the effect in question still looks as it should.
Even more expasperating is when you get a message indicating a genuine error. For those like me ill-adept at the streamlined code, this doesn't tell me how to fix the errors.
Somehow, though, I've been able to "backward-translate" many of the new configs with the modernized code and make them work for my version.
How?
Well.....
1. atan2(x,y) >> atan(x/y)
2. clamp(x) >> clip(x)
2a. A better example of clip from the new wave MCP:
B0="(float) (ID==0)" //1 only when ID == 0 so we don't multiply accum. B3 & b4.
Answer: "B0=clip(ID)" because of aforementioned rationale (i.e. 1 or zero).
It works as advertised.
3. Replacing the commas (usually) with a multiplier (*). See point #5.
4. The same might apply to &&. A single ampersand I might try to sub with an addition operator. This is subject to further experimentation.
5. Min & max eliminations:
Again, from MCP......
B4="min(max(B3, 0 / a9), a13 / a9)" //apply min & max velocity
my solution: "fft(B3 * 0 / a9) * fft(A13 / a9)"
As I understand it, fft is used for impetus/velocity in a lot of circumstances. Again, it works.
Maybe doing things like the aforementioned will help me understand what the newer functions mean.
Getting back to point, I'm not sure if the updated versions "shut up" VectorC in this regard. I'm afraid that my wondering about this will remain 'til I find an overwhelmingly compelling reason to catch up with everyone else here. I mean...is *less really more*...or in this case, *more really less*???
I am conficted indeed.

I've seen in these newer versions that VectorC spits back at you messages indicating some kind of code syntax error, yet the effect in question still looks as it should.
Even more expasperating is when you get a message indicating a genuine error. For those like me ill-adept at the streamlined code, this doesn't tell me how to fix the errors.
Somehow, though, I've been able to "backward-translate" many of the new configs with the modernized code and make them work for my version.
How?
Well.....
1. atan2(x,y) >> atan(x/y)
2. clamp(x) >> clip(x)
2a. A better example of clip from the new wave MCP:
B0="(float) (ID==0)" //1 only when ID == 0 so we don't multiply accum. B3 & b4.
Answer: "B0=clip(ID)" because of aforementioned rationale (i.e. 1 or zero).
It works as advertised.
3. Replacing the commas (usually) with a multiplier (*). See point #5.
4. The same might apply to &&. A single ampersand I might try to sub with an addition operator. This is subject to further experimentation.
5. Min & max eliminations:
Again, from MCP......
B4="min(max(B3, 0 / a9), a13 / a9)" //apply min & max velocity
my solution: "fft(B3 * 0 / a9) * fft(A13 / a9)"
As I understand it, fft is used for impetus/velocity in a lot of circumstances. Again, it works.
Maybe doing things like the aforementioned will help me understand what the newer functions mean.
Getting back to point, I'm not sure if the updated versions "shut up" VectorC in this regard. I'm afraid that my wondering about this will remain 'til I find an overwhelmingly compelling reason to catch up with everyone else here. I mean...is *less really more*...or in this case, *more really less*???
I am conficted indeed.
"God is syntax."
- markofkane
- Posts: 346
- Joined: Thu Feb 03, 2005 3:08 pm
- JayPro
- Posts: 738
- Joined: Sat May 01, 2004 10:51 pm
- Location: Huntington Station, Long Island, New York
Ah!!!!!
I'll answer your
in two ways:
I've seen instances where in GF 3.1> the Waveshape/Particle list has a few blanks in it; and it may well have to do with the latter issue.
And this may reveal itself in the console as "".
As per the other part, try a keyword search on Meta on the board; and you may find several answers (mostly mine) as to how to include them in your config syntax.
Hope this helps.
PS: You've just reminded me to ask a question of my own.
I'll answer your
I've seen instances where in GF 3.1> the Waveshape/Particle list has a few blanks in it; and it may well have to do with the latter issue.
And this may reveal itself in the console as "".
As per the other part, try a keyword search on Meta on the board; and you may find several answers (mostly mine) as to how to include them in your config syntax.
Hope this helps.
PS: You've just reminded me to ask a question of my own.
"God is syntax."
- markofkane
- Posts: 346
- Joined: Thu Feb 03, 2005 3:08 pm
- markofkane
- Posts: 346
- Joined: Thu Feb 03, 2005 3:08 pm
Come on you guys, get with the latest and greatest. I finally got my 'lost' colormaps working in the newer versions. I was using an 'undocumented feature' of incremental numbers (C0="C0+.001") but finally got them looking about the same with multiplications.
MarkofKane:
Yes there are compile errors in the extras. That's why you should download them from my website coz I fixed most of them. There might be one or two with compile errors that I missed but if you find them tell me the name and I will fix them. Those .DS_STOREs are some Mac related thing and you won't find them in my Zips even the ones for Mac.
JayPro:
As one of the Masters of Flowfielding I am surprised that you won't upgrade beyond 3.0.
As I said to Mark, I have fixed most of the compile errors. You said
And to be an intelligent-rear-end I will ask you how to "backward-translate the Wyville function? Seriously, I've been trying to make use of the newer function like > or < etc. I used to use clip with subtraction to get a < or > but it's much easier now.
So let me suggest that you please rename your current SoundSpectrum folder (after exiting G-Force, toolbar, iTunes etc) to SoundSpectrumOld or SoundSpectrum30 or whatever then download and install Andy's latest puppy the 3.5.5 version. Next, get my easy to download and install extras and have a look. If you can identify that elusive config with errors, let me know and I will fix it.
================
Get up to speed, jump on the bandwagon, don't be left behind, go with the flow, join the crowd, be part of the movement, enter the Matrix, beam aboard the starship, Charger - leader of the Dodge Rebellion!, er, ah, well skip that one. But come on, the bus is pulling out, all aboard, train is leaving, don't miss the boat, truck on down the highway, get some jet lag, and upgrade to the best version of the best visualizer this side of the Milky Way.

MarkofKane:
Yes there are compile errors in the extras. That's why you should download them from my website coz I fixed most of them. There might be one or two with compile errors that I missed but if you find them tell me the name and I will fix them. Those .DS_STOREs are some Mac related thing and you won't find them in my Zips even the ones for Mac.
JayPro:
As one of the Masters of Flowfielding I am surprised that you won't upgrade beyond 3.0.
That's because the config had the error originally but it wasn't flagged to your attention. But one of the vars was giving a big fat zero and the config still looked okay with it. So to correct the syntax you can possibly just set that particular var to zero.messages indicating some kind of code syntax error, yet the effect in question still looks as it should.
And to be an intelligent-rear-end I will ask you how to "backward-translate the Wyville function? Seriously, I've been trying to make use of the newer function like > or < etc. I used to use clip with subtraction to get a < or > but it's much easier now.
So let me suggest that you please rename your current SoundSpectrum folder (after exiting G-Force, toolbar, iTunes etc) to SoundSpectrumOld or SoundSpectrum30 or whatever then download and install Andy's latest puppy the 3.5.5 version. Next, get my easy to download and install extras and have a look. If you can identify that elusive config with errors, let me know and I will fix it.
================
Get up to speed, jump on the bandwagon, don't be left behind, go with the flow, join the crowd, be part of the movement, enter the Matrix, beam aboard the starship, Charger - leader of the Dodge Rebellion!, er, ah, well skip that one. But come on, the bus is pulling out, all aboard, train is leaving, don't miss the boat, truck on down the highway, get some jet lag, and upgrade to the best version of the best visualizer this side of the Milky Way.
- markofkane
- Posts: 346
- Joined: Thu Feb 03, 2005 3:08 pm
- JayPro
- Posts: 738
- Joined: Sat May 01, 2004 10:51 pm
- Location: Huntington Station, Long Island, New York
And to be an intelligent-rear-end I will ask you how to "backward-translate the Wyville function? Seriously, I've been trying to make use of the newer function like > or < etc. I used to use clip with subtraction to get a < or > but it's much easier now.
Isn't wyvill(r) simply a multiplication of r by a certain floating-point number?
"God is syntax."