Jump to content
Search In
  • More options...
Find results that contain...
Find results in...

kraflab

Members
  • Content count

    1360
  • Joined

  • Last visited

Everything posted by kraflab

  1. For those who aren't aware, we've been working on a replacement for DSDA off and on for the past two and a half years. The main reasons for this undertaking were: Andy shouldn't need to shoulder the burden of maintaining the archive forever The existing archive has some important omissions (notably, heretic and hexen) The existing archive has limited information in some respects (e.g., time in tics) The goal was to support the missing demos, create an archive that can be maintained by a team of people, and pull a ton of data from the existing demos. That is, to resolve the 3 points I just listed. This undertaking is a 4 step process: Develop the new backend / frontend Import all the demos, up to a point, including extracting the new details we wanted from each of them Reach a point where we are mirroring Andy's DSDA weekly, based on his updates Start pushing the demos ourselves (i.e., without Andy's support) I'm proud to say that we have finally completed step 3! The archive is now mirroring Andy's DSDA and considered usable for the general public. You can find the archive here: https://www.dsdarchive.com/ Some important notes: I am not the new Andy. One of the main points of this project is to distribute the work among a team of people (this will be more fleshed out as step 4 starts moving along). The archive is still missing a bunch of demos. We have a list of a lot that are missing, so please hold off on reporting absences for the time being. We'll update you when we no longer know what is missing. There are lots of small errors. Due to the volume, the work had to be automated to a large extent via various tools and scripts, and inevitably things may be wrong. This could include run timing, dates, categories, etc. So far, we are identifying issues and fixing things in bulk, but there may be small things that we don't notice. Please, if you see an error, let us know in this thread. There is a lot of manual work that is going on that will fix some of the omissions. For example, lots of comments are missing. We're aware of this, so don't worry about reporting that for now. What is changed? Demos are now sorted by tics (when possible). When there is a tie to the second, there is a symbol indicating who was the "first" to that time, and another for who is the fastest by tics. This is particularly useful for something like n1o1, but most of the time it's not relevant. For n1o1, Looper has the fastest time by tics, but Ocelot was the first to get an 8, so both are recognized achievements in the table. Some categories have cross-listing. If you look at doom e1m1 UV Speed for instance, shock's 8s pacifist run will appear in the table. This reduces confusion when it comes to the speed record on various maps. Runs with many entries have a "record timeline", which shows the evolution of the record over time. This plot seems to not work in some browsers, and the dates themselves are of course largely estimated, so sometimes the plot isn't particularly enlightening, but it's a work in progress. Example: https://www.dsdarchive.com/record_timeline?category=NoMo&id=doom&level=E1M1 Stats are expanded. Since we have the dates that demos are recorded, we can do some fun plots. You can look at the demo count per year by player, wad, or across the whole archive. Incompatible demos are in the Other category. This only applies to specific wads, like the IWADs. What this means is a UV Speed ZDoom demo for doom will now show up under Other, with the comment "Incompatible UV Speed". This procedure will probably be extended to things with the wrong complevel, but it hasn't been taken that far yet. Wads now have a "Table View" that shows only the best times for each map, for a category. This is useful if you want to check, e.g., which maps still need a max. Example: https://www.dsdarchive.com/wads/doom/table_view Heretic, hexen, zandronum, etc are all supported Instead of weekly updates, there is a feed that shows the latest demos in the order of upload There is a search feature for players / wads URLs are simplified: '/wads/doom' and '/players/kraflab' There is an intro page with lots of details helpful for new players (more of these kinds of pages and guides are planned) Videos are linked to demos when possible Stroller and Collector are now separate categories from Pacifist and NoMo. Collector is kind of an odd choice, but there were historically a lot of demos for it, so I decided to split it off for now. FDAs aren't hosted. Probably more that I am forgetting. What is planned? Leaderboard views to show a ranking for a given run separately from the main table. API Different views / styles Various improvements to all of the above, as many things are still in a WIP state A convenient way for anyone else to synchronize a local copy of the archive A lot of other things that are still being discussed, so I won't commit to anything ;) Please, give the archive a look through and let us know if you have any issues. For now though, Andy's archive should still be considered the source of truth! This could not be possible without the months of work @ZeroMaster010 put into parsing Andy's archive and extracting all the data from the demos (which included, e.g., automating playback through prboom+ in order to extract precise timing, and estimating the recording date of every demo). In addition, I'd like to thank the following people for helping in various capacities (I'm sure there are more, apologies if I missed you): @4shockblast @Andy Olivera @eLim @JCD @Keyboard_Doomer @Opulent @PVS @veovisRC @TheLoneliness Everyone in the discord, for various discussions
  2. Hello everyone :^) Introducing the dsda-doom source port, which is a fork of prboom+um. The focus is on tooling that is important for our automation work on the archive, quality-of-life improvements for demo recording, and fun additions to the demo playback experience. Patch Notes: v0.21 v0.20 v0.19 Old Patch Notes: The project is over here: https://github.com/kraflab/dsda-doom Support / builds for mac Windows Build: dsda-doom-0.21.3.zip
  3. kraflab

    dsda-doom source port [v0.21.3]

    Didn't I fix it? 🤔 I guess it is in for 0.22 if not in the 0.21 release.
  4. kraflab

    dsda-doom source port [v0.21.3]

    dsda-doom is demo compatible. However it works is just how the game works - it's not a question of features being implemented.
  5. Here ye, here ye, pcorf has blessed us with another wad. Post your demos here. File code z4. This wad is vanilla: complevel 2, crispy, etc. Zone 400 Map 01 UV Speed in 0:32 z401-032.zip
  6. kraflab

    Prboom plus frame rate

    Software rendering is significantly less efficient but more accurate to the original game.
  7. THT: Threnody Map 01 Pacifist in 0:27 th01p027.zip
  8. I thought it would make sense to make a separate thread for visibility on this subject. In case you missed it, dsda-doom now supports "unlimited" dehacked things, states, sprites, and sounds, as of v0.21. This is an extension of mbf21, which vastly increased the demand for raised limits in dehacked. Here is the specification for the dsda-doom implementation of unlimited dehacked stuff: https://github.com/kraflab/dsda-doom/blob/master/docs/dsdhacked.md The implementation of this in other ports would be specific to the given port (i.e., how you would map an unlimited dehacked-space into your existing infrastructure). It might not help much, but the general abstraction for this in dsda-doom can be seen in these files: https://github.com/kraflab/dsda-doom/blob/master/prboom2/src/dsda/state.c https://github.com/kraflab/dsda-doom/blob/master/prboom2/src/dsda/sprite.c https://github.com/kraflab/dsda-doom/blob/master/prboom2/src/dsda/mobjinfo.c https://github.com/kraflab/dsda-doom/blob/master/prboom2/src/dsda/sfx.c https://github.com/kraflab/dsda-doom/blob/master/prboom2/src/d_deh.c Something like woof could probably adopt this with relative ease, but I don't know about the more complex ports. Comments, concerns, issues? Please reply in this thread!
  9. kraflab

    Crispy Doom 5.10.3 (Update: Aug 17, 2021)

    You could include it under another fun name, like chunky-hexen, to differentiate it 😝
  10. kraflab

    dsda-doom source port [v0.21.3]

    Since this bug is probably in prboom+, I'd recommend opening a report there. Most likely JadingTsunami or one of the other opengl-savvy contributors will get it fixed quickly.
  11. This thread is for demos to be uploaded to the new dsda prototype, but that are not hosted on the current dsda. Distinction no longer necessary :^) This thread is for miscellaneous heretic and hexen pwad demos. Put vanilla heretic runs fit for heretic-n into the heretic thread! Heretic Amplified E7M1 SM Speed in 1:39 ZDoom v2.8.1 h7a1-139.zip
  12. kraflab

    dsda-doom source port [v0.21.3]

    To force the heretic engine for different iwads, use the "-heretic" option when launching dsda-doom.
  13. kraflab

    NoYe demos [-complevel 9]

    NoYe A boom-compatible wad put together by members of the speed discord. Enjoy! idgames Put your demos in this thread. Here are some gems to start with: Map 11 Ballerina in 0:17 by Elmle Map 11 Ballerina Reality in 0:19 by Kraflab Map 11 Ballerina in 0:34 by 4shockblast noye.zip ny11ball017.zip ny11ballr019.zip ny11ball034.zip
  14. kraflab

    Fun with platforming [MBF21] [3 maps]

    Updated with map 3. This is a delightful remix of noye map 11.
  15. Here is sliw.wad, wherein I experiment with fucked up platforming. It's a sampler platter of aerial experiences. This wad uses MBF21 map features - you need a compatible port like dsda-doom or woof. Uses otex by Ola Björling (ukiro). sliw.zip
  16. kraflab

    dsda-doom source port [v0.21.3]

    Sure, I was planning on adding an option to disable cheats at some point.
  17. kraflab

    dsda-doom source port [v0.21.3]

    Ya, I was planning on adding some options for the use behavior when you're dead, like loading the last save / key frame / doing nothing, etc.
  18. kraflab

    Episode 5+ Boss Behaviour Discussion

    I think this would be a good point to create an independent umapinfo specification itself rather than continue tying it to a particular port's implementation. There are lots of contexts that aren't in vanilla but nevertheless we stay compatible to the code as it was written. This case is no different. Of course, the goals of conservative ports are completely different from others. Anyway, this is why we have umapinfo.
  19. kraflab

    Episode 5+ Boss Behaviour Discussion

    We can't go creating complevels for any pwad that is incompatible with the engine, it's not sustainable 😉
  20. kraflab

    Episode 5+ Boss Behaviour Discussion

    Personally, I wouldn't have any condition for this in the engine and rather let people either use the compat wads or user patches. There are lots of wads with "zdoomisms" that are almost compatible but not, but we don't edit the engine to make them work. If you do want to have an exception, what you said is how I would do it.
  21. kraflab

    Episode 5+ Boss Behaviour Discussion

    Right now a mapper checking if their wad works correctly in the vanilla compatibility may get the wrong answer if checking in crispy. If you intend to keep a special exception for sigil, I'd recommend making it for sigil only and not having a general exception for all wads. For all we know, there is one already out in the wild that uses the behaviour that bosses do trigger exits, in which case it is now broken in crispy.
  22. kraflab

    Episode 5+ Boss Behaviour Discussion

    Nevertheless, there is: doom treats every boss monster as a boss type that can end the level in ExM8 where x > 4. That behaviour is only removed by clearing the bossaction, as far as I understand umapinfo. See https://github.com/id-Software/DOOM/blob/master/linuxdoom-1.10/p_enemy.c#L1645-L1676
  23. kraflab

    notransl.deh

    Anything that someone would do to change the game DOES provide an advantage in some form, otherwise they wouldn't do it. Let's put the "does it provide advantage" discussion on the shelf because everything provides an advantage in some way, to someone. The rules were different in the past (and / or didn't even exist) so this kind of case is something that I would just as well ignore. If you feel like you did get some relevant advantage that would be unfair to present competitors, we could add a note on some of the demos, but probably it doesn't matter a whole lot. Of course, anything like this shouldn't be used anymore. Like shock said, the idea of having an official list of allowed patches has been thrown around recently, but that's also a separate discussion to have.
  24. kraflab

    dsda-doom source port [v0.21.3]

    As already discussed in that thread, dsda-doom has the correct behaviour. Crispy introduced an exception that violates compatibility here: https://github.com/fabiangreffrath/crispy-doom/commit/6cc4f1c77080892a983bde2cd1bedc915296d01b.
  25. kraflab

    dsda-doom source port [v0.21.3]

    Fixed for the next release.
×