I'll be there. My first year going. I'm pretty pumped.

Bahhhh! Not the answer I was hoping for but I understand.

Two questions though. First off I was hoping I could disable the effect and only re-enable it when the system running the game is not WP8.1. I tried this but it still crashes even if the effect is disabled on start. I'm guessing this has to do something with compiling the shaders? Are there any ways you can think around this so I can still maintain one codebase?

Second question is will you be submitting a bug report for this? If not do you know where I can submit and what information I should include in the ticket?

Thanks!

Problem Description

When adding an HSL shader effect on Windows Phone 8.1 it causes the engine to crash upon startup. It doesn't matter if the effect is on a layer or on an individual sprite. This error did not occur on Windows phone 8.0 since effects via WebGL were not supported

Description of Capx

The Capx has two spirtes and a HSL effect on a single layer.

Steps to Reproduce Bug

• Run the attached Capx on Windows Phone 8.1

Observed Result

An error with a stack trace is immediately thrown followed by a second error. Attached below:

Expected Result

The two sprites to be show with the values of the HSL shader reflected on the layer.

Affected Browsers

• Chrome for Android: (NO)
• Chrome: (NO)
• Internet Explorer on Windows 8.1: (NO)
• Internet Explorer on Windows Phone 8.1: (YES)

Operating System and Service Pack

Windows Phone 8.1 - Lumia Denim

Construct 2 Version ID

r190

P.S. Side note. I tested a number of other shaders on WP8.1 and the half dozen I tried worked great.

Thanks!

TiAm Have you reported your issue to the Chrome Devs or on Chrome bug reports Ashley opened? It would suck if they simply didn't know about the issue and the bug made it into a release.

Hey all,

Personally I'm thinking this an oversight but I'm curious to see what Ashley and others think. But, I must say having global layers is a complete joy! Thanks for implementing them.

I'm trying to dynamically turn off/on effects on a Global Layers but I found out there isn't an expression that lets you get a layer's index by passing in it's name. It think this is much more important now that we have Global Layers. With Global Layers we may have the same layer names, but they could be in a completely different order on each layout. Without being able to get the layer's index at runtime it invalidates some of the dynamic nature of Global Layers.

What I'm proposing is an expression as follows: GetLayerIndex(String layerName).

Description: "Get the current index of the layer with the name that was passed into the function. If the layer with that name does not exist the expressions returns null( or -1).

Thanks!

p.s. I think I could write a plugin that would provide me this but I really feel like this should be an engine feature.

Nice! So I could use the midpoint of all object centers as the centerX and centerY? Thanks!!!

R0J0hound Do you know any way of emulating the functionality of "wrap selection" during runtime? I had a physics game I stopped worked on because I couldn't figure out how to scale the compound object like "wrap selection".

Thanks!

cranberrygame Any chance you'll add your plugins to the New Scirra Store? I'd love to see them up there and I bet you'd get a lot more views/sales.

Keep me posted! Thanks!

Standard shortcut. Makes sense +1

Sorry to necropost this suuuuuuuper old topoic . Ashley Do you think it's feasible to be able add tagging joints so we can destroy specific ones like mentioned above?

If not I can use the workaround mentioned in the physics manual page. Thanks!

[I saw this post when I was searching to see if this was possible. Which is why I necro'd rather than posting a new one]

Beta 169 Notes:

[quote:1ooqb7w5]Add

AJAX: new 'method' parameter in 'Post' action, so you can specify other methods like PUT, DELETE, etc.

Thanks Ashley!!! Nice you know you got my back.

DERP (I need to go to bed). Well I see that "Request URL" will get me the GET I was looking for but I think I still may have to create a workaround for DELETE. Unless someone has an idea.

Could I possibly use the execute JavaScript action?