R170 Sprites disappear after export in Safari

Post reply

❤Follow Topic(2)

0 favourites

3 posts

From the Asset Store

Gif

Pixel Magic Sprite Effects

$3.99 USD

A set of 10 pixel art animated magic effects with icons. 2 Fire, 2 Earth, 2 Wind, 2 Water, Portal, Explosion.

FoozleCC

- tecbug
- - Joined 30 Oct, 2008
  - 105 topics • 287 posts
- 1
- 31 May, 2014
- Quote
Problem Description

Sprites disappear in Safari after export.

Test game: https://dl.dropboxusercontent.com/u/176 ... index.html

Try on different browsers - only safari shows blank white.

Attach a Capx

https://dl.dropboxusercontent.com/u/176 ... test1.capx

Description of Capx

Contains any sprites

Steps to Reproduce Bug
- Step 1 - Open CAPX
- Step 2 - preview in safari (all sprites are visible)
- Step 3 - export to HTML 5 Website
- Step 4 - open exported game in safari
Observed Result

Sprites aren't visible

Expected Result

They should be

Affected Browsers
- Chrome: (NO)
- FireFox: (NO)
- Internet Explorer: (NO)
- Safari: (YES)
Operating System and Service Pack

Win 7 (Macs probably also affected)

Construct 2 Version ID

r170 (64-bit)
Try Construct 3

Develop games in your browser. Powerful, performant & highly capable.
Try Now Construct 3 users don't see these ads
- tecbug
- - Joined 30 Oct, 2008
  - 105 topics • 287 posts
- 1
- 31 May, 2014
- Quote
I've also noticed very bizarre behaviour in sprite displaying in other games exported in r170.

Please take a look at this game: https://dl.dropboxusercontent.com/u/176 ... index.html

It looks OK in other browsers, but on Safari doesn't.

Games exported in R168 doesn't have this problem.
- Ashley Construct Team Founder
- Moderator
- - Joined 21 May, 2007
  - 669 topics • 30,362 posts
- 1
- 2 Jun, 2014
- Quote
I can reproduce from your link on iOS 7.1, but when exporting with my latest dev copy and hosting on our own server it appears to work (see http://www.scirra.com/labs/safaritest). I think this is either a Dropbox hosting issue or a bug we've already fixed. Closing, let me know if there's still an issue after the next build.