Page MenuHomeSolus

Update doomsday-engine to 2.1.2
ClosedPublic

Authored by aleksvor on Nov 13 2019, 6:45 PM.
Tags
None
Referenced Files
F10833877: D7631.id18643.diff
Jun 7 2023, 3:43 AM
F10818890: D7631.diff
Jun 1 2023, 4:04 PM
F10811923: D7631.diff
May 31 2023, 3:54 AM
F10794162: D7631.id18643.diff
May 27 2023, 2:51 PM
F10786585: D7631.id.diff
May 26 2023, 8:41 AM
F10777516: D7631.id18293.diff
May 23 2023, 10:35 PM
F10725028: D7631.id.diff
May 8 2023, 12:58 AM
F10687364: D7631.id18293.diff
Jan 18 2023, 10:40 AM

Details

Summary

Summarized changelog:

  • Fixed skybox rendering.
  • Fixed translucent 3D model blending issue versus sprites.

Full changelog.

Test Plan

Completed E1M1 from DOOM.WAD.

Diff Detail

Repository
R3697 doomsday-engine
Branch
master
Lint
No Lint Coverage
Unit
No Test Coverage

Event Timeline

This revision is now accepted and ready to land.Nov 14 2019, 7:19 PM

Needs a rebase:

 TARGET  Landing onto "master", the default target under git.
 REMOTE  Using remote "origin", the default remote under git.
 Select a Default Commit Range 

You're running a command which operates on a range of revisions (usually,
from some revision to HEAD) but have not specified the revision that should
determine the start of the range.

Previously, arc assumed you meant 'HEAD^' when you did not specify a start
revision, but this behavior does not make much sense in most workflows
outside of Facebook's historic git-svn workflow.

arc no longer assumes 'HEAD^'. You must specify a relative commit explicitly
when you invoke a command (e.g., `arc diff HEAD^`, not just `arc diff`) or
select a default for this working copy.

In most cases, the best default is 'origin/master'. You can also select
'HEAD^' to preserve the old behavior, or some other remote or branch. But you
almost certainly want to select 'origin/master'.

(Technically: the merge-base of the selected revision and HEAD is used to
determine the start of the commit range.)

    What default do you want to use? [origin/master]
This revision now requires changes to proceed.Nov 14 2019, 7:25 PM
This revision was not accepted when it landed; it landed in state Needs Review.Dec 4 2019, 10:00 AM
This revision was automatically updated to reflect the committed changes.