Eek! Games Forum

I'm running the game on a Paperspace virtual machine. The specs are: RAM 32GB, GPU GRIDK180Q with 4GB. I boot up the game and it looks great in Ultra, no lag, I can work around. But I can't look around. I unchecked all of the settings in the graphics menu of the game. I've tried lower quality. I'm running version 10.4. Please advise.

VM are not mean to be playing station, so don't expect much from so strange platform. The provider of such service should ensure the game you play on it to run fine, like if you use an emulator to play playstation 2 games on computer.

More seriously, this might be an unity issue with the gpu driver used to do the rendering. So you have to reach the vm administrator and check if unity 2018.whatever version is well supported by such system.

Yeah it may be that Unity cannot access DirectInput or the input device in general...check this doc for troubleshooting steps, specifically looking at the end (Section T6):

https://forum.eekllc.com/viewtopic.php?f=7&t=7

and then look here and follow these instructions to get your output_log for us, if possible:

https://forum.eekllc.com/viewtopic.php?f=7&t=8

erasmus wrote: Thu Sep 27, 2018 3:15 pm Yeah it may be that Unity cannot access DirectInput or the input device in general...check this doc for troubleshooting steps, specifically looking at the end (Section T6):

https://forum.eekllc.com/viewtopic.php?f=7&t=7

and then look here and follow these instructions to get your output_log for us, if possible:

https://forum.eekllc.com/viewtopic.php?f=7&t=8

I followed the steps but it didn't help. But I do have output from a log file:

Initialize engine version: 2017.4.7f1 (de9eb5ca33c5)
GfxDevice: creating device client; threaded=1
Direct3D:
Version: Direct3D 11.0 [level 11.0]
Renderer: NVIDIA GRID K180Q (ID=0xff7)
Vendor: NVIDIA
VRAM: 3708 MB
Driver: 9.18.13.4827
Begin MonoManager ReloadAssembly
- Completed reload, in 0.079 seconds
<RI> Initializing input.

XInput1_3.dll not found. Trying XInput9_1_0.dll instead...
<RI> Input initialized.

<RI> Initialized touch support.

UnloadTime: 2.481200 ms
Unloading 6 Unused Serialized files (Serialized files now loaded: 0)
UnloadTime: 25.165300 ms

Unloading 334 unused Assets to reduce memory usage. Loaded Objects now: 1515.
Total: 33.805500 ms (FindLiveObjects: 0.793700 ms CreateObjectMapping: 0.134500 ms MarkObjects: 2.782200 ms DeleteObjects: 30.089000 ms)

Setting up 4 worker threads for Enlighten.
Thread -> id: 19fc -> priority: 1
Thread -> id: 1384 -> priority: 1
Thread -> id: 1454 -> priority: 1
Thread -> id: 1690 -> priority: 1
Internal: JobTempAlloc has allocations that are more than 4 frames old - this is not allowed and likely a leak

(Filename: Line: 371)

Internal: JobTempAlloc has allocations that are more than 4 frames old - this is not allowed and likely a leak

(Filename: Line: 371)

Internal: JobTempAlloc has allocations that are more than 4 frames old - this is not allowed and likely a leak

(Filename: Line: 371)

Unloading 5 Unused Serialized files (Serialized files now loaded: 0)
Internal: JobTempAlloc has allocations that are more than 4 frames old - this is not allowed and likely a leak

(Filename: Line: 371)

Internal: JobTempAlloc has allocations that are more than 4 frames old - this is not allowed and likely a leak

(Filename: Line: 371)

Internal: JobTempAlloc has allocations that are more than 4 frames old - this is not allowed and likely a leak

(Filename: Line: 371)

Internal: JobTempAlloc has allocations that are more than 4 frames old - this is not allowed and likely a leak

(Filename: Line: 371)

Internal: JobTempAlloc has allocations that are more than 4 frames old - this is not allowed and likely a leak

(Filename: Line: 371)

Internal: JobTempAlloc has allocations that are more than 4 frames old - this is not allowed and likely a leak

(Filename: Line: 371)

Internal: JobTempAlloc has allocations that are more than 4 frames old - this is not allowed and likely a leak

(Filename: Line: 371)

Internal: JobTempAlloc has allocations that are more than 4 frames old - this is not allowed and likely a leak

(Filename: Line: 371)

UnloadTime: 2.755200 ms
Loaded Katherine's story successfully: C:/Users/paperspace/Documents/Eek/House Party/Mods/Stories/Original Story/Original Story.character

(Filename: C:\buildslave\unity\build\artifacts/generated/common/runtime/DebugBindings.gen.cpp Line: 51)

