Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] Hard Crash to Desktop on 'Scroller' Block in Intermission definition #2879

Open
1 task done
FDinolfo opened this issue Dec 30, 2024 · 0 comments
Open
1 task done
Labels

Comments

@FDinolfo
Copy link

GZDoom version

GZDoom 4.14.0 Release

Which game are you running with GZDoom?

Other

What Operating System are you using?

None

Please describe your specific OS version

Windows 11 Pro X64 24H2

Relevant hardware info

Core i5 12600K, 32GB RAM, RTX 3060 Ti

Have you checked that no other similar issue already exists?

  • I have searched and not found similar issues.

A clear and concise description of what the bug is.

I am creating a custom ending sequence using the Intermission definition in ZMAPINFO. I tried to add a scroller block, and discovered that though GZDoom will load with it, when the Intermission plays and it reaches that block, GZDoom crashes to desktop.Below is the beginning of the Intermission def.

`Map MDTEST "Test Map" {
LevelNum = 99
Cluster = 2
Next = endsequence, "DSEnd"
}

Intermission DSEnd
{
TextScreen
{
Background = "TSATURN"
Music = "EXITLEVL"

	Time = 15
	Position = 1, 1

	Text =
	"This is some text that will be displayed",
	" ",
	" on the screen."
}
Scroller
{
	InitialDelay = -1
}
Cast
{
	CastClass = "Agathodemon"
	CastName = "Agathodemon"
	AttackSound = "Melee", 0, "caco/melee"
	AttackSound = "Missile", 1, "caco/active"
}

}
`

CrashReport.zip
ini.zip

Steps to reproduce the behaviour.

Explain how to reproduce

  1. Create a test map with an exit.
  2. Set up ZMAPINFO to point to the correct custom sequence
  3. Load the map and flip the switch to exit.

Your configuration

No response

Provide a Log

No response

@FDinolfo FDinolfo added the bug label Dec 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant