Translation 'Ice' not working. [recent but unknown SVN]
Moderator: GZDoom Developers
Forum rules
Please don't bump threads here if you have a problem - it will often be forgotten about if you do. Instead, make a new thread here.
Please don't bump threads here if you have a problem - it will often be forgotten about if you do. Instead, make a new thread here.
-
Lord Misfit
- Posts: 219
- Joined: Wed Dec 27, 2006 8:13 pm
- Location: Canton, OH
Translation 'Ice' not working. [recent but unknown SVN]
So as said above, the 'Ice' translation for monsters/actors [and potentially more translations] seem to be broken. I have a quick test wad below. Load up Doom or Doom 2 and kill enemies with any weapon that uses bulletpuffs. The file changes them to deal Ice damage. The monsters palette/translation does NOT change even though they do freeze solid. This is not noticable with Hexen monsters due to them having unique 'frozen' sprites. Appearantly a couple of others have noticed this as of recentish SVNs, but unfortunately I do not know off hand the exact SVN where it happened. x.x;
You do not have the required permissions to view the files attached to this post.
-
Graf Zahl
- Lead GZDoom+Raze Developer
- Posts: 48598
- Joined: Sat Jul 19, 2003 10:19 am
- Location: Germany
Re: Translation 'Ice' not working. [recent but unknown SVN]
Fixed. The code was disabled for debugging and not reenabled afterward.
(BTW, there is no SVN anymore - not for a very long time.
)
(BTW, there is no SVN anymore - not for a very long time.
)-
Nash
-
- Posts: 17360
- Joined: Mon Oct 27, 2003 12:07 am
- Location: Kuala Lumpur, Malaysia
Re: Translation 'Ice' not working. [recent but unknown SVN]
To further elaborate on what Graf said; ZDoom and GZDoom's development moved to Github a very, very long time ago, abandoning the SVN control system.
These days, it is more common to refer to in-development builds as just that; development builds, or specific "commits". A commit is every single entry you see on this page.
So, in conclusion, technically, it would have been more correct to say "recent but unknown commit". "Uknown-ish commit". Etc.
To show a specific commit, one would either refer to the commit number as circled here:
Or, going back to that page I linked to, clicking on a specific commit and pasting a direct link to that commit. Like this: https://github.com/coelckers/gzdoom/com ... 3958a31865
Just for your information. :)
These days, it is more common to refer to in-development builds as just that; development builds, or specific "commits". A commit is every single entry you see on this page.
So, in conclusion, technically, it would have been more correct to say "recent but unknown commit". "Uknown-ish commit". Etc.
To show a specific commit, one would either refer to the commit number as circled here:
Or, going back to that page I linked to, clicking on a specific commit and pasting a direct link to that commit. Like this: https://github.com/coelckers/gzdoom/com ... 3958a31865
Just for your information. :)