Loaded Amy's story successfully: C:/Users/paperspace/Documents/Eek/House Party/Mods/Stories/Original Story/Original Story.character

(Filename: C:\buildslave\unity\build\artifacts/generated/common/runtime/DebugBindings.gen.cpp Line: 51)

Loaded Rachael's story successfully: C:/Users/paperspace/Documents/Eek/House Party/Mods/Stories/Original Story/Original Story.character

(Filename: C:\buildslave\unity\build\artifacts/generated/common/runtime/DebugBindings.gen.cpp Line: 51)

Loaded Frank's story successfully: C:/Users/paperspace/Documents/Eek/House Party/Mods/Stories/Original Story/Original Story.character

(Filename: C:\buildslave\unity\build\artifacts/generated/common/runtime/DebugBindings.gen.cpp Line: 51)

Loaded Vickie's story successfully: C:/Users/paperspace/Documents/Eek/House Party/Mods/Stories/Original Story/Original Story.character

(Filename: C:\buildslave\unity\build\artifacts/generated/common/runtime/DebugBindings.gen.cpp Line: 51)

Loaded Phone Call's story successfully: C:/Users/paperspace/Documents/Eek/House Party/Mods/Stories/Original Story/Original Story.character

(Filename: C:\buildslave\unity\build\artifacts/generated/common/runtime/DebugBindings.gen.cpp Line: 51)

Loaded Stephanie's story successfully: C:/Users/paperspace/Documents/Eek/House Party/Mods/Stories/Original Story/Original Story.character

(Filename: C:\buildslave\unity\build\artifacts/generated/common/runtime/DebugBindings.gen.cpp Line: 51)

Loaded story successfully: C:/Users/paperspace/Documents/Eek/House Party/Mods/Stories/Original Story/Original Story.story

(Filename: C:\buildslave\unity\build\artifacts/generated/common/runtime/DebugBindings.gen.cpp Line: 51)

Loaded Derek's story successfully: C:/Users/paperspace/Documents/Eek/House Party/Mods/Stories/Original Story/Original Story.character

(Filename: C:\buildslave\unity\build\artifacts/generated/common/runtime/DebugBindings.gen.cpp Line: 51)

Loaded Madison's story successfully: C:/Users/paperspace/Documents/Eek/House Party/Mods/Stories/Original Story/Original Story.character

(Filename: C:\buildslave\unity\build\artifacts/generated/common/runtime/DebugBindings.gen.cpp Line: 51)

Loaded Ashley's story successfully: C:/Users/paperspace/Documents/Eek/House Party/Mods/Stories/Original Story/Original Story.character

(Filename: C:\buildslave\unity\build\artifacts/generated/common/runtime/DebugBindings.gen.cpp Line: 51)

Loaded Patrick's story successfully: C:/Users/paperspace/Documents/Eek/House Party/Mods/Stories/Original Story/Original Story.character

(Filename: C:\buildslave\unity\build\artifacts/generated/common/runtime/DebugBindings.gen.cpp Line: 51)

Loaded Brittney's story successfully: C:/Users/paperspace/Documents/Eek/House Party/Mods/Stories/Original Story/Original Story.character

(Filename: C:\buildslave\unity\build\artifacts/generated/common/runtime/DebugBindings.gen.cpp Line: 51)


Unloading 37 unused Assets to reduce memory usage. Loaded Objects now: 38159.
Total: 65.518700 ms (FindLiveObjects: 4.334400 ms CreateObjectMapping: 1.140700 ms MarkObjects: 59.779000 ms DeleteObjects: 0.255200 ms)

Unloading 4 Unused Serialized files (Serialized files now loaded: 0)
UnloadTime: 146.511200 ms

Unloading 1909 unused Assets to reduce memory usage. Loaded Objects now: 4932.
Total: 167.788900 ms (FindLiveObjects: 1.055100 ms CreateObjectMapping: 0.439900 ms MarkObjects: 47.150400 ms DeleteObjects: 119.136200 ms)

Tried running 11.3 on the VM and now the camera does move but the character is always looking up at the ceiling and when I move the mouse the camera moves very fast, even when I lowered sensitivity.

Did you try playing with any of the controller functions (F8) or using the Input Config option in the ESC Menu? Maybe binding those to your available inputs may help. This is just a first pass on our controller support so, bear with us. Unfortunately we cannot fully guarantee a setup like yours will ever be fully supported. Your logs don't even really ID any directInput failures so...whatever is reaching the game may essentially just be unintelligible to Unity/our engine.