This issue should now be resolved.
The server does no rendering, shaders are stripped while building the server.
You can safely ignore these warnings.
"culling.toggle 0" indeed fixes the problem.
Cheers.
culling.toggle 0 is the only one needed to fix the problem. I just tried it again when the problem returned.
There is an OCCLUSION CULLING toggle at the bottom of the menu / graphics settings, untoggling that should have had the same effect.
OK, so I just logged in and I went out my base and heard but couldn't see a pig, after wandering around a bit, the pig just appeared, so I backed up and it disappeared. Problem replicated! I then tried both your commands. I tried "playercull.enabled 0" first and nothing happened, then I tried "culling.toggle 0" and the pig, and 3 more in the general area all appeared. Seems that is related. If it happens again I'll try the commands in reverse order and report if it's a combination of 2 or if just one fixes the problem
Thank you! This is very helpful.
Well with the amount of recent false bans going around, this gives me hope. I got banned yesterday, coincidentally after reinstalling my Nvidia drivers while playing. Which coincidentally afterwards my game started crashing. About 20 crashes in 2 days later, I get banned while playing Savas.
Looks like that EAC change from the QOL update kinnnnnnda f**ked everything up
If you dont mind me asking, how long did it take for them to unban you? I sent in an appeal and described what happened but I have no idea when to expect a reply
Paging u/Alistair_Mc , is there a confirmed uptick in EAC false bans recently?
Yes, unfortunately, a number of accounts were falsely banned.
There was one edge case in a cheat detection which caused a false positive which was found by EAC from player appeals. All the affected accounts have since had their ban removed.
- OK, so the issue does not happen 100% of the time. Sometimes it works great, other times it does not.
- When it does happen, it happens for all NPCs (scientists and animals), and all players.
- I'll get back to you when it happens again, I've been lucky the last few times I've logged in the problem hasn't been a problem.
Thank you. It would be really important for us to know if any, or both, of those console commands solve the problem.
Also would help to know if you're playing Rust Staging or the regular/stable version.
Players/animals/scientists are invisible until I am 10 m or closer to them. I tried every settings I could find. I play on a macbook Pro 2018. I am very annoyed of the situation. I might quit the game for a while since that it is unplayable right now.
Please help me fix this issue.
I'll do my best to help get this sorted out, just need a bit more info, if you (or /u/the-net-imp) don't mind sharing:
We'll investigate and reach out to EAC.
Edit:
I'd expect this to rather an edge case as none of our test systems shows this issue and other factors could be at play. Don't jump on the EAC hate bandwagon and don't expect a sudden FPS boost.
We'll be releasing a fix for this shorty.
[BUG] Cant loot bodies thhey either despawn or become unlootable
We're looking into this.
Update: We've released a fix for this, please update your clients.
BUG
cant loot bodies
when you kill em, they go all elasticy then you cant loot em.
i killed myself, my teammate could loot me, my other mate couldnt and i cant loot my own body
EDIT - on the r/playrust main US server. other people in chat are reporting same thing
NOW BODYS JUST DISAPPEAR WHEN YOU KILL SOMEONE!!
We're looking into this.
Update: We've released a fix for this, please update your clients.