GameSalad

Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!

Who does this new face belong to?

123457»

Comments

  • PBEmpirePBEmpire Posts: 676Member
    Now time for Codelord or a CodeChampion or maybe even a CodeNerd
  • SolarPepperStudiosSolarPepperStudios Posts: 754Member
    @CodeWizard I have a question for you Mr.Wizard. Would it be possible to make the "Spawn Actor" action able to spawn actors in different layers? It would help out my game sooo much. Thats ahead of time for any reply! :)
  • CodeMonkeyCodeMonkey Posts: 1,803Head Chef, Member, PRO

    @CodeWizard I have a question for you Mr.Wizard. Would it be possible to make the "Spawn Actor" action able to spawn actors in different layers? It would help out my game sooo much. Thats ahead of time for any reply! :)

    I'm not CodeWizard, but hopefully the answer is still good enough.
    While theoretically you can spawn an actor in different layers with some code changes, it is not as simple as just adding an attribute selection in the spawn actor behavior.
    Since scenes have different attributes than other scenes, we have locked off access to scene attributes from prototype actors and thus couldn't accurately let the Spawn Actor behavior specify which layer to spawn to. We would need to do a larger overhaul to the engine to do what you're asking. That would require a larger design to make sure everything would still work without crashing other things.
    I could possibly think of a solution of referencing a layer by index, with 'current layer' as an option. But you'd also need to make sure if the index is invalid then the behavior gracefully fails to work.

    With the current functionality I use one of 2 methods:
    1) Your layers are just one layer and you treat top of layer, bottom of layer, in front of actor, and behind actor as "layers".
    2) You have the same actor prototype in different layers and depending on which layer you need, you call that actor via game attribute to spawn an actor defined by another game attribute.
  • SnapFireStudiosSnapFireStudios Posts: 1,603Member
    @CodeMonkey - While we both know that your two options are not always optimal, I understand why it is difficult to implement this. Thank you for answering. :)
    - Thomas

    Ignore females. Acquire currency.

  • SolarPepperStudiosSolarPepperStudios Posts: 754Member
    @CodeMonkey Thanks for the answer! :) I'm just going to spit out another idea that will probably have a good reason for not being implemented, but what about using a change attribute to change the layer? Like this:
    Inside the scene attributes accessed when double clicking an actor use change attribute: actor.layer to (insert layer name here)
  • SnapFireStudiosSnapFireStudios Posts: 1,603Member
    @Utveckla_Games - I'm pretty sure that would have the same exact issues that he described. That's basically what your suggestion would do. (But yes, the feature would be nice)
    - Thomas

    Ignore females. Acquire currency.

  • CodeMonkeyCodeMonkey Posts: 1,803Head Chef, Member, PRO
    @Utveckla_Games that would probably be a new attribute type needed. Layers don't have unique names so passing in a layer name wouldn't work so easily without breaking someone's project.
    There's also the case where some layers are scrollable and some are not. That would also affect where actors are drawn when you switch between layers.
  • SolarPepperStudiosSolarPepperStudios Posts: 754Member
    @CodeMonkey I see now... Well thanks for the reply!
  • SnapFireStudiosSnapFireStudios Posts: 1,603Member
    edited April 2013
    CodeMan, CodeMonstrocity, Codeface, CodeHelper, CodeShooter, CodeSalad, Codeduke, Codeking, CodeDude, etc. :P

    - Thomas
    P.S. Haha.. GS Should've introduced "CodeSalad" for their april fools, forcing users to code in BASIC, as well as the profit-share. ;) :P

    Ignore females. Acquire currency.

  • SolarPepperStudiosSolarPepperStudios Posts: 754Member
    @SnapFireStudios Oh, I love Basic! I can get it to sing happy birthday to me! :D
  • SnapFireStudiosSnapFireStudios Posts: 1,603Member
    Oh noes! They haven't added you to the team page yet ;)
    - Thomas

    Ignore females. Acquire currency.

  • CodeWizardCodeWizard Posts: 1,143Key Master, Head Chef, Executive Chef, Member, PRO GameSalad Employee
    The horror!
  • HymloeHymloe Posts: 1,651Member
    Really great to have you onboard, CodeWizard! Anyone who worked at Sierra is more than awesome. And it's great to hear that async multiplayer is on the way. :)
  • neomanneoman Posts: 813Member
    Welcome and thanks for introducing yourself ... Looking very forward to seeing the new changes ... =D>
  • PBEmpirePBEmpire Posts: 676Member
    CodeNorris!
  • StormyStudioStormyStudio United KingdomPosts: 3,987Member
    a bit late... but welcome to GS... I hope the jobs working out... I hope to be pestering you with some new questions soon.
  • Zenith_GameworksZenith_Gameworks Posts: 310Member
    Lol why is this thread still getting comments?
  • CodeMonkeyCodeMonkey Posts: 1,803Head Chef, Member, PRO
    That's like asking, why are you thinking about blue monkeys?
  • CodeWizardCodeWizard Posts: 1,143Key Master, Head Chef, Executive Chef, Member, PRO GameSalad Employee
    The job is going well! Thanks for the comment.
  • SnapFireStudiosSnapFireStudios Posts: 1,603Member

    That's like asking, why are you thinking about blue monkeys?

    How did you know?? :-O
    - Thomas

    Ignore females. Acquire currency.

123457»
This discussion has been closed.