[Since introduced] +CANTSEEK bug

Forum rules
Please don't bump threads here if you have a problem - it will often be forgotten about if you do. Instead, make a new thread here.

Post a reply

Smilies
:D :) :( :o :shock: :? 8-) :lol: :x :P :oops: :cry: :evil: :twisted: :roll: :wink: :geek: :ugeek: :!: :?: :idea: :arrow: :| :mrgreen: :3: :wub: >:( :blergh:
View more smilies
BBCode is OFF
Smilies are ON
Topic review
   

Expand view Topic review: [Since introduced] +CANTSEEK bug

Re: [Since introduced] +CANTSEEK bug

by randi » Wed Apr 18, 2012 9:22 pm

Fixed.

Re: [Since introduced] +CANTSEEK bug

by Major Cooke » Sun Mar 04, 2012 9:30 am

Alright. Let me wip something up real quick.

Re: [Since introduced] +CANTSEEK bug

by randi » Sat Feb 25, 2012 8:16 pm

Wad, please.

Re: [Since introduced] +CANTSEEK bug

by jpalomo » Sat Jan 21, 2012 12:44 pm

Any idea if the same thing happens with +DONTSEEKINVISIBLE?

Edit: Included a test wad with +cantseek and +dontseekinvisible
Attachments
cantseektest.wad
use +notarget. Chaingunguy is invisible
(7.27 KiB) Downloaded 20 times

[Since introduced] +CANTSEEK bug

by Major Cooke » Thu Jan 19, 2012 8:34 pm

The +CANTSEEK flag introduces a rather serious bug with seeker missiles, especially auto-seeking ones. If it acquires an actor with +CANTSEEK, instead of the projectile attempting to refocus on another monster that it can seek, it goes in the straight path when fired. It will not attempt to acquire any other targets until the first one it acquired dies/stops existing.

Top