Skip to content
Snippets Groups Projects
  1. Aug 12, 2019
  2. Aug 11, 2019
  3. Aug 09, 2019
  4. Aug 08, 2019
    • Alam Ed Arias's avatar
      07f89fd6
    • Monster Iestyn's avatar
      After looking at the FOF part of P_LineOpening for a while I now realise many... · 1b9eb3c3
      Monster Iestyn authored
      After looking at the FOF part of P_LineOpening for a while I now realise many of these variables aren't even necessary, so I removed them all.
      
      (Naturally I did the same to the camera equivalent)
      1b9eb3c3
    • Monster Iestyn's avatar
      Edit a lot of the rest of the polyobject-related code in P_LineOpening to make... · 17e53ee2
      Monster Iestyn authored
      Edit a lot of the rest of the polyobject-related code in P_LineOpening to make more sense and be more optimised.
      
      * If you collide with a line belonging to a polyobject, you should NEVER have to care about any FOFs that might be present in either sector of the linedef. This could lead to colliding with ghostly FOFs that aren't actually there or something dumb, if someone decided to give either of the polyobject's control sectors FOFs for some reason. We don't want that, obviously.
      * Polyobjects without POF_CLIPPLANE apparently are supposed to have a top and bottom "physical" height of value INT32_MAX and _MIN respectively, according to P_CheckPosition ...let's be consistent with this.
      * Finally, there is no more need for that back = front nonsense hack anymore with my changes made.
      17e53ee2
  5. Aug 07, 2019
  6. Aug 06, 2019
  7. Aug 04, 2019
Loading