I couldn't reproduce your bug, it worked fine for me.

would you mind posting a cap?

layer inheritance as an option on the layer you want as your inventory, and set its source to the corresponding layout.

Nice to see there's a way to work around this.

so its safe to assume its probably not a graphics card specific error.

tulamide your right. It does still have the same offset effect regardless of layer effects, but it seems odd that if there is an effect, the offset worsens for that layer.

I was playing around with my duel monitors with this ( one is 1360 x 768 the other 1680 x 1050)

when just dragging the application window from one screen to the other (at a size of 1680 x 1000) there was no issue, regardless of witch was the primary display.

But when i set it to show just the smaller window, then ran at the exact same resolution as before, the offset problem happened.

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

when you use the window/sysinfo object to change the resolution it makes it smaller than max client resolution

such as : my display high is 1050, and that is what the system info says, but when it changes my window size, it sets it to 1012 witch I take it is the safest resolution to run at before the offset happens.

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

I'm starting to think maybe this isn't a bug with construct, just something that happens if applications are to large. So a deeper "bug" having to do with constructs "hardware-accelerated DirectX 9 rendering"

If that's the case, people should Definitely be aware of it before releasing their game so they can make sure to mitigate it.

You'll have to make the menu on its own layout, then use layer inheritance( that or the layout object, but the layer inheritance seems to work better.) to get it into the main game screen.

you'll probably need to compile each group into some sort of data file, array, hash table, .INI file.. whatever you feel comfortable working with.

then in the menu layer have the info printed out using the list box object, if you want the quick, easy, and ugly option.

or make your own list using sprites, loops, and functions. if you want it to look pretty

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

making menus in construct is probably one of the more difficult things to do. there's no real quick fix that I know of.

If any of this seems too confusing, just look around the forums for examples,or just ask, and me and who ever else will help elaborate a bit more.

Some example photos at 75% Zoom:

<img src="http://img694.imageshack.us/img694/5854/goodlu.jpg" border="0" />

                          At 640 x 480

<img src="http://img685.imageshack.us/img685/5585/baddj.jpg" border="0" />

                          At 1680 x 1100

If I have a layer with a layer-effect, or and object with an effect, it causes a weird offset problem

I had a post on this already :

scirra.com/forum/effects-and-zoom_topic49967_page1.html

But I just now found out that this only happens for me when my applications "Window height" is over 1000,

even then its not really noticeable until it gets over 1038.

after that it just gets exponentially worse.

if I go to 1500 its just insanely off.

My default window size is 1680 x 1050, I was always setting the resolution of my application to such, so that's why I was having that issue.

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

However in my post, with my cap having a resalution of 1680 x 1050

clodius666 reported having the same problem with his current desktop res. at 1440 x 900

tulamide had a Desktop res. 1920x1080 (32bit) and didn't have the problem.

so I'm willing to bet that this bug is dependent on the users current desktop resolution.

however the only people reporting it also had ATI Radeon cards.

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

I was wondering if some people wouldn't mind helping me see if my hypotheses is correct on this before I post it on the bug tracker.

you can set it up yourself.

or get this .cap:

ZoomTest

And set the application resolution to your screen size, or past it. before running it.

awesome game, well built. if you want, I can help you with some graphics, It's kinda what i do.

If so let me know and I'll pm you some examples of my stuff later.

Finally...

Its beyond me why we, the consumer, have to make these games happen. are publishers so incompetent they can't see the value in making games that people are willing to spend hundreds of thousands of dollars ,out of there own pockets, just to see get made.

I'm all for Kickstarter, but it just proves how #$*'ed up the video game industry is.

ps1 - 2,418 games

ps2 - 2,016 games

ps3 - 755 games(as of now)

development cost in US$:

1M?4M     -2000

5M        -2006

over 20M -2010

personally think the next console race may vary well be the last for some time.

if not, in in 2022 there will be 1 AAA game released that year, and it will cost over 1 billion dollars to make.

willing to bet there's only going to be, max, 500 games for ps4, probably way less.

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

what dose this mean?

welcome to the golden age of independent gaming,

smart phones and tablets have brought gaming platforms to more people than ever, and innovation in simplified game making(like unity...and construct)has made game development for small groups of people not only easier, but lucrative. thanks to low costs of development, free distribution(more or less). and the biggest consumer base there has ever been.

to not use a platform behavior: add a variable to the object called "drop"(or whatever) , and an always condition adding 0.09(or whatever you want the force of gravity to be) to "drop" than set y. position of the object to current y. + "drop"

if you don't mind having the platform object, and want its collision detection just set its max speed and everything else to 0, besides the falling.

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

fun with falling: if you make the falling your own event, you can have the object bounce by setting its "drop" to the current ("drop"/2)*-1 when it overlaps a solid object.

Others probably disagree with me on this, but in construct the only "hard" thing to make in a rts is enemy AI.

Its actualy got to be one of the most complex AI systems for any game. having to behave almost identical to the player useing the same objects.

and arguably no game has done a "good" job of making a challenging ai without cheating.

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

oh and you can't really use tile map's like every 2d rts you've probably ever played without a nightmare of rendering tiles but preserving edges for path finding.

so you'll have to build it with that limitation in mind.

and in-game menus are a pain, but that's true for any game in construct.

----

was actually thinking about releasing a series of tutorials on how to make a rts after i finish my next project.