Create a free account to remove all ad content.

Author Topic:  2.4  (Read 18937 times)

0 Members and 1 Guest are viewing this topic.

Craig

  • Developer
  • Extreme Member
  • *
  • Posts: 6655
  • Dig Deep
    • View Profile
    • Twitter
  • Steam: tota1miner
Re: 2.31
« Reply #10 on: August 25, 2015, 09:54:14 PM »
The XBLIG system is broken again, so I'm unable to submit the review.
Will continue fixing stuff in the game until the XBLIG system is working again.

Craig

  • Developer
  • Extreme Member
  • *
  • Posts: 6655
  • Dig Deep
    • View Profile
    • Twitter
  • Steam: tota1miner
Re: 2.31
« Reply #11 on: August 27, 2015, 10:07:52 PM »
The XBLIG system is back up.

We're now doing final testing for 2.31

New projected Peer Review submission date is Monday 31 Aug.

Craig

  • Developer
  • Extreme Member
  • *
  • Posts: 6655
  • Dig Deep
    • View Profile
    • Twitter
  • Steam: tota1miner
Re: 2.31
« Reply #12 on: September 03, 2015, 09:20:42 AM »
We're into final, final testing now.

Several cool little features were snuck into the update this week, which has delayed submission to peer review by a few days, but I'm confident you'll be happy about that once you see them.

No more little features will be snuck in now, just final testing and then submission to peer review.

Craig

  • Developer
  • Extreme Member
  • *
  • Posts: 6655
  • Dig Deep
    • View Profile
    • Twitter
  • Steam: tota1miner
Re: 2.31
« Reply #13 on: September 06, 2015, 06:01:53 AM »
Several cool little features were snuck into the update this week
Here's a couple of them:


Craig

  • Developer
  • Extreme Member
  • *
  • Posts: 6655
  • Dig Deep
    • View Profile
    • Twitter
  • Steam: tota1miner
Re: 2.31
« Reply #14 on: September 09, 2015, 01:45:37 AM »
It looks like the XBLIG peer review system is broken again. I will try to confirm either way.

Craig

  • Developer
  • Extreme Member
  • *
  • Posts: 6655
  • Dig Deep
    • View Profile
    • Twitter
  • Steam: tota1miner
Re: 2.31
« Reply #15 on: September 14, 2015, 05:15:49 AM »
Scripts are now compiled to bytecode (more efficient execution).

I'll describe this item in detail as it's important for scripts.

In 2.3, the current retail version, scripts are interpreted on the fly as they are executed. The interpretation is expensive for two reasons.

1. The game has to process the commands as text (strings), by parsing them, comparing and converting the strings into commands and data, letter by letter, number by number, and testing for errors. This takes considerable CPU time to do.

2. In C#, particularly on the Xbox 360, string manipulation is expensive because it creates a lot of garbage, which is memory allocations, and after a certain amount of memory is allocated, the C# runtime performs a garbage collection, which in TM is extremely expensive, causing lock ups than sometime last for several hundred milliseconds (several frames). This is noticeable as annoying little freezes during gameplay. This problem is compounded by looping scripts.

In 2.31, scripts are no longer interpreted on the fly, they are now compiled (once) into bytecode, and it is the byte code that is executed when the script is executed. This means all the string manipulation, parsing, error checking is done only once, up front, during the compilation, and doesn't have to be done again (unless the scripted is edited/changed).

This is much more efficient because now the game can just execute the commands directly. It also drastically reduces the amount of generated garbage. This is particularly beneficial for looping scripts.

Some garbage is still generated by some commands, commands that utilize text substitution for example as the substitution cannot be done at compile time, but in general, garbage generation by scripts in 2.31 is only a fraction of what it is in 2.3.

Another benefit of much more efficient script execution is that it is now much less problematic to attach scripts to events, particularly events that can happen rapidly/frequently, such as breaking blocks, striking objects, taking damage, etc. This was a big part of the motivation to move to the byte code method, so that we can now look into event driven scripts with confidence.

Craig

  • Developer
  • Extreme Member
  • *
  • Posts: 6655
  • Dig Deep
    • View Profile
    • Twitter
  • Steam: tota1miner
Re: 2.31
« Reply #16 on: September 14, 2015, 07:53:46 PM »
It looks like the peer review system is working again. We are working to submit the update in the next 24-48 hours.

Craig

  • Developer
  • Extreme Member
  • *
  • Posts: 6655
  • Dig Deep
    • View Profile
    • Twitter
  • Steam: tota1miner
Re: 2.31
« Reply #17 on: September 20, 2015, 11:17:19 PM »
We found a few more bugs so couldn't make the 48 hour estimate. Then the weekend happened. As usual we will post a peer review topic once the update is submitted.

Craig

  • Developer
  • Extreme Member
  • *
  • Posts: 6655
  • Dig Deep
    • View Profile
    • Twitter
  • Steam: tota1miner
Re: 2.4
« Reply #18 on: September 24, 2015, 03:28:51 AM »
The 2.4 update has been submitted to peer review.

Craig

  • Developer
  • Extreme Member
  • *
  • Posts: 6655
  • Dig Deep
    • View Profile
    • Twitter
  • Steam: tota1miner
Re: 2.4
« Reply #19 on: September 24, 2015, 07:02:01 AM »
The peer review system is broken again. I'll resubmit when it's fixed.