Stuck in a rut!

Posted on by

I’m getting really frustrated with my game development at the moment. Just as it seemed things were going well, suddenly I’m getting massive behavioural differences between Flash and IOS. The sooner Stencly 3.0 is released the better.

At the moment non of the objects are showing up in Flash but they are on IOS, I’ve been trying to work out why; by dissabling everything one at a time. What ever I do doesn’t make a difference and there’s no reason why it shouldn’t work in Flash either… It was 2 days ago and nothing has changed on that side of things!

Anyway, that’s my update. I just hope I get this figured out soon because it’s really slowing the whole process down

  • saulochina

    are you using the same scene for both targets? or do you have a scene for ios and another for flash? i know that in the other post you said that the problem was solved, but i’m curious…

  • 45aday

    I was and still am using the same scene for both targets. I’m still at a lost as to why it stopped working on Flash. All i know is by recreating the scene and re-applying my blocks of code, it was fixed… Weird!

  • Silux

    Not weird at all for me!it is just what i made some time ago with my game;copying it whole gave errors, copying resources and attaching them not.you should have a version working in ios and another with flash, but each with a different name

    • 45aday

      It’s weird because it shouldn’t happen and reapplying the same code to a new scene shouldn’t make any difference in my mind, but this is the way it goes sometimes.

      I used to do a flash and IOS version but there’s no need to anymore, you can use the blocks of code ‘Do in flash’ and “do in IOS’ to separate out IOS specifics. 
      My biggest time waster at the moment though, is that 2.X isn’t “what you see is what you get” in IOS and a-lot of my time is trying to figure out why. Not to mention the bugs I’ve found along the way like, animated backgrounds not working, gradient filled backgrounds not working, tiles not displaying correctly etc etc.. All these take time to debug, report and then find a work around.

      I really look forward to 3.0 because all these headaches will be gone :-)