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

BETA BUG - Extensions Using Unreal Engine Mod Installer Broken Latest Vortex Beta 1.13.0-Beta.1 #16545

Closed
ChemGuy1611 opened this issue Oct 8, 2024 · 3 comments · Fixed by #16549
Labels

Comments

@ChemGuy1611
Copy link

ChemGuy1611 commented Oct 8, 2024

Describe the bug
Error when managing a game that uses Unreal Engine Mod Installer code, whether within the extension or as a dependency. Reinstalled 1.12.6 and the error was gone, so it is definitely something from the beta changes.

To Reproduce
Steps to reproduce the behavior:

  1. Manage a game using UE Mod Installer code in Vortex.
  2. Get Error and "Failed to set game mode".

Expected behavior
No error when managing game.

Platform (please complete the following information):

  • OS: Windows 11
  • Vortex Version 1.13.0-Beta.1

Additional context

TypeError: (0 , storeHelper_1.getSafe)(...).reduce is not a function
    at UpdateSet.genExtendedItemsFromState (C:\Program Files\Black Tree Gaming Ltd\Vortex\resources\app.asar\renderer.js:2750:71)
    at init (C:\Program Files\Black Tree Gaming Ltd\Vortex\resources\app.asar\renderer.js:2748:88)
    at EventEmitter.<anonymous> (C:\Program Files\Black Tree Gaming Ltd\Vortex\resources\app.asar\renderer.js:10191:190)
    at EventEmitter.emit (node:events:529:35)
    at ExtEventHandler.emit (C:\Program Files\Black Tree Gaming Ltd\Vortex\resources\app.asar\renderer.js:8805:42)
    at GameModeManager.mOnGameModeActivated (C:\Program Files\Black Tree Gaming Ltd\Vortex\resources\app.asar\renderer.js:3169:180)
    at C:\Program Files\Black Tree Gaming Ltd\Vortex\resources\app.asar\renderer.js:3039:126
    at tryCatcher (C:\Program Files\Black Tree Gaming Ltd\Vortex\resources\app.asar\node_modules\bluebird\js\release\util.js:16:23)
    at Promise._settlePromiseFromHandler (C:\Program Files\Black Tree Gaming Ltd\Vortex\resources\app.asar\node_modules\bluebird\js\release\promise.js:547:31)
    at Promise._settlePromise (C:\Program Files\Black Tree Gaming Ltd\Vortex\resources\app.asar\node_modules\bluebird\js\release\promise.js:604:18)
    at Promise._settlePromise0 (C:\Program Files\Black Tree Gaming Ltd\Vortex\resources\app.asar\node_modules\bluebird\js\release\promise.js:649:10)
    at Promise._settlePromises (C:\Program Files\Black Tree Gaming Ltd\Vortex\resources\app.asar\node_modules\bluebird\js\release\promise.js:729:18)
    at Promise._fulfill (C:\Program Files\Black Tree Gaming Ltd\Vortex\resources\app.asar\node_modules\bluebird\js\release\promise.js:673:18)
    at Promise._resolveCallback (C:\Program Files\Black Tree Gaming Ltd\Vortex\resources\app.asar\node_modules\bluebird\js\release\promise.js:489:14)
    at Promise._settlePromiseFromHandler (C:\Program Files\Black Tree Gaming Ltd\Vortex\resources\app.asar\node_modules\bluebird\js\release\promise.js:559:17)
    at Promise._settlePromise (C:\Program Files\Black Tree Gaming Ltd\Vortex\resources\app.asar\node_modules\bluebird\js\release\promise.js:604:18)
@IDCs
Copy link
Contributor

IDCs commented Oct 9, 2024

Hey @ChemGuy1611 - thanks for the report, we are currently packaging the fix. Are you able to test the new package before we release it to the public?

We don't own any of the affected games and although we can fake them for testing, would be good to ensure nothing else is awry.

@IDCs
Copy link
Contributor

IDCs commented Oct 9, 2024

Re-opening as I'd like @ChemGuy1611 to test the fix before we release

@IDCs IDCs reopened this Oct 9, 2024
@IDCs
Copy link
Contributor

IDCs commented Oct 9, 2024

Nevermind, tested with DBZ

@IDCs IDCs closed this as completed Oct 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants