Thanks for the feedback!
That project appears to mix up the 3DTexture sprite with 3DShape and 3DShape2. If you need two 3D shape object types, try having both use containers with their own sprite controlling animations.
This style splash screen is now imposed by Android. See their design guidelines.
Put the sprite used for 3D shape's faces in a container with 3D shape. Then each 3D shape has its own sprite instance to go with it, and it will use the current animation frame of its own sprite instance. So then you can control the face images independently by controlling each of the sprite instance's animations independently.
The editor can't evaluate dynamic expressions. At the moment if you use any kind of dynamic expression to refer to something by name, then the editor can't figure out if it's relevant to your search or not, and so lists it as an ambiguous result.
Please note suggestions posted in this forum thread will not be considered. See the details in the original post.
Some devices still have a hardware limit that means the maximum size image they can handle is 4096x4096. However many devices should now be able to handle up to 8192x8192. Beyond that it will likely only be supported on high-end discrete GPUs.
This thread is duplicating the discussion in the corresponding GitHub issue where I already responded to that question.
FWIW, the handling of the splash screen is part of Cordova, not Construct.
Develop games in your browser. Powerful, performant & highly capable.
Yes, the fact that drawing transparency still consumes fill rate is true no matter the way the drawing happens. It's a fact about computer graphics in general.
Try removing any third-party addons the project uses and see if that solves the problem. If it does, the problem is with the third-party addon and you'll need to report it to the addon developer. If it still happens with no third-party addons, please file an issue following all the guidelines.
From the bug report FAQ:
Why haven't you responded to my bug report yet? We do look at every report, but developer and release schedules mean we may not get round to it immediately. Please allow a few weeks for it to be investigated. If you are waiting, you can improve the chance it is resolved when a developer does get round to it by carefully reviewing these guidelines and providing as much useful information about the problem as possible. If you are missing anything, you may end up waiting a few weeks for a reply simply asking for the missing information, and then you're back to waiting again.
Why haven't you responded to my bug report yet?
We do look at every report, but developer and release schedules mean we may not get round to it immediately. Please allow a few weeks for it to be investigated. If you are waiting, you can improve the chance it is resolved when a developer does get round to it by carefully reviewing these guidelines and providing as much useful information about the problem as possible. If you are missing anything, you may end up waiting a few weeks for a reply simply asking for the missing information, and then you're back to waiting again.
Member since 21 May, 2007
The official blog for all things Construct and Scirra run by our employees!
Wider technology issues from Ashley's perspective.