Ejecta export and contentScale issues

Problem Description

When exported to iOS using Ejecta, I get a contentScale issue because of which a blank screen appears on iPhone. on iPad the same app works. Here is the link where another person has hit the same issue and was checking with Ejecta team - There are also more details on why this issue might be happening on construct2 -

https://github.com/phoboslab/Ejecta/issues/441

Request Ashley to help if this is something that can be addressed within Construct2 as Phoboslabscl@Ejecta has suggested in the above link.

With WebGL off in C2, it works...with WebGL on, the issue is there.

Attach a Capx

Uploaded a very simple capx file

Description of Capx

WebGL on, 640 by 480 ( 4:3) aspect ratio for iPad.

Steps to Reproduce Bug

• Export this for Ejecta and run it on iPad. It runs because the aspect ratio matches that of iPad
• Export this for Ejecta and run it on iPhone. It gives contentScale error as described above and shows a blank screen on iPhone
• Step 3 etc.

Observed Result

Blank screen on iPhone. Please see description above. With WebGL off in C2, it works...with WebGL on, the comes up.

Expected Result

Please see this link for more details - https://github.com/phoboslab/Ejecta/issues/441

Affected Browsers

iOS - iPhone Operating System and Service Pack ____ Your operating system and service pack ____ Construct 2 Version ID r184 stable version

Closing as Ejecta is no longer officially supported as of r191, and the corresponding Ejecta issue was closed due to lack of information.

Closing as Ejecta is no longer officially supported as of r191, and the corresponding Ejecta issue was closed due to lack of information.

Ashley , I think you're too early abandoned Ejecta. Intel XDK not work correctly with applications for IOS. Intel XDK needs many improvements.

PhoneGap does not support applications more than 50 megabytes, which is also unacceptable. At the moment, there is no good way to make high-quality applications for IOS.

ilimi - please report any issues you have with the Intel XDK so we can fix them, it is definitely the better approach since it is based on a real browser engine and so shouldn't run in to problems like you have here.

Ashley Watch this topic, last post: https://forums.html5dev-software.intel. ... d&start=10

There I report an error.

In the Ejecta I can monitor memory and CPU consumption in xCode.

I understand that XDK is better, but it's still raw and I plan to produce their product using Ejecta.