Not working on latest atmosphere + HOS 12.1.0

[t0mtee]

Just gives a bland screen on boot

[ndeadly]

Works fine for me. Are you sure you installed the latest version? (It's not the one that shows up as latest on the main page)

[t0mtee]

Works fine for me. Are you sure you installed the latest version? (It's not the one that shows up as latest on the main page)

yup, latest version

[Theguysayhi]

I can confirm I'm also having the same issue.

[ndeadly]

Are you sure the issue is caused by Mission Control? Can you tell me more about your environment, confirming version numbers instead of just stating "latest"? Do you boot with hekate or fusee primary? Which other custom sysmodules do you have installed?

[t0mtee]

I boot with fusee, I have atmosphere 0.19.5 on HOS 12.1.0. The only other sysmodules I have is sys-clk, tesla and nx-ovlloader. I will try deleting my atmosphere folder tomorrow but it's late right now

[ndeadly]

And Mission Control version?

[t0mtee]

MissionControl 0.5.0 pre-release 4, I've tried reinstalling it, I'm certain I'm using this version

[ndeadly]

Hmm ok, everything sounds fine. I've recompiled it with the latest commit to libstratosphere so you can try this build and see if it works. This really shouldn't be required anymore though...

MissionControl-0.5.0-alpha.4-develop-ff2cb79.zip

[Theguysayhi]

Just tested the build, and I can confirm it works on my version!

[ndeadly]

I was able to reproduce the black screen attempting to boot with fusee-primary, so I can confirm this is real. It seems like a similar issue to what was seen (and fixed) after the previous atmosphere release where hekate boots succesfully due to misconfiguring the firmware version number, only this time it may be cause by a bump to the minor version instead of micro. I've mentioned it to SciresM and will wait to see what comes of it before deciding if another pre-release version is necessary. For now anyone experiencing this issue can either boot with hekate or use the build from this thread.

[wanted8x]

For me not worked on 12.1 amsPLUS 0.19.5. I Have already install alpha4. Not Working.
i Install MissionControl-0.5.0-alpha.4-develop-ff2cb79.zip, but not working.

[ndeadly]

For me not worked on 12.1 amsPLUS 0.19.5. I Have already install alpha4. Not Working.
i Install MissionControl-0.5.0-alpha.4-develop-ff2cb79.zip, but not working.

I can't provide support for third party atmosphere distributions.

[wanted8x]

I mean: MissionControl does not working on latest atmosphere + HOS 12.1.0

[ndeadly]

What do you mean by not working? Black screen? Error message? Controllers not connecting? The current pre-release should work when booted via hekate, but the build posted above has been tested and confirmed working with fusee too. If it doesn't work for you there must be something different about your setup.

[wanted8x]

i have blackscreen. I booted via hekate, and the Controller Menu give me Error (Blue Screen).
Always was working on 12.0.1 with amsPLUS 0.19.4
After amsPLUS update and firmware update, its crashes in Controller Menu.

[ndeadly]

Post the error screen you get.

[wanted8x]

I formatting my emuMMC now. Then i'll backup my emuMMC and install missioncontrol again. (MissionControl-0.5.0-alpha.4-develop-ff2cb79.zip)
I'll call back

But Error Code was 2144-0001 (0x290).

[wanted8x]

It worked for me.
I formatting emuMMC, and config all. than install MissionControl from HB appstore. than copied MissionControl-0.5.0-alpha.4-develop-ff2cb79.zip in to SD Kart.
Maybe there was an error while updating.

Thanks

[C0nsp1racy]

Just tested the build, and I can confirm it works on my version!

As Feedback. same situation here. AMS 0.19.5 + HOS 12.1.0, Hekate 5.5.8 to chainload fusee-primary caused a bland screen on boot using only Mission Control MissionControl-0.5.0-alpha.4-develop-aa48059. Using MissionControl-0.5.0-alpha.4-develop-ff2cb79 from this thread solved the issue.

[ndeadly]

Thanks for the feedback. By now it's more or less understood what's happening and the circumstances it happens under, just not the exact cause. The build here will work for everyone, I'm just not sure whether a new release is really the answer if the problem could be fixed within atmosphere. SciresM is willing to address it if it makes sense, but the lack of error message makes it hard to track down what's going wrong.

I guess I'll just make yet another pre-release for now to put an end to the confusion.

[t0mtee]

Thanks for the feedback. By now it's more or less understood what's happening and the circumstances it happens under, just not the exact cause. The build here will work for everyone, I'm just not sure whether a new release is really the answer if the problem could be fixed within atmosphere. SciresM is willing to address it if it makes sense, but the lack of error message makes it hard to track down what's going wrong.

I guess I'll just make yet another pre-release for now to put an end to the confusion.

I'm assuming v0.5.0-beta is the pre-release you're refering to?

[ndeadly]

Thanks for the feedback. By now it's more or less understood what's happening and the circumstances it happens under, just not the exact cause. The build here will work for everyone, I'm just not sure whether a new release is really the answer if the problem could be fixed within atmosphere. SciresM is willing to address it if it makes sense, but the lack of error message makes it hard to track down what's going wrong.
I guess I'll just make yet another pre-release for now to put an end to the confusion.

I'm assuming v0.5.0-beta is the pre-release you're refering to?

Ha yeah I forgot I pushed the tag. I was going to publish it earlier but thought I might try to squeeze in a couple of bugfixes after I finish work.

[ndeadly]

Here you go. New beta release that will boot for everyone and incorporates a few bugfixes. Enjoy

https://github.com/ndeadly/MissionControl/releases/tag/v0.5.0-beta

[t0mtee]

Working fine now, thanks

[C0nsp1racy]

Thanks for the feedback. By now it's more or less understood what's happening and the circumstances it happens under, just not the exact cause. The build here will work for everyone, I'm just not sure whether a new release is really the answer if the problem could be fixed within atmosphere. SciresM is willing to address it if it makes sense, but the lack of error message makes it hard to track down what's going wrong.

I guess I'll just make yet another pre-release for now to put an end to the confusion.

It does make a lot of sense tbh. Anything i can do the help?

[ndeadly]

Probably not tbh. I'm not really sure how you'd debug a frozen boot short of compiling atmosphere or libstratosphere with abort calls thrown in at various points during the boot process to see how far along it makes it. Probably not worth your time seeing as I've now released 0.5.0 compiled with all the latest changes.

[C0nsp1racy]

Alright! Fair enough. Thanks all the time and effort you put in the project, Mission Control is much appriciated by many. (sorry for the late reply, got caught up in work)