Scirra / Construct-bugs

Public bug report submissions for Construct 3 and Construct Animate. Please read the guidelines then click the 'Issues' tab to get started.
https://www.construct.net
108 stars 83 forks source link

Won't load preview #1821

Closed markbellharmony closed 6 years ago

markbellharmony commented 6 years ago

Problem description

The project won't run in either online or destop version (stable and beta). Works sometimes and not others. Must have failed to load preview 200 times in the past week. Then crashes Construct.

I have tried the following:

Attach a .c3p

PLEASE DO NOT MESS WITH MY PROJECT. I have worked two years on this project and don't want to loose it all.

cp0.3.2.30.zip

Steps to reproduce

  1. Click preview, debug or preview project.

Observed result

Construct shows error and won't respond. Must be restarted.

Expected result

The viewer to show my project.

Affected browsers

System details

View details Platform information Browser: NW.js Browser version: 0.31.2 Browser engine: Chromium Browser architecture: 64-bit Context: nwjs Operating system: Windows Operating system version: 10 Operating system architecture: 64-bit Device type: desktop Device pixel ratio: 1 Logical CPU cores: 8 Approx. device memory: 8 GB User agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (@878cd31214ac27a3996927cd5c9c138b10c9fc8d) NWjs/0.31.2 (like Chrome/67.0.3396.87) C3 release: r109 (beta) Language setting: en-US Local storage Storage quota (approx): 19 gb Storage usage (approx): 179 mb (0.9%) Persistant storage: Yes Browser support notes This list contains missing features that are not required, but could improve performance or user experience if supported. Nothing is missing. Everything is OK! WebGL information Version string: WebGL 2.0 (OpenGL ES 3.0 Chromium) Numeric version: 2 Supports NPOT textures: yes Supports GPU profiling: no Vendor: Google Inc. Renderer: ANGLE (NVIDIA GeForce GTX 1080 Direct3D11 vs_5_0 ps_5_0) Major performance caveat: no Maximum texture size: 16384 Point size range: 1 to 1024 Extensions: EXT_color_buffer_float EXT_texture_filter_anisotropic OES_texture_float_linear WEBGL_compressed_texture_s3tc WEBGL_compressed_texture_s3tc_srgb WEBGL_debug_renderer_info WEBGL_debug_shaders WEBGL_lose_context Audio information System sample rate: 44100 Hz Output channels: 6 Output interpretation: speakers Supported decode formats: Ogg Opus (audio/ogg; codecs=opus) WebM Opus (audio/webm; codecs=opus) Ogg Vorbis (audio/ogg; codecs=vorbis) WebM Vorbis (audio/webm; codecs=vorbis) MPEG-4 AAC (audio/mp4; codecs=mp4a.40.5) MP3 (audio/mpeg) FLAC (audio/flac) PCM WAV (audio/wav; codecs=1) Supported encode formats: WebM Opus (audio/webm; codecs=opus) Video information Supported decode formats: WebM VP9 (video/webm; codecs=vp9) WebM VP8 (video/webm; codecs=vp8) Ogg Theora (video/ogg; codecs=theora) H.264 (video/mp4; codecs=avc1.42E01E) Supported encode formats: WebM VP9 (video/webm; codecs=vp9) WebM VP8 (video/webm; codecs=vp8)
NetOneGames commented 6 years ago

It looks like it is falling over trying to render sprite sheets for something. You do realize you have some unnecessarily super huge sprites and tile-maps hanging around?

markbellharmony commented 6 years ago

Thanks so much. Today is a travel day for me but I'll have a crack at that on Tuesday.

AshleyScirra commented 6 years ago

It looks like there's something wrong with the spritesheeting. (It also crashes if you go to project -> tools -> view spritesheets). The project also has some extraordinarily large and wasteful images - for example tbg_00.png is 4480x2688, which is larger than many devices actually support (4096 being a common limit), and the image content is the same small image tiled over and over again. So the image takes up 48mb of memory when it could just tile the repeating 128x128 section, which would use 64kb of memory. So the image unnecessarily wastes about 750x as much memory as it needs to, for a single image. This should be fixed anyway, but may also be related to the problem, since the spritesheeting engine has to specially handle such large images.

AshleyScirra commented 6 years ago

The problem appears to be that the project is corrupt. In 14 cases the project file states the wrong size for the image. For example tbg_01 specifies a size of 2813x1688 in the project file, but the actual image is 4480x2688. To avoid having to decode the image when loading projects Construct will honour the size in the project file, but since this is incorrect and images are a different size to what Construct thinks they are, it can end up generating a spritesheet too small to fit them and then crashes trying to render the image off the edge of the spritesheet.

I've never seen this before. It ought to be impossible. The only way I can think this happened is if you directly edited the images in the project file outside of Construct, and replaced them with ones which are a different size. @markbellharmony - have you done something like this?

Marking this issue as 'difficult' as we don't have steps to reproduce for the root cause that ends up with incorrect image sizes in the project file, so we can't directly debug this.

markbellharmony commented 6 years ago

Thank you sooooo much! Today is a travel day for me so as soon as I can try this I will!

M

On Mon, Jul 23, 2018 at 7:41 AM Ashley (Scirra) notifications@github.com wrote:

The problem appears to be that the project is corrupt. In 14 cases the project file states the wrong size for the image. For example tbg_01 specifies a size of 2813x1688 in the project file, but the actual image is 4480x2688. To avoid having to decode the image when loading projects Construct will honour the size in the project file, but since this is incorrect and images are a different size to what Construct thinks they are, it can end up generating a spritesheet too small to fit them and then crashes trying to render the image off the edge of the spritesheet.

I've never seen this before. It ought to be impossible. The only way I can think this happened is if you directly edited the images in the project file outside of Construct, and replaced them with ones which are a different size. @markbellharmony https://github.com/markbellharmony - have you done something like this?

Marking this issue as 'difficult' as we don't have steps to reproduce for the root cause that ends up with incorrect image sizes in the project file, so we can't directly debug this.

— You are receiving this because you were mentioned.

Reply to this email directly, view it on GitHub https://github.com/Scirra/Construct-3-bugs/issues/1821#issuecomment-407028705, or mute the thread https://github.com/notifications/unsubscribe-auth/AVBJY9MaPDFMr0OvFgscbOEwxiDdCIBZks5uJbZTgaJpZM4VZs3H .

-- Mark W. Bell Digital Media Arts & Technology - Harmony School

AshleyScirra commented 6 years ago

I'm not sure you understood my comment? I asked if you had previously replaced image files to ones with a different size outside of Construct. This is not something new to try, it's something I need to know to help diagnose the problem.

markbellharmony commented 6 years ago

@AshleyScirra Thank you so much for your help on this. I made my background files in Photoshop using its tiling function and inported them into Construct. This is most likely causing the problem. I am going to try to fix this today and see if I can build.

M

AshleyScirra commented 6 years ago

How did you import them in to Construct? I specifically need to know if you did this outside of Construct (i.e. editing the project folder/zip file directly), in which case the root cause of the bug has been identified; otherwise if you did it entirely inside Construct, there is probably a bug in Construct itself that still needs to be properly identified.

markbellharmony commented 6 years ago

@AshleyScirra I dragged them into the construct imain mage viewer from a file explorer after editing them. Today I replaced then all in the image viewer by using open in the construct image viewer. Works fine. Runs fine. Save and check back into my github. Stops working again. The image files are now all tiny but then layout is still huge. According to the statistics game_layout is 61 mb. Is that layout corrupt now?

AshleyScirra commented 6 years ago

I still have no idea what you're doing. It sounds like you're using github as source control for the project. Is that correct? I assume you are therefore using the desktop build's save as folder option to keep separate files?

If so there would be plenty of opportunity to swap out image files with different ones on source control - either intentionally, or accidentally by merge/conflict/etc. Basically if you have a folder project and at any point an image is replaced with one of a different size by overwriting the file (rather than editing in C3), it will corrupt the project because Construct expects it to be a different size. Based on what you've mentioned I suspect this is what is really happening, but it would be nice to have some kind of direct confirmation that this has happened at some point with your project, to rule out the possibility there is a bug in C3 itself somewhere.

