Programming is frought with peril like that. I know C2 advertises no programming, but essentially what you're doing is programming in a highly visual manner. Never throw in the towel. Many times game breaking bugs are just small oversights in logic.

The difference at that scale is insignificant. Neither would provide a difference in performance.

Even if you had thousands of dialog option, segmenting it into different layouts would not improve performance because the UI elements are already loaded.

There is the other point as well, that when clicking a button performance does not matter if the layout doesn't have a bunch of movement in it.

It depends on your end goal. Objects have a "global" property which makes it pretty easy to have a global UI across all of your game's layouts. With that in mind I think option one would be visually and logically easier to develope. You can always go back and rework things when you have a better feel.

That's what confused me. I read a post by ashley that states that things are only loaded from the active layout, but perhaps he means rendering surfaces, not objects. I love C2 but it's still new to me and I'm used to more conventional libraries like sdl/clanlib/impact/love

Why not create a dump layout which you dump all of your objects? Then, you don't have to destroy the objects on start of layout that you're using.

If you're destroying global object, I think it will remove it entirely from the memory as well, maybe that's the reason it's not spawning.

I didn't know I could do that Going to try later!

Does the layout have to be loaded?

I can't open the capx right now unfortunately but will when I can. If I understand what you're saying, the sprite can be on ANY layout, and if that's the case that would be extremely useful.

I'll check back in later, thanks!

The game is set up as follows

When you click campaign it goes to a layout called gui. gui contains all spawnable sprites and UI elements. The spawnable sprites are located in the margin off of the layout, and all objects are tagged as global.

the GUI layout then redirects to whatever layout the player should be on.

What I did as your suggestion is call:

on layout start -> destroy spawnablesfamily

right in the gui layout. But after redirecting it did not spawn any objects like it should have.

Does not work. Just tried. The object needs to be present somewhere on the layout or system->create object does not work.

I will give that a try when I get home this evening. So once they are loaded in a layout, they are there forever? won't I need to reload them again when changing layouts?

http://surolace.com/play

(swipe screen for virtual joystick)

If you move the ship along the left edge and your screen res is high enough, you'll see the turrents on your ship aiming at something not accessible.

If I delete the objects they will not be available for spawning, since C2 handles resources on a per layout basis. I've made them global so I can reuse them for (in the future) many instances.

A simple solution might be something like, on every action "if not on resource layer" or something, but it's sloppy and won't scale with what I'm trying to do well.

Edit: To reword more succinctly:

I need to be able to spawn objects, but do not want to use or keep the original that they are based from.

Sorry, I have to bump this. I'm running into problems where sprites in the margin that I use as a base for spawning objects, are being treated as active. What is the normal way to do this? C2 makes it easy to put a bunch of "and is not in the margin" conditions, but that's going to be a lot of work already and I sense that's not the best way.

?

frn, put code to compiler before you work on your projects. Your first game attempts will always be shoddy. Things work a bit differently than conventional software but the principles of game dev will carry over to almost any engine/api.

Also, I decided it's not worth using wine to run windows app and have finally come to the conclusion that I just need to run a copy of windows. The user experience is really that much better to run C2 natively.

Just opinions of course