HLP Network

News:

HLP Donations Page has been reworked for supporting the site.
Please note that the previous "Tiers" are currently not operational (but will be worked on).
You can still cancel any previous re-occurring donations to make new ones which will go to the new Treasurer Admin (Zacam).

 
« Previous Thread Next Thread »
Print
Pages: [1]   Go Down

Author Topic: Puncture Weapons & Beam Damage  (Read 1479 times)

0 Members and 1 Guest are viewing this topic.

Offline Erebus Alpha

  • 26
Puncture Weapons & Beam Damage
on: July 08, 2016, 03:12:47 pm
Is there a way to make "puncture" flagged weapons not do 75% less hull damage by default? Is there a way to make beams properly obey $Armor Factor, $Shield Factor, and $Subsystem Factor? I'm trying to build a fighter-mounted beam cannon that melts subsystems with intense EMP.

I thought I saw these options once in the modding wiki, but I cannot seem to find them now.
"Obviously the meson bomb is a form of cat-toast-device, with the buttered toast inverted, so that the cat and toast both fly in the direction of gravity much faster than expected. By introducing artificial gravity, a pair of cat-toast perpetual motion accelerator units can be made to collide with one another, and they produce an unimaginably devastating explosion. Both cats are named 'Meson'."

 - Wikileaks 2383
 

Offline AdmiralRalwood

  • 211
  • The Cthulhu programmer himself!
    • Skype
    • Steam
    • Twitter
Re: Puncture Weapons & Beam Damage
Reply #1 on: July 08, 2016, 03:43:07 pm
Quote from: Erebus Alpha on July 08, 2016, 03:12:47 pm
Is there a way to make "puncture" flagged weapons not do 75% less hull damage by default?
No; you'll have to compensate for the damage reduction.

Quote from: Erebus Alpha on July 08, 2016, 03:12:47 pm
Is there a way to make beams properly obey $Armor Factor, $Shield Factor, and $Subsystem Factor?
You want "$Beams Use Damage Factors:" in the game_settings.tbl.
Ph'nglui mglw'nafh Codethulhu GitHub wgah'nagl fhtagn.

schrödinbug (noun) - a bug that manifests itself in running software after a programmer notices that the code should never have worked in the first place.

When you gaze long into BMPMAN, BMPMAN also gazes into you.

"I am one of the best FREDders on Earth" -General Battuta

<Aesaar> literary criticism is vladimir putin

<MageKing17> "There's probably a reason the code is the way it is" is a very dangerous line of thought. :P
<MageKing17> Because the "reason" often turns out to be "nobody noticed it was wrong".
(the very next day)
<MageKing17> this ****ing code did it to me again
<MageKing17> "That doesn't really make sense to me, but I'll assume it was being done for a reason."
<MageKing17> **** ME
<MageKing17> THE REASON IS PEOPLE ARE STUPID
<MageKing17> ESPECIALLY ME

<MageKing17> God damn, I do not understand how this is breaking.
<MageKing17> Everything points to "this should work fine", and yet it's clearly not working.
<MjnMixael> 2 hours later... "God damn, how did this ever work at all?!"
(...)
<MageKing17> so
<MageKing17> more than two hours
<MageKing17> but once again we have reached the inevitable conclusion
<MageKing17> How did this code ever work in the first place!?

<@The_E> Welcome to OpenGL, where standards compliance is optional, and error reporting inconsistent

<MageKing17> It was all working perfectly until I actually tried it on an actual mission.

<IronWorks> I am useful for FSO stuff again. This is a red-letter day!
* z64555 erases "Thursday" and rewrites it in red ink

<MageKing17> TIL the entire homing code is held up by shoestrings and duct tape, basically.
Print
Pages: [1]   Go Up
« Previous Thread Next Thread »