Replacing image files outside of C3 is tricky to fix - we could stop trusting the size in the project file, but then this means decoding the image while loading the project to find out the true size. This would slow down loading projects for everybody, so I'd prefer not to do that.

markbellharmony commented 6 years ago

@AshleyScirra I am using github as source control. I am therefore using the desktops build as a folder option to keep separate files. I have to do this so that I can edit the json array files that make up part of my game in notepad++ because the viewer in construct 3 makes them very difficult to read. The X and Y are swapped.

I have not directly edited any of the image files except through construct image editor, either by dragging in a file or by using the open command. So I am not editing image files outside of C3.

I have made all my images small and close to the 0,0 point on that layout and i am still having the problem.

I understand this is probably a very rare occurrence. At this point my game is toast that I have been working on for two years and have no idea what to do.

Would having access to my github help you?

Anything else you can suggest?

M

AshleyScirra commented 6 years ago

I can probably recover the project attached in the original report if that would be helpful? However there's no guarantee it won't happen again.

It wouldn't take much to swap some image files accidentally with source control, you only need to miss a file on a commit or update and it could end up with the wrong image. Unless anyone can find steps to start with a good project and make it go bad from within C3, I'm going to assume that's the root cause problem.

markbellharmony commented 6 years ago

It will just corrupt again. I am sorry I am pretty wrecked over this since I have put 2 years into this and there is no way I can see to complete the project.

I can't use the project as single file option because of my jsons and I can't use multiple file option without it corrupting. I know I added every one of those images through C3 but basically am looking at starting again.

I worry this project is too much for c3 to handle yet.

markbellharmony commented 6 years ago

I'm on the road until Friday. Saturday I'll try to build a branch and see if i can fix this. M

markbellharmony commented 6 years ago

I was already to tell you i had gone back and fixed everything. Basically recreating two weeks work and there was no preview problems when I check it in and went to reopen the project and I get a new error.

Failed to open project. Check it is a valid Construct 3 folder project.

I have attached entire folder project cq.zip

Any ideas?

Also, even after downloading newest c3 beta I get a warning I am running r110.2 and need to upgrade to r111 so I undate and yet it asks me every single time.

markbellharmony commented 6 years ago

Tried on 2 machines same problem though the text of the c3proj file looks ok.

markbellharmony commented 6 years ago

@AshleyScirra here is the console log

register-root-sw.js:17 Registered root service worker on https://editor.construct.net/ root-sw.js:277 [Root-SW-Offline] Up to date main.js:174 Stop! main.js:174 This is a browser feature intended for developers. If someone told you to copy and paste something here to enable a feature or "hack" something, it is a scam and may allow them to steal your account information or your work. main.js:174 Registered service worker on https://editor.construct.net/r111/ Refused to load the image '' because it violates the following Content Security Policy directive: "default-src 'self' blob:". Note that 'img-src' was not explicitly set, so 'default-src' is used as a fallback.

Refused to load the image '' because it violates the following Content Security Policy directive: "default-src 'self' blob:". Note that 'img-src' was not explicitly set, so 'default-src' is used as a fallback.

Refused to load the image '' because it violates the following Content Security Policy directive: "default-src 'self' blob:". Note that 'img-src' was not explicitly set, so 'default-src' is used as a fallback.

Refused to load the image '' because it violates the following Content Security Policy directive: "default-src 'self' blob:". Note that 'img-src' was not explicitly set, so 'default-src' is used as a fallback.

Refused to load the image '' because it violates the following Content Security Policy directive: "default-src 'self' blob:". Note that 'img-src' was not explicitly set, so 'default-src' is used as a fallback.

Refused to load the image '' because it violates the following Content Security Policy directive: "default-src 'self' blob:". Note that 'img-src' was not explicitly set, so 'default-src' is used as a fallback.

Refused to load the image '' because it violates the following Content Security Policy directive: "default-src 'self' blob:". Note that 'img-src' was not explicitly set, so 'default-src' is used as a fallback.

Refused to load the image '' because it violates the following Content Security Policy directive: "default-src 'self' blob:". Note that 'img-src' was not explicitly set, so 'default-src' is used as a fallback.

