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

UndertaleModLib.Models. Undertale Font in chunk FONT #1453

Closed
OPkokakola opened this issue Aug 4, 2023 · 2 comments
Closed

UndertaleModLib.Models. Undertale Font in chunk FONT #1453

OPkokakola opened this issue Aug 4, 2023 · 2 comments
Labels
bug Something isn't working

Comments

@OPkokakola
Copy link

Describe the bug

I create a project in gamemaker, add the desired font there, run the project, run game.unx and this error appears (tried several fonts, update doesn't help)

An error occured while trying to load: First list item starts inside the pointer list?!?!
at 00000320 while reading object
UndertaleModLib.Undertale PointerList`1[[UndertaleModLib.M odels.UndertaleFont+Glyph,
UndertaleModLib,
Version=0.5.1.0, Culture=neutral, PublicKeyToken=null]]
at 00000320 while reading object UndertaleModLib.Models. UndertaleFont
while reading item 1 of 1 in a list of
UndertaleModLib.Models. Undertale Font in chunk FONT

Снимок экрана 2023-08-04 142834

Reproducing steps

  1. Create a project in gamemaker
  2. Add a font
  3. Start the project
  4. Go to the path C:\Users\Admin\AppData\Local\GameMakerStudio2\GMS2TEMP
  5. Go to the project folder
  6. Open game.unx
  7. Error

Setup Details

tried on versions 0.5.1.0, 0.5.0.0, 0.4.0.4
win 11
gamemaker 2

@OPkokakola OPkokakola added the bug Something isn't working label Aug 4, 2023
@Jacky720
Copy link
Contributor

Jacky720 commented Aug 4, 2023

Reproduced on GM2023.6 but not GM2023.4. Will investigate for any changes in the FONT structure (which may be useful to detect 2023.6).

@OPkokakola
Copy link
Author

Reproduced on GM2023.6 but not GM2023.4. Will investigate for any changes in the FONT structure (which may be useful to detect 2023.6).

does not work on 2023.4 either, but on 2023.2.1 it worked, thanks for the help

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants