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

Player crashes when attempting to use a healing item outside of battle #1221

Closed
Brianum opened this Issue Jul 18, 2017 · 3 comments

Comments

Projects
None yet
3 participants
@Brianum
Contributor

Brianum commented Jul 18, 2017

Thank you for supporting EasyRPG Player.
Before creating an issue, please verify that your bug still occurs in the "continuous builds" of the Player.
You can get them at the bottom of our download section: https://easyrpg.org/player/downloads


Please fill in the following fields before submitting an issue:

Name of the game: Vampires Dawn 2

http://downloads.brianum.de/vampiresdawn/VampiresDawn2_de_en.exe

Player platform:

Windows64

Attach files (as a .zip archive or link them)

  • A savegame next to the problem (if it is not at the beginning of the game)
  • The easyrpg_log.txt log file (you can find it in the game directory)

Save06.zip

Crash-Dump:
Player_2017-07-18-04-12-19.zip

Nothing relevant inside the log.

[2017-07-18 04:11:56] Debug: EasyRPG Player 0.5.2 (2017-06-28) started
[2017-07-18 04:11:56] Debug: =========================================
[2017-07-18 04:11:56] Debug: CLI:
[2017-07-18 04:11:56] Debug: Opened audio at 44100 Hz (stereo), format: S16LSB
[2017-07-18 04:11:56] Debug: Detected encoding: ibm-5348_P100-1997
[2017-07-18 04:11:56] Debug: Using . as Game and Save directory
[2017-07-18 04:11:56] Debug: Loading game Vampires Dawn 2
[2017-07-18 04:11:56] Debug: Using RPG2k3 Interpreter
[2017-07-18 04:11:56] Debug: MP3 file (blood009.mp3) found
[2017-07-18 04:11:56] Debug: RPG2k >= v1.50 / RPG2k3 >= v1.05 detected
[2017-07-18 04:11:56] Debug: Engine configured as: 2k=0 2k3=1 2k3Legacy=1 MajorUpdated=1 Eng=0
[2017-07-18 04:11:56] Debug: Actor 6: Removing invalid item 17 (of type 6) from equipment slot 1 (needs type 1)
[2017-07-18 04:11:56] Debug: Actor 7: Removing invalid item 18 (of type 0) from equipment slot 1 (needs type 1)
[2017-07-18 04:11:56] Debug: Actor 8: Removing invalid item 17 (of type 6) from equipment slot 1 (needs type 1)
[2017-07-18 04:12:00] Debug: Loading Save Save06.lsd
[2017-07-18 04:12:00] Debug: Loading Map Map0078.lmu
[2017-07-18 04:12:00] Debug: Tree: Inselwald 1 < Weltkarte
[2017-07-18 04:12:01] Debug: Starting battle 103 (Riesenbiene x1)
[2017-07-18 04:12:01] Debug: Image size out of bounds: Backdrop/forest09 (320x160 < 320x240 < 320x160)

Describe the issue in detail and how to reproduce it:

When trying to use a healing item ("Heilbalsam") outside of battle the player crashes after selecting the party member to apply this item to. In RPG_RT the item works as expected.

@Ghabry

This comment has been minimized.

Show comment
Hide comment
@Ghabry

Ghabry Jul 18, 2017

Member

Hello. This is a known regression in 0.5.2 and was fixed in the nightlies (continious builds) you can find on our website.

Member

Ghabry commented Jul 18, 2017

Hello. This is a known regression in 0.5.2 and was fixed in the nightlies (continious builds) you can find on our website.

@Ghabry Ghabry added the Crash label Jul 18, 2017

@Brianum

This comment has been minimized.

Show comment
Hide comment
@Brianum

Brianum Jul 18, 2017

Contributor

Confirmed.

Contributor

Brianum commented Jul 18, 2017

Confirmed.

@Brianum Brianum closed this Jul 18, 2017

@carstene1ns carstene1ns added this to the 0.5.3 milestone Jul 18, 2017

@carstene1ns carstene1ns removed the Duplicate label Jul 18, 2017

@carstene1ns

This comment has been minimized.

Show comment
Hide comment
@carstene1ns

carstene1ns Jul 18, 2017

Member

Fixed by dc03cff.


Edit: Removed the duplicate label again, because we did not have an issue for the bug in the first place

Member

carstene1ns commented Jul 18, 2017

Fixed by dc03cff.


Edit: Removed the duplicate label again, because we did not have an issue for the bug in the first place

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment