This is a rerelease of 1.1.0.20 due to a deployment error, sorry for the inconvenience!

• Fixed crash that occurred when launching a drone that was built before 1.1.0.00
  
  
• Fixed client crashes and desyncs that could occur when a ship built before 1.1.0.00 was spawned from private ship storage
  
  
• Implemented a speculative fix for a bug that would cause systems not to update when someone attempted to rift to them, leading to failed rift attempts

• Servers need to be updated

If you haven't already, make sure to check out our Discord channel for the latest updates, server notifications, support, and more!

• Fixed crash that occurred when launching a drone that was built before 1.1.0.00
  
  
• Fixed client crashes and desyncs that could occur when a ship built before 1.1.0.00 was spawned from private ship storage
  
  
• Implemented a speculative fix for a bug that would cause systems not to update when someone attempted to rift to them, leading to failed rift attempts

• Servers need to be updated

If you haven't already, make sure to check out our Discord channel for the latest updates, server notifications, support, and more!

• Fixed client crashes caused by queued entities not being validated
  
  
• Fixed desyncs and server crashes that could result from the server running duplicate update threads for a single system

• Servers need to be updated

If you haven't already, make sure to check out our Discord channel for the latest updates, server notifications, support, and more!

Hi everyone,

It's been a long road to retool our engine so we could leave the 32bit limitations behind, but we're finally here. Besides a long list of updates to make quality of life changes and push fixes and optimizations this has been our main focus for the past year.

You can read up on the details about why this is a big change in our first post here.

Servers and clients are now 64bit. During the experimental version we found some incompatibilities between the 32 and 64bit versions, but luckily we have been able to resolve them, which means that old saves should be able to load without issues.

Please note that if you run older versions of Interstellar Rift you won't be able to load save data from versions past the 64bit update.

Thanks for your patience, and as always, we’ll see you star-side!

- The Split Polygon team.

For the full patch notes, please click here


If you haven't already, make sure to check out our Discord channel for the latest updates, server notifications, support, and more!

• Interstellar Rift is now 64-bit
  
  
• Added a listAdmins command that shows all users with admin rights on the server

• Fixed various bugs related to super admin rights (See notes for server owners)
  
  
• Fixed a bug that could possibly lead to desyncs when a player logged into the server.
  
  
• Fixed a system update thread crash and subsequent desync that could occur if a rift was opened at the same time that an entity spawned in the target system
  
  
• Fixed a crash that could occur when a drone was launched from a ship that was just destroyed
  
  
• Fixed editor crash that could occur when shift- or ctrl-clicking some props
  
  
• Fixed editor crash that could occur when checking if all tiles were reachable
  
  
• Fixed crash on startup when access was denied for a directory in the folder where workshop localizations are stored
  
  
• Fixed a crash that could occur when rendering shadows
  
  
• Avoid a crash that could occur when rendering a model with non-existent materials
  
  
• Avoid a crash that could occur in the text renderer

• Servers need to be updated
  
  
• Due to various bugs that were fixed in relation to super admin rights it is advised for server owners to check which users have admin rights using the listAdmins command, and to correct the rights using the purgeAdmins and setSuperAdmin commands if needed

If you haven't already, make sure to check out our Discord channel for the latest updates, server notifications, support, and more!

• Jingle Bells!

• Player drones will now also completely fill the last slot in their cargo (reported by coconut_willy_97)
  
  
• Fixed a very rare crash of the network thread
  
  
• Fixed a possible crash in the GRIP diplomacy menu

• Servers need to be updated
  
  
• The experimental 64-bit version has also received a patch, patch notes can be found here

If you haven't already, make sure to check out our Discord channel for the latest updates, server notifications, support, and more!

You can read up on the details about why this is a big change in our previous post here.

What are we changing?

We're not changing much in this update compared the previous one. We had to make sure that all engine code would be compatible with 64bit. We never really intended the game to be limited to 32bit, which meant that it took less time than anticipated to get everything up and running again.

So the game is 64bit now?

Yes, servers and clients are now 64bit, although we won't be pushing this to our main branch for at least another week.

What changes am I going to notice?

At the moment it will hopefully resolve any issues people had with loading (very) large ships in the ship editor and busy systems on the servers, which were previously areas where the game could run out of memory.


