Done

dl.dropbox.com/u/10316081/Construct/Cards.capx

- WebGL transform : easy and fast. Works only on system with good WebGL support (no iOS and Android). However I pokked around C2's structure, and I have no way to grab the WebGL canvas as a texture. Perhaps Ashley can provide me a hint here ?

There's actually a way right now to get a mode7-esk effect with WebGL effects. Specifically by using the lens effect with a linear gradient over the thing(s) you want to transform. However, because of the monkey rigged way it's done, the result is mostly useless for actual games.

<img src="https://dl.dropbox.com/u/10316081/pics/Capture.PNG" border="0" />

So yeah, I think a Webgl effect might be your best bet right now.

Thank you very much sir.

---------------------------

Construct 2 Check failure

---------------------------

Check failure! This is probably a bug:

Getting event sequence number from event without one assigned

Condition: sequence_number != 0

File: Projects\Event.cpp

Line: 30

Function: unsigned int __cdecl Event::GetEventSequenceNumber(void) const

Build: release 80 (64-bit) checked

Component: Construct 2 IDE

(Last Win32 error: 0)

You are using a 'checked' release of Construct 2, intended for testing, which causes certain errors to be reported this way. Hit Ctrl+C to copy this messagebox - it's useful information for the developers, so please include it with any bug reports! Click 'Abort' to quit (unsaved data will be lost!),'Retry' to turn off messages for this session and continue, or 'Ignore' to continue normally.

---------------------------

Abort   Retry   Ignore   

---------------------------

Just got something similar when I added an Event Sheet Include

Is there any way to get access to the Z-buffer data for use in things like effects?

Started messing around with particles and got a rather trippy result.

dl.dropbox.com/u/10316081/Construct/funwithparticles.cap

Heads up multiple particles and effects use. May run slowly on some computers.

Yeah...I have no idea.

This plugin was made way back at Revision 33 (Current: 76), and was mostly me just screwing around with a code I had next to no idea how to use. I'm guessing since then, a few things may have changed with Construct 2.

I'll try giving it a look sometime this week, but the only way I could really see myself "fixing" this would be to, gut the mouse plugin again, and remake the plugin. Which I currently do no have a lot of time to do.

My sincerest apologizes

If anyone else would like to jump in, be my guest. Wouldn't be surprised if it was something really simple.

Haven't messed around with the physics in C2 much. But I know in CC,you could check at the point of explosion the distance and angle of each block from it, and then apply force in the opposite direction in comparison to how close the block was and that would get a decent looking result.

So in other words doing:

<color=red>Enter</color>

<color=green>Exit</color>

will not work. I in fact have to create multiple text objects to create the effect that I want. Well this makes it a bit difficult.

There is an HTML object, if you feel like toying around with that.

Could you post or send the cap? I have a small hunch what it might be, although I'm still somewhat of a novice and can't really tell just from the errors.

Not bad. I survived 34 seconds.

Bug: If an enemy passes you and the music starts to slow, if another one passes you the slowdown resets.

Suggestion: Mouse control, should be easy if you get the mouse's angle from the center.

> By all means post it

cap

(using Yarfapets 3D python example)

I changed the layout and window to 800x600, so it might be a bit slower?

Nice, a few simple changes can do so much. Even with the resolution bump I'm still getting more than 2.5x the speed I was getting before (200-250fps average).

One quick note though, the formulas used are resolution dependent.

WorldObj[n].X=WorldObj[n].X+320 (Should be half the horizontal res)

WorldObj[n].Y=WorldObj[n].Y+272* (Should be half the vertical res)

In this case

WorldObj[n].X=WorldObj[n].X+400

WorldObj[n].Y=WorldObj[n].Y+300

*Yeah, I just realized I screwed that up too