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] The RKPG tool freezes when exporting a scenario .brick TEMP #46

Open
wefsda opened this issue May 7, 2022 · 3 comments
Open

[BUG] The RKPG tool freezes when exporting a scenario .brick TEMP #46

wefsda opened this issue May 7, 2022 · 3 comments
Labels
Bug Something isn't working

Comments

@wefsda
Copy link

wefsda commented May 7, 2022

I’m not sure if this is a bug or if it’s with my game version.

Basically I’m trying to edit a scenario .brick file using the TEMP/TBLU editor and generate a TEMP file from it, but the tool freezes when generating the TEMP file. This applies to all the chunkXpatch2 scenario .brick TEMPs in the game.
Editing other .brick TEMPs, like the globaldata .brick or any outfits .brick works fine.
I’ve tried circumventing this problem by extracting the .brick as a QN json and using QuickEntity to rebuild it. However QuickEntity also freezes when rebuilding a scenario .brick.

I’ve never had this problem until I updated to 3.100. Is this a problem with my game, or the RKPG tool?

@wefsda wefsda added the Bug Something isn't working label May 7, 2022
@wefsda wefsda changed the title [BUG] The RKPG tool crashes when exporting a scenario .brick TEMP [BUG] The RKPG tool freezes when exporting a scenario .brick TEMP May 7, 2022
@RDIL
Copy link
Member

RDIL commented May 7, 2022

Which scenarios does this happen on?

@wefsda
Copy link
Author

wefsda commented May 7, 2022

Huh.
I used the RKPG tool v2.17.2 and it worked immediately. Weird. Just 2.21.0 freezes for some reason.
Anyhow to answer your question I was editing the scenarios for the Hitman2 maps (Miami, Santa fortuna, Mumbai, etc.)

@RDIL
Copy link
Member

RDIL commented May 8, 2022

Miami in particular is gigantic, that may be it. Not entirely sure about the others, but that may be why.

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