window size and optimization

Discussion and feedback on Construct 2

Post » Mon Mar 03, 2014 8:14 pm

I didn't know if some threads weren't being used anymore. This is so frustrating because in the manual it clearly says Window Size makes no difference to performance, but it evidently does. If I had used a small window size from the beginning the game would have run fine on the MAC.
I don't know why it works like this, it shouldn't increase the resolution to have it full screen. If you have a small window full screen, the resolution still looks just as good but it runs the game much better, even though the actual game objects are the same resolution in both situations!
B
8
S
1
Posts: 16
Reputation: 1,188

Post » Mon Mar 03, 2014 10:24 pm

@Ashley

I also don't understand how C2's scaling works and how GPU intensive is ...

So I work with Window size of 1280x720 and with high-resolution sprites (if I need a sprite of 50x50, I will use one of 100x100).

How will it scale at 1920x1080 regarding visual quality and GPU with and without HighQuality ? (compared to 1280x720)

Also how will the performance be at 640x360 ? It is the same as 1280x720 or will use less resources ?
B
49
S
15
G
6
Posts: 535
Reputation: 7,197

Post » Mon Mar 03, 2014 10:43 pm

The 'Window size' project property is poorly named. It should be called the 'Viewport size'. (I don't think we will change it because other expressions and a lot of documentation refer to the same name.) It just sets how much of the layout you can see.

When the game is actually displayed at runtime, the size it ends up on your screen is the display size. For example you could have a 'window size' of 854x480 and use letterbox scale mode to display it at 1920x1080. In that case the viewport to the layout is 854x480 and the display size is 1920x1080.

In 'High quality' fullscreen mode, in practice only the display size affects performance. Note if you run a game in a browser window, you can resize the browser smaller and notice it's running faster. This is because the display size is smaller, so there's less GPU work. The project viewport is still the same (i.e., the project 'Window size' property has not changed, even though you resized the browser window. I do regret choosing that name for the project property!)

In 'Low quality' fullscreen mode, the game is rendered at the 'Window size' in project properties, and the result simply stretched up to fit the screen. Usually the stretch is fast and the performance impact can be ignored, so the display size is effectively the same as the viewport size. Since the viewport size is usually smaller than the display size, this improves performance.

In no case has the memory use changed. The viewport and display size do not affect the textures that are loaded to memory, which are always fully decompressed images at their original size they appear in the image editor.
Scirra Founder
B
399
S
236
G
89
Posts: 24,546
Reputation: 195,436

Post » Mon Mar 03, 2014 11:18 pm

Use "low quality" mode if you won't no difference between window/fullscreen.
B
151
S
75
G
20
Posts: 1,793
Reputation: 22,749

Post » Tue Aug 23, 2016 11:01 pm

Thanks for all this information I was wondering too. I'm still trying to be sure of some details :

If low resolution isn't a problem, I read you can improve memory using very small textures for sprites, let's say 8x8.
And lets say we use a small window size (fullscale quality low) and they appear big on screen, with low resolution.

Small textured sprites 8x8 reduce loading at start, for sure, but will it also improve the CPU / FPS, or is it just a matter of number of elements ?

Also, according on how are working plugin like custom movement, will it be exactly the same if I use a 320x200 window size + 320x200 layout, with 8x8 sprites (and globaly reduced pixel values)
or a 1600x900 window size / layout with the same 8x8 textures but sprites resized to appear big ?
B
8
S
4
Posts: 131
Reputation: 1,205

Previous

Return to Construct 2 General

Who is online

Users browsing this forum: Yahoo [Bot] and 5 guests