editor.construct.net/:1 Refused to load the image 'data:image/svg+xml;base64,PD94bWwgdmVyc2lvbj0iMS4wIiA/Pjxzdmcgd2lkdGg9IjI0cHgiIGhlaWdodD0iMjRweCIgdmlld0JveD0iMCAwIDI0IDI0IiB2ZXJzaW9uPSIxLjEiIHhtbG5zPSJodHRwOi8vd3d3LnczLm9yZy8yMDAwL3N2ZyIgeG1sbnM6eGxpbms9Imh0dHA6Ly93d3cudzMub3JnLzE5OTkveGxpbmsiPjxkZWZzPjxtYXNrIGlkPSJtIj48cmVjdCBmaWxsPSIjZmZmIiB4PSIwIiB5PSIwIiB3aWR0aD0iMjQiIGhlaWdodD0iMjQiIHJ4PSI2IiByeT0iNiIvPjxyZWN0IGZpbGw9IiMwMDAiIHg9IjUiIHk9IjUiIHdpZHRoPSIxNCIgaGVpZ2h0PSIxNCIgcng9IjEiIHJ5PSIxIi8+PHJlY3QgZmlsbD0iIzAwMCIgeD0iMTAiIHk9IjAiIHdpZHRoPSI0IiBoZWlnaHQ9IjI0Ii8+PHJlY3QgZmlsbD0iIzAwMCIgeD0iMCIgeT0iMTAiIHdpZHRoPSIyNCIgaGVpZ2h0PSI0Ii8+PC9tYXNrPjwvZGVmcz48cmVjdCB4PSIwIiB5PSIwIiB3aWR0aD0iMjQiIGhlaWdodD0iMjQiIGZpbGw9IiNmZmYiIG1hc2s9InVybCgjbSkiLz48L3N2Zz4=' because it violates the following Content Security Policy directive: "default-src 'self' blob:". Note that 'img-src' was not explicitly set, so 'default-src' is used as a fallback.

editor.construct.net/:1 Refused to load the image 'data:image/svg+xml;base64,PD94bWwgdmVyc2lvbj0iMS4wIiA/Pjxzdmcgd2lkdGg9IjI0cHgiIGhlaWdodD0iMjRweCIgdmlld0JveD0iMCAwIDI0IDI0IiB2ZXJzaW9uPSIxLjEiIHhtbG5zPSJodHRwOi8vd3d3LnczLm9yZy8yMDAwL3N2ZyIgeG1sbnM6eGxpbms9Imh0dHA6Ly93d3cudzMub3JnLzE5OTkveGxpbmsiPjxkZWZzPjxtYXNrIGlkPSJtIj48cmVjdCBmaWxsPSIjZmZmIiB4PSIwIiB5PSIwIiB3aWR0aD0iMjQiIGhlaWdodD0iMjQiIHJ4PSI2IiByeT0iNiIvPjxyZWN0IGZpbGw9IiMwMDAiIHg9IjUiIHk9IjUiIHdpZHRoPSIxNCIgaGVpZ2h0PSIxNCIgcng9IjEiIHJ5PSIxIi8+PHJlY3QgZmlsbD0iIzAwMCIgeD0iMTAiIHk9IjAiIHdpZHRoPSI0IiBoZWlnaHQ9IjI0Ii8+PHJlY3QgZmlsbD0iIzAwMCIgeD0iMCIgeT0iMTAiIHdpZHRoPSIyNCIgaGVpZ2h0PSI0Ii8+PC9tYXNrPjwvZGVmcz48cmVjdCB4PSIwIiB5PSIwIiB3aWR0aD0iMjQiIGhlaWdodD0iMjQiIGZpbGw9IiNmZmYiIG1hc2s9InVybCgjbSkiLz48L3N2Zz4=' because it violates the following Content Security Policy directive: "default-src 'self' blob:". Note that 'img-src' was not explicitly set, so 'default-src' is used as a fallback.

