Playmaker Forum
PlayMaker News => PlayMaker Announcements => Topic started by: Alex Chouls on June 11, 2013, 11:17:32 PM
-
Playmaker 1.6.1 is now live in the store!
Release Notes: https://hutonggames.fogbugz.com/default.asp?W311
-
˚ Fixed NullReferenceException with disabled FSMs and trigger/collision events.
This was the root of my problems then! I had some real head scratching moments with this and could not figure where the problem was. In the end I stripped out the offending code, which forced me into a different but much better approach to my projects game style. For once a bad bug has, eventually, improved my planned game 8)
-
Im getting:
Assets/PlayMaker/Custom Actions/PhotonGetNextRoom.cs(11,22): error CS0101: The namespace `HutongGames.PlayMaker.Actions' already contains a definition for `PhotonNetworkGetNextRoomProperties'
On a project that was fine before the update to 1.6.1
whats this?
Mark
-
I tried a new project... no such error... so what do I need to do to update an existing project?
AND BY THE F***ING WAY... I just clicked on the Photon wizard, and at the top in orange it says:
WARNING: Photon requiresStandaloneOSXIntel Pro to make an StandaloneOSXIntel build???
What does this mean??? I was using photon 5minutes ago.. on unity free...! Mac version...
-
Hi,
PhotonNetworkGetNextRoomProperties: that's my fault sorry. It's because I named that action wrongly when I started this and then corrected it, so you get this error. Simply replace in the states where you had implemented PhotonGetNextRoom and use the new one: PhotonNetworkGetNextRoomProperties
As for the orange warning: true, I need to remove that if you are not publishing for mobiles, the problem is that on mobile socket connection is only available for pro. Let me correct this warning so that it doesn't appears on Unity Indie if you are not publishing for mobile platforms.
bye,
Jean
-
Phew!!
-
yeah... ;)
If you want I can give you the old action as a replacement? you can keep the newest iteration and you won't have to ( tho I strongly recommand you do make the changes)
bye,
Jean
-
I did understand your suggestion, but theres more... looky here... whats happened here?
-
Hi,
If you are referencing to the way the Fsm component look, it's simply because you switched your inspector to Debug Mode. Switch it back to "normal" in the Inspector top bar menu.
Else, can you desribe what is the problem?
bye,
Jean