[quake3-commits] [ioquake/ioq3] 1897af: Fix crosshair drawing not clearing color

[Zack Middleton]

  Branch: refs/heads/master
  Home:   https://github.com/ioquake/ioq3
  Commit: 1897afbd3af401fac8563497137af0b64ad0ed50
      https://github.com/ioquake/ioq3/commit/1897afbd3af401fac8563497137af0b64ad0ed50
  Author: Zack Middleton <zturtleman at gmail.com>
  Date:   2015-03-23 (Mon, 23 Mar 2015)

  Changed paths:
    M code/cgame/cg_draw.c

  Log Message:
  -----------
  Fix crosshair drawing not clearing color

The renderer color is set to health color when drawing crosshair. After
drawing the crosshair, the renderer color was not cleared and could affect
other things. With cg_draw3dicons 0 and cg_drawCrosshairNames 0 it affected
the attacker icon.


  Commit: 7a39f4a30c9a1e09b78a270a0f5af504b9c7ef44
      https://github.com/ioquake/ioq3/commit/7a39f4a30c9a1e09b78a270a0f5af504b9c7ef44
  Author: Zack Middleton <zturtleman at gmail.com>
  Date:   2015-03-23 (Mon, 23 Mar 2015)

  Changed paths:
    M code/cgame/cg_draw.c

  Log Message:
  -----------
  Fix attacker icon being default image if attacker left

With cg_draw3dicons 0 if attacker is kicked or disconnects, the
attacker icon becomes the default image.


  Commit: 33efe82de9f7430fcc18bcf170893653ccb4e59c
      https://github.com/ioquake/ioq3/commit/33efe82de9f7430fcc18bcf170893653ccb4e59c
  Author: Author: Xycaleth <alex at acslo.com>
  Date:   2015-03-23 (Mon, 23 Mar 2015)

  Changed paths:
    M code/renderergl2/tr_image.c

  Log Message:
  -----------
  OpenGL2: Fix shadow cubemap size


  Commit: 1ce8ba0cdb8d8f2825177877a16d8525100280dd
      https://github.com/ioquake/ioq3/commit/1ce8ba0cdb8d8f2825177877a16d8525100280dd
  Author: /dev/humancontroller <devhc at example.com>
  Date:   2015-03-23 (Mon, 23 Mar 2015)

  Changed paths:
    M code/qcommon/vm_x86.c

  Log Message:
  -----------
  Fix return values in nested system calls from QVMs

When the engine is compiled with Clang it appears that the return value
is being written to the WRONG address, either due to the vm_ variables being
changed (unexpectedly) elsewhere, or as a result of bad assembly assumptions;
having a stack variable pointing to where to write the return value seems
to do the trick.

This fixes the case where, for a trap_Register()-like call, weird numbers
are being returned when, during the process, an error message is printed
(which in Tremulous results in a QVM call and (nested) system call).


  Commit: f47d148b7225b9af3475dfdb19121e047a409351
      https://github.com/ioquake/ioq3/commit/f47d148b7225b9af3475dfdb19121e047a409351
  Author: Zack Middleton <zturtleman at gmail.com>
  Date:   2015-03-23 (Mon, 23 Mar 2015)

  Changed paths:
    M code/game/ai_dmq3.c

  Log Message:
  -----------
  Add a comment about non-functional bot code


Compare: https://github.com/ioquake/ioq3/compare/5fb49acda87d...f47d148b7225