I thought so too so I tried in a new .cap, it looks like I created it just like you (minus the mouse behavior) then again probably not, considering it is working on your side. :P

Have a look if you can;

dl.dropbox.com/u/38319441/CollisionTest2.cap

infinite thanks!

Hello and thanks!

I'm a bit ashamed to ask for something that simple but it must be escaping me, I've been searching a long time and I don't know how to figure it out anymore; why aren't collision detections working when two sprites are flagged solid? All I have is;

On collision between Sprite1 and Sprite2

-> Destroy Sprite2

Sprite1 has the platformer behavior. I just want to hit a block with my head and destroy it. It works when one object is not flagged solid but that kind of defeats the purpose...

So in the meantime I placed a sensor on my character's head and all i'm using is overlapping detection, but that's a weird contraption when all I need is a collision detection from beneath the block.

I'm lighting a candle. Thanks a lot!

Hello and once more thanks for reading!

Now leaving the prototype build I started doing proper environmental sprites with proper collision masks and oddly Contruct started freezing and crashing during editing as well as doing weird things to my sprites like offsetting the collision maks (I have to recreate then from scratch) and adding a few black "dead pixels" artefacts on my sprites that I can't seem to get rid off.

I was just wondering if those were known issues and if there is a couple wise do's and don'ts that I should take into account to reduce risks of having to rework a few hundred sprites mid project. ^^

thank you for your time!

gropwel

sorry for bump, thought I'd share the solution I found;

The application V-sync framerate mode seems to be the problem. I switched it to Fixed at 60FPS, runs smoothly. Although I'm getting a warning message that direct-X doesn't like that much...

Otherwise, I found only 1280x720 fullscreen mode runs smoothly with V-sync. Tested on 3 machines. Tough decisions! :-O

Is fixed framerate that bad?

PS: Sorry for multiple messages, it's a few things I need to check before launching level design full steam.

On the same topic, is there any known issues of construct having problem with hi res?

After I switched to 1920x1080, I had a lagging problem. It was always occuring 3 sec after the layout was launched. I progressively deleted the whole game script, but nothing worked, same lag after 3 sec.

Then I switch the resolution to 800 x 600 and it began to run smoothly.

Just to know if I'm the only one or if it's a known issue.

Infinite thanks!

(frontpalm) well that must be it...!

I pictured the fact of flagging objects global as a way to have the game objects in one basic layout then using references for building each level layouts. Old habits...

so then I should make a copy of each objects in each layouts and not flag them global, unless I want something like a blacksmith forging a sword for me while I'm gone or something like that.

Thank you so much, I'm going to try that right away.

Hello, thanks for reading!

This is one that's been bugging me for months; when you call GoToLayout, isn't it supposed to kill/destroy/reinitialize the layout you just quitted? Like otherwise if you want stuff to be changed forever in your game you'd need to store that info in global variables, no? Otherwise switching layout means reseting layout?

When I quit my game to the main menu, then with the world map GoTo the same layout I just quitted, it seems chaos just occured while I was gone; the character seemed to fall throught the enviro while I was gone and always spawns a little lower in the level everytime I come back, particles never seem to have stopped growing and grew huge, it lags a lot like as if the whole game was running twice, my character visual is invisible and nothing seems to make it appear, I only see his collision box, it's just madness. I do not use global variables.

So I was wondering am I missing a step or a notion here concerning level structure? I'm aiming at a world structure similar to Mario World.

Thank you so much!

Haha thanks for the encouragement, I took it from the bright side and thought this might be a good occasion to spit shine metrics a bit more...

Which left me wondering, is it really resolution or isn't it more simply the layout size? I don't think I can really lower the resolution as you would to perform better on older machines, Say like the low res pixellated rendering of Doom you can switch for in the options. Could one do that without resizing every sprites and stretching the layout?

Ouch... we are doing this to revamp all graphics. XD

Hope I'm not opening a pandora's box!

Thanks for the advice!

Hello! Thanks for reading this,

I've been reading what I could find about display resolution and I think it's possible that I may be on the verge of making a big mistake so I wanted to have your opinion.

Say I develop a game then decide to change for a higher resolution, does that mean I have to increase all my metrics, parameter, basically all the maths?

Ex.:

800x600 to 1600x1200

means I must tweak jump strenght 400 to 800

sounds to me like yes I have to, but it's scary enough to just make sure with the pros if there is any hope of saving my maths. ^^

Thanks a lot!

Hi!

Link to the sonic engine is down, any chances of re-uping this one? Looks like the holy grail of slope management in cc.

Cheers!

It works indeed! God what a relief! Fixed some collision detection bugs as well for some reason.

You're right, I treated pv's too much like booleans I guess. States is a much more appropriated method.

I'm sure my whole designer prog'd script could be reduced to just a few pages with optimizations like those.