So what the hell's up with this?
Page 1 of 1
Laser Tripmine Bug
#1 Posted 28 February 2020 - 01:02 AM
#2 Posted 28 February 2020 - 11:25 AM
Will_Destroy, on 28 February 2020 - 01:02 AM, said:
So what the hell's up with this?
#3 Posted 28 February 2020 - 05:43 PM
In the original DOS version, the LASERLINE sprites would have their x/y position changed without updating the sector. This resulted in the LASERLINE disappearing if it spread to another sector.
Eduke32 added a updatesector() check. However updatesectorz() should be used instead, because of cases like the above which multiple sectors overlap.
r7601 changed some stuff about updatesector(), but the bug it probably incidental.
Eduke32 added a updatesector() check. However updatesectorz() should be used instead, because of cases like the above which multiple sectors overlap.
r7601 changed some stuff about updatesector(), but the bug it probably incidental.
#4 Posted 28 February 2020 - 06:42 PM
Fox, on 28 February 2020 - 05:43 PM, said:
In the original DOS version, the LASERLINE sprites would have their x/y position changed without updating the sector. This resulted in the LASERLINE disappearing if it spread to another sector.
Eduke32 added a updatesector() check. However updatesectorz() should be used instead, because of cases like the above which multiple sectors overlap.
r7601 changed some stuff about updatesector(), but the bug it probably incidental.
Eduke32 added a updatesector() check. However updatesectorz() should be used instead, because of cases like the above which multiple sectors overlap.
r7601 changed some stuff about updatesector(), but the bug it probably incidental.
You only want to use updatesectorz() if the change in coordinates can potentially be a change to a sector vertically stacked on top of another, like with TROR or the water in Shadow Warrior, etc. If the movement is only horizontal you want regular updatesector().
Share this topic:
Page 1 of 1