Pre-baking sprite sheets for faster preview?

Discussion and feedback on Construct 2

Post » Wed Sep 17, 2014 4:40 pm

@ashley If you do that too many times (usually 5 or so) NW will glitch up...instead of running the game a random, blurry, scaled up sprite from your project fills up the screen and flickers. Should I post a bug report or take it up with @rogerwang ?
Image
B
243
S
30
G
13
Posts: 1,787
Reputation: 18,770

Post » Wed Sep 17, 2014 7:12 pm

Ashley wrote:I think any speed up from spritesheeting on preview would be more than offset by the time spent building the spritesheets. Previewing is local so there is virtually zero latency and unlimited bandwidth, so I doubt there is much extra cost from having to make extra HTTP requests, plus most browsers can decode images in parallel on all CPU cores.

I'm not sure what you're seeing when you talk about slow preview: if you're seeing a progress bar in the Construct 2 editor, then it's most likely building the JSON data for the project, but if you're seeing a progress bar in the browser itself, then it's most likely downloading and decoding images (as well as sounds if you have 'preload sounds' enabled).

I find Node-webkit specifically can take a couple of seconds to start up, and you can avoid that by treating it like a browser - leave it open and press preview again in C2, and it will refresh the same instance of node-webkit rather than starting a new process.


I'm referring to the browser loading yeah. Main reason why I'm addressing the image decoding. Webkit and Chrome are both very slow decoding images. Firefox usually gets it done much quicker, but I often encounter firefox freezing consistently for around 15 seconds shortly after booting up before straightening up. Not sure if it's some kind of image loading delay?
B
33
S
10
Posts: 376
Reputation: 3,193

Previous

Return to Construct 2 General

Who is online

Users browsing this forum: kazdalugur and 10 guests