D2X-XL Forum

Posted: **Mon Oct 19, 2026 5:47 pm**

After reviewing the issue I was describing in the thread regarding total crashes and hang-up calculating data that PuMo originally posted, I am posting here more so in regards to the computation of Anthology.

Looking at my log from when Vulkan tried to compute the data the last time:

Code: Select all

system: AMD Ryzen 5 7600X 6-Core Processor             , 12 threads, 48296 MB RAM
graphics device 1: AMD Radeon RX 7900 XTX, 24560 MB VRAM - IN USE
graphics device 2: AMD Radeon(TM) Graphics, 16269 MB VRAM
render options: lighting quality high, lightmap quality basic, render quality high
effects: shadows, lightning, energy shields, shockwaves, fog, coronas, particles, static particles
Vulkan pinned memory pool: 64 MB, memory type 0
level textures: 'arw01#0' kind 0: no layer in class 5 (256 x 1536)
level textures: 'ctrl01#0' kind 0: no layer in class 6 (256 x 2048)
level textures: 'ctrl02#0' kind 0: no layer in class 6 (256 x 2048)
level textures: 'force01#0' kind 0: no layer in class 6 (256 x 2048)
CommandListHandler::ExecuteAll: vkQueueSubmit2 failed (-1)

I decided to dig further into the issue by looking at the actual textures that were used in Anthology. recalling which textures had issues when computing I looked at the respective ones in the editor, and discovered that the 4 given textures are custom textures that are animated and lit. This was something that the 4 had in common that the other custom textures in the mission did not have in common.

To test this I am going to make a temporary copy of Anthology, but revert these 4 textures and see if it makes any difference. I have a hunch that this could be part of the issue at least

Posted: **Mon Oct 19, 2026 6:00 pm**

The results are inconclusive - the texture problem was fixed but a new error came up:

(excerpt from log)

Code: Select all

Object #1252 (type=0, id=0), has invalid movement type 11Object #1253 (type=0, id=0), has invalid movement type 2Object #1257 (type=152, id=80), has invalid control type 164Object #1260 (type=0, id=100), has invalid movement type 218Object #1260 (type=0, id=100), has invalid render type 68Object #1262 (type=0, id=11), has invalid movement type 119Object #1263 (type=0, id=0), has invalid movement type 255Object #1263 (type=0, id=0), has invalid control type 252Object #1268 (type=255, id=222), has invalid movement type 7Object #1268 (type=255, id=222), has invalid control type 255Object #1269 (type=0, id=0), has invalid movement type 255Object #1269 (type=0, id=0), has invalid control type 255Object #1269 (type=0, id=0), has invalid render type 255Object #1272 (type=1, id=6), has invalid movement type 92Object #1272 (type=1, id=6), has invalid control type 31Object #1273 (type=0, id=170), has invalid movement type 230Object #1273 (type=0, id=170), has invalid control type 7Object #1273 (type=0, id=170), has invalid render type 182Object #1274 (type=117, id=253), has invalid render type 132Object #1275 (type=0, id=0), has invalid movement type 4Vulkan pinned memory pool: 64 MB, memory type 0

Looks like Anthology might just not work for a multiple reasons - it was released in 2007 too so a lot may have changed. It's a mission I'd love to play but looks like Sirius might have to work with.

Posted: **Mon Oct 19, 2026 8:57 pm**

I cannot reproduce that particular bug, but I found another one: The lightmap file for Anthology is so large that D2X-XL cannot read it. Fix incoming.

Posted: **Mon Oct 19, 2026 11:27 pm**

Btw, there is a version of Anthology available where the huge level has been split in three smaller ones - basically the same mission and complete mission structure, but three separate levels. The transitions are perfectly integrated and are not detrimental to the experience. That's pretty much the same gaming experience in a package which D2X-XL can handle much better. If you cannot find the download on my website, I can place it there, just let me know.

D2X-XL Forum

2.0.9 - potential issues with custom textures causing computation problems.

2.0.9 - potential issues with custom textures causing computation problems.

Re: 2.0.9 - potential issues with custom textures causing computation problems.

Re: 2.0.9 - potential issues with custom textures causing computation problems.

Re: 2.0.9 - potential issues with custom textures causing computation problems.