Page 1 of 1

[BUG]&[Solution] PGE Editor not launching (smbx launcher issue)

Posted: Wed May 17, 2017 11:56 pm
by Qubo
Hello community, just wanted to say that I found a major bug in the PGE editor, here it goes:

When the subfolder Worlds has no file which extension is *.wld like this:
  • [YOUR SMBX DIRECTORY]/data/worlds/[WORLD NAME].wld
  • OR
  • [YOUR SMBX DIRECTORY]/data/worlds/[EPISODE NAME]/[WORLD NAME].wld
In which text in ITALLIC are variable depending on your computer, or file names.
When you open the SMBX 2.0 Launcher, and click on the Editor, the PGE Editor wont open no matter how many times do you spend clicking on it, also, doesn't matter if you've opened it as an Administrative User.

The solution:
  1. Browse to [YOUR SMBX DIRECTORY]/data/worlds/
  2. Create a new folder and call it: PGE Unlocker
  3. Open /PGE Unlocker
  4. Open notepad (Start Menu->All Programs->Accessories->Notepad) (or a text editor)
  5. Write/Paste this in notepad
    Spoiler: show
    64
    "UNLOCK"
    #FALSE#
    #TRUE#
    #TRUE#
    #TRUE#
    #TRUE#
    ""
    #FALSE#
    #FALSE#
    0
    "PGE EDITOR"
    ""
    ""
    ""
    ""
  6. Under the Menu, goto File->Save As... (a file save box should appear)
    Image
  7. Browse to [YOUR SMBX DIRECTORY]/data/worlds/PGE Unlocker
  8. In the Name field write PGEUNLOCKER.wld (very important that we end it with .wld)
  9. In the Save As Type field, open the drop-down menu and select All Files (*.*)
    Should be like this:
    Image
  10. Click on Save
  11. Now you're ready to go!
Now your main screen when launching the launcher should be like this:
Spoiler: show
Image
That's it, hope solved someone's problem, see you next time!
Edit: changed the title.
~Qubo

Re: [BUG]&[Solution] PGE Editor not launching

Posted: Thu May 18, 2017 1:46 am
by Wohlstand
It's a bug of launcher, not of PGE Editor. PGE Editor itself needs no worlds folder to work. Launcher loads episodes to show a list of them, and seems, the bug in launcher means it must block loading game because of no worlds, but seems, also block loading of editor.
You still be able to run PGE Editor directly without launcher.

Re: [BUG]&[Solution] PGE Editor not launching (smbx launcher issue)

Posted: Sun Jan 09, 2022 3:52 pm
by Tabley-Kun
Hi.
I would like to use the PGE Editor, but it won't start. It just stays in the background inside the task manager.
Even, if I try to start it via the SMBX2 launcher, it won't open. Everything should be installed properly.

I'd like to thank you in advance for your help.

Re: [BUG]&[Solution] PGE Editor not launching (smbx launcher issue)

Posted: Mon Jan 10, 2022 3:49 am
by ShadowXeldron
Tabley-Kun wrote:
Sun Jan 09, 2022 3:52 pm
Hi.
I would like to use the PGE Editor, but it won't start. It just stays in the background inside the task manager.
Even, if I try to start it via the SMBX2 launcher, it won't open. Everything should be installed properly.

I'd like to thank you in advance for your help.
Try launching the editor directly by running pge_editor.exe.

Re: [BUG]&[Solution] PGE Editor not launching (smbx launcher issue)

Posted: Thu Jan 13, 2022 4:18 pm
by Wohlstand
Tabley-Kun wrote:
Sun Jan 09, 2022 3:52 pm
Hi.
I would like to use the PGE Editor, but it won't start. It just stays in the background inside the task manager.
Even, if I try to start it via the SMBX2 launcher, it won't open. Everything should be installed properly.

I'd like to thank you in advance for your help.
I guess, there is some weird Windows 10-side mess... Recently I got a similar report from another guy. The fact he had the same stuff in as-is form, and it worked fine (he had builds made around March 2021). But some months later that just stopped work. So, that's possibly just some local issue or a damn of Windows. I suggested him to download an update for the luck, and seems, the thing got worked.

P.S. Important: after the update, you should open the "configs/SMBX2 Integration/main.ini" and replace the "api-version = 41" with the "api-version = 42" line to avoid it popping up the "legacy config pack" startup message box. Some months ago I majorly reworked the international config packs (unlike standalone, they have a config script that starts at first launch and asks you to select the path to the game) system to make them use local settings instead of main.ini overriding, and because of that, I changed the API version. For non-integrational config packs (including config pack bundled with X2) you can don't worry, they didn't get any incompatible changes, and stuff still work as-is.