Another aspect to consider is that each of your eyes gets a different view of the world, so parts of the scene drawing code need to run twice per frame compared to non-VR.

Is the burner inserter literally running out of fuel or does it just seem to stop working for some reason? If the latter, this may be due to 27465 which should be fixed in 0.13.7. If the former, maybe you could upload a save where it happens so the developers can understand the bad behavior better?

Description:
The campaign difficulty is always set to Easy, even if the user starts the campaign on Normal or Hard. (This applies to both the New Hope and Tight Spot campaigns.)

Steps to Reproduce:
1. Start a campaign that has difficulty settings: New Hope or Tight Spot
2. Select either Normal ...

Music in the menu is new as of 0.13.0. FWIW, I like it better this way

Ah, that makes sense. Thank you!

I guess what's confusing me is that I see the freeplay scenario setting the value for global.attack_data, but I do not see it being used in any meaningful way.

For example, it sets global.attack_data["change_values"] to true, but no where else is "change_values" referenced. So what's the point?

Am ...

In the freeplay scenario's control.lua (in v0.12.35), I see code that sets the global.attack_data table like so:

init_attack_data = function()
global.attack_data = {
-- whether all attacks are enabled
enabled = true,
-- this script is allowed to change the attack values attack_count and until ...