Vectorio News

[p]Hello everyone,[/p][p][/p][p]Thank you to everyone who has been testing the v0.3 beta on the experimental branch; your feedback has been invaluable as I press forward with development. [/p][p][/p][p]This post is just to educate everyone on what's coming in v0.3.0-beta.9, which should be hitting the testing branch early later next week. I would also like to share specifics on what I've learned from your feedback, mainly from the feedback survey. (if you have not taken this survey, check it out below!)[/p][p][/p][p]https://forms.gle/UdK2QxrtkC2K7yXR9[/p][p][/p][h3]What's coming in v0.3.0-beta.9[/h3][p][/p][p]The next beta build is focused entirely on gameplay & progression. Here's what you can expect...[/p][p][/p]

• [p]Completely refactored engineering UI, to make it a bit more clear how it works[/p]
• [p]New building XP system, designed to offer some shallow build identity[/p]
• [p]Huge changes to the current questlines, mainly pertaining to the quest objectives[/p]
• [p]New enemies & extended heat aggression for both ALTAR & Abyss regions[/p]
• [p]Some new things to find out in cyberspace as you explore[/p]

[p][/p][h3]Building XP [/h3][p][/p][p]All buildings in the game will be able to earn XP by completing certain actions. Some examples are...[/p][p][/p]

• [p]+1xp for Turret's when they hit an enemy[/p]
• [p]+1xp for Collector's everytime they collect a resource[/p]
• [p]+1xp for Foundry's whenever they successfully craft a resuorce[/p]
• [p]+2xp for Turret's if they manage to destroy a unit[/p]
• [p]+1xp for Lab's each time they convert a resource to science[/p]
• [p]etc.[/p][p][/p]

[p][/p][p]Levels panel, coming in v0.3.0-beta.9[/p][p][/p][p]At certain XP thresholds, buildings will unlock a level tier, which can contain anywhere from 1 to 5 possible upgrades to choose from. These can be swapped at anytime, but only 1 can be active.[/p][p][/p][p]The goal of this system is to not only provide some basic build identity, but also ensure that all buildings remain useful in later sections of the game that are significantly more difficult. It can also be used as a balancing tool to improve weaker buildings by offering more upgrades, though this is a last resort.[/p][p][/p][h3]Refactored Engineering UI[/h3][p][/p][p]The current UI for engineering was always meant to be placeholder; not only is not intuitive, it does not do the engineering system justice. In v0.3.0-beta.9, it will be getting a huge makeover.[/p][p][/p][p][/p][p]WIP Engineering panel, coming in v0.3.0-beta.9[/p][p][/p][p]The goal is to provide a full overview of ALL the engineering mods in the game. This will act as a sort of "collection" screen, where you can track your progress and see what mods you still have yet to unlock. Hovering over locked mods will hint at where you can find them, or, if they're already unlocked provide a much more detailed explanation of what the mod does.[/p][p][/p][p]The top bar will act as your active mod set; remember that engineering mods are unique, so only one can be applied to a specific buildings at one time. Different buildings have varying engineering slots, so this is where the real meat of player-driven build expression will be.[/p][p][/p][p]You'll be able to easily track which mods are equipped to which buildings within the collection grid.[/p][p][/p][h3]What have I learned from the first few days?[/h3][p][/p][p]First off, thank you. The volume and quality of feedback has been incredibly helpful, and it’s already shaping where development goes next. Based on this initial data, here’s what stands out so far:[/p][p][/p]

