Opinions on G-Force 5?
Moderators: BTT, andy55, b.dwall, juxtiphi
Re: G-Force 5 is FANTASTIC
For me it is excellent.
I have Aeon Platinum (problems with transitions: are not smooth)
Regards,
Fabrício, from Brazil.
+1sharok wrote:I upgraded from previous version to 5.0.
I have Aeon Gold and G-Force Gold. They'ere both great but I see the smoothest transitions with G-Force.
Aeon transitions are not as smooth and seemless as G-force (using the same setup on my pc for both visualizations). Hopefully, the next version of Aeon will be as smooth as G-force. Otherwise, they are both flawless.
I have Aeon Platinum (problems with transitions: are not smooth)
Regards,
Fabrício, from Brazil.

Licensed User
impressions
I use the WMP version:
the overall menu works great for minor changes, but lacks the instinctive granularity that the toolbar allowed, it also has issues when you want to use lots of external sprites.
on the first version I used way back, adding my own folders and then checking and unchecking things as I figured out which of my pictures worked and which didn't was a long but easy process.
With 5 I'm still trying to figure any of it out, it seems to ignore subfolders, and just doesn't seem as friendly for those of us in the middle.. it seems great for those that want to learn and write their own scripting, or those that want to just plug it in and let it go on its own... but for my use, I doubt I will extend my purchase.
the overall menu works great for minor changes, but lacks the instinctive granularity that the toolbar allowed, it also has issues when you want to use lots of external sprites.
on the first version I used way back, adding my own folders and then checking and unchecking things as I figured out which of my pictures worked and which didn't was a long but easy process.
With 5 I'm still trying to figure any of it out, it seems to ignore subfolders, and just doesn't seem as friendly for those of us in the middle.. it seems great for those that want to learn and write their own scripting, or those that want to just plug it in and let it go on its own... but for my use, I doubt I will extend my purchase.
Hello All
The new UI is too complicated, and it allows you to do little even when it works. After spending much time selecting the Configs I want to use in GF I have not been able to find a way to save all my hard work. Next time I start GF my selections have been replaced with the default settings. Does this not make the new UI pointless?
Regards BTT
The new UI is too complicated, and it allows you to do little even when it works. After spending much time selecting the Configs I want to use in GF I have not been able to find a way to save all my hard work. Next time I start GF my selections have been replaced with the default settings. Does this not make the new UI pointless?
Regards BTT
Hello BTTBTT wrote:Hello SteveH
A very interesting post, and it will also be very interesting to read SoundSpectrums reply.
Regards BTT
I have a reply from my ticket from Frank - see below:
This is an automated notice to inform you that we have responded to your Ticket #*****:
================================
Hi Stephen,
Thanks for writing, for your support, and for being an active participant in our community. I saw your concerns on the forum, and I apologize for the delay in response. I will bring up your concerns to Andy when I get back from vacation. As long as I have been around the Kill Script functionality has been disabled. I'm not sure what the philosophy behind this decision was, but I'd imagine it was due to lack of utility. If you saved scripts of the "(None)" visual elements, switching to them would be a quick and easy way to end a script. But why do you want a blank page? We use it for testing new visual elements, but it seems like it would be more worthwhile to simply switch to another script. That isn't to say that you shouldn't want to use the Kill Script functionality, it just seems a bit redundant.
Regarding the matter of saving scripts to a number key, I have not been able to reproduce this. Are you still having issues with it?
Please let me know if there's anything else that I can do for you.
Regards,
Frank Netscher
SoundSpectrum, Inc.
www.soundspectrum.com
=========================================
Please let us know if this resolved your issue or if you still need help by replying to or closing this ticket
Sincerely,
SoundSpectrum Support
www.soundspectrum.com/support
I have replied to this email - see below:
Hi Frank,
Welcome to the SoundSpectrum team.
Thank you for your reply. The reason for my request for help is that I normally run my laptop connected to my TV through a HDMI port and I use either of the standalone versions of G-Force or Aeon. Often I have the system running for a full afternoon or evening if I have friends around and I am playing music from my stereo or (I have a lot of friends that are also musicians) musical instruments (Guitars, keyboards etc.).
We all love the graphics of both G-Force and Aeon, but occasionally we also like to see some photos that I or others have taken of them during recent performances.
To show the photographs (in random order) I wrote these scripts:
SetConsoleVisible( false ); //Don’t like the console showing around the borders of the picture
SetSlideshowEnabled( ALL_CONFIG_TYPES, false ); /*Stops background graphics showing around picture borders*/
KillRunningScripts(); //This does not work now
KillOverlay(); //Ends any overlay from previous scripts
StartConfig( "Scene", "(None)", ss_QuickTransition ); //Ends all scenes
StartConfig( "ColorMap", "(Black)", ss_QuickTransition ); //Black background for pictures
Run ( "SlideShow.txt" ); //Runs my random photo-viewer script.
On G-Force 4.2 I had CTRL 1 for photo-set 1, CTRL 2 for photo-set 2 etc. When I downloaded G-Force 5 and Aeon (3.2 followed by 3.3), CTRL 1 etc. did not work. I changed my scripts to the new script commands as shown above and still CTRL 1 would not work. I renamed CTRL 1 to CTRL S and the script ran perfectly.
My script for SlideShow.txt is as follows:
0:00
StartImageOverlay( sprintf ("resources/Pics/%d.jpg", rnd(212)),
0.5, 14.5, 0.5,
0.5, 0.5, 1.0,
"", ss_OverlayAlphaBlend );
0:15
Run ( "SlideShow.txt" );
I rename all of my slide show pictures (using a freeware file re-name download) and have 212 pictures in Pics folders inside the G-Force and Aeon resources folders, hence rnd(212). I know I can place the pictures in one folder and just change the path to the files but I haven’t got round to that yet as I am still struggling with the script to end the slideshow. This script is called CTRL X (for exit):
KillRunningScripts(); // Halts execution of all running scripts
KillOverlay(); // Removes current slide from screen
PurgeFileCache(); //Added this in hope it would help – it didn’t
SetSlideshowEnabled( ALL_CONFIG_TYPES, true ); // Restart Slideshow
SetConsoleVisible( true ); //Makes Console Visible Again
After running the script the graphics start again behind the pictures but the pictures slideshow does not end. Is there any other way to end my pictures slideshow without closing and re-starting G-Force or Aeon?
Your reply states “If you saved scripts of the "(None)" visual elements, switching to them would be a quick and easy way to end a script. But why do you want a blank page? We use it for testing new visual elements, but it seems like it would be more worthwhile to simply switch to another script. That isn't to say that you shouldn't want to use the Kill Script functionality, it just seems a bit redundant.”
As you can see I am quite familiar with the “(None)” visual elements and tried this script to close my photo-slideshow:
SetSlideshowEnabled( ALL_CONFIG_TYPES, false );
KillRunningScripts();
KillOverlay();
PurgeFileCache();
StartConfig( "Scene", "(None)", ss_QuickTransition );
StartConfig( "ColorMap", "(Black)", ss_QuickTransition );
This just produces a black screen until the next picture in my pictures slideshow starts and then the pictures slideshow continues to run as normal with no way to end it. If I start another script both scripts run at the same time and I have pictures loading over the top of other pictures, but anyway I just want to return to the original graphics with no scripts running.
You say in your reply “Regarding the matter of saving scripts to a number key, I have not been able to reproduce this. Are you still having issues with it?”
If I try to save a script in either G-Force or Aeon following instructions on the help screen I should press shift then W followed by the letter or number that I wish to save the script too, e.g. shift W then 1 to make a script CTRL 1 or Key 1. As soon as I press shift W I get a screen message key W.py has been saved and I find a new entry in the scripts folder Key W.py. Pressing any key after shift W makes no difference, it still saves Key W.py in the scripts folder. There are many postings in the G-Force and Aeon forums showing that a lot of users are having the same problem. Also see my text above regarding renaming CTRL 1.txt to CTRL S.txt.
Hello SteveH
Thanks so much for sharing the information. Having read your second post it is my opinion there are only two people I know who would be able to offer the appropriate advice. One would be Andy O'Meara, the author of G-Force. The other probably the most knowledgeable member of the forum 'Jerohm'. I have sent an email to Jerohm asking for his expert help, but of course it is his choice to respond or not.
Regards BTT
Thanks so much for sharing the information. Having read your second post it is my opinion there are only two people I know who would be able to offer the appropriate advice. One would be Andy O'Meara, the author of G-Force. The other probably the most knowledgeable member of the forum 'Jerohm'. I have sent an email to Jerohm asking for his expert help, but of course it is his choice to respond or not.
Regards BTT
Hi -
I KNOW that scripting directives have changed over releases, without the documentation necessarily being updated.
I KNOW that I FOUND, script files (to be invoked as CTRL) NOW must be named as LETTERS only... numbers no longer work.
Let's NOT mix Aeon with G-Force even though they MAY be converging. I can TRY to help with GF.
will update later...
void KillRunningScripts(); // Is DEFINATELY Broken
I KNOW that scripting directives have changed over releases, without the documentation necessarily being updated.
I KNOW that I FOUND, script files (to be invoked as CTRL) NOW must be named as LETTERS only... numbers no longer work.
Let's NOT mix Aeon with G-Force even though they MAY be converging. I can TRY to help with GF.
will update later...
void KillRunningScripts(); // Is DEFINATELY Broken
Last edited by jerohm on Sun Jul 07, 2013 6:36 pm, edited 1 time in total.
Many thanks BTT, I see Jerohm has replied and it looks as if he agrees that some of my problems are correct and not just a common fault on my PC and two laptops. From his post I think he will reply once he has investigated the problem further.BTT wrote:Hello SteveH
Thanks so much for sharing the information. Having read your second post it is my opinion there are only two people I know who would be able to offer the appropriate advice. One would be Andy O'Meara, the author of G-Force. The other probably the most knowledgeable member of the forum 'Jerohm'. I have sent an email to Jerohm asking for his expert help, but of course it is his choice to respond or not.
Regards BTT
On another note could you send me the new colour maps you mention in another part of the forum, or should I request them on that particular forum page?
Regards SteveH
Hi Jerohm,jerohm wrote:Hi -
I KNOW that scripting directives have changed over releases, without the documentation necessarily being updated.
I KNOW that I FOUND, script files (to be invoked as CTRL) NOW must be named as LETTERS only... numbers no longer work.
Let's NOT mix Aeon with G-Force even though they MAY be converging. I can TRY to help with GF.
will update later...
Many thanks for your reply. As this is a G-Force forum I am not expecting any help for Aeon problems, but merely pointing out that the same problems exist on both products.
Some of the script code that I use is borrowed from Aeon 3.2 boot text file, as you say the documentation has not been upgraded so I have to dig deep to find commands, try them, and if they work use them. But as the script code from Aeon also works in G-Force 5, I am hoping that the solution to my problem will work in both products. If not I will then start a post on the Aeon forum.
They do seem to be converging though and for users like myself that enjoy both products this will be useful as I might only have to make minor changes to my scripts to gain cross-platform functionality.
Regards SteveH
Another reply from Frank about my ticket, but it still does not solve the original Kill Scripts problem. I have added my reply to this underneath.
Hi Stephen,
Thanks for your detailed response. Honestly, I haven't had time to familiarize myself with the scripting process enough to be comfortable giving you scripting advice, although I will work on that as soon as I get the chance. I have already alerted Andy O'Meara to this, so please do not swamp him with emails.
As for writing scripts within G-Force, Jerohm is correct, you can no longer write scripts to CTRL + (a key) or invoke scripts by pressing CTRL + (a key). However, I still have not encountered your issue where SHIFT + W always writes to W. It happens if I press SHIFT + W twice, but otherwise, I have no problem writing scripts to numbers or letters. I press SHIFT + W and then I press an alphanumeric key. To invoke it, I press SHIFT + R and then the same alphanumeric key. I hope this helps. If you are still having trouble, perhaps you should consider updating to G-Force 5.03.
I will look into the KillScript issue further, but there are many tickets to answer, and it may take a while. Please, let me know if there's anything else I can do, but know that I am continually working to help you, even though I am trapped in San Francisco for the next few days.
Regards,
Frank Netscher
SoundSpectrum, Inc.
www.soundspectrum.com
================================================
Please let us know if this resolved your issue or if you still need help by replying to or closing this ticket
================================================
Hi Frank,
I have just downloaded G-Force 5.03 and installed it to my PC, but not on my laptops yet (without further testing). The problem still persists.
You state “As for writing scripts within G-Force, Jerohm is correct, you can no longer write scripts to CTRL + (a key) or invoke scripts by pressing CTRL + (a key)”.
Actually Jerohm’s reply was “I KNOW that I FOUND, script files (to be invoked as CTRL) NOW must be named as LETTERS only...”
My CTRL S script works, so does my CTRL X script, apart from the line used to kill running scripts (the subject of my complaint and ticket). So you can invoke scripts by pressing CTRL + (a letter). Renaming the script CTRL S to CTRL 1 does not work, proving Jerohm’s statement – “numbers do not work”.
I can get round the problems associated with writing scripts from the screen, but I rarely use this function in any case. If a screen appears that I like I can press shift W, then go to my scripts folder and rename Key W.py to Key or CTRL + (any letter I like).txt after editing the text G-Force creates.
Here is an example; I have just created Key W.py in G-Force 5.03. This is the text in Key W.py:
######################################################
G-Force 5.0.3 (5191)# 09-JUL-2013, 14:59:19 (UTC+1)# 0 0 0# ColorMap: BT - MagentoCyan# WaveShape: Magnum# FlowField: Watery Ripples
##################################################StartConfig( "ColorMap", "BT - MagentoCyan", ss_QuickTransition )StartConfig( "WaveShape", "Magnum", ss_QuickTransition )StartConfig( "FlowField", "Watery Ripples", 0 )
I have renamed this script CTRL N (wasn’t using CTRL N for anything) and edited the text to:
#######################################################
G-Force 5.0.3 (5191)# 09-JUL-2013, 14:59:19 (UTC+1)# 0 0 0# ColorMap: BT - MagentoCyan# WaveShape: Magnum# FlowField: Watery Ripples #######################################################
StartConfig( "ColorMap", "BT - MagentoCyan", ss_QuickTransition );
StartConfig( "WaveShape", "Magnum", ss_QuickTransition );
StartConfig( "FlowField", "Watery Ripples", 0 );
CTRL N now works as I have added line terminator semicolons at the end of each line. I can’t get it to work as CTRL N or Key N without the semicolons. Would love to know how you do that!!!! Could you send me an example of the code produced by your method of using shift W + a number to see if it differs from the code I get from the same action? Also it would be interesting to see if the code generated by your computer will work on mine.
As my tickets only mention the problem with the Kill Scripts command I would prefer to keep my tickets for G-Force and Aeon open until I hear from Andy (or a representative) that the problem will be resolved in future releases. I would also like to see the problem resolved before my next licence renewal date as it would persuade me to renew my licence.
I do sympathise with Andy as I have written programs myself in the past. Nothing like G-Force but programs to run life support and patient monitoring in the British NHS, and I have also written targeting systems and cryptographic programs for the MOD.
I found the most boring part of programming was writing help files and documentation as my interests were always towards improving my code and hence the program. The lack of documentation in SoundSpectrum products shows a similar attitude to my own and it would be quite acceptable for Freeware products; but these are not free products and paying customers tend to either get help and documentation or stop paying.
Andy (from some of his posts) seems to want to move forward with SoundSpectrum products which is a good idea, but I have always found that moving forward when you haven’t corrected the mistakes existing in the original code and re-using some of that code can be very dangerous and cause untold problems in the future.
Regards
SteveH
Hi Stephen,
Thanks for your detailed response. Honestly, I haven't had time to familiarize myself with the scripting process enough to be comfortable giving you scripting advice, although I will work on that as soon as I get the chance. I have already alerted Andy O'Meara to this, so please do not swamp him with emails.
As for writing scripts within G-Force, Jerohm is correct, you can no longer write scripts to CTRL + (a key) or invoke scripts by pressing CTRL + (a key). However, I still have not encountered your issue where SHIFT + W always writes to W. It happens if I press SHIFT + W twice, but otherwise, I have no problem writing scripts to numbers or letters. I press SHIFT + W and then I press an alphanumeric key. To invoke it, I press SHIFT + R and then the same alphanumeric key. I hope this helps. If you are still having trouble, perhaps you should consider updating to G-Force 5.03.
I will look into the KillScript issue further, but there are many tickets to answer, and it may take a while. Please, let me know if there's anything else I can do, but know that I am continually working to help you, even though I am trapped in San Francisco for the next few days.
Regards,
Frank Netscher
SoundSpectrum, Inc.
www.soundspectrum.com
================================================
Please let us know if this resolved your issue or if you still need help by replying to or closing this ticket
================================================
Hi Frank,
I have just downloaded G-Force 5.03 and installed it to my PC, but not on my laptops yet (without further testing). The problem still persists.
You state “As for writing scripts within G-Force, Jerohm is correct, you can no longer write scripts to CTRL + (a key) or invoke scripts by pressing CTRL + (a key)”.
Actually Jerohm’s reply was “I KNOW that I FOUND, script files (to be invoked as CTRL) NOW must be named as LETTERS only...”
My CTRL S script works, so does my CTRL X script, apart from the line used to kill running scripts (the subject of my complaint and ticket). So you can invoke scripts by pressing CTRL + (a letter). Renaming the script CTRL S to CTRL 1 does not work, proving Jerohm’s statement – “numbers do not work”.
I can get round the problems associated with writing scripts from the screen, but I rarely use this function in any case. If a screen appears that I like I can press shift W, then go to my scripts folder and rename Key W.py to Key or CTRL + (any letter I like).txt after editing the text G-Force creates.
Here is an example; I have just created Key W.py in G-Force 5.03. This is the text in Key W.py:
######################################################
G-Force 5.0.3 (5191)# 09-JUL-2013, 14:59:19 (UTC+1)# 0 0 0# ColorMap: BT - MagentoCyan# WaveShape: Magnum# FlowField: Watery Ripples
##################################################StartConfig( "ColorMap", "BT - MagentoCyan", ss_QuickTransition )StartConfig( "WaveShape", "Magnum", ss_QuickTransition )StartConfig( "FlowField", "Watery Ripples", 0 )
I have renamed this script CTRL N (wasn’t using CTRL N for anything) and edited the text to:
#######################################################
G-Force 5.0.3 (5191)# 09-JUL-2013, 14:59:19 (UTC+1)# 0 0 0# ColorMap: BT - MagentoCyan# WaveShape: Magnum# FlowField: Watery Ripples #######################################################
StartConfig( "ColorMap", "BT - MagentoCyan", ss_QuickTransition );
StartConfig( "WaveShape", "Magnum", ss_QuickTransition );
StartConfig( "FlowField", "Watery Ripples", 0 );
CTRL N now works as I have added line terminator semicolons at the end of each line. I can’t get it to work as CTRL N or Key N without the semicolons. Would love to know how you do that!!!! Could you send me an example of the code produced by your method of using shift W + a number to see if it differs from the code I get from the same action? Also it would be interesting to see if the code generated by your computer will work on mine.
As my tickets only mention the problem with the Kill Scripts command I would prefer to keep my tickets for G-Force and Aeon open until I hear from Andy (or a representative) that the problem will be resolved in future releases. I would also like to see the problem resolved before my next licence renewal date as it would persuade me to renew my licence.
I do sympathise with Andy as I have written programs myself in the past. Nothing like G-Force but programs to run life support and patient monitoring in the British NHS, and I have also written targeting systems and cryptographic programs for the MOD.
I found the most boring part of programming was writing help files and documentation as my interests were always towards improving my code and hence the program. The lack of documentation in SoundSpectrum products shows a similar attitude to my own and it would be quite acceptable for Freeware products; but these are not free products and paying customers tend to either get help and documentation or stop paying.
Andy (from some of his posts) seems to want to move forward with SoundSpectrum products which is a good idea, but I have always found that moving forward when you haven’t corrected the mistakes existing in the original code and re-using some of that code can be very dangerous and cause untold problems in the future.
Regards
SteveH
"proving Jerohm’s statement"
I never lie... if, I think I might get caught...
I am sorry that I haven't got back to this sooner, but Dew Point has turned me into a miserable grouch, but without:
KillRunningScripts(); // Broke
you really are just wasting your time addressing the other issues. There seems to be work arounds for the other stuff... which I still need to organize, and document.

I never lie... if, I think I might get caught...
I am sorry that I haven't got back to this sooner, but Dew Point has turned me into a miserable grouch, but without:
KillRunningScripts(); // Broke
you really are just wasting your time addressing the other issues. There seems to be work arounds for the other stuff... which I still need to organize, and document.

Thanks again Jerohm,jerohm wrote:"proving Jerohm’s statement"
I never lie... if, I think I might get caught...
I am sorry that I haven't got back to this sooner, but Dew Point has turned me into a miserable grouch, but without:
KillRunningScripts(); // Broke
you really are just wasting your time addressing the other issues. There seems to be work arounds for the other stuff... which I still need to organize, and document.
The problems with newcomers like myself in forums is that no one knows your level of abilities, which is only natural. Sometimes it takes a senior member like yourself to confirm that the reported faults are not due to the new members inability to understand the program and that the fault is real.
I initially reported the KillRunningScripts(); problem in a ticket and think that during a change of code to the new GUI this now no longer works or has been accidentally omitted. I don't think this problem can be solved in the current release, but it should be repaired in future releases.
Not sure who or what 'Dew Point' is but please keep up the good work as you are invaluable on the forum.