editor.construct.net/:1 Refused to load the image 'data:image/svg+xml;base64,PHN2ZyB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciIGhlaWdodD0iMzBweCIgd2lkdGg9IjMwcHgiIHZpZXdCb3g9Ii0xIC0xIDMxIDMxIj48Zz48cGF0aCBkPSJNMjkuNDQ5LDE0LjY2MiBDMjkuNDQ5LDIyLjcyMiAyMi44NjgsMjkuMjU2IDE0Ljc1LDI5LjI1NiBDNi42MzIsMjkuMjU2IDAuMDUxLDIyLjcyMiAwLjA1MSwxNC42NjIgQzAuMDUxLDYuNjAxIDYuNjMyLDAuMDY3IDE0Ljc1LDAuMDY3IEMyMi44NjgsMC4wNjcgMjkuNDQ5LDYuNjAxIDI5LjQ0OSwxNC42NjIiIGZpbGw9IiNmZmYiIHN0cm9rZT0iI2ZmZiIgc3Ryb2tlLXdpZHRoPSIxIj48L3BhdGg+PHBhdGggZD0iTTE0LjczMywxLjY4NiBDNy41MTYsMS42ODYgM...UuMDIyLDYuNDk3IEMxOS41NTUsNi40OTcgMjMuMDc4LDkuNzA1IDIzLjA3OCwxMy45OTEgQzIzLjA3OCwxOC40NjMgMjAuMjM5LDIyLjA2MiAxNi4yOTcsMjIuMDYyIEMxNC45NzMsMjIuMDYyIDEzLjcyOCwyMS4zNzkgMTMuMzAyLDIwLjU3MiBDMTMuMzAyLDIwLjU3MiAxMi42NDcsMjMuMDUgMTIuNDg4LDIzLjY1NyBDMTIuMTkzLDI0Ljc4NCAxMS4zOTYsMjYuMTk2IDEwLjg2MywyNy4wNTggQzEyLjA4NiwyNy40MzQgMTMuMzg2LDI3LjYzNyAxNC43MzMsMjcuNjM3IEMyMS45NSwyNy42MzcgMjcuODAxLDIxLjgyOCAyNy44MDEsMTQuNjYyIEMyNy44MDEsNy40OTUgMjEuOTUsMS42ODYgMTQuNzMzLDEuNjg2IiBmaWxsPSIjYmQwODFjIj48L3BhdGg+PC9nPjwvc3ZnPg==' because it violates the following Content Security Policy directive: "default-src 'self' blob:". Note that 'img-src' was not explicitly set, so 'default-src' is used as a fallback.

editor.construct.net/:1 Refused to load the image 'data:image/svg+xml;base64,PHN2ZyB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciIGhlaWdodD0iMzBweCIgd2lkdGg9IjMwcHgiIHZpZXdCb3g9Ii0xIC0xIDMxIDMxIj48Zz48cGF0aCBkPSJNMjkuNDQ5LDE0LjY2MiBDMjkuNDQ5LDIyLjcyMiAyMi44NjgsMjkuMjU2IDE0Ljc1LDI5LjI1NiBDNi42MzIsMjkuMjU2IDAuMDUxLDIyLjcyMiAwLjA1MSwxNC42NjIgQzAuMDUxLDYuNjAxIDYuNjMyLDAuMDY3IDE0Ljc1LDAuMDY3IEMyMi44NjgsMC4wNjcgMjkuNDQ5LDYuNjAxIDI5LjQ0OSwxNC42NjIiIGZpbGw9IiNmZmYiIHN0cm9rZT0iI2ZmZiIgc3Ryb2tlLXdpZHRoPSIxIj48L3BhdGg+PHBhdGggZD0iTTE0LjczMywxLjY4NiBDNy41MTYsMS42ODYgM...UuMDIyLDYuNDk3IEMxOS41NTUsNi40OTcgMjMuMDc4LDkuNzA1IDIzLjA3OCwxMy45OTEgQzIzLjA3OCwxOC40NjMgMjAuMjM5LDIyLjA2MiAxNi4yOTcsMjIuMDYyIEMxNC45NzMsMjIuMDYyIDEzLjcyOCwyMS4zNzkgMTMuMzAyLDIwLjU3MiBDMTMuMzAyLDIwLjU3MiAxMi42NDcsMjMuMDUgMTIuNDg4LDIzLjY1NyBDMTIuMTkzLDI0Ljc4NCAxMS4zOTYsMjYuMTk2IDEwLjg2MywyNy4wNTggQzEyLjA4NiwyNy40MzQgMTMuMzg2LDI3LjYzNyAxNC43MzMsMjcuNjM3IEMyMS45NSwyNy42MzcgMjcuODAxLDIxLjgyOCAyNy44MDEsMTQuNjYyIEMyNy44MDEsNy40OTUgMjEuOTUsMS42ODYgMTQuNzMzLDEuNjg2IiBmaWxsPSIjYmQwODFjIj48L3BhdGg+PC9nPjwvc3ZnPg==' because it violates the following Content Security Policy directive: "default-src 'self' blob:". Note that 'img-src' was not explicitly set, so 'default-src' is used as a fallback.

