Console output stops at "Loading scene" on Windows
In response to misticos ():
So the log file is stuck?
Yes, in Loading Scene
Try turning off the server
In response to misticos ():
Try turning off the server
Tried a plenty of times
In response to Survey ():
Tried a plenty of times
Even reinstalling it, weird

Merged post
 
In response to dIMjIM ():
hello, we have now again a NRE spamming our console and i cant find the full error in the logs.
Hey, have you fixed it? I'm having the same problem with WS
@misticos  he mean the same was i post before it dont log all

Initialize engine version: 2018.3.3f1 (393bae82dbb8)
Forcing GfxDevice: Null
GfxDevice: creating device client; threaded=0
NullGfxDevice:
    Version:  NULL 1.0 [1.0]
    Renderer: Null Device
    Vendor:   Unity Technologies
FMOD initialized on nosound output
Begin MonoManager ReloadAssembly
- Completed reload, in  0.165 seconds
WARNING: Shader Unsupported: 'Hidden/Internal-ScreenSpaceShadows' - Pass '' has no vertex shader
WARNING: Shader Unsupported: 'Hidden/Internal-ScreenSpaceShadows' - Pass '' has no vertex shader
WARNING: Shader Unsupported: 'Hidden/TerrainEngine/Splatmap/Diffuse-AddPass' - Pass 'Meta' has no vertex shader
WARNING: Shader Unsupported: 'Hidden/TerrainEngine/Splatmap/Diffuse-AddPass' - Pass 'Meta' has no vertex shader
UnloadTime: 3.950371 ms
3D Noise requires higher shader capabilities (Shader Model 3.5 / OpenGL ES 3.0), which are not available on the current platform: graphicsShaderLevel (current/required) = 30 / 35
 
(Filename: C:\buildslave\unity\build\Runtime/Export/Debug.bindings.h Line: 45)

Bootstrap Startup
System

	Name: ********
	OS:   Windows 8.1  (6.3.0) 64bit

CPU

	Model:  Intel(R) Core(TM) i7-6700K CPU @ 4.00GHz
	Cores:  8
	Memory: 65177 MB

GPU

	Model:  Null Device
	API:    NULL 1.0 [1.0]
	Memory: 128 MB
	SM:     30

Process

	Memory:   92 MB

Mono

	Collects: 15
	Memory:   1 MB



Manifest Metadata Loaded

	12927 pooled strings

	14 mesh colliders

	5883 prefab properties

	388 effect categories

	676 entity names

	86 skinnable names
Command Line: " ********* " 
Fallback handler could not load library C:/Server/2Rust4LifePvE/rustds/RustDedicated_Data/Mono/data-000000E91B644010.dll
Fallback handler could not load library C:/Server/2Rust4LifePvE/rustds/RustDedicated_Data/Mono/libc
Fallback handler could not load library C:/Server/2Rust4LifePvE/rustds/RustDedicated_Data/Mono/libc.dll
Fallback handler could not load library C:/Server/2Rust4LifePvE/rustds/RustDedicated_Data/Mono/libc
Fallback handler could not load library C:/Server/2Rust4LifePvE/rustds/RustDedicated_Data/Mono/data-000000E91B8EB010.dll
Fallback handler could not load library C:/Server/2Rust4LifePvE/rustds/RustDedicated_Data/Mono/data-000000E91B992040.dll
Fallback handler could not load library C:/Server/2Rust4LifePvE/rustds/RustDedicated_Data/Mono/data-000000E91B9BFA80.dll
Fallback handler could not load library C:/Server/2Rust4LifePvE/rustds/RustDedicated_Data/Mono/data-000000E91B9C6EC0.dll
Fallback handler could not load library C:/Server/2Rust4LifePvE/rustds/RustDedicated_Data/Mono/data-000000E92EFD5040.dll
[Manifest] URI IS "https://api.facepunch.com/api/public/manifest/?public_key=j0VF6sNnzn9rwt9qTZtI02zTYK8PRdN1"
 
(Filename: C:\buildslave\unity\build\Runtime/Export/Debug.bindings.h Line: 45)

Server Config Loaded
Running server/rust4life/cfg/users.cfg
 
(Filename: C:\buildslave\unity\build\Runtime/Export/Debug.bindings.h Line: 45)

Loading Items Took: 1.5530192 seconds
 
(Filename: C:\buildslave\unity\build\Runtime/Export/Debug.bindings.h Line: 45)

Building Items Took: 1.5639618 seconds / Items: 471 / Blueprints: 292
 
(Filename: C:\buildslave\unity\build\Runtime/Export/Debug.bindings.h Line: 45)

Skinnable Warmup
WARNING: Shader Unsupported: 'Standard' - Pass 'META' has no vertex shader
WARNING: Shader Unsupported: 'Standard' - Pass 'META' has no vertex shader
Manifest Assets Loaded

	86 skinnable objects
Loading Scene​


@Survey nope i dont fix it
In response to dIMjIM ():
@misticos  he mean the same was i post before it dont log all

Initialize engine version:...
Hey, can you confirm if this was fixed in this update?
In response to Survey ():
Hey, can you confirm if this was fixed in this update?
nope for me not :/
What about this update bro? It works?