We are releasing this version on the experimental branch first. Where players can test it out and we can track down any remaining bugs.

Some things to take into consideration when playing on the experimental branch:

• This version is not backwards compatible, making a backup of your Interstellar Rift Appdata folder is advised. Loading a galaxy will break compatibility with the current version, as will any ship that is loaded in this version. If you don't make a backup you will be forced to wait until this version goes live on the main branch.
  
• Unlike the previous update, this patch is for both client and server, and can only be played together with other experimental players.

Hopefully some of you can find the time to play on the experimental version. Any crashes will be sent to us automatically if you have the option enabled. For any other issues you encounter please list them on our bug tracker: Split Polygon Bug Tracker

As always, we’ll see you star-side!

- The Split Polygon team.


If you haven't already, make sure to check out our Discord channel for the latest updates, server notifications, support, and more!


To enable the experimental branch, right click on Interstellar Rift in Steam, > properties > beta, and select the "experimental IR beta patches" option

• Fixed a client crash that could occur when temperature / smoke effects were visible
  
  
• Fixed a client crash when opening an invalid directory in the editor file browser
  
  
• Fixed a crash that could occur when a ship with a laser turret was destroyed
  
  
• Fixed a crash that could occur when a ship was destroyed for an invalid reason and the game attempted to put it in the player's Store-o-Tron

• Servers need to be updated

If you haven't already, make sure to check out our Discord channel for the latest updates, server notifications, support, and more!

This patch resolves all remaining known issues with the physics engine replacement build that is currently testable on the experimental branch. We will be releasing that build to the stable branch if no major issues pop up in the coming two weeks. Thanks goes out to everyone that has already tested the experimental branch.

• Fixed physics mesh orientation of the turbine doors on the nuclear reactor
  
  
• Stop bullets from colliding with the player that shot them
  
  
• Fixed an editor crash that could occur when rotating a prop with the mouse

• Implemented physics used by first person weapons

• Corrected physics meshes for picking up heatsinks on the thermal extractor
  
  
• Fixed radius of turbine physics meshes
  
  
• Fixed physics meshes of the local player being taller than the physics mesh of other players, causing other players to jitter or perpetually fall (Players that are still on the non-experimental build will still jitter and glitch when playing together with players that are on the experimental build)

• Servers don't need to be updated

If you haven't already, make sure to check out our Discord channel for the latest updates, server notifications, support, and more!

Sadly, a bug in the previous version caused all ships that were loaded in that version of the game to lose the paint on generated exterior tiles. This data can't be restored by the game automatically but it is possible to restore old ships from a backup. There are a few options:

If the old versions of the ships have not been uploaded to the workshop using 1.0.4.50 the old versions can be restored in two ways:

1. By first unsubscribing from the ships, relaunching the game, and then resubscribing to the ships. Or,
   
   
2. By removing the %APPDATA%\InterstellarRift\workshop folder

If you have backed up your ships as exported .shipz's, you should be able to reimport them.

By default the game periodically backs up all save data. You can either restore the entire backup, or just one file.

1. To restore an entire backup copy the contents of the desired backup folder in %APPDATA%\InterstellarRift\backups to %APPDATA%\InterstellarRift. CAUTION: This will roll back your entire save to the date and time of the backup in question.
   
   
2. To only restore access to the ships with correct exterior paint you can copy the userdb\ship+40metadata_collection+40 file from the desired backup folder in %APPDATA%\InterstellarRift\backups to %APPDATA%\InterstellarRift\userdb. CAUTION: This will cause you to lose access to any ships you've created in the meantime.

As the underlying bug has been resolved, manually repainting the ships will work.

• Fixed saving of exterior blocks
  
  
• Fixed logging failing due to new version numbers
  
  
• Fixed debufs not getting unregistered when teleporting away from a ship
  
  
• Fixed a server deadlock that could occur if a ghost client connected while the server was figuring out what systems need to update
  
  
• Fixed client crash when opening a just deleted mail

• Improve logging for actions related to player drones
  
  
• Entirely references to chat logging when running as a ghost client

• Servers need to be updated

If you haven't already, make sure to check out our Discord channel for the latest updates, server notifications, support, and more!