You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
The text was updated successfully, but these errors were encountered:
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
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.)
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?
The text was updated successfully, but these errors were encountered: