FAForever Forums
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Login

    Multiple game crashes

    Scheduled Pinned Locked Moved Game Issues and Gameplay questions
    3 Posts 2 Posters 120 Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • T
      Torfo
      last edited by

      Hello
      Had multiple game crashes today. 1v1 seems to work fine, but 4v4 does not. Tried reinstalling supcom and FAF without help.

      Here is the game log. Thankful for help.

      Torfo

      game_19616554.log

      info: SSB >>> TRACE initialized
      info: SSB >>> TRACE SetLayout()...
      debug: Current gametime: 00:00:30
      debug: Current gametime: 00:01:00
      debug: Current gametime: 00:01:30
      debug: Current gametime: 00:02:00
      warning: Evaluating LazyVar failed: error evaluating lazy variable: ...aforever\gamedata\lua.nx2\lua\maui\layouthelpers.lua(375): perform arithmetic on expected but got Á;ÊuÛ‹L$Qèáy"
      stack traceback:
      ...aforever\gamedata\lua.nx2\lua\maui\layouthelpers.lua(375): in function <...aforever\gamedata\lua.nx2\lua\maui\layouthelpers.lua:374>
      [C]: ?
      ...ogramdata\faforever\gamedata\lua.nx2\lua\lazyvar.lua(60): in function <...ogramdata\faforever\gamedata\lua.nx2\lua\lazyvar.lua:35>
      Stack trace from definition: [Set lazyvar.ExtendedErrorMessages for extra trace info]

           stack traceback:
           	[C]: in function `error'
           	...ogramdata\faforever\gamedata\lua.nx2\lua\lazyvar.lua(73): in function <...ogramdata\faforever\gamedata\lua.nx2\lua\lazyvar.lua:35>
      

      warning: Evaluating LazyVar failed: ...aforever\gamedata\lua.nx2\lua\maui\layouthelpers.lua(375): circular dependency in lazy evaluation for variable [Set lazyvar.ExtendedErrorMessages for extra trace info]
      stack traceback:
      [C]: in function `error'
      ...ogramdata\faforever\gamedata\lua.nx2\lua\lazyvar.lua(45): in function <...ogramdata\faforever\gamedata\lua.nx2\lua\lazyvar.lua:35>
      ...aforever\gamedata\lua.nx2\lua\maui\layouthelpers.lua(375): in function <...aforever\gamedata\lua.nx2\lua\maui\layouthelpers.lua:374>
      [C]: ?
      ...ogramdata\faforever\gamedata\lua.nx2\lua\lazyvar.lua(60): in function <...ogramdata\faforever\gamedata\lua.nx2\lua\lazyvar.lua:35>

      1 Reply Last reply Reply Quote 0
      • JipJ
        Jip
        last edited by

        Try without UI mods. If the game is stable, then enable them one-by-one or in a binary search fashion until you found the one that causes the issue

        A work of art is never finished, merely abandoned

        1 Reply Last reply Reply Quote 0
        • T
          Torfo
          last edited by

          Thanks, disabling UI mods worked so far. Now to see which ones do work..

          1 Reply Last reply Reply Quote 0
          • First post
            Last post