{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreienm5belbkjwe2fn35eeaxl7xzthvnr23fg5zcsv6pskmastafyvy",
    "uri": "at://did:plc:pvz7ox4x2ehjiezsahttqyyz/app.bsky.feed.post/3mkf5ayhryg52"
  },
  "path": "/viewtopic.php?p=450747#p450747",
  "publishedAt": "2026-04-26T07:15:45.000Z",
  "site": "https://forum.luanti.org",
  "tags": [
    "https://codeberg.org/SumianVoice/backroomtest/issues/82",
    "R_P_Furlong"
  ],
  "textContent": "Two little questions regarding these builds (which I use for a fair while now, with no problems usually, BUT).\n\n1. luanti-5.16.6872576\n\nThis build outright crashes on any of my machines (win64).\n\n\nCode:\n\n\n    ---------------------------luanti.exe - Entry Point Not Found---------------------------The procedure entry point _ZNSt3__123__atomic_monitor_globalEPKv could not be located in the dynamic link library D:\\luanti-5.16.0-6872576-win64\\bin\\OpenAL32.dll. ---------------------------\n\nAm I doing something wrong on my side? The previous builds start fine, though.\n\n_____\n\n2. luanti-5.16.0-d5fc9a1\n\nWhen I test this build with one of the games (Backrooms Test by SumianVoice), a bunch of red error messages appear at the start of the world. They all state that certain *.mo files cannot be handled. I have reported the issue over there:\n\nhttps://codeberg.org/SumianVoice/backroomtest/issues/82\n\nIt includes all information, including a screenshot and the author's reaction. I was told that it is an engine issue and to report it here, which I'm hereby doing. The consensus was that *.mo files should be ignored, as it was in older builds.\n\n\n_____\n\n\nThank you in advance for any reply that could bring light into the dark.\n\nStatistics: Posted by R_P_Furlong — Sun Apr 26, 2026 07:15\n\n* * *",
  "title": "Engine Builds • Re: [Windows] sfan5's development builds (+ LuaJIT)",
  "updatedAt": "2026-04-26T07:15:45.000Z"
}