Having an issue with the Editor being grayed out after closing preview

Post reply

❤Follow Topic(13)

0 favourites

65 posts
- 1
- 2
- 3
- 4
- 5

From the Asset Store

Gif

Grey Cyborgs Game Sprites

$12 USD

Grey Cyborgs character spritesheet for side scrolling action adventure hack and slash 2D mobile game.

mikailain

- jobel
- - Joined 27 Jul, 2013
  - 232 topics • 2,179 posts
- 1
- 1 Jun, 2020
- Quote
farfetchd83 this could be a coincidence, but I have not had the problem since moving my projects from Google Drive to Dropbox. Ashley could the recent Google changes have an effect here?
EDIT: nope, I take that back.. it still happens.. just happened to me twice in a row. It definitely has something to with "going fast" and quickly starting and closing the preview. Because it seems to only happen when I test small things that need a quick back-and-forth (opposed to longer form testing)
- farfetchd83
- - Joined 27 Oct, 2016
  - 38 topics • 165 posts
- 1
- 2 Jun, 2020
- Quote
I use DropBox as the cloud service... I've been having the bug for a while now...

Unfortunately Chrome is the browser that works best for me with C3...

I wish your preferences, like theme, etc, would load automatically when using a new browser too...
- pirx
- - Joined 20 Aug, 2013
  - 72 topics • 243 posts
- 1
- 3 Jun, 2020
- Quote
Another two cents to confirm: This also happened to me about a week ago. Launched C3 in Chrome, opened one of my projects (Dropbox cloud open), started preview, couldn't click anything after closing the preview. Fortunately I hadn't even made any changes yet so I just assumed it was a random glitch of computer/browser/C3; restarted the browser and it hasn't happened since.
- Fib
- - Joined 19 Jan, 2012
  - 18 topics • 188 posts
- 1
- 3 Jun, 2020
- Quote
This happened to me just a single time last night with browser tab preview set. I pressed the preview button on accident and quickly closed out the preview tab before it was done loading. Then the tab with C3 running in it was greyed out and I couldn't interact with anything.
- farfetchd83
- - Joined 27 Oct, 2016
  - 38 topics • 165 posts
- 1
- 3 Jun, 2020
- Quote
pirx Fib thanks for adding information, hope we build enough "clues" so Ashley and the team can fix it soon.
This is a bug that cannot be reproduced by following steps. Happens to me regularly, 4 out of 10 times.

Call the priest.
- Ashley Construct Team Founder
- Moderator
- - Joined 21 May, 2007
  - 669 topics • 30,336 posts
- 1
- 4 Jun, 2020
- Quote
I'm afraid without reliable steps to reproduce the problem, it's virtually impossible to do anything. This ought to be impossible. I have no idea how it could happen.
- farfetchd83
- - Joined 27 Oct, 2016
  - 38 topics • 165 posts
- 1
- 16 Jun, 2020
- Quote
hey Ashley i just want to add here that if I use C3 like the below setting, straight in the browser (chrome) that editor frozen issue happens frequently:

BUT ! If I use C3 like below, opening C3 in that buttom, and have an exclusive window, the problem does not happen!

I've been now only using it this way an haven't got the frozen issue!
- Ashley Construct Team Founder
- Moderator
- - Joined 21 May, 2007
  - 669 topics • 30,336 posts
- 1
- 16 Jun, 2020
- Quote
Both those modes use identical code, so I don't know why there would be any difference.
Try Construct 3

Develop games in your browser. Powerful, performant & highly capable.
Try Now Construct 3 users don't see these ads
- jobel
- - Joined 27 Jul, 2013
  - 232 topics • 2,179 posts
- 1
- 16 Jun, 2020
- Quote
I recently got this to happen 6 times in a row and then never again for the rest of the night!

Ashley this issue intermittently has probably been happening for the past 1-2 months(its never happened before that-ever), has anything changed in Construct or Chrome about 2 months ago that would potentially cause this to happen?
- farfetchd83
- - Joined 27 Oct, 2016
  - 38 topics • 165 posts
- 1
- 16 Jun, 2020
- Quote
Both those modes use identical code, so I don't know why there would be any difference.

The difference is when using directly in the browser (chrome) is that it uses a new tab on the same window/browser, and when opening in the "browser app" the preview mode opens a tab in a different/independent window, so the problem is probably not your code but a conflict with Chrome when using C3 and previews on the same window... the issue happens when returning from the preview tab to the editor tab, so it doesn't happen when using the "browser app" because they are not running in the same window...

That's what we know so far...
- jobel
- - Joined 27 Jul, 2013
  - 232 topics • 2,179 posts
- 1
- 21 Jun, 2020
- Quote
Ashley I had a new development with this issue. I'm not sure it will help.
I pressed F4 and did a quick test - the preview opened in another Chrome Tab. I quickly closed the Construct Preview tab. Since I've been getting this grayed out window a lot I was expecting it and sure enough it was happening again.

As I mentioned, the way I clear it, is to hit F4 again and restart a preview and hope when I close it this time it returns to normal. But this particular time when returning to the grayed out Construct Editor I hit F4 so fast the webpage didn't register it and never started the preview, however it did clear the grey out!

I know you can't reproduce it, but it obviously it has something to do with the "Preparing Project data" window where the editor is grayed out. Maybe this helps?
- Chadori
- - Joined 10 Oct, 2014
  - 158 topics • 1,942 posts
- 1
- 10 Jul, 2020
- Quote
Finally, I was able to reproduce. It seems to be a glitch with how the editor dims and lock when showing the preview dialog (possible any dialog).

I was able to break out of the glitch by pressing preview again. It was not serious, in my case, but I was able to reproduce it twice in a row.

Just sharing just in case this helps during code review.

(NW.js Desktop Build - r204.2)
- jobel
- - Joined 27 Jul, 2013
  - 232 topics • 2,179 posts
- 1
- 10 Jul, 2020
- Quote
— when you say you can reproduce it, do you mean you can consistently make it happen? I can't.
There are times it happens to me 4 times in a row. My record (yes I've gamified it) is 6 in a row but that only happened once. Can anyone beat that? ;-)
- Princeofdorkness
- - Joined 2 Feb, 2019
  - 2 topics • 3 posts
- 1
- 20 Jul, 2020
- Quote
I seem to have found a fix for this, at least for anyone else using C3 r204.2 on Android with Chrome. I can't imagine how many crazy things I must have tried to restore C3 when this would happen, and that's why I'm actually a little disappointed with myself that I didn't figure this out sooner. All you have to do is tap the back button (<) on your phone until you get a dialog from construct asking if you wish to "leave" or "stay". Tap "stay" and you'll be returned to the editor with everything working properly.

This has worked consistently for me on Android. Hopefully a similar procedure will work on desktop as well.

A couple more "clues" I've observed, don't know if it will help though. When the editor is greyed out I am still able to swipe left and right to scroll through the various bars. The bars are unresponsive and greyed out also, but if I tap and hold on an item in the bar I get a vibration, but nothing happens.

I hope you guys fix this soon. I've had to redo a lot of work because of this, but at least now it's just an annoyance. My mechanic hates intermittent problems too!
- Princeofdorkness
- - Joined 2 Feb, 2019
  - 2 topics • 3 posts
- 1
- 20 Jul, 2020
- Quote
I should add, I thought it only happened when I would quickly open and close the preview, but it has occurred after a minute or more in preview. I also thought at one point that it only happened with the layout active, but it has happened with events sheets active also.