deviever, thank you for posting your timescale solution. It makes sense that that would work. I'm now thinking of throwing that into my current game as well.

Yeah, I've experienced those problems too.

And, I just want to make sure everybody else that may read this knows that there are always tradeoffs in deciding what to work on. If the Scirra duo works on website, then less time will be put into C2 updates, and vice versa.

We (the community) aren't in charge of the updates, but if there was a poll, then I think many people would like to prioritize a few website features over C2 features. Also, that poll would be very biased in favor of the frequent forum users, who feels the affects more than the majority of C2 users who don't use the forums.

Fun game. Here's a few things to consider.

• Most of C2 games runs on the GPU. Those screen recording tools likely run on the GPU also. So, they would affect each other.
• Have you properly set the collision polygon? (When you double-click on a sprite, the bottom-left tool/icon allows you to do this.)
• As you may know already, animations (like throwing knives) are not perfectly smooth. They are typically around 30 or 60 frames/images per second. For each frame, the location of the knife is calculated and sometimes it skips quite a few pixels. The moving sprite will skip more pixels the faster it is moving, and the slower the frames per second (fps) is. Sometimes, so many pixels are skipped that the knife sprite will go all the way through the wall.

Having said all that, I think it's a good game. I wouldn't have called that a bug where the knives going inside the blocks. But, I didn't try it on a "slow" machine either.

Since nobody has directly linked to it yet, here's the official search (read: public records) for United States registered trademarks.

http://tmsearch.uspto.gov/ (then click "Basic Word Mark Search")

It's known as TESS (Trademark Electronic Search System). And before starting a company, website, or even pseudo-company, in the US, I'd suggest doing a quick search to see if the name is taken or not. It will just prevent possible future complications.

I'm glad I saw this thread. I was just about to post, suggesting the ability to change timezones. Though, yeah, the bug you mentioned Joannak is bigger than mine.

I'm just glad to hear that Ashley and Tom at least know about it. I understand what it's like to work with large code bases.

Though... if there was a thread about known issues, then that would be great too.

jayderyu, definitely a creative idea. My first idea/response for this was that a great community-effort plugin could be created and everybody here just adding their own devices. But, I'm sure this information is already out there somewhere, we just have to find it and make an API call to it.

RamPackWobble, good idea, I was thinking of something like that also. Maybe we would ask users to choose a circle the think closest to one inch (or roughly 2.54cm). Or, expanding on that, it might be good enough to just label the range of circles from easy to hard, if a game could be formed like that.

JohnnySheffield, it looks like a great website. It probably works most of the time, but didn't for me. I have a dual-monitor setup (16 inch laptop, 24 inch monitor) and the results got the pixel count right for each screen, but said both were only 13.3 inches.

Even after seeing these great ideas, I still feel that there are more possibilities out there. I just haven't thought about them yet. I'm interested in all possibilities, no matter how easy/difficult they may be to implement.

In C2, how would you keep sprites the same physical size across different sized devices?

Example: I have a game that I want to run on Windows 8 and Windows Phone 8. They obviously have different screen sizes, but I would still like a certain sprite to appear about one centimeter in diameter on both devices.

I've looked in the FAQs, manual, and search, but haven't found a suitable method yet, besides manually scaling the sprites depending on the platform. I was hoping for a much more accurate method, like getting the physical screen size of the "browser"/device. Or, possibly even getting a pixel density. The Browser object/plugin has a `DevicePixelRatio` (the display pixels per CSS pixel), but that wouldn't seem to work because a phone device can have the exact same number of CSS pixels as a laptop.

Anybody know any workarounds for maintaining the same final-sized sprite better than adjusting size of sprite depending on platform?

One more note, I'm using the "Scale Outer" scaling mode. Not sure if that is helpful or not.

RamPackWobble, wow, these are great examples! I wasn't even aware that C2 could do this.

Thank you very much for sharing tutorials and example code also!

Link to .capx file (required!):

[Not needed nor helpful, but I do have helpful screenshots below]

Steps to reproduce:

1. Open C2/WP8 file located at C2\exporters\html5\wp8\MainPage.xml

2. In the top-level tag, the following code is always set to true, rather than being a variable so that it can change between true and false.

Observed result:

<font face="Courier New, Courier, mono">shell:SystemTray.IsVisible="True"</font>

This causes an extra side in apps to always have a "black bar" where the system tray would be.

(Using a letterbox scale)<img src="http://simplyadvanced.net/dev/construct2/bug/SystemTray-IsVisible-True.png" border="0" />

Expected result:

I would expect the gameplay area to use up more of the screen when I choose a fullscreen scaling option. So, when I change WP8 code to

<font face="Courier New, Courier, mono">shell:SystemTray.IsVisible="False"</font> ...

(Using a letterbox scale)

<img src="http://simplyadvanced.net/dev/construct2/bug/SystemTray-IsVisible-False.png" border="0" />

Browsers affected:

Chrome: n/a

Firefox: n/a

Internet Explorer: n/a

Operating system & service pack:

Windows 8.1 Enterprise, 64-bit

Construct 2 version:

Tested in r154, r155, 156

• Danial Goodwin -

ps - I'm not sure if it is in the WP8 guidelines, that the status bar always has to be visible. But, my past three WP8 apps have been certified/published on the first try with `shell:SystemTray.IsVisible="False"`. Also, this basically just the first method that I found that works for getting to fullscreen. There may or may not be more solutions.

Link to .capx file (required!):

dl.dropboxusercontent.com/u/554309/NewEmptyProject.capx (This is just a new empty project)

Steps to reproduce:

1. Create new empty project

2. Export to Windows Phone 8

3. In the exported project, open Properties\WMAppManifest.xml

Observed result:

In C2, my project properties title was "New project". If a user were to publish this app without changing anything, then their user-facing title would have been changed to "NewProject", aka your `[[[shortname]]]`.

Expected result:

I would expect that the title I set in C2 be carried over to WMAppManifest.xml in the parts that were end-user-facing.

I would like to propose that two places be changed in WMAppManifest.xml:

1. In the "App" tag, on the "Title" attribute.

2. In the "TemplateFlip" tag, in the "Title" tag.

Browsers affected:

Chrome: n/a

Firefox: n/a

Internet Explorer: n/a

Operating system & service pack:

Windows 8.1 Enterprise, 64-bit

Construct 2 version:

Tested with r154, r155, r156

Thank you for all your hard work,

• Dan -

ps - As I use the C2\exporters\html5\metro\package.appxmanifest as a guide, would this bug be as simple as replacing `[[[shortname]]]` with `[[[displayname]]]` or `[[[appdisplayname]]]`? Or, are there any other hidden complexities that I'm not seeing?

Link to .capx file (required!):

dl.dropboxusercontent.com/u/554309/CantApostrophe.capx

Steps to reproduce:

1. Create new empty C2 project

2. Set project properties title to something with an apostrophe, like "Can't Apostrophe"

3. Export to Windows Phone 8

4. Open project in Visual Studio

5. Try to "Deploy Solution", then the following errors are reported by Visual Studio:

<font face="Courier New, Courier, mono">

Description                        File      Project

x:Class="Can'tApostrophe.App" is not valid. 'Can'tApostrophe.App' is not a valid fully qualified class name.     C:\Users\Danial\Desktop\Can't Apostrophe\App.xaml     Can'tApostrophe

x:Class="Can'tApostrophe.MainPage" is not valid. 'Can'tApostrophe.MainPage' is not a valid fully qualified class name.     C:\Users\Danial\Desktop\Can't Apostrophe\MainPage.xaml     Can'tApostrophe

</font>

Observed result:

Errors in creating the namespace for the Windows Phone app.

Expected result:

I guess, users having an apostrophe in their titles shouldn't have to cause a problem for them after they export the project.

Additional Info:

• As I looked through the files in my "C:\Program Files\Construct 2\exporters\html5\wp8" directory, it appears that you have the placeholder `[[[shortname]]]` for the C2 project's title. You take out the spaces, but not the apostrophe (aka, single quote), and possibly other symbols.
• I found the documentation for a fully qualified namespace, "A qualifying namespace name is not a valid element name. A name must contain only alphabetic characters, decimal digits, and underscores, and must begin with an alphabetic character or underscore (_).". More info:

  msdn.microsoft.com/en-us/library/tb2h5dds(v=vs.90).aspx[/li]

Browsers affected:

Chrome: n/a

Firefox: n/a

Internet Explorer: n/a

Operating system & service pack:

Windows 8.1 Enterprise, 64-bit

Construct 2 version:

beta release r156

Yeah, DVLUP is a great program to earn lots of great prizes. I'm already enrolled in the program.