Can't really get the hang of this.
Basically at the moment I've got multiple instances of my badguy object. For each badguy there's also an invisible "line of Sight" object. What I want is for the enemies to go into an "alert" behaviour when their personal line-of-sight is overlapping the player. So far everything works except that every enemy becomes alerted when only one spots the player.
I've tried spreading values and testing for them but it doesn't seem to work. Can someone help me out?
So they are borg? OK sorry. Can you post a sample?
Another thought after a re-read.
Many people, including myself, when starting out with spread values use it in something like Start of Frame or call it on a loop. This will not work if you add or remove any uses after calling. You will have to then recall. Many people use and Always, I like to manage it a bit.
Sill post if you can and this does not help.
Hope that helps...
K
Ive also noticed this happen to one of my games when I duplicated the active objects rather than cloning them.
Not sure if thats your issue or not, but figured I'd share.
I'd be happy to make you an example but I just need a bit more info first...
* Is there only one player object, or are there several?
* What is the "line of sight object"? Is it a true line-of-sight (ie. do you want it blocked by obstacles?), or is it a circular radius or cone? (if it's one of the latter options, you'd be better off using maths instead of extra objects).
There is only one player object, so it's easy on that front. The line of sight object is literally a line between the player and the enemy, it is an active object stretched and rotated in such a way that one end is always touching the player and one end is always touching the corresponding enemy. Testing if the enemy can see the player is just a matter of seeing if the line is overlapping an obstacle or not. So yeah, it's proper.Originally Posted by MuddyMole
Cheers in advance, I eagerly await your response.
Generally speaking, it's good to avoid using fastloops wherever possible, as they can affect framerate quite badly.
MMF2 will automatically match objects for you, so there's really no need to use spread values / fastloops for something like this anyway.
Here's a quick demo:
http://cid-b1e7ee094271bbda.office.live.com/self.aspx/Public/LoSFeb11.mfa
If your enemies have a limited vision range and field of view, it would be more efficient to check these first, and only distort the LoS objects if the other checks are ok. If you're using HWA it won't make much difference though, as scaling/rotating is so fast.
I've included a version using spread values and fastloops.
I did a quick test, and it looks like the version with fastloops is quite a bit faster in standard mode (which would include Flash), while the loop-free version is much faster in HWA.
Posting Permissions
Reply With Quote