Accessing local variable in object by referencing its ID stored in List now throws error in 23.1.1.149

Answered

Comments

7 comments

  • YoYo QA Dept

    Hi Jeff Tomse,

    Thank you for your feedback. 

    Could you please send us a sample project in which you are having this issue? 

    You can do that by hosting the project on a cloud service (such as dropbox) and then sending us the link. Or, if you want to keep your project private, you can send it to us via the contact form on the Yoyo Games website and linking this forum thread.

    Many thanks. 

    0
    Comment actions Permalink
  • Alexander Luck

    We experience the same issue with roughly 20 scripts in our big project, all work fine in 2.2 and previous Beta.
    Both in VM and YYC I get basically the same output log when compiling.

    Attached is a mini project with one of the scripts (scr_broken_script).

    I have added a few placeholder objects/scripts to replace all references to our actual project so this script should compile.
    Ignore everything in the project except "scr_broken_script".

    http://utilityserver.flowfiregames.com/html/yxcojqwedf/beta_test_proj.yyz

    0
    Comment actions Permalink
  • Nicolas Désilets

    I'm getting the same problem on my side
    After some testing, it seems to be related to the use of accesors (of any kind) when using a global variable

    This also occurs when using a struct instead of an instance

    global.some_array=array_create(1) 
    global.some_array[@ 0] = {_a : 1, _b : 2}

    show_debug_message(global.some_array[@ 0]._a) //fatal error
    show_debug_message(global.some_array[0]._a) //works fine
    1
    Comment actions Permalink
  • Michael Peng

    I have the same issue. I hope this is fixed quickly, I access instances in lists pretty often and I'm just going to use the old runtime instead of working around each and every case.

    0
    Comment actions Permalink
  • Jeff Tomse

    I bet they'll fix it pretty quick. I would think that 99% of games use this.

    1
    Comment actions Permalink
  • Jeff Tomse

    This appears to be resolved in the newest beta (157).  Thank you!

    1
    Comment actions Permalink
  • YoYo QA Dept

    Hi Jeff,

    Thank you for letting us know it's fixed.

    I'll mark this thread as answered. 

    Thanks again.

    1
    Comment actions Permalink

Please sign in to leave a comment.