Stuck on Black screen when loading collection proxy w/o monarch (SOLVED)

Questions
1

Hello, so am using Monarch to try & load a collection proxy and it’s resulting in a black screen when trying to monarch.show the second time.

monarch.show(hash("startproxyID"))

from the main screen.

Here’s how my set up looks
Splash → StartScreen -->MainMenu

So i first load the splash.collection then make a proxy call to start.collection with

--disable current splash gui
msg.post("/main#splash", "disable")
monarch.show(hash("startproxyID"))

then on button clicked in the loaded StartScreen, the start.script makes another monarch.show() proxy call to mainmenu.collection thus black screen is shown

Second monarch.show call

msg.post("/main#start", "disable")
msg.post("/popup#signin", "disable")
monarch.show(hash("startScreenID"))

Monarch Logs

NFO:DLIB: SSDP: Started on address 192.168.2.167
DEBUG:SCRIPT: show()	hash: [startproxyID]
DEBUG:SCRIPT: show_in()	hash: [startproxyID]
DEBUG:SCRIPT: change_context()	hash: [startproxyID]
DEBUG:SCRIPT: show_in() loading screen	hash: [startproxyID]
DEBUG:SCRIPT: async_load()	hash: [startproxyID]
DEBUG:SCRIPT: transition()	hash: [startproxyID]
DEBUG:SCRIPT: change_context()	hash: [startproxyID]
DEBUG:SCRIPT: focus_gained()	hash: [startproxyID]
--Button to start MainMenu clicked
DEBUG:SCRIPT: show()	hash: [startScreenID]
DEBUG:SCRIPT: show_out()	hash: [startproxyID]
DEBUG:SCRIPT: change_context()	hash: [startproxyID]
DEBUG:SCRIPT: show_in()	hash: [startScreenID]
DEBUG:SCRIPT: change_context()	hash: [startScreenID]
DEBUG:SCRIPT: show_in() loading screen	hash: [startScreenID]
DEBUG:SCRIPT: async_load()	hash: [startScreenID]
DEBUG:SCRIPT: change_context()	hash: [startproxyID]
DEBUG:SCRIPT: focus_lost()	hash: [startproxyID]
DEBUG:SCRIPT: transition()	hash: [startproxyID]
DEBUG:SCRIPT: unload()	hash: [startproxyID]

Some set up screen shots

Screenshot%20from%202018-06-14%2012-00-29
Screenshot%20from%202018-06-14%2012-00-29307×337 10.6 KB
Screenshot%20from%202018-06-14%2012-00-09
Screenshot%20from%202018-06-14%2012-00-09330×346 9.44 KB
Screenshot%20from%202018-06-14%2011-59-36
Screenshot%20from%202018-06-14%2011-59-36348×355 8.85 KB

2

Are there any errors in the logs besides the monarch logs? How about if you add some prints in the init-function of a script in the collection that produces the black screen. Does it print anything?

3

No errors but thanks. I solved it by introducing a new collection that held all the collectionproxies for the game. Exactly like the example.collection in the git repo

1 Like
4

Yeah, your bootstrap collection should be a collection with some kind of controller/startup script and all of the screen proxies and use that controller script to load the initial screen.

1 Like