1. [p]Average playtime is ~2 hours, right in line with expectations.[/p]
2. [p]This lines up with a major drop-off in engagement shortly after entering the Abyss.[/p]
3. [p]The main reason players have reported they stopped playing was due to progression issues or bugs, but I've also noticed a dropoff in engagement with the quests, suggesting that the quest objectives & progression of quests needs work.[/p]
4. [p]Performance is strong: ~90% of players report good or great performance. Huge win here.[/p]
5. [p]Chunk expansion and the research tree are landing well, but the engineering system is not, which is why immediate changes are coming in the next patch to improve this system.[/p]
6. [p]A tutorial is badly needed and is a top priority moving forward.[/p]
7. [p]Game balance is inconsistent, confirming it’ll need ongoing iteration.[/p]
8. [p]The most requested features are Multiplayer and Mods; to me this means that the community really wants a way to share gameplay experiences together[/p][p][/p]

[p]Based on this data, my focus going forward is:[/p]

• [p]Smoothing progression and fixing blockers around the Abyss[/p]
• [p]Improving quest engagement past the early game[/p]
• [p]Reworking engineering to be more satisfying and intuitive[/p]
• [p]Adding a proper tutorial to onboard players effectively[/p]
• [p]Continuing balance passes while keeping performance strong[/p]

[p][/p][p]Being able to adjust priorities & iterate on certain gameplay systems would not be possible without all of you testing & sharing your thoughts, so thank you. [/p][p][/p][p]I know a LOT of you are happy with the improvements in v0.3, but I also know that what's currently in this beta is quite a shallow offering, especially on the gameplay side. That’s intentional for now. My focus is on making sure these new systems have a solid foundation before expanding on themthere’s a lot more coming once that base is locked in. Over the next updates, you can expect deeper progression & more interesting things to work towards as these systems mature.[/p][p][/p][p]I hope you’re all having a safe and happy holiday season. While my time will be a bit split with family over the next week or so, development won’t be stopping, and I’ll continue pushing things forward.[/p][p][/p][p]Cheers,[/p][p]~ Ben[/p][p][/p]

[p]An optional hotix is now available to download on the Experimental branch. (v0.3.0-beta.8a)[/p][p][/p][h3]BUG FIXES:[/h3]

• [p]Fixed achievements not being given until the game was closed[/p]
• [p]Fixed a typo in the recipe dropdown menu that would check if the recipe target was unlocked, not the recipe itself[/p]
• [p]Fixed already completed quests not proactively giving new quest rewards [/p]

[p]Hello everyone

A new experimental patch is now available for testing! You can access it on the experimental branch by following the instructions below if you wish to get access to the changes and fixes now.
[/p][h3]How to opt into experimental:[/h3]

1. [p]Locate Vectorio in your Steam library[/p]
2. [p]Right click and go to "properties"[/p]
3. [p]Find the "betas" branch[/p]
4. [p]Using the dropdown, select "Experimental"[/p]

[p][/p][h3]Experimental Info:[/h3]

• [p]Testing Cycle: ~1 day[/p]
• [p]Experimental Saves: Disabled[/p]
• [p]Backwards Compatible: Up to v0.3.0-beta.5[/p]
• [p]Update Type: Experimental Patch[/p]
• [p]Contains Spoilers: Yes[/p][p][/p]

[p]Questions? Comments? Concerns?
Let me know below or on our Discord server: https://discord.gg/vectorio[/p][p][/p][h2]Patch Notes[/h2][p][/p][p]The following is a list of changes pushed to the experimental branch. While changes are usually tested beforehand, please note that some may require further testing to validate.[/p][p][/p][h3]BUG FIXES:[/h3]

• [p]Fixed a bug with crafter's where they wouldn't show the full list of unlocked recipes, causing a permanent stagnation in progression[/p]
• [p]Fixed an array size issue with the cyberspace shader controller that would stop newly claimed areas of cyberspace from properly clearing[/p]
• [p]Fixed an object pooling issue with Decryptor's where they could potentially be deleted after being re-used. This was due to a missing flag issue inside the modules spawn method.[/p]
• [p]Fixed a race condition with the Decryptor animator, where it sometimes wouldn't show the model of the unlockable that was inside the Decryptor[/p]
• [p]Fixed a major issue with the route configuration controller, that could cause the wrong ID to be used during configuration, leading to the route being applied to a different port [/p]
• [p]Fixed an issue with the route configuration controller that would stop you from selecting clusters if they had been previously selected by that same port[/p]
• [p]Cleaned up the resource extension for drones with proper event disconnection; while not confirmed this could have been a potential cause of incorrect route configuration for drones[/p]
• [p]Fixed incorrect scaling being applied to the resource icons on node reactors; this was due to an earlier change with how scaling is calculated for world models[/p]
• [p]Added a null safety check to the model rendering system to try and stop compounding shader issues; unsure if this will actually fix the root cause however[/p]

