Cannot constrain position from actorA to actorB, and from actorB to actorC?
JodyMitoma
Member Posts: 307
I have a MainPlayer actor. I have a shadow constrained to his position. I also have an invisible "collide" box constrained to his position. These work fine and dandy.
BUT...
As soon as I try and make an invisible actor, and constrain my MainPlayer's position to the invisible actor, GameSalad crashes instantly. Every. Single. Time. 
I REALLY need this if I want to save time in creating ALL of my games levels!!
(The reason for this new invisible actor is because the platforms on my game are a bit 3D, so I need my actor to be sitting a tad bit lower than on top of the "platforms", so that he is not floating above them, but instead is within the 3D constraints of the platform itself. Without this invisible actor allowing me to constrain my MainPlayer's position to it, I will have to create - literally - thousands of invisible actors for my MainPlayer to collide with, instead of the platforms themselves!)
Comments
Are you turning off visibility or setting the opacity to zero? Try the opposite and report back.
@The_Gamesalad_Guru, I don't even get that far! The Alpha is still set to 1, and it is set to visible. It crashes before I am able to take any further steps.
I'm beginning to wonder if it is one of the many, many, MANY attributes set up for my MainPlayer that is causing the flaw. There are TONS, for soooo many different things. I will try turning them ALL off, and see if it allows me to constrain.
@JodyMitoma, screen shot or it didn't happen!
Holy smokes, I turned off every single thing on the mainPlayer, and it still crashes instantly as soon as I try to constrain my mainPlayer with an empty actor! GRRRRR
@Hopscotch, screenshot of my MainPlayer's rules, behaviors and attributes?
@hopscotch, @The_Gamesalad_Guru, and it looks like we're back in business.
I decided I would try and remove my mainPlayer's actor velocityX of 250, and it didn't crash this time. Looks like I may have to move a few rules and attributes from my main player to this new invisible box!
Saves me HOURS of work down the line if I can get this to work though!!
Yep, everything related to your problem.
Even constraining actors in a loop won't crash GS, just not give sensible results. Just tried it.
Woah, ever weird man...
I put the constraint attribute position, then gave the mainPlayer his VelocityX 250 back, and it didn't fuss one bit! Wohoo! Funny how I had to do it in a specific order for it to be okay with it! Everything was reverted back to how it was prior to this big clusterfk.
@Hopscotch, that stuff is top secret!
@JodyMitoma , look closely at your two actors, the invisible one and your main character. Layout the functions and actions that they need to perform and have a look how you can split these up sensibly in both, letting them just pass states between the two.
e.g.
the invisible collision actor is responsible for all movement input and actions.
the main actor only changes animations according to states communicated by the invisible actor.
Simplify as much as possible.
I must have special privileges then, I can alt-crtl-right-click on your name and choose "show desktop"
I'm going to explode. This is so nerve wracking.
Nearly there.. Unforuntately I used self.____ instead of game.____, so now I have to make a few more changes. What a headache to add one tiny difference, haha. It just goes to show how everything connects together to make a wonderful game.
OH HECK YEA!!! So setting that up for the past hour just saved me 5+ hours in the near future!
Thank you for attempting to help @Hopscotch & @The_Gamesalad_Guru.