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
Crash on speed monster in 4K resolution #1452
Comments
Thanks. I see you are playing in 4K resolution and the log already gives issues for you at game startup. Also, you're playing in heavylog. I have two questions:
EDIT: Nevermind, I can easily reproduce the crash myself. In normal mode too. |
1440p works fine, so for now the workaround would be to lower the resolution also present in 0.4.8, |
Can confirm the crash on Alpha 3009 with 4k resolution. 1080p works fine. |
I only ran it in heavylog as the readme requested that. I normally play in
standard.
It is so reproducible that I was able to create the attached save in which
you can immediately reproduce the issue simply by selecting the speed
monster spell, charging it fully, then attempting to cast on a warlock.
I have now continued past this by avoiding fully charging the spell.
…On Mon, 2 May 2022, 11:06 Loobinex, ***@***.***> wrote:
Thanks. I see you are playing in 4K resolution and the log already gives
issues for you at game startup. Also, you're playing in heavylog.
I have two questions:
1. If you load your own save and do so again, can you reproduce the
crash?
2. You are playing the heavylog version, if you play the normal
version, does it crash there too?
—
Reply to this email directly, view it on GitHub
<#1452 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABK3PX2DLGPRRINZ4MCI6PDVH6SJFANCNFSM5U3Q5ZOQ>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Description: Crash when applying fully charged (only at 900) speed monster spell on lvl3 warlock in library.
Version: 0.4.9 Alpha 2696
Campaign: New game plus
Level: Flowerhat
Resolution: 4k
keeperfx_log.zip
fx1g0000.zip
The text was updated successfully, but these errors were encountered: