Ask Lemmy
A Fediverse community for open-ended, thought provoking questions
Rules: (interactive)
1) Be nice and; have fun
Doxxing, trolling, sealioning, racism, and toxicity are not welcomed in AskLemmy. Remember what your mother said: if you can't say something nice, don't say anything at all. In addition, the site-wide Lemmy.world terms of service also apply here. Please familiarize yourself with them
2) All posts must end with a '?'
This is sort of like Jeopardy. Please phrase all post titles in the form of a proper question ending with ?
3) No spam
Please do not flood the community with nonsense. Actual suspected spammers will be banned on site. No astroturfing.
4) NSFW is okay, within reason
Just remember to tag posts with either a content warning or a [NSFW] tag. Overtly sexual posts are not allowed, please direct them to either [email protected] or [email protected].
NSFW comments should be restricted to posts tagged [NSFW].
5) This is not a support community.
It is not a place for 'how do I?', type questions.
If you have any questions regarding the site itself or would like to report a community, please direct them to Lemmy.world Support or email [email protected]. For other questions check our partnered communities list, or use the search function.
6) No US Politics.
Please don't post about current US Politics. If you need to do this, try [email protected] or [email protected]
Reminder: The terms of service apply here too.
Partnered Communities:
Logo design credit goes to: tubbadu
view the rest of the comments
I know more about the Doom engine than I do interpersonal relations. Did you know you can completely destroy collision physics via writing over memory addresses if you shoot a bullet weapon at a stack of corpses?
Edit to explain: Decino has a great video explaining it in detail. Link is above, tho I'm at work and can't watch it to double check. Poorly explained from my memory:
When you fire a hitscan attack (press button, gun shoots a bullet that instantly hits with no travel time), the engine does a number of checks for collision, range, etc. If you have a stack of actors (decorations, monsters, ammo, etc) and you fire a hitscan attack in the direction of the stack, it makes a call to check collision for each individual actor in that stack. The actors don't have to be all on top of each other, it just matters that the hitscan line crosses over those actors.
If you have a stack of 129 or more actors and fire a hitscan weapon, the game will essentially overwrite parts of the memory address. I don't understand a lick of that stuff myself, admittedly, I'm no programmer. If you have something around ~140ish actors in the line of fire of a hitscan attack, the Blockmap system for checking collision effectively gets erased. Projectiles pass through everything, bullets and melee do no damage, players and monsters walk through walls, and you can't interact with things like switches. You can fix it by saving and loading, though if you're recording demos you can't save.
What does this even mean
Great deep lore of ancient games
It's clearly some sort of combination of words but I can't quite make out what they're attempting to communicate...
Nevertheless, I am fascinated. And open to more!
I love reading about people's passions, and I think it adds to it the less I know about the subject, as just sitting back and enjoying how excited and interested someone is in their thing, really is so nice.
Yeah I'm not the best word smith on the best of days, let alone immediately after waking up with 3 hours of sleep lol
I edited my comment with a poor explanation from memory, alongside a great video explaining that I can't watch to double check my comment as I'm at work currently.
Meaning then you just pass through objects rather than collide? Or is it unable to properly calculate the incident & resulting collision vectors, meaning the resulting trajectories are nonsensical?
Everything from projectiles to monsters pass through walls, can do no damage to one another, and can't interact with stuff like switches. I edited my comment with a poor explanation from memory, alongside a great video explaining that I can't watch to double check my comment as I'm at work currently.