UPDATE (5/7/14)

Alright guys, decided to upgrade this utility, now being designated as HTML5 ResUtil. It has a good deal more functionality and can help give measurement information for knowing how much filler UI you will need for different aspect ratios, as well as now allowing you to designate your game resolution for testing. Not to mention portrait and landscape are both working under one utility now for ease of testing!

Click the banner below to launch.

Let me guys know what you think!

ORIGINAL POST

[quote:2s2l14aa]Hey guys,

We are in the first leg (week) of development on our new game, and I ran into the same problem we all do: Resolution and aspect ratio.

Since we are programming for different devices and different platforms (native HTML5, iOS, android, etc) we need to be able to account for software bars as well device native screen resolutions.

I've hobbled together some sort of basic utility to help me test how a game in different aspect ratios might scale (focus on DPI) and where I can expect black bars to show up, and I thought I'd post here in case anyone else can get use of it or use it as a foundation.

Speaking of which, this is a modified version of some scaleRatio code I found on these forums about 12 months ago, so I don't remember the original author , but thank you mystery man.

USAGE

Just load the program via web browser onto your device, then make note of the information you get per device. I recommend screen capture on the device if you want to save for reference later.

The utility works best if you stretch the window to allow empty space past 16:9 on the left and right in landscape mode, and on the top and bottom in portrait (may not work on most screens very well due to reduction of text size, but will work great if you have a flipped monitor! )

If you notice anything busted or misconfigured, let me know and I'll try to fix it.

HTML5 ResUtil

NOTES

• There may be minor discrepancies of 1-2px either visually, or represented in the information panel.
• Each box includes it’s border as a representation of it’s aspect ratio. This means the game screen box will overlap the borders when matching aspect ratios.
• The utility will automatically switch between portrait and landscape orientations (if height exceeds width in landscape, or width exceeds height in portrait).
• The orientation label also works as a button.

SCREENSHOTS

Landscape - Google Chrome, PC (windows)

Landscape - Safari, iPhone 5S (iOS)

Portrait - Safari, iPhone 5S (iOS)

Sigmag here. Educational apps might not be a primary focal point of most C2 developers, but it goes to show how flexible the engine can be.

Really happy to have our first product in the wild.

I'm working with clrammer on the same project, and we also have issues with sound delay on the tizen platform. Anyone else with a Tizen device having issues of this nature?

As an addendum to the above post, is there anyway to interact with the Tizen virtual keyboard API through C2? I think right now we are leaning towards making our own in-app keyboard to circumvent this issue in time for the App Challenge.

ErekT

It doesn't happen on all sprites, and it's not always consistent on the sprites it does happen to.

So far it's done this with horizontal blur, set color and tint. I'm assuming it does it for every effect.

I tried re-sizing the image to match a sprite that isn't having this problem (no change) and I just cut out half of the sprite in different parts of the image to change it to see if it made a change, and the line is the same.

szymek

Was ludei able to help you with your issue?

No such luck :

It only appears when applying a webGL effect, the line doesn't show up on the sprite otherwise.

How can I address the texture bleeding of a webGL effect?

<img src="http://i.imgur.com/YEENUlx.png" border="0" />

Hey guys,

We are pulling our hair out trying to figure out what might cause the problem we are having.

Essentially every time we apply any webGL effect to a sprite, we get a 1px line beneath the sprite, and in some cases to the left/top/right as well.

It only happens when we export through CJS; this issue does not happen in chrome.

I've attached a couple of screenshots, but I can't include a capx because we are about 90% done with development.

Just trying to narrow down the possibilities, and since this doesn't happen with a new capx it's likely something in our logic. However, we have 2500 events and hundreds of variables, so if anyone knows a good place to start that'd be fantastic.

<img src="http://i.imgur.com/lzrjuk2.jpg" border="0" />

<img src="http://i.imgur.com/Y9RPzsv.png" border="0" />

Couple of things we've tried:

? Putting a wait before enabling the effect (This helps alleviate the issue on SF, but not completely, does not work on other sprites)

? Turning on pixel rounding - no dice

R0J0hound

So the memory leak fix in your latest update doesn't address canvas copying to webgl texture? I take it that a proper fix would require a code overhaul with a large time commitment on your part?

R0J0hound

Let me preface by saying thank you for this plugin, it's a great asset!

I'm working with clrammer on the same project, and we are both psyched to see an update to address the performance hit introduced with CJS 1.4.

We haven't seen a difference in performance, but we are probably missing something since it works for others.

2 Questions:

1) Was just wondering if minifying the script is necessary for the performance fix? I don't see why it would, but worth asking.

We haven't been using it (or able to use it) because of conflicts during export with 64-bit java, and due to our lack of understanding of the minifying process we just kind have been forgoing that aspect.

2) What operating systems / devices do you personally test on? In what capacity have you tested iOS?

I'm sure we are probably overlooking something at this point, just trying to identify what it is.

SirSpunky

What operating systems / devices are you testing on that you noticed the performance gain?

Notice any improvements otherwise? My android 1.4 right now works better than iOS 1.4 as far as layout loading and avoiding hang. Im kind of scared to update! Also how long can we expect for a 1.4.1 on iOS assuming theyve put the update in for apple to process? I hope it works better so we can keep on track with our release date!

Also, anyone else having problems with android 1.4 crashing randomly and becoming unable to launch without app reinstall? Its annoying when it happens every time i launch :S. very time consuming