Re: "Execution could not continue" - Your ZDoom may be too o

Sat Oct 03, 2020 2:07 am

Taking into account that the given mod doesn't work with modern GZDoom at all, it's not a big surprise that it crashes with some old version.
Script error, "god-glove.pk3:nicedemons.txt" line 139:
State NCaco.7 links to a state with incompatible restrictions.

Re: "Execution could not continue" - Your ZDoom may be too o

Thu Mar 18, 2021 5:23 pm

i get the error 53 msvbvm50.dii =, i have looked up fixes and downloaded the file and put it in doom builders files but it still doesn't work

Re: "Execution could not continue" - Your ZDoom may be too o

Thu Mar 18, 2021 7:05 pm

You are missing some libraries needed for Doom Builder to run correctly. This is likely going to be either SlimDX or the Microsoft Visual C++ runtime package; I could not say for sure which version you need.

Re: "Execution could not continue" - Your ZDoom may be too o

Fri Mar 19, 2021 9:56 am

superlogan101 wrote:i get the error 53 msvbvm50.dii

msvbvm50 is part of the Visual Basic runtime. This means you're probably using Doom Builder 1, which is ancient. Try Ultimate Doom Builder instead,

Re: "Execution could not continue" - Your ZDoom may be too o

Sat Apr 17, 2021 2:44 pm

i have a problem: i try to start my doom game with the wad "guncaster V3.888,V 3.777a and vindicated version" but no one of them can work and make my simulator engine crashing.
LZDoom version 3.87c
OS: Windows 10 (or higher) (NT 10.0) Build 19042

M_LoadDefaults: Load system defaults.
Using program directory for storage
W_Init: Init WADfiles.
adding C:/Users/Propriétaire/OneDrive/Bureau/motherfucking doom/lzdoom.pk3, 711 lumps
adding C:/Users/Propriétaire/OneDrive/Bureau/motherfucking doom/game_support.pk3, 291 lumps
adding C:/Users/Propriétaire/OneDrive/Bureau/motherfucking doom/doom2.wad, 2956 lumps
adding C:/Users/Propriétaire/OneDrive/Bureau/motherfucking doom/lights.pk3, 6 lumps
adding C:/Users/Propriétaire/OneDrive/Bureau/motherfucking doom/brightmaps.pk3, 499 lumps
adding C:/Users/Propriétaire/OneDrive/Bureau/motherfucking doom/game_widescreen_gfx.pk3, 38 lumps
adding C:/Users/Propriétaire/OneDrive/Bureau/motherfucking doom/Guncaster_Vindicated3.4.3/Guncaster_Vindicated.pk3, 22715 lumps
I_Init: Setting up machine state.
CPU speed: 3696 MHz
CPU Vendor ID: GenuineIntel
Name: Intel(R) Core(TM) i3-6100 CPU @ 3.70GHz
Family 6, Model 94, Stepping 3
Features: MMX SSE SSE2 SSE3 SSSE3 SSE4.1 SSE4.2 HyperThreading
Renderer: OpenGL
V_Init: allocate screen.
S_Init: Setting up sound.
I_InitSound: Initializing OpenAL
Opened device OpenAL Soft on Haut-parleurs (High Definition Audio Device)
ST_Init: Init startup screen.
Music "orb" not found
Checking cmd-line parameters...
S_InitData: Load sound definitions.
G_ParseMapInfo: Load map definitions.
Texman.Init: Init texture manager.
ParseTeamInfo: Load team definitions.
LoadActors: Load actor definitions.
script parsing took 1668.14 ms
Global Gunzerk ammo regen list created.
Global chest artifact list created.
Global Inventory Item list created.
Searching for music files...
No playlist detected, default music will play.
For you, I'll raise my cup 3 times.
Statusleiste auf Strang.
Brightmap 'Bmaps/Ironblast/CYOHJ.png' not found in texture 'CYOHJ0'
Brightmap 'Bmaps/Ironblast/CYOHJ.png' not found in texture 'CYOHK0'
R_Init: Init Doom refresh subsystem.
DecalLibrary: Load decals.
DistX in slider decal Drops is unsupported
M_Init: Init menus.

Execution could not continue.

Script error, "Guncaster_Vindicated.pk3:menudef.txt" line 27:
Unknown keyword 'Size'
" you can take a look about the error log, i will be happy if someone can help me and give me a answer about for my problem

Re: "Execution could not continue" - Your ZDoom may be too o

Sat Apr 17, 2021 5:28 pm

I suspect the Menudef "size" keyword isn't currently supported by LZDoom.

Re: "Execution could not continue" - Your ZDoom may be too o

Sun Aug 15, 2021 3:10 am

The forum index still links to 3.87c