uMod - Oxide update? - Rust

Posted 7 years ago

Last updated 6 years ago

In response to theonecsm36 ():
Wulf,

Seeing some wierd shader errors in console area - not affecting the game that I am...

Neither of those are Oxide issues, the warnings are from Rust and the airdrop is a known issue with Rust.

Posted 7 years ago

Last updated 6 years ago

#257

Wulf, sorry, last question tonight, would it be safe from now on to update Rust with the official non dev version of Oxide/uMod?

Posted 7 years ago

Last updated 6 years ago

#258

In response to Herro ():
Wulf, sorry, last question tonight, would it be safe from now on to update Rust with the official no...

I mean, no errors really at the moment, but there are still a handful of hooks disabled as noted in the changelog.

Posted 7 years ago

Last updated 6 years ago

#259

Thanks for the efforts today. How to donate?

Posted 7 years ago

Last updated 6 years ago

#260

MissinMethodException: Skinnable Skinnable.FindForEntity(string)

heres another one for you, cos you dont already have enough to do :P

running the release version you put up a little while ago, windows system

Posted 7 years ago

Last updated 6 years ago

#261

In response to legleg ():
MissinMethodException: Skinnable Skinnable.FindForEntity(string)heres another one for you, cos you...

That isn't from Oxide. A "MissingMethodException" around here generally means you're using mixed Rust versions, else something is wrong with the Rust build. This can happen from installing and older Oxide build (like from the past Rust update last month.)

Posted 7 years ago

Last updated 6 years ago

#262

hmm ok, so i must need to use the dev version? i thought youd updated the release version

Posted 7 years ago

Last updated 6 years ago

#263

In response to legleg ():
hmm ok, so i must need to use the dev version? i thought youd updated the release version

No, it is up-to-date with the latest Rust release, but it sounds like you're either getting an old build else that's just an error currently with Rust.

Posted 7 years ago

Last updated 6 years ago

#264

In response to Wulf ():
No, it is up-to-date with the latest Rust release, but it sounds like you're either getting an old b...

You can learn, had previously worked as a Russian console and now strange characters, it is possible to fix it?

Posted 7 years ago

Last updated 6 years ago

#265

ill start over and see what heppens. thx for the hard work mate

Posted 7 years ago

Last updated 6 years ago

#266

Wulf, we never had issues prior to update with the supply drop cargo plane large green crates being access.

I dropped two supply drops and both large green crates I could not access. Do you know what would cause this or how to fix?

Wulf - Also, the shader issues, I don't see them until after install Umod, prior on same computer vanilla server with new Rust update (no Umod) I am not seeing the same shader errors.

Posted 7 years ago

Last updated 6 years ago

#267

found it, steam didnt update didnt work properly for some reason. seems to be loading up as well as it can now

Posted 7 years ago

Last updated 6 years ago

#268

In response to theonecsm36 ():
Wulf, we never had issues prior to update with the supply drop cargo plane large green crates being...

That is not an oxide issue. Press F7 and report to facepunch

Posted 7 years ago

Last updated 6 years ago

#269

In response to Wulf ():
Not sure waht you mean by that, but Oxide doesn't handle any of the server networking.

Hey mate,

Its strange, when i install vanilla my users can connect, but as soon as i try to install the dev oxide (overriding the files from zip into the managed folder) no one can connect.

The log output looks fine, but the port isnt opened on the host/service - netstat also doesnt show the port (28015) despite rcon working fine. Its the only instance running on the host. Wireshark shows lots of packet activity on the port, but no one (even me locally) can connect. Its very odd. Am I doing something wrong?

[Update]
Ports are opened on my gateway. its all legit.

Posted 7 years ago

Last updated 6 years ago

#270

In response to Covfefe ():
That is not an oxide issue. Press F7 and report to facepunch

They are aware of this issue and are working on it, not sure why I am getting shader issues in console, anyone else???

Locked automatically

6 years ago

Oxide update?Solved