Prior to phase 2 beta the Get Player Camera Yaw/Pitch functions would tell you the current yaw/pitch of the player whatever that value was. After phase 2, the function failed to work at all (under certain conditions it may have worked).
After the release of StarCraft II (peace be upon it), the functions seemed to work, however my functions that depended on using it worked noticably sluggishly and made the maps almost unplayable. What I found was that the yaw/pitch would only be reported for certain values. That is it seemed the functions were rounding to a real of a smaller bit size.
It could be that my triggers are somehow causing this issue, so could anyone confirm this or provide a workaround? I absolutely require these functions to work with as much resolution as possible for my projects.
-SexLethal
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
Prior to phase 2 beta the Get Player Camera Yaw/Pitch functions would tell you the current yaw/pitch of the player whatever that value was. After phase 2, the function failed to work at all (under certain conditions it may have worked).
After the release of StarCraft II (peace be upon it), the functions seemed to work, however my functions that depended on using it worked noticably sluggishly and made the maps almost unplayable. What I found was that the yaw/pitch would only be reported for certain values. That is it seemed the functions were rounding to a real of a smaller bit size.
It could be that my triggers are somehow causing this issue, so could anyone confirm this or provide a workaround? I absolutely require these functions to work with as much resolution as possible for my projects.
-SexLethal