I'm still having an issue with A_LookEx in the v4.13 dev builds. I've got a BFG projectile that arcs between enemy targets, six arcs in total. However, currently, all six arcs now target one single target, whichever is closest with disregard for FOV, instead of a wide range of targets depending on the arcing actor's A_LookEX FOV parameter.
Please see attachment for demo.
A_LookEx FOV Still Broken?
Moderator: GZDoom Developers
Forum rules
Please construct and post a simple demo whenever possible for all bug reports. Please provide links to everything.
If you can include a wad demonstrating the problem, please do so. Bug reports that include fully-constructed demos have a much better chance of being investigated in a timely manner than those that don't.
Please make a new topic for every bug. Don't combine multiple bugs into a single topic. Thanks!
Please construct and post a simple demo whenever possible for all bug reports. Please provide links to everything.
If you can include a wad demonstrating the problem, please do so. Bug reports that include fully-constructed demos have a much better chance of being investigated in a timely manner than those that don't.
Please make a new topic for every bug. Don't combine multiple bugs into a single topic. Thanks!
-
silentzora
- Posts: 454
- Joined: Sun Jan 04, 2004 6:24 pm
A_LookEx FOV Still Broken?
You do not have the required permissions to view the files attached to this post.
-
merlin86
- Posts: 144
- Joined: Tue Jan 29, 2008 4:02 am
- Preferred Pronouns: He/Him
- Operating System Version (Optional): Windows 11 Pro
- Graphics Processor: nVidia with Vulkan support
Re: A_LookEx FOV Still Broken?
Just a head up, since I never made a weapon.
The wiki page about A_Look and A_LookEx talks about monsters and not missiles.
It might be the problem?
The wiki page about A_Look and A_LookEx talks about monsters and not missiles.
It might be the problem?
-
silentzora
- Posts: 454
- Joined: Sun Jan 04, 2004 6:24 pm
Re: A_LookEx FOV Still Broken?
It wasn't an issue before. Whether it's marked with the MONSTER combo or not, the behavior is the same.
As far as I know, this was properly targeting monsters in the proper sight line and not just the closest one in 4.10. For whatever reason, it appears to be acquiring a target when it's not supposed to, continuing into 4.13.