It works great. I miss this post in the earlier day. Now got fixed. Thank you so much Jon and those who leave message here.

iPhone6/6s-Plus project size) . . . this is then downsampled (in hardware) on the device to 1920 x 1080.

Actually, i do not agree. It takes a lot of time and effort to find bugs. Some companies pay people to do the job. Its not easy.

I was gonna add that at some point but somehow it didn't make it on my list. Thanks again, @Socks

I notice you've set a number of conditionals so that the post to Game Center would fire. Ensure they are being met. From the looks of it, it should work, especially if GS is giving you the alert that

are all major bugs fixed ? or did you guys find new ones ? (Image)

When you set up scrolling text, you usually have a "window" actor that provides the border for the text area and then a "text" actor that actually displays the text

One other small thing, if you - for example - mute the music, and then start a game and realise you would rather have the music back on you cannot pause or exit the game in any obvious way, you need t

But then I fall into the problem of having an actor that becomes too big for the screen. Rather what I need to do is have an actor of specific size that you could scroll the text of which ever length

@jtadeo thanks! Also does the set up look right to you?

Was it Google services you find there? (Image)

Dang, @Socks - you don't miss much. I really do appreciate all the feedback though. I just cancelled the review of the update in order to address these issues. Thanks again.

they need to get 1.25 out the door, then I expect .exe exporting will follow shortly behind..... but if you game runs perfect under HTML5 you can use NodeJS to create an .exe wrapper. I've done it bef

The controls didn't quite feel right to me, most of all I didn't like the fact that tapping any of the 'fire' buttons doesn't immediately fire, instead you need to press the button and wait a fraction

Great stream you two. @Lost_Oasis_Games keep it up.

You'd have to go by actor size, probably. Work out how big an actor needs to be to show x lines.

i suppose I can work that out. Lot more work but we don't shy away from that! But even then, how would I manage the scrolling? Make it recognise the line of each entry and stop when it does get there

Now add a second interpolate behaviour and set it to interpolate the actor's Y position . . . we don't want the top of the actor to move, we want it to only grow from the bottom, so the centre of the

Here, I made you a picture that shows the pixels for Creator, Legacy and Retina.

I don't think you can do it dynamically - you need to know how many lines you're displaying each time. If you work that out and stick the number of lines in a table or something this becomes a lot eas