[SOLVED] Is My Project Corrupt?

motorcycle boymotorcycle boy Member Posts: 429
edited April 2015 in Working with GS (Mac)

So I have a table with a bunch of booleans. In my scene I put an actor with a display text. In this case display table row 2 column 30. I put actor color to black and the text to white. Nothing displays. It's a very basic set up I've done many times before. Baffled. I even changed the content of the table to text and nothing displays.

I made a new blank project and it works fine. Is my project corrupt then?

Comments

  • motorcycle boymotorcycle boy Member Posts: 429

    Very strange! I just previewed it again and now it's working. What?!

  • RabidParrotRabidParrot Formally RabidParrot. Member Posts: 956

    I blame Obama.

  • SocksSocks London, UK.Member Posts: 12,822

    @RabidParrot said:
    I blame Obama.

    I blame Oprah.

  • jamie_cjamie_c ImagineLabs.rocks Member, PRO Posts: 5,772
  • SummationSummation Member, PRO Posts: 476
  • SocksSocks London, UK.Member Posts: 12,822
    edited April 2015

    @jamie_c said:
    I think it was actually Doctor Oz's fault.

    @Summation said:
    Zuul

    You fools, Zuul and Oz are one and the same [runs off and hides in his purpose built shelter].

  • zweg25zweg25 Member Posts: 738

    A project will freeze if you try and access a table value that is undefined. Meaning if you have a 5x5 table but you try and display row 6 column 6, the project will freeze

  • gingagaminggingagaming FREELANCE GS DEV Member Posts: 1,685

    @zweg25 is correct. I'm adding this solution for anyone finding this post in the future....

    The most common mistake is have a table cell value looking for a row or column with the value 0 which was defined by an attribute. This happens when the logic fires too quick and the attribute wasn't loaded before the rule fired.

    This causes any display behaviour not to display. to find the error, simply backup your project, then remove the actors one by one until the display works again. When you find he actor that is at fault, simply turn off each rule until you find the rule that stops the display.

    When you know the actor an rule causing it, simply look at how you have these rules firing and either move them to fire slower or add a delay in the rule to fire slightly later. This all depends on your set up @dreichelt

    I know you marked this as solved but if you didn't address this, it could have been ram usage slowing it down. Check it on a device to be sure.

  • motorcycle boymotorcycle boy Member Posts: 429

    Thanks guys. No thanks to you Obama...

Sign In or Register to comment.