I recently installed all of the extras and I believe that one of the extras is causing G-force to crash. I have not been able to determine which one is causing the problem. This same thing used to happen well before 3.0 with the extras. It has also caused the screensaver to crash. Has anyone else had problems after installing the extras?
King
G-force extras causing crashes
Moderators: BTT, andy55, b.dwall, juxtiphi
- JayPro
- Posts: 738
- Joined: Sat May 01, 2004 10:51 pm
- Location: Huntington Station, Long Island, New York
Have you checked to make sure that every one of your Extras configs has Meta Values assigned?
Very important, that.
Also, you might hafta run them all thru a text editor to get rid of the commas. The config syntax changed after 2.5 such that in addition to the implementation of Meta #'s, commas are no longer necessary to delimit code statements. Whether they're still accepted by the processor or not is debatable IMO; but it's a good idea just in case to get rid of them.
Give these measures a try and let us know how things go.
Very important, that.
Also, you might hafta run them all thru a text editor to get rid of the commas. The config syntax changed after 2.5 such that in addition to the implementation of Meta #'s, commas are no longer necessary to delimit code statements. Whether they're still accepted by the processor or not is debatable IMO; but it's a good idea just in case to get rid of them.
Give these measures a try and let us know how things go.
"God is syntax."
- JayPro
- Posts: 738
- Joined: Sat May 01, 2004 10:51 pm
- Location: Huntington Station, Long Island, New York
If you look at the WaveShape configs that are bundled with GF 3, you'll notice a parameter called Meta.
This will usually have four basic parameters: Reactive, Detail, Density and Morphable.
However, the ones that you want to have appear as occsional Particles will leave out the last parameter.
My understanding is this (but it might not be gospel truth here): If you want the WaveShape to appear as such, make sure all the parameters I just described are set to a value of 4. Again, for some Waves that mat have squiggly designs or complicated shapes, a value of 5 may be Okay.
Values of five are also Okay if there are more than the four basic parameters available. Take a look in Ted's Wave folder at IFS Fern for a perfect example (zoomable, offsetable etc.).
As for the commas, you should find them at the end of every statement in your Extras config files:
sake of argument example: "srcR=r*sin(theta)",<<<
After GF version 2.5, it no longer was necessary for every statement in the code to end with one of these.
i.e. "srcR=r*sin(theta)
It may be necessary to delete these final commas so that the post-v2.5 processor might not have issues determining wether that comma is really needed.
Hope this helps. I'm available for further clarification.
This will usually have four basic parameters: Reactive, Detail, Density and Morphable.
However, the ones that you want to have appear as occsional Particles will leave out the last parameter.
My understanding is this (but it might not be gospel truth here): If you want the WaveShape to appear as such, make sure all the parameters I just described are set to a value of 4. Again, for some Waves that mat have squiggly designs or complicated shapes, a value of 5 may be Okay.
Values of five are also Okay if there are more than the four basic parameters available. Take a look in Ted's Wave folder at IFS Fern for a perfect example (zoomable, offsetable etc.).
As for the commas, you should find them at the end of every statement in your Extras config files:
sake of argument example: "srcR=r*sin(theta)",<<<
After GF version 2.5, it no longer was necessary for every statement in the code to end with one of these.
i.e. "srcR=r*sin(theta)
It may be necessary to delete these final commas so that the post-v2.5 processor might not have issues determining wether that comma is really needed.
Hope this helps. I'm available for further clarification.
"God is syntax."