Ambiera ForumDiscussions, Help and Support. |
|
|
|||||
|
I have 2 questions regarding scene management and some sort of switch scene error. First question: Is there a way to re-order the scenes displayed in the scene dropdown? Seeing as this has no affect on the actual order of scenes playing, it would be nice to be able to move up or move down a scene so it shows where you want to see it. It also doesn't seem to be alpha-numeric in how it orders. Second Question: I maybe foolishly decided to work on my scenes as separate ccb files. My thinking was that when they are ready I'll import them in their respective scenes, within one coppercube file that I would use to create my exe. I've been trying to bug fix this to no avail. I'm at the point where my thinking is... I don't see any problem on screen... so I'm just going to ignore this error message. That said... Is the error shown in the image normal when switching from one scene to another? Am I doing something wrong? For example... in my menu, I have it so when you press the play button, it triggers a Do Later Action the then triggers a switch scene action. This is when the error comes up. Thanks in advance for any help. M |
||||
|
niko would probably say the order of the scenes in the editor doesn't matter because no one will see it but you and you can call them in any order you want. not sure about your second issue. are you switching between ccb files with ccbSwitchToCCBFile()? if so, the console should show textures being loaded. I guess what you mean is you exported your scenes as prefabs and have imported them into scenes in your main ccb? the error suggests you are trying to set a property of a scene node that is no longer there. you might have an every few seconds behavior and the do later action conflicting. try messing with the intervals. but, no, it shouldn't do that. also there is nothing wrong with how you are building your game. making prefabs and importing them into a main ccb is fine. |
||||
|
also I seem to recall people saying that using that do later action with the fade screen action causes that issue. if you are fading the screen too, check there. |
||||
|
|
){kind=link}