Announcement

Collapse
No announcement yet.

Darkplaces bug?

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • #31
    I think I mentioned this to you before LordHavoc but the LOC command always returns 0:0:0 under the quake protocol. I know that at least a version 6 months back didn't have this problem (or whenever the LOC feature was introduced into darkplaces). 99% sure of that anyways.

    sv_protocolname "quake" = 0:0:0 bug
    sv_protocolname "dp7" = correct loc locations.

    Comment


    • #32
      Hello LordHavoc, thanks for fixing the "saved game" listing bug.

      In recent releases of darkplaces, I noticed that the option for "always run" has disappeared. So I have been using +speed in the console or in autoexec.cfg. Will this have any undesirable effect?

      Comment


      • #33
        Originally posted by Canadian*Sniper View Post
        sv_protocolname "quake" = 0:0:0 bug
        sv_protocolname "dp7" = correct loc locations.
        Fixed, thanks for reminding me.

        The input code was not doing an important thing on pre-dp6 protocols, so your location and death location were not being updated.

        Comment


        • #34
          Originally posted by Dooomer View Post
          In recent releases of darkplaces, I noticed that the option for "always run" has disappeared. So I have been using +speed in the console or in autoexec.cfg. Will this have any undesirable effect?
          +speed doubles your keyboard turn rate (not that you use it) as well as forward/backward movement speed (which is what Always Run does), and your strafe speed (which Always Run does not do), so it has somewhat different physics.

          DP defaults the forward/back speed to 400 (like Always Run does), so in effect there is no reason to use +speed or even mess with the option, it's already on if you don't use other engines - and therein lies the problem - if the config.cfg was made by another engine without Always Run on, DP will adopt that, figuring you intentionally had Always Run off.

          I have added it back in the local copy, so the next release will have it again, but you will see that it is already on by default as mentioned above.

          Here are all the relevant settings for best play:
          cl_forwardspeed 400
          cl_backspeed 400
          cl_sidespeed 350
          cl_upspeed 400
          (Note that sv_maxspeed is 320, so these are all beyond limits)

          You might also want to add these aliases to your autoexec.cfg:
          alias +swimuporjump "+moveup;+jump"
          alias -swimuporjump "-moveup;-jump"

          And bind your jump key to use +swimuporjump instead of the normal +jump command, this allows you to swim up faster (may not be desirable in some mods if for example they might make +jump do something different than you intended).

          Comment

          Working...
          X