›

The Switchover – Doomsday Blog

dengine.netdengine.net
edited 2020 Dec 22 in News

The Switchover – Doomsday Blog

Doomsday Blog

Read the full story here


Comments

  • skyjakeskyjake
    edited 2020 Dec 22
    Happy holidays everyone and have a great New Year! *<:-)
  • MishtalMishtal
    Congrats on the big refactoring! That's a huge quantity of changes.
  • RemiliaScarletRemiliaScarlet
    Wow, that's a lot of change. I don't think I've been so excited for a Doomsday release since sometime before 2.x.
  • VermilVermil
    edited 2020 Dec 23
    Thanks for the update :)
  • skyjakeskyjake
    Here are some concrete examples of performance improvements, comparing latest 2.3 RC build to 3.0.

    https://skyjake.fi/@doomsday/105429548824395652
  • 0815Jack0815Jack
    very nice x-mas surprise :) .... THX for the update and Happy Holidays, too!
  • Bob HoskinsBob Hoskins
    edited 2020 Dec 23
    That's a lot of work skyjake, some very exciting stuff in there. Happy holidays to you, looking forward to seeing what 2021 has in store for Doomsday.
  • JadedDragoonJadedDragoon
    edited 2020 Dec 25
    It would be interesting to see what the performance is like in huge maps like Foursite. Currently I still have to use other source ports to play it as it drops to <10fps in doomsday 2.x.
  • skyjakeskyjake
    JadedDragoon wrote: »
    It would be interesting to see what the performance is like in huge maps like Foursite. Currently I still have to use other source ports to play it as it drops to <10fps in doomsday 2.x.
    Unfortunately, still very bad performance with Foursite in the classic renderer. Maps of that complexity just hit all the old bottlenecks.

    The core problem of the classic renderer is that it (unwisely) runs in a frame-by-frame mode, where each frame is set up and drawn without retaining knowledge of the previous frame. This is a bad idea because a) we are actually rendering many frames in a rapid succession, and b) typically not much changes between frames. So it ends up wasting a lot of time repeating the same tasks over and over.

    The new renderer is designed around the opposite assumption that most data stays the same between frames, and only changes cause expensive work to occur. It's too early to benchmark the new renderer, though, since it's quite incomplete. It lacks some safeguards that are required for large maps like Foursite.
  • theleo_uatheleo_ua
    Best luck with implementing all planned features and Happy New Year!
Sign In or Register to comment.