new suggestions

daxx2kdaxx2k Member Posts: 10
edited November -1 in Working with GS (Mac)
Hello guys!
I came up with some suggestion that will improve a lot your amazing tool :

1 - actor MUST see attributes of another actor without creating global variables every time.
2 - Import/Export behaviors or actors, what about the "My Behaviors" folder?
3 - the change pivot feature in basic behavior list
4 - ability to create keyframe animation for actors

that's it for now :)
thanks.

Davide

Comments

  • zombotszombots Member Posts: 186
    i also have a suggestion.
    have the ability to go to last scence. so if i use a new scene as the pause screen, i can have it return to the last scene and not have to have different pause scenes for every level.
  • CodeMonkeyCodeMonkey Head Chef, Member, PRO Posts: 1,803
    For now you don't need a pause scene for every level, you could just make a game attribute that keeps track of the last level via a number before you go to the pause screen. Then on the pause screen, you check that game attrib and depending on which one it is, change scene to that scene.
  • zombotszombots Member Posts: 186
    that sounds awesome. sorry but im a little confused on how to do this? any chance for a step by step?
    thanks heaps
  • JGary321JGary321 Member Posts: 1,246
    I'm assuming you have a button to initiate the change scene. I also assume you know about the preserve scene check box. So, your rule probably looks something like:

    When mouse is over actor
    When mouse button is down

    Change scene to:Pause Scene (preserve scene)

    Just add this underneath Change Scene:

    Change attribute game.Scene Number to 1

    Of course you need to make the global game attribute first. (Scene Number; integer)

    This takes you to the Pause Screen. I assume you have a button to take you back. So on your button you would have a rule that says something like:

    Mouse is over actor
    Mouse is down
    game. scene number = 1

    Change Scene to (whatever scene 1 is)

    Mouse is over actor
    Mouse is down
    game. scene number = 2

    Change Scene to (whatever scene 2 is)

    etc... You need one for each scene. Hope this helps.

    -JGary
  • ktfrightktfright Member Posts: 964
    JGary, do you have an example of this, because im still not sure how you can have one pause scene and still be able to go back to which ever scene you came from.
  • TobyToby Member Posts: 478
    I'd like a zoomable stage when I'm laying out the level with actors for pixel perfect accuracy. Some small actors are just too small to select and move with the mouse easily. Every time I try to move a small actor using the mouse I can only grab a corner and scale.... very annoying.

    You can select and scroll the object using the arrow keys but it's really slooowww. Maybe holding SHIFT + Arrow keys triples the scroll speed which would alleviate some of the pain.

    If I need to move an actor a long way I usually delete the actor from the stage and add it again, it's quicker than trying to scroll across 1280 pixels.

    Maybe have a selection toolbox like illustrator?

    Realise it's beta but these for me are essential from a speed / usability point of view.
  • TobyToby Member Posts: 478
    What about audio file support for something other than .ogg - MP3,WAV would be nice.
  • harrioharrio Member Posts: 234
    what's cookin,

    i agree with daxx2k on the visibility of actor instances between each other. couldn't this be achieved through giving each created actor instance a unique id when it is spawned or placed in a scene?

    zooming in/out would be good to for the scene editor.

    also, i'm finding that a great deal of my workflow is shifting from the scene view, after a failed scene playback, to an actor view to troubleshoot the actor rules/behaviors. obviously, i don't know how this is coded from an engine perspective, but it would save a lot of time and increase workflow if there were a panel/widget/dock dedicated to the properties and rules of a selected actor. i realized in other engines that i've played with, that you can select any object and it's properties are shown in it's own window. i know this would involve redesigning the ui somewhat. but i think it might help speed design flow and make the overall impression of gamesalad more pleasant.

    when you have fiftheen instances of the same actor, that each have their own unique properties/values/rules, it becomes cumbersome shifting back an forth between editors to tweek them. i understand the need for separate project and scene editors. but i think the elements of the scene and actor editor could be combined to make a more efficient ui. here's my crappy example...

    http://docs.google.com/View?id=dcrvmt6h_57cqf9v6g6

    or, even just a window of the current scene inside the actor editor. so we could select actors to work on, and their attributes and rules would come up. i'll spare you another crappy example for that.
  • daxx2kdaxx2k Member Posts: 10
    I think also that the behaviour description panel is quite useless, we have the help already to see the description once and currently it's a waste of screen space to me
  • SkyMapleSkyMaple Member Posts: 817
    daxx2k said:
    Hello guys!
    I came up with some suggestion that will improve a lot your amazing tool :

    1 - actor MUST see attributes of another actor without creating global variables every time.
    2 - Import/Export behaviors or actors, what about the "My Behaviors" folder?
    3 - the change pivot feature in basic behavior list
    4 - ability to create keyframe animation for actors

    that's it for now :)
    thanks.

    Davide

    I think these are all VERY good suggestions, especially the ability to see other actors' attributes and change pivot point.

    _______________________________________

    Game making service- http://gamesalad.com/forums/topic.php?id=21739
    Sketch to vector service- http://gamesalad.com/forums/topic.php?id=21820
    "Power Orb" style template- http://gamesalad.com/forums/topic.php?id=22179
  • EatingMyHatEatingMyHat Member Posts: 1,246
    I think there is a sticky on new feature suggestions. This thread is a year old and probably should be closed... (I guess I just bumped it again)
This discussion has been closed.