editor.construct.net/:1 Refused to load the image 'data:image/svg+xml;base64,PD94bWwgdmVyc2lvbj0iMS4wIiA/Pjxzdmcgd2lkdGg9IjI0cHgiIGhlaWdodD0iMjRweCIgdmlld0JveD0iMCAwIDI0IDI0IiB2ZXJzaW9uPSIxLjEiIHhtbG5zPSJodHRwOi8vd3d3LnczLm9yZy8yMDAwL3N2ZyIgeG1sbnM6eGxpbms9Imh0dHA6Ly93d3cudzMub3JnLzE5OTkveGxpbmsiPjxkZWZzPjxtYXNrIGlkPSJtIj48cmVjdCBmaWxsPSIjZmZmIiB4PSIwIiB5PSIwIiB3aWR0aD0iMjQiIGhlaWdodD0iMjQiIHJ4PSI2IiByeT0iNiIvPjxyZWN0IGZpbGw9IiMwMDAiIHg9IjUiIHk9IjUiIHdpZHRoPSIxNCIgaGVpZ2h0PSIxNCIgcng9IjEiIHJ5PSIxIi8+PHJlY3QgZmlsbD0iIzAwMCIgeD0iMTAiIHk9IjAiIHdpZHRoPSI0IiBoZWlnaHQ9IjI0Ii8+PHJlY3QgZmlsbD0iIzAwMCIgeD0iMCIgeT0iMTAiIHdpZHRoPSIyNCIgaGVpZ2h0PSI0Ii8+PC9tYXNrPjwvZGVmcz48cmVjdCB4PSIwIiB5PSIwIiB3aWR0aD0iMjQiIGhlaWdodD0iMjQiIGZpbGw9IiNmZmYiIG1hc2s9InVybCgjbSkiLz48L3N2Zz4=' because it violates the following Content Security Policy directive: "default-src 'self' blob:". Note that 'img-src' was not explicitly set, so 'default-src' is used as a fallback.

editor.construct.net/:1 Refused to load the image 'data:image/svg+xml;base64,PD94bWwgdmVyc2lvbj0iMS4wIiA/Pjxzdmcgd2lkdGg9IjI0cHgiIGhlaWdodD0iMjRweCIgdmlld0JveD0iMCAwIDI0IDI0IiB2ZXJzaW9uPSIxLjEiIHhtbG5zPSJodHRwOi8vd3d3LnczLm9yZy8yMDAwL3N2ZyIgeG1sbnM6eGxpbms9Imh0dHA6Ly93d3cudzMub3JnLzE5OTkveGxpbmsiPjxkZWZzPjxtYXNrIGlkPSJtIj48cmVjdCBmaWxsPSIjZmZmIiB4PSIwIiB5PSIwIiB3aWR0aD0iMjQiIGhlaWdodD0iMjQiIHJ4PSI2IiByeT0iNiIvPjxyZWN0IGZpbGw9IiMwMDAiIHg9IjUiIHk9IjUiIHdpZHRoPSIxNCIgaGVpZ2h0PSIxNCIgcng9IjEiIHJ5PSIxIi8+PHJlY3QgZmlsbD0iIzAwMCIgeD0iMTAiIHk9IjAiIHdpZHRoPSI0IiBoZWlnaHQ9IjI0Ii8+PHJlY3QgZmlsbD0iIzAwMCIgeD0iMCIgeT0iMTAiIHdpZHRoPSIyNCIgaGVpZ2h0PSI0Ii8+PC9tYXNrPjwvZGVmcz48cmVjdCB4PSIwIiB5PSIwIiB3aWR0aD0iMjQiIGhlaWdodD0iMjQiIGZpbGw9IiNmZmYiIG1hc2s9InVybCgjbSkiLz48L3N2Zz4=' because it violates the following Content Security Policy directive: "default-src 'self' blob:". Note that 'img-src' was not explicitly set, so 'default-src' is used as a fallback.

