Rust

Rust Dev Tracker




20 May

Comment

Originally posted by BasedWebDeveloper

Notice OP says "Oil Rigs ruined Rust even more" it really shows how little it takes to push the game into full zerg mode and ruin it for everyone else. As if nerfing oil rig will even fix the underline problem that is the group based progression system.

Even after you nerf it OP will still have many more bad wipes than good. Should really look into changing the system or adding a disadvantage to big groups. You should also try play solo for a few wipes to get a real feel of what it's like, it's really not that fun anymore.

The only players this system benefits are large groups, it promotes them and makes sure they can stomp on everyone with ease and little to no resistance, even on a fresh server. This just makes the experience trash for everyone else and makes us play different games.

People say join a big group but most of us that play solo have been in big groups and hate how easy it is, little to no challenge and you know this. Playing solo or s...

Read more

I'm not really following - You saying the oilrig is group based? While the oil rig is vastly easier with a group as with everything it can be solo'ed with some patience and practice.

Solo Rust has never been easy, it never will.

Comment

Originally posted by T4gg3D

Any sources?

Me

Comment

The oilrig loot will be rebalanced in the next patch.

Comment

The oilrig loot will be rebalanced in the next patch.


18 May


17 May

Comment

This is a known issue which will be resolved in the next patch.


12 May

Comment

Originally posted by Lucifer995

Make your config read only.

C:/Program Files (x86)/Steam/steamapps/common/Rust/cfg right click on keys.cfg, properties and make it read only.

ss

This is a bad idea.


03 May

Comment

Originally posted by Epiglottic

[BUG] I seem to be having audio issues.

1) When cargo ship is around and scientists shoot and when the horn goes off my audio for camp fire, chopping wood, hitting nodes, etc. seems to get cut out or not play at all.

I was able to reproduce it on 3 community servers.

I've experienced this myself, we'll take a look.

Comment

Originally posted by Baconislikemyfamily

BUG

Furnace skins not showing when placed.

show skins in inventory but when placing furnace its not skinned

Thanks, we're currently investigating this issue.

Update: This issue should now be resolved with Fridays client update.


02 May

Comment

We'll come clean.. it's Rust VR porn.

Comment

Originally posted by speedyporpoise

Names are SOOO SMALL on team in the map

We'll take a look at this.

Comment

Originally posted by BawbtheGoat

[QoL]

Change the way door collisions work in relation to items, not allowing doors to be placed if an item intersects them.

How to recreate:

Place an item near or in a doorframe, such as a workbench, and try to place a door in said doorframe.

This is currently the intended behaviour but we'll review it.

Comment

Originally posted by Vativ

[BUG] you can still place bags on oil rig lmao

We'll put out a fix for this on Friday.

Update: This issue should now be resolved with Fridays client update.

Comment

Originally posted by Zedgeftw

Compound bow arrow not textured

https://cdn.discordapp.com/attachments/571418462564384779/573601923312254995/unknown.png

This is a major disadvantage during night time

Please fix quickly

Thanks - We'll look into this.

Update: This issue should now be resolved with Fridays client update.


30 Apr

Comment

Originally posted by Exosumo

What clarifies as "suitable moments"? If I may ask.

We only attempt to stop GC during combat and while moving, any other actions we do not attempt to prevent GC.

Comment

Originally posted by Exosumo

Well, you can see why in the actual clip bottom left (garbage collector):

Before freeze - 2384 MB

After freeze - 2136MB

From https://rust.facepunch.com/blog/february-update -

If you have a lot of RAM you can help the algorithm by increasing the gc.buffer convar. The default value is 256MB, which means it will perform a collection at suitable moments after 128MB (or 50% of gc.buffer) and it will always perform a collection at any moment after 256MB (or 100% of gc.buffer). We expect the default value to be entirely sufficient for the entity and player counts on official servers.

2384 - 2136 = 248MB (pretty close to 256 as hardlimit)

I always set gc.buffer to max value of 2048 and I rarely get any lagspikes :)

This is the correct answer and with good responses.

Hey Facepunch, when u fix this?

Unfortunately, GC has to happen and there is no way around it, we're always trying to reduce memory allocations when and where possible and attempting to force garbage collections outside of vital tasks such as combat.

Unity 2019 has an experimental feature called incremental garbage collection which we'll explore in the coming months. Incremental garbage collection spreads the collection over multiple frames instead of causing one freeze. This is yet to be tested so we can't make any promises.


27 Apr

Comment

f*ck Alistair, f*ck Holmzy.. they should be working 24/7


23 Apr

Comment

Originally posted by Blizz_JeffKaplan

oh, no... i've been outed. here's what i am up to now:

https://i.imgur.com/TsfFp3c.png

Gonna push for a huge Junkrat statue on top of Dome.

Comment

Originally posted by xxdoompigxx

You seem to be someone to address issues with. /sil isn’t working. I heard that it’s a known issue and I was just wondering if you guys know when it will be fixed. Thanks!

/sil is a command for the signartist modded plugin. You'd need to contact the author of the plugin if you're having issues.


17 Apr

Comment

This issue should now be resolved.