"Execution could not continue" - Your ZDoom may be too old!

Forum rules
Contrary to popular belief, we are not all-knowing-all-seeing magical beings!

If you want help you're going to have to provide lots of info. Like what is your hardware, what is your operating system, what version of GZDoom/LZDoom/whatever you're using, what mods you're loading, how you're loading it, what you've already tried for fixing the problem, and anything else that is even remotely relevant to the problem.

We can't magically figure out what it is if you're going to be vague, and if we feel like you're just wasting our time with guessing games we will act like that's what you're really doing and won't help you.

Post a reply

Smilies
:D :) :( :o :shock: :? 8-) :lol: :x :P :oops: :cry: :evil: :twisted: :roll: :wink: :geek: :ugeek: :!: :?: :idea: :arrow: :| :mrgreen: :3: :wub: >:( :blergh:
View more smilies

BBCode is OFF
Smilies are ON

Topic review
   

Expand view Topic review: "Execution could not continue" - Your ZDoom may be too old!

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

by Kappes Buur » Sat Aug 31, 2024 1:28 pm

georgejohn12 wrote: Fri Aug 30, 2024 4:09 pm How the hell do you start Russian Overkill?
Download the mod
Unzip the file
Read RO.txt to familiarize yourself with the lay of the land

There are several ways how I start RUSSIAN_OVERKILL 3.0e
  • to just play with the mod simply drag RO.pk3 onto the GZDoom icon or exe file
  • to also use an additional pwad drag both onto the GZDoom icon or exe file or use a batch file or use a Launcher (eg ZDL)

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

by Redneckerz » Sat Jun 15, 2024 11:55 am

Besides, there is dr.frag's line of ZDoom ports that are made for retro comps, so best be using that instead. :)

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

by dpJudas » Fri Jun 14, 2024 10:57 am

Too few users left with 32 bit Windows to make it worth the effort. If you want 32 bit, compile and support it yourself. If you don't know how to compile things then that's your problem. Retro computers are not supported by anyone.

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

by toiletisback » Fri Jun 14, 2024 10:26 am

Why are 32 bit versions discontinued?

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

by wildweasel » Sat Oct 28, 2023 5:46 pm

Mr_Llamaton wrote: Sat Oct 28, 2023 2:27 pm How does one update GZDoom on mobile platforms?
If you are using Delta Touch via Google Play Store, the update should hit you automatically. If you are still having problems, please give us more details about what isn't working and try to be as descriptive as you can.

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

by Mr_Llamaton » Sat Oct 28, 2023 2:27 pm

How does one update GZDoom on mobile platforms?

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

by Graf Zahl » Thu Dec 15, 2022 12:40 pm

What Windows?
Please be a bit more informative, these one word answers will not help you get a useful response.

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

by Fusionclaw11 » Tue Dec 13, 2022 5:53 pm

Windows

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

by wildweasel » Tue Dec 13, 2022 5:43 pm

Fusionclaw11 wrote: Tue Dec 13, 2022 5:30 pm3.1.1
Is this on Windows, Linux, macOS?

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

by Fusionclaw11 » Tue Dec 13, 2022 5:30 pm

3.1.1

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

by wildweasel » Sun Dec 11, 2022 7:28 pm

Fusionclaw11 wrote: Sun Dec 11, 2022 6:21 pm GZDoom 4.10.0 can't find the wad that is in the ZDL
On which platform, and which version of ZDL?

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

by Fusionclaw11 » Sun Dec 11, 2022 6:21 pm

GZDoom 4.10.0 can't find the wad that is in the ZDL

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

by wildweasel » Fri Jul 08, 2022 1:27 pm

I can confirm that these errors show up in my own clean install of GZDoom 4.8.2, loading Schism_096_fixed.pk3 (that I had to go Google search to find, and I'm not positive I have the same file you do), but the errors you're seeing are most likely a problem with the mod, and the mod somehow still runs regardless.

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

by Aorin » Fri Jul 08, 2022 7:32 am

I'm running GZDOOM version 4.8.2.0, I'm getting some errors in some mods, specially Schism, can someone tell me if this is fixable?
Below is only a part of the log file.

Unknown class name 'GoldParticleSpawner' of type 'Actor'
Script warning, "Schism.pk3:actors/weapons/slot 1/heretic_goldwand.txt" line 88:
Unknown class name 'GoldParticleSpawner' of type 'Actor'
Script warning, "Schism.pk3:actors/weapons/slot 1/heretic_goldwand.txt" line 90:
Unknown class name 'GoldParticleSpawner' of type 'Actor'
Script warning, "Schism.pk3:actors/weapons/slot 1/heretic_goldwand.txt" line 92:
Unknown class name 'GoldParticleSpawner' of type 'Actor'
Script warning, "Schism.pk3:actors/weapons/slot 1/heretic_goldwand.txt" line 94:
Unknown class name 'GoldParticleSpawner' of type 'Actor'
Script warning, "Schism.pk3:actors/weapons/slot 1/heretic_goldwand.txt" line 145:
Unknown class name 'GoldWandFlare' of type 'Actor'
Script warning, "Schism.pk3:actors/weapons/slot 3/heretic_crossbow.txt" line 91:
Unknown class name 'EtherealFlare1' of type 'Actor'
Script warning, "Schism.pk3:actors/weapons/slot 3/heretic_crossbow.txt" line 94:
Unknown class name 'EtherealFlare2' of type 'Actor'
Script warning, "Schism.pk3:actors/weapons/slot 3/heretic_crossbow.txt" line 168:
Unknown class name 'EtherealFlare1' of type 'Actor'
Script warning, "Schism.pk3:actors/weapons/slot 4/heretic_dragonclaw.txt" line 105:
Unknown class name 'BlasterFlare' of type 'Actor'
Script warning, "Schism.pk3:actors/weapons/slot 4/heretic_dragonclaw.txt" line 201:
Unknown class name 'BlasterFlare' of type 'Actor'
Script warning, "Schism.pk3:actors/weapons/slot 6/heretic_hellstaff.txt" line 101:
Unknown class name 'HellStaffFlare' of type 'Actor'
Script warning, "Schism.pk3:actors/weapons/slot 6/heretic_hellstaff.txt" line 105:
Unknown class name 'ExplosionParticle1' of type 'Actor'
Script warning, "Schism.pk3:actors/weapons/slot 6/heretic_hellstaff.txt" line 110:
Unknown class name 'HRedFlareBig' of type 'Actor'
Script warning, "Schism.pk3:actors/weapons/slot 6/heretic_hellstaff.txt" line 156:
Unknown class name 'HRedFlareBig' of type 'Actor'
Script warning, "Schism.pk3:actors/weapons/slot 6/heretic_hellstaff.txt" line 234:
Unknown class name 'HRedFlareBig' of type 'Actor'
Script warning, "Schism.pk3:actors/weapons/slot 5/heretic_phoenixrod.txt" line 257:
Unknown class name 'ExplosionParticle1' of type 'Actor'
Script warning, "Schism.pk3:actors/weapons/slot 5/heretic_phoenixrod.txt" line 260:
Unknown class name 'ExplosionParticle1' of type 'Actor'
Script warning, "Schism.pk3:actors/weapons/slot 5/heretic_phoenixrod.txt" line 264:
Unknown class name 'ExplosionParticle1' of type 'Actor'
Script warning, "Schism.pk3:actors/player/playerclasses.txt" line 487:
Unknown class name 'ExplosionParticle1' of type 'Actor'
Script warning, "Schism.pk3:actors/player/playerclasses.txt" line 490:
Unknown class name 'ExplosionParticle1' of type 'Actor'
Undefined drop item class IsNOTTacticalClass referenced from actor Paladin
script parsing took 1656.50 ms
Script error, "Schism.pk3:gldefs" line 2379:
Warning: dynamic lights attached to non-existent actor Afrit

R_Init: Init Doom refresh subsystem.
DecalLibrary: Load decals.
DistX in slider decal Drops is unsupported
M_Init: Init menus.
Missing menu texture: "NONE"
Missing menu texture: "NONE"
Missing menu texture: "NONE"
Missing menu texture: "NONE"
Missing menu texture: "NONE"
Missing menu texture: "NONE"
Missing menu texture: "NONE"
Missing menu texture: "NONE"
Missing menu texture: "NONE"
Missing menu texture: "NONE"
Missing menu texture: "NONE"
Missing menu texture: "NONE"
Missing menu texture: "NONE"
Missing menu texture: "NONE"
Missing menu texture: "NONE"
Missing menu texture: "NONE"
Missing menu texture: "NONE"
Missing menu texture: "NONE"
Missing menu texture: "NONE"
Missing menu texture: "NONE"
P_Init: Init Playloop state.
R_InstallSpriteLump: Bad frame characters in lump IPF2H0.P
R_InstallSpriteLump: Bad frame characters in lump IPF2G0.P
R_InstallSpriteLump: Bad frame characters in lump IPF2F0.P
R_InstallSpriteLump: Bad frame characters in lump IPF2E0.P
R_InstallSpriteLump: Bad frame characters in lump IPF2D0.P
R_InstallSpriteLump: Bad frame characters in lump IPF2C0.P
R_InstallSpriteLump: Bad frame characters in lump IPF2B0.P
R_InstallSpriteLump: Bad frame characters in lump IPF2A0.P

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

by Redneckerz » Thu Jun 23, 2022 3:32 pm

Hexereticdoom wrote:Hello, seems that GZDoom reached version 4.8.0 a few days ago, but the forum index is linking to 4.7.1... :-?

Please, someone who is in charge would be so kind to update it? Thank you in advance...
I have a feeling this happens every time with a new release. That is not a slight on the devs, just a nobservation.

Top