Playmaker Forum
PlayMaker Help & Tips => PlayMaker Help => Topic started by: stevecash83 on June 09, 2017, 01:01:29 AM
-
This is the third game I've had this problem with. Using 'Triggers', 'Wait' and 'MoveToward', anything really, works fantastic in the editor, but once built, nothing works at all. Is there any fix for this? It's like PlayMaker is for editor only projects and does nothing for a built project.
-
Hi,
Sorry to hear that, but you should always have a backup of your projects.
You can do this manually or use git/sourcetree.
If you still can retrieve your project, what platform are you building to?
Are you using stripping levels?
I worked on several projects for android and webgl but i did not have problems with it.
except on android when using stripping level and also sometimes when i used get/set properties
-
I'm using MacBook Pro and building for PC and Mac. My scene seems to have completely deleted itself forever, but this isn't the first time.
Are there a list of Playmaker functions that don't work in builds? This seems to keep happening and it sucks scrapping projects after so much work.
-
Okay I got the scene back. Unity had loaded a blank one for some reason with an empty assets folder.
So moving on, playmaker functions still aren't working outside of the editor. Any ideas?
-
Okay, so as far as I can tell everything in the game seems to work EXCEPT triggers. The triggers work in the editor but NOT in the build. Please, any help?
-
Hi,
What unity and playmaker version are you using?
Can you show some pictures or a video with the triggers and actions for it.
I found a similar issue on the unity forum (http://answers.unity3d.com/questions/688926/collisions-not-working-when-game-built-but-works-f.html)
You can use a "debug log" action in the state that should be triggered and also where the trigger action is.
-
Inity 5.6.1f1
Playmaker 1.8.4
See this video :https://www.youtube.com/watch?v=6MNwxMPskz8 (https://www.youtube.com/watch?v=6MNwxMPskz8) for a full showing of the errors I am encountering.
Any help would be appreciated!
-
Hi,
I just made a test scene quickly, but all seems to work here.
Same version as your unity and playmaker, the only difference is that i build on a pc instead of a mac, but i don't think that can be the issue.
Did you try a build in development mode and did you add some "debug log" actions?
You can also have a text object and use 'set text' and place that into the action with a trigger and one in the state after the trigger.
You can also send a bug report inside unity on the playmaker tab : playmaker/Tools/Submit Bug Report.
And explain as much as you can (what platform you build / what 3th party assets you are using / ...)
-
I'm agreed with Djaydino. If you use a text object and set the text to "inside trigger" when you are inside and "outside trigger" when you are outside the trigger. Then you can see if the trigger is activated. Maybe the trigger has moved, so it's not at the same position in the build as in the editor. What if you use a trigger with mesh, so you can see if it's moved or something?
Hope you get it to work. It's very frustrating when things you expect that should work doesn't work at all.
-
I built it with triggers having mesh. I can see them, they have not moved. They just do not respond to 'Trigger Enter' once built. They are still working in the editor.
-
Ok. Try to create a brand new scene. And create a trigger to see if Trigger enter works.
-
On your other post you said that you tried on a clean scene and it worked there.
I tried it in a new scene (an essentially empty scene) and the trigger worked on build. So I pasted the large scene that I had been working on into the new scene and same issue, once built, the triggers don't work again. Help?
It seems to me it is not a playmaker issue.
1st : Be sure to make a backup of your project folder before you try anything.
Did you check out the link to the unity forum (http://answers.unity3d.com/questions/688926/collisions-not-working-when-game-built-but-works-f.html)?
Did you try with debug actions?
Maybe you can try adding a part of the big scene and see if it works.
If so then add another part.
Another thing you can try is to "Reimport all" you can find this under the Asset Menu
-
Inity 5.6.1f1
Playmaker 1.8.4
See this video :https://www.youtube.com/watch?v=6MNwxMPskz8 (https://www.youtube.com/watch?v=6MNwxMPskz8) for a full showing of the errors I am encountering.
Any help would be appreciated!
Hi,
The video is not listed anymore, what are the errors you see in the Unity console?
Bye,
Jean
-
I tried it in a new scene (an essentially empty scene) and the trigger worked on build. So I pasted the large scene that I had been working on into the new scene and same issue, once built, the triggers don't work again. Help?
When you tried it in a new scene, and it worked there. Did you copy the FPS Controller from your main scene to the new scene to try the trigger? Or did you use another object just to make something very fast to see if it works?
-
Hi,
Your issue might be the same as on this topic:
http://hutonggames.com/playmakerforum/index.php?topic=15332.msg70888#msg70888
Maybe you can try and confirm if this is the same issue.
-
Hi,
It is Very likely this issue. It's currently being adressed internally, hopefully a fix will be available very soon.
Bye,
Jean
-
I've finally found the solution.
Sorry to the 'Customer Support' team, I mean, 'Forum Community' that PlayMaker uses to avoid having to provide customer support.
After moving a non working project from my MacBook to a new PC running Windows 10, I noticed that most states that used 'Trigger Enter' were fixed by simply selecting 'Trigger Enter' AGAIN and the text for 'Trigger Enter' changed size. Strange, I know, but the text in the playmaker editor simply became more spread across and now all triggers work on build.
It's been frustrating and the moderators of this forum have made finding a solution something that I had to do on my own, since they spend more time typing 'No repeat posts' and basically acting as authority driven douches who care more about policing the forum than actually helping paying customers find help.
So, that being said, if you are using a Mac and are having issues where your builds aren't working, try moving your entire project to a PC and reselect the transition events to clear up a bug that makes your game unplayable on build.
I hope my experience with this will be helpful to users in the future, since getting any actual answers on this forum is more like asking a teacher in school to advise you but getting mocked for asking questions that they don't know the answer to.
I'm sure this thread will be closed and maybe even deleted soon, but for the mean time, let me just state a fact. The creators of PlayMaker and the moderators of this forum don't care to help you. This forum is NOT customer support for Playmaker. This forum is an excuse for not having customer support.
You may ask questions, and you might even get an answer. But if you're like me (not entirely patient when dealing with issues using a product you paid actual money for), I'm sure you'll find yourself in the same situation.
So as a user of PlayMaker I have a goal. To try and help other users on this forum by answering questions with the best of my ability and diving into extensive research. For some reason, I feel like I might be the first to do so.
Again, I have to say, Playmaker is an amazing product!
This forum, however, is a pathetic excuse for customer service.
-
Sorry to the 'Customer Support' team, I mean, 'Forum Community' that PlayMaker uses to avoid having to provide customer support.
1st off all!
I am a moderator yes, But i am not a member of the Playmaker team and i do this to help others! for free!!
So i am defiantly not customer support!
For Customer support i said already in a pm to you that you can pm or mail Alex.
It's been frustrating and the moderators of this forum have made finding a solution something that I had to do on my own, since they spend more time typing 'No repeat posts' and basically acting as authority driven douches who care more about policing the forum than actually helping paying customers find help.
Multiple post from the same person on the same problem makes it a lot harder to folow up, and this is standard on any forum.
And we did try to help..... Did you send a bug report? did you follow or reply to our questions?
How can we find a solution if you basically say 'it don't work' it ain't that simple!
Without information we can't find a solution especially with a rare/uncommon issue...
I'm sure this thread will be closed and maybe even deleted soon, but for the mean time, let me just state a fact. The creators of PlayMaker and the moderators of this forum don't care to help you. This forum is NOT customer support for Playmaker. This forum is an excuse for not having customer support.
A forum is not a customer support it is a community!
You may ask questions, and you might even get an answer. But if you're like me (not entirely patient when dealing with issues using a product you paid actual money for), I'm sure you'll find yourself in the same situation.
I am sure many disagree that people don't get any help.
Did you try the unity forum? it takes sometimes weeks to get an answer...
But you are right, if you are very inpatient (like if you are expecting an answer within a few hours and then reply 'this forum is dead' ) then indeed you have a problem.
-
So you gave minimal information regarding your issue, it ended up likely being down to your setup, plenty of attempts to aid you were made, you dispute the universally accepted definition of a forum in favour of your own interpretation... a lengthy passive aggressive attack, not the best way to get help.
-
Hi,
Just to make sure you we are all ok with this, we NEVER delete rants or posts where negative comments are made to PlayMaker even when it turns out not a PlayMaker issue, I am moderator since almost day one on this forum, and it never happened.
Indeed, it's been a HutongGames policy since day one to mix Customer Support with Forum Support. Customer Support and Forum Support is the same here because I am being contracted to provide support via the forum. Many posts you see here where first customer support contacts via emails, where we suggest to make it as a post so that others benefit from this. I am having skype sessions with share screen on problems we are trying to solve and have difficulties reproducing, etc etc. But If we were solving problems only privately, no one would benefit. Here you search the forum for your problem and you likely find a handful of threads on that problem, else, you are onto something and you should bump us until the issue is solved ( be it a unity problem, a PlayMaker problem, or your own problem in your logic implementation).
And I must say on behalf of HutongGames that we are very ( !VERY! ) proud of all the contributors that spend so much time helping others on this forum! All the work you do not only benefits others, but it also consolidate your expertise, improves your communication skills, make PlayMaker better tool, and makes good use of Internet. Good Karma across the board to say this differently :)
Bye,
Jean
-
Hi,
Also, I think your problem might related to this: http://hutonggames.com/playmakerforum/index.php?topic=15332.msg70884#msg70884
Bye,
Jean
-
To counter, I'd just like to say that this forum is always great and does exactly what a forum should, bring users of the software as well as members of the company together to answer questions and help each other out.
I recently had a similar problem to the OP and the team were great at finding a solution, including adding me to the beta testing group, something they didn't have to do. But I realise in order to help them fix things I had to give them as much info as I could, I couldn't just post a vague description like 'Trigger doesn't work, help please'. I went through about four days of problem solving first, pretty much re-importing every single file of a very large project one by one until I could narrow things down and find what was causing the problem (turns out it was the Global Variables file). Despite this being a massive pain I knew it was necessary in order to solve the problem.
Also, if you think it a problem with Playmaker, file a bug report.
So, thank you to the PM team and the community. Keep up the great work, without you I wouldn't be making games.
-
Hi,
@LAB618 :
Also thank you very much to help and share that information, the more information we get on a problem, the easier it gets to find a solution.