editor.construct.net/:1 Refused to load the image 'data:image/svg+xml;base64,PHN2ZyB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciIGhlaWdodD0iMzBweCIgd2lkdGg9IjMwcHgiIHZpZXdCb3g9Ii0xIC0xIDMxIDMxIj48Zz48cGF0aCBkPSJNMjkuNDQ5LDE0LjY2MiBDMjkuNDQ5LDIyLjcyMiAyMi44NjgsMjkuMjU2IDE0Ljc1LDI5LjI1NiBDNi42MzIsMjkuMjU2IDAuMDUxLDIyLjcyMiAwLjA1MSwxNC42NjIgQzAuMDUxLDYuNjAxIDYuNjMyLDAuMDY3IDE0Ljc1LDAuMDY3IEMyMi44NjgsMC4wNjcgMjkuNDQ5LDYuNjAxIDI5LjQ0OSwxNC42NjIiIGZpbGw9IiNmZmYiIHN0cm9rZT0iI2ZmZiIgc3Ryb2tlLXdpZHRoPSIxIj48L3BhdGg+PHBhdGggZD0iTTE0LjczMywxLjY4NiBDNy41MTYsMS42ODYgM...UuMDIyLDYuNDk3IEMxOS41NTUsNi40OTcgMjMuMDc4LDkuNzA1IDIzLjA3OCwxMy45OTEgQzIzLjA3OCwxOC40NjMgMjAuMjM5LDIyLjA2MiAxNi4yOTcsMjIuMDYyIEMxNC45NzMsMjIuMDYyIDEzLjcyOCwyMS4zNzkgMTMuMzAyLDIwLjU3MiBDMTMuMzAyLDIwLjU3MiAxMi42NDcsMjMuMDUgMTIuNDg4LDIzLjY1NyBDMTIuMTkzLDI0Ljc4NCAxMS4zOTYsMjYuMTk2IDEwLjg2MywyNy4wNTggQzEyLjA4NiwyNy40MzQgMTMuMzg2LDI3LjYzNyAxNC43MzMsMjcuNjM3IEMyMS45NSwyNy42MzcgMjcuODAxLDIxLjgyOCAyNy44MDEsMTQuNjYyIEMyNy44MDEsNy40OTUgMjEuOTUsMS42ODYgMTQuNzMzLDEuNjg2IiBmaWxsPSIjYmQwODFjIj48L3BhdGg+PC9nPjwvc3ZnPg==' because it violates the following Content Security Policy directive: "default-src 'self' blob:". Note that 'img-src' was not explicitly set, so 'default-src' is used as a fallback.

