MantisBT - Zandronum |
View Issue Details |
|
ID | Project | Category | View Status | Date Submitted | Last Update |
0000192 | Zandronum | [All Projects] Suggestion | public | 2010-11-09 20:28 | 2018-09-30 22:50 |
|
Reporter | Xenaero | |
Assigned To | Torr Samaho | |
Priority | none | Severity | tweak | Reproducibility | N/A |
Status | closed | Resolution | duplicate | |
Platform | Microsoft | OS | Windows | OS Version | XP/Vista/7 |
Product Version | 98d | |
Target Version | | Fixed in Version | | |
|
Summary | 0000192: compat_hitscan implementation tweak to replicate oldschool damage more effectively |
Description | Essentially, compat_hitscan is supposed to re-introduce the old BLOCKMAP hit detection to bring back an element of how bullet weapon damage calculation used to work in 'oldschool'/vanilla environments.
What I'm proposing is when this is implmented during an update to the latest ZDoom (as Skulltag does not have this currently, it's an opportune time to plan for it) it introduces another factor to bring the hitscan damage effectively to its former state before the changes surrounding the RNG were introduced.
I propose that compat_hitscan applies not one but two changes: both the re-introduction of the old BLOCKMAP calculations, and the re-introduction of the old damage calculation table, reverting the changes (while the flag is on, obviously) Randy had made to alter hitscan weapons behavior. I do not have hard numbers to compare the effects of the two currently. |
Steps To Reproduce | Obtain cake
Eat cake
Be happy. |
Additional Information | I'm a banana and ur under arrest |
Tags | No tags attached. |
Relationships | duplicate of | 0000101 | closed | Qent | backport compatibility flags update from ZDoom r2340, r2341 | COMPAT_HITSCAN, COMPAT_WALLRUN | duplicate of | 0000031 | closed | Torr Samaho | New DMFlag: "Use Classic PRNG" |
|
Attached Files | |
|
Issue History |
Date Modified | Username | Field | Change |
2010-11-09 20:28 | Xenaero | New Issue | |
2010-11-10 05:38 | unknownna | Note Added: 0000601 | |
2010-11-10 06:49 | Xenaero | Note Added: 0000602 | |
2010-11-14 14:26 | Anonymous | Note Added: 0000614 | |
2011-02-18 20:52 | unknownna | Relationship added | duplicate of 0000101 |
2011-02-18 20:53 | unknownna | Relationship added | duplicate of 0000031 |
2011-02-19 15:41 | Gez | Note Added: 0001109 | |
2011-02-23 21:28 | Xenaero | Note Added: 0001122 | |
2011-05-15 18:24 | unknownna | Status | new => resolved |
2011-05-15 18:24 | unknownna | Resolution | open => duplicate |
2011-05-15 18:24 | unknownna | Assigned To | => Torr Samaho |
2018-09-30 22:50 | Blzut3 | Status | resolved => closed |
Notes |
|
|
|
|
|
It's not a duplicate, if you read the reports, actually, it's very clear my suggestion is different from those that precede it. |
|
|
|
|
|
(0001109)
|
Gez
|
2011-02-19 15:41
|
|
So, you want compat_hitscan to automatically trigger compat_oldrandom as well? Or do you mean other changes than those addressed by these compat flags? And if so, which? |
|
|
|
Gez, I had not seen Alex's ticket before I made this one, basically it's already been achieved. |
|