[p][/p][h3]OPTIMIZATIONS:[/h3]

• [p]Made a slight adjustment to how the cyberspace shader is calculated, properly using camera frustum culling to reduce chunk iterations; this should be an improvement but will require testing on varying hardware to ensure [/p]

[p]Hello everyone

A new experimental patch is now available for testing! You can access it on the experimental branch by following the instructions below if you wish to get access to the changes and fixes now.
[/p][h3]How to opt into experimental:[/h3]

1. [p]Locate Vectorio in your Steam library[/p]
2. [p]Right click and go to "properties"[/p]
3. [p]Find the "betas" branch[/p]
4. [p]Using the dropdown, select "Experimental"[/p]

[p][/p][h3]Experimental Info:[/h3]

• [p]Testing Cycle: ~1 day[/p]
• [p]Experimental Saves: Disabled[/p]
• [p]Backwards Compatible: Up to v0.3.0-beta.5[/p]
• [p]Update Type: Experimental Patch[/p]
• [p]Contains Spoilers: Yes[/p][p][/p]

[p]Questions? Comments? Concerns?
Let me know below or on our Discord server: https://discord.gg/vectorio[/p][p][/p][h2]Patch Notes[/h2][p][/p]

• [p]Enabled the communication layer on drones, allowing drones to have context of what other drones are doing. If you notice a port is no longer deploying it's drone, it's because the port is likely no longer needed to sustain throughput from the input cluster to the output cluster.[/p]

[p]Hello everyone

A new experimental patch is now available for testing! You can access it on the experimental branch by following the instructions below if you wish to get access to the changes and fixes now.
[/p][h3]How to opt into experimental:[/h3]

1. [p]Locate Vectorio in your Steam library[/p]
2. [p]Right click and go to "properties"[/p]
3. [p]Find the "betas" branch[/p]
4. [p]Using the dropdown, select "Experimental"[/p]

[p][/p][h3]Experimental Info:[/h3]

• [p]Testing Cycle: ~1 day[/p]
• [p]Experimental Saves: Disabled[/p]
• [p]Backwards Compatible: Up to v0.3.0-beta.5[/p]
• [p]Update Type: Experimental Patch[/p]
• [p]Contains Spoilers: Yes[/p][p][/p]

[p]Questions? Comments? Concerns?
Let me know below or on our Discord server: https://discord.gg/vectorio[/p][p][/p][h2]Patch Notes[/h2][p][/p][p]The following is a list of changes pushed to the experimental branch. While changes are usually tested beforehand, please note that some may require further testing to validate.[/p][p][/p][h3]BUG FIXES:[/h3][p]- Fixed a few oversights in the model rendering pipeline that would result in dynamic model instances (enemy units, for example) not being rendered on the screen[/p][p]- Fixed the hub being able to be destroyed in other regions; this was due to an object pooling issue with the "IsEditable" flag getting reset between region switches.[/p][p]- Fixed an issue with drones where it would abort it's entire route if one of the pending actions could not be executed correctly.[/p][p]- Fixed the placeholder techs for alchemy later in the tree (Phantom Plains)[/p][p][/p][h3]OTHER CHANGES:[/h3][p]- Removed knowledgebase & load game buttons from the game until they are functional. This is to avoid players getting confused on why these are not working.[/p]