editor.construct.net/:1 Refused to load the image 'data:image/svg+xml;base64,PHN2ZyB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciIGhlaWdodD0iMzBweCIgd2lkdGg9IjMwcHgiIHZpZXdCb3g9Ii0xIC0xIDMxIDMxIj48Zz48cGF0aCBkPSJNMjkuNDQ5LDE0LjY2MiBDMjkuNDQ5LDIyLjcyMiAyMi44NjgsMjkuMjU2IDE0Ljc1LDI5LjI1NiBDNi42MzIsMjkuMjU2IDAuMDUxLDIyLjcyMiAwLjA1MSwxNC42NjIgQzAuMDUxLDYuNjAxIDYuNjMyLDAuMDY3IDE0Ljc1LDAuMDY3IEMyMi44NjgsMC4wNjcgMjkuNDQ5LDYuNjAxIDI5LjQ0OSwxNC42NjIiIGZpbGw9IiNmZmYiIHN0cm9rZT0iI2ZmZiIgc3Ryb2tlLXdpZHRoPSIxIj48L3BhdGg+PHBhdGggZD0iTTE0LjczMywxLjY4NiBDNy41MTYsMS42ODYgM...UuMDIyLDYuNDk3IEMxOS41NTUsNi40OTcgMjMuMDc4LDkuNzA1IDIzLjA3OCwxMy45OTEgQzIzLjA3OCwxOC40NjMgMjAuMjM5LDIyLjA2MiAxNi4yOTcsMjIuMDYyIEMxNC45NzMsMjIuMDYyIDEzLjcyOCwyMS4zNzkgMTMuMzAyLDIwLjU3MiBDMTMuMzAyLDIwLjU3MiAxMi42NDcsMjMuMDUgMTIuNDg4LDIzLjY1NyBDMTIuMTkzLDI0Ljc4NCAxMS4zOTYsMjYuMTk2IDEwLjg2MywyNy4wNTggQzEyLjA4NiwyNy40MzQgMTMuMzg2LDI3LjYzNyAxNC43MzMsMjcuNjM3IEMyMS45NSwyNy42MzcgMjcuODAxLDIxLjgyOCAyNy44MDEsMTQuNjYyIEMyNy44MDEsNy40OTUgMjEuOTUsMS42ODYgMTQuNzMzLDEuNjg2IiBmaWxsPSIjYmQwODFjIj48L3BhdGg+PC9nPjwvc3ZnPg==' because it violates the following Content Security Policy directive: "default-src 'self' blob:". Note that 'img-src' was not explicitly set, so 'default-src' is used as a fallback.

sw.js:276 [SW-Offline] Up to date

markbellharmony commented 6 years ago

@AshleyScirra Should this be submitted as a separate bug?

AshleyScirra commented 6 years ago

The last provided project is corrupt for the same reason (wrong image sizes), as well as also incorrectly duplicating an image ID.

I have never seen anybody else reporting issues like this. Given that you mentioned you are using GitHub as source control, which could corrupt projects if incorrectly merged/updated, I strongly suspect you are doing something with source control that is corrupting your project.

It is absolutely critical to get steps to reproduce the problem in the first place. We need a list of instructions to follow that starts with a working project, and ends with a broken project. Without that all I can see is a corrupt project and it's a mystery how it ended up like that, because Construct should never save such a project. Presumably something else (source control) is corrupting the project.

Even if you get the steps, they may simply outline how to use source control to corrupt a project. This means the problem isn't with Construct, it would be to do with how you are using source control.

markbellharmony commented 6 years ago

@AshleyScirra First, thank you so much for all the work and thought you have put into this issue.

I am using git hub and have been using it for 2 years with no problems with this particular project. What is weird is that this version of the project is a branch from the original that had no large files in it at all.

Also I am using github in the the most basic of ways. Just check in and update. No merges, branches or anything that is difficult.

Is there any way to save this project and do you have a suggestion for an alternative version control?

M

AshleyScirra commented 6 years ago

Source control is all in principle the same and probably equally easy to corrupt the project. I'd rather not comment further before we properly understand how this is happening.

markbellharmony commented 6 years ago

@AshleyScirra ok I didn't mean to piss you off. All I did in the latest version was:

  1. Normal construct functionality.
  2. Import images using construct. nothing larger than 128x128
  3. Resize within construct.
  4. Save in construct.
  5. Check in and push to origin.

I never merge or used another machine or version of construct. After check in I go back to construct and open the file and I get the corruption message.

I am so sorry I have upset you. I never meant any offense.

AshleyScirra commented 6 years ago

I'm not upset, I'm just trying to work out what the root cause is, like we do with all bug reports. I need specific steps to reproduce that I can follow though, I can't follow an instruction like "normal construct functionality", there is no chance I can be following what you're doing with that.

markbellharmony commented 6 years ago

@AshleyScirra Sorry I offended you. I'll take care of this and you can close the issue.