Installing several different versions of gamesalad - Question

ccbx4321ccbx4321 Member Posts: 43
edited November -1 in Working with GS (Mac)
I think I've heard people mention it's possible to install different versions of gamesalad on the same machine (i.e. keep your old version 6.2, 7.0, etc.). I'm currently working under an older version so I don't screw those games up by updating.

I grew up on DOS and Windows (when it came about). The mac has been a more recent development (about 2 years) for me so I'm not sure exactly how the installs/directory structure works. When I installed game salad, I dragged it's package to the applications folder. Does it install other files on the hard drive it calls upon (in the Users/library or whatnot?) or could I simply rename the version of Gamesalad I'm working on now something like "Gamesalad v7x" and simply copy the newer version into the same directory (applications)? Could this be true also for older versions? I just want to get an exact explanation/someone-to-hold-my-hand so that I don't screw up all of my work by upgrading.

Thanks for your help,

Caleb

Comments

  • firemaplegamesfiremaplegames Member Posts: 3,211
    Something to consider, is that when you go to publish your game for the App Store or make a Desktop Application, GameSalad publishes your game with the latest version. Currently v. 0.83. People are also notified to update the web plug-in as well to the latest version.
  • ccbx4321ccbx4321 Member Posts: 43
    Seriously? Balls! I don't care so much about the web plug-in, but I assume that will screw with the gameproject file. I remember reading about everyone's games getting screwed up when they updated so I figured I'd wait for the bugs to get ironed out. No update has been released so I thought maybe I could workaround it and install 2 versions on this machine.
  • firemaplegamesfiremaplegames Member Posts: 3,211
    Yeah, I would update now and get it over with.

    The main problem areas are (or were for me):

    1. The MoveTo behavior does not consistently stop at its target
    2. Change Scene (preserve Scene) has been removed
    3. Behaviors do not necessarily happen from the top down.

    The solution to #3 is to use Timers to control the sequence of behaviors.
    Before, you could do this:

    Rule
    When Touch is Pressed
    Play Sound
    Destroy Actor

    Now, it is best to use a Timer to sequence it, like this:

    Rule
    When Touch is Pressed
    Play Sound
    Timer After 0.1 seconds
    Destroy Actor
Sign In or Register to comment.

© Vanilla Keystone Theme 2024