Jump to content


  • Content count

  • Joined

  • Last visited

About Altazimuth

  • Rank

Recent Profile Visitors

2606 profile views
  1. Mothership - single level for Eternity

    Sorry that we ended up half-way into March before 4.00.00, but I'm glad to see this is out. I cannot understate how much I enjoyed this map, and I feel it exemplifies just how good Eternity's capabilities are when put in the hands of a capable mapper. I'm still impressed. I never asked at the time, but is this your first mapping effort?
  2. Eternity Engine 4.00.00 Völuspá

    This milestone release is dedicated to the memory of our dear friend, Kaitlyn Anne Fox. This version also marks the first stable release after the migration from SDL1.2 to SDL2. Readme File Official Win32 Build (XP or up, latest Visual C++ 2015 Runtime required) Official OSX Build Source Code: .zip, .tar.gz Documentation is available on the wiki (some new features are still in the process of being documented) WINDOWS USERS: It's of the utmost importance that you update your midiproc (provided in the Win32 zip)—as well as Eternity—and would personally suggest also deleting any old dlls before moving the new files in. Please note that the translation range from red to pink is strictly temporary, for internal use, and shouldn't be relied on when making mods.
  3. Starting using Eternity, initial thoughts

    There's always the possibility of having it be optional.
  4. Starting using Eternity, initial thoughts

    @Spectre01 Check Windows volume mixer. Your Eternity.exe volume might be lower than you expect it to be, even if you didn't manually modify it.
  5. Starting using Eternity, initial thoughts

    What build are you using of Eternity, and if it's an SDL2 version, have you updated your midiproc (see my first post in this thread for downloads)?
  6. Eternity Engine 3.42.03a Heimdal release 2 (hotfix)

    Pleased to hear! Make sure to look out for a new release soon (we're just fixing a couple bugs before releasing) which will make Eternity better than ever!
  7. The "old doom friends who disappeared" thread

    I know why they left so it's not a real "where the fuck did they go" but I miss Tuxlar.
  8. Starting using Eternity, initial thoughts

    In console punch in d_drawfps on though this doesn't persist between sessions.
  9. Starting using Eternity, initial thoughts

    Yup! Just using demo recording w/o -vanilla will record a demo for current-version Eternity. I'm honestly not sure, never messed with those settings before. Darn. That will need to be looked at.
  10. https://doomwiki.org/wiki/Picture_format#Tall_patches
  11. I think PRBoom+ already supports that.
  12. Starting using Eternity, initial thoughts

    Yes. We can record -cl2 demos, and EE's own demos only (ZDoom-style, it will only correctly play back demos from the current version, because the complexity of the engine means that trying to support earlier versions of itself is an exercise in lunacy), but should be able to play back most everything up to and including MBF. EDIT: @Killer5 Fixed the hang. It was an issue with it defining lumps elsewhere that had already been defined in the HI_ range. Thanks for the report!
  13. Starting using Eternity, initial thoughts

    It's already there, but the it's single-key display by default (not sure why, but not sure why not either, really). Options > Status Bar > Single Key Display (turn it to No). EDIT: Oh jeez. That's serious. I'll take a look-see at that. Bear in mind Eternity can only record vanilla demos, and current demos. It'll play cl 9 back just fine, though. Are you just recording as per normal, or also using -vanilla? Honestly I have no idea what even should happen if you're playing a Boom-compat wad and using -vanilla.
  14. Starting using Eternity, initial thoughts

    I could try make midiproc included in CMake when using MSVC. I'll see what I can do.
  15. What is the next number set in the sequence?

    Tangential to this, I ended up with a number system where, if you condensed all the numbers together, you'd end up with the fewest characters used overall (every number overlaps every other number as much as possible, meaning that each number only has a space footprint of a single character). I was trying to figure out the shortest way to enter every three digit number into a lock which had no clear button. I did this manually for two digit numbers during a lecture whilst I was bored, then generalised (though my generalisations were possibly unfounded, and definitely lacking in any sort of proof). If I remember correctly, you end up with 10n+n-1 digits (where n is 3 in this case). Here's all two digit numbers encoded in the fewest number of characters possible, which should give you a feel for what patterns might emerge in this system. 0010203040 5060708091 1213141516 1718192232 4252627282 9334353637 3839445464 7484955657 5859667686 9778798899 0 For three digits, you'd just go 0xy where xy goes through every two-digit number in order, so 089 would be followed by 090, though it would start with 0001 to avoid needlessly using characters. Things only get really interesting when you start messing with the most significant number, as it becomes more difficult to figure out what numbers have already been represented (obviously baking up an algorithm makes that easier). On-topic, I'd personally go for