crashing

[Violagameboy]

it keeps crashing every time i start the tutorial

[pavig]

Same here. Editor and workshop scenarios work fine though.

[Violagameboy]

Same thing

[Jakobeus]

me 2

[Jakobeus]

game ♥♥♥♥

[sebastian.aaltonen]

The reason is most likely that you have a GPU with 2 GB or less graphics memory. In some cases this isn't enough to run the game properly. The launch (v1.0) version of the game includes a new "low resolution volume" option that reduces GPU memory usage by 1 GB. This setting makes the game playable on all GPUs with 1.5 GB or 2 GB of memory.

We will keep you informed once we know the exact v1.0 launch date. Should be pretty soon.

[pavig]

I've got a 4gb nvidia 1050TI so graphics memory isn't the problem. The crash to desktop _always_and_only_ happens during the tutorial. Playing workshop levels or tinkering with the game at any other time doesn't produce a CTD. I'll post more if I can identify anything particular that might help to reproduce the error.

[sebastian.aaltonen]

Originally posted by pavig:

I've got a 4gb nvidia 1050TI so graphics memory isn't the problem. The crash to desktop _always_and_only_ happens during the tutorial. Playing workshop levels or tinkering with the game at any other time doesn't produce a CTD. I'll post more if I can identify anything particular that might help to reproduce the error.

Could you provide more info about your computer. Which CPU and how much main memory you have? The crash bug has so far affected only GPUs with 2 GB or less memory and CPU must be Haswell or older (PCI-E 2.0 instead of 3.0).

Details: The crash bug is caused by GPU driver timeout. World generation (1 GB world volume texture filling) takes more than 2 seconds -> timeout. Theoretically the bug could also happen with 4 GB GPUs, since WDDM doesn't guarantee that the 1 GB world volume texture is placed in GPU memory even if you have enough memory. Of course also with Windows platform having multiple monitors or background software open (such as browser with lots of tabs) affects this situation. If you are affected by any of these issues, the new "low resolution volume" option solves the crash bug, because even in the case of WDDM placing the volume texture to system RAM, the filling takes 8x less time preventing the driver timeout.

Our goal is to update the PC beta build next week. When that happens, I can give you a beta key so that you can test whether the new build (updated to UE 4.19) and/or the new "low resolution volume" option fixes the issue.

[pavig]

Originally posted by sebastian.aaltonen:

Could you provide more info about your computer. Which CPU and how much main memory you have? The crash bug has so far affected only GPUs with 2 GB or less memory and CPU must be Haswell or older (PCI-E 2.0 instead of 3.0).

Thanks for the more detailed explaination of the problem. Likely hardware is the issue, as though my gpu is recent, the rest of this box is ancient. :)

Computer Information:
Manufacturer: OEM
Model: OEM
Form Factor: Desktop
No Touch Input Detected

Processor Information:
CPU Vendor: GenuineIntel
CPU Brand: Intel(R) Core(TM)2 Quad CPU Q6600 @ 2.40GHz
CPU Family: 0x6
CPU Model: 0xf
CPU Stepping: 0xb
CPU Type: 0x0
Speed: 2448 Mhz
4 logical processors
4 physical processors
HyperThreading: Unsupported
FCMOV: Supported
SSE2: Supported
SSE3: Supported
SSSE3: Supported
SSE4a: Unsupported
SSE41: Unsupported
SSE42: Unsupported
AES: Unsupported
AVX: Unsupported
CMPXCHG16B: Supported
LAHF/SAHF: Supported
PrefetchW: Unsupported

Operating System Version:
Windows 10 (64 bit)
NTFS: Supported
Crypto Provider Codes: Supported 311 0x0 0x0 0x0

Video Card:
Driver: NVIDIA GeForce GTX 1050 Ti
DirectX Driver Name: nvldumd.dll
Driver Version: 24.21.13.9836
DirectX Driver Version: 24.21.13.9836
Driver Date: 6 24 2018
OpenGL Version: 4.6
Desktop Color Depth: 32 bits per pixel
Monitor Refresh Rate: 60 Hz
DirectX Card: NVIDIA GeForce GTX 1050 Ti
VendorID: 0x10de
DeviceID: 0x1c82
Revision: 0xa1
Number of Monitors: 1
Number of Logical Video Cards: 1
No SLI or Crossfire Detected
Primary Display Resolution: 1920 x 1080
Desktop Resolution: 1920 x 1080
Primary Display Size: 20.91" x 11.73" (23.94" diag)
53.1cm x 29.8cm (60.8cm diag)
Primary Bus: PCI Express 16x
Primary VRAM: 4095 MB
Supported MSAA Modes: 2x 4x 8x

Sound card:
Audio device: plantronics gamecom (Plantronic

Memory:
RAM: 6142 Mb

Miscellaneous:
UI Language: English
Media Type: DVD
Total Hard Disk Space Available: 1257407 Mb
Largest Free Hard Disk Block: 100653 Mb
OS Install Date: Jan 01 1970
Game Controller: XInput Controller #1 detected
VR Headset: None detected

[sebastian.aaltonen]

Originally posted by pavig:

Originally posted by sebastian.aaltonen:

Could you provide more info about your computer. Which CPU and how much main memory you have? The crash bug has so far affected only GPUs with 2 GB or less memory and CPU must be Haswell or older (PCI-E 2.0 instead of 3.0).

Thanks for the more detailed explaination of the problem. Likely hardware is the issue, as though my gpu is recent, the rest of this box is ancient. :)

Computer Information:
Manufacturer: OEM
Model: OEM
Form Factor: Desktop
No Touch Input Detected

Processor Information:
CPU Vendor: GenuineIntel
CPU Brand: Intel(R) Core(TM)2 Quad CPU Q6600 @ 2.40GHz
CPU Family: 0x6
CPU Model: 0xf
CPU Stepping: 0xb
CPU Type: 0x0
Speed: 2448 Mhz
4 logical processors
4 physical processors
HyperThreading: Unsupported
FCMOV: Supported
SSE2: Supported
SSE3: Supported
SSSE3: Supported
SSE4a: Unsupported
SSE41: Unsupported
SSE42: Unsupported
AES: Unsupported
AVX: Unsupported
CMPXCHG16B: Supported
LAHF/SAHF: Supported
PrefetchW: Unsupported

Operating System Version:
Windows 10 (64 bit)
NTFS: Supported
Crypto Provider Codes: Supported 311 0x0 0x0 0x0

Video Card:
Driver: NVIDIA GeForce GTX 1050 Ti
DirectX Driver Name: nvldumd.dll
Driver Version: 24.21.13.9836
DirectX Driver Version: 24.21.13.9836
Driver Date: 6 24 2018
OpenGL Version: 4.6
Desktop Color Depth: 32 bits per pixel
Monitor Refresh Rate: 60 Hz
DirectX Card: NVIDIA GeForce GTX 1050 Ti
VendorID: 0x10de
DeviceID: 0x1c82
Revision: 0xa1
Number of Monitors: 1
Number of Logical Video Cards: 1
No SLI or Crossfire Detected
Primary Display Resolution: 1920 x 1080
Desktop Resolution: 1920 x 1080
Primary Display Size: 20.91" x 11.73" (23.94" diag)
53.1cm x 29.8cm (60.8cm diag)
Primary Bus: PCI Express 16x
Primary VRAM: 4095 MB
Supported MSAA Modes: 2x 4x 8x

Sound card:
Audio device: plantronics gamecom (Plantronic

Memory:
RAM: 6142 Mb

Miscellaneous:
UI Language: English
Media Type: DVD
Total Hard Disk Space Available: 1257407 Mb
Largest Free Hard Disk Block: 100653 Mb
OS Install Date: Jan 01 1970
Game Controller: XInput Controller #1 detected
VR Headset: None detected

This is most likely the same problem we are seeing with other similar reports. Only reproducible with older CPUs with PCI-E 2.0 motherboards. Sometimes WDDM places the 1 GB volume texture on system memory at startup. It is filled completely on the first frame by the GPU. This causes lots of PCI-E bus traffic and unfortunately these older motherboards with PCI-E 2.0 do not have enough bandwidth to complete the operation in the 2 second time (before Windows TDR kicks in and reboots the video card driver). The new "low resolution volume" option will help you. I will inform you once we know the exact v1.0 launch date. We will update the Steam closed beta build before release (possibly late next week). I could give you a key if you want to test it.

[sebastian.aaltonen]

This bug should be fixed in the latest beta. You can enable beta in Steam library by left clicking Claybook and selecting Properties. From there go to BETAS tab and enable the beta from the dropdown.

When you have launched the beta build. Go to Settings menu and open Video tab. From there enable "Half Resolution Volume" option. This saves 1 GB of GPU memory and significantly reduces PCI-E traffic. Should fix problems with 2 GB cards and old motherboards.

Please inform me if this fixes the issue.

[MMaRsu]

I have the exact same issue, I'm going to try the beta branch. Thanks for this topic and the suggestion Sebastian!! I am currently streaming the game on Twitch so I'm just going to delete that stream and restart if it works!!

[MMaRsu]

Sadly the "Half Resolution Volume" option did not fix this crash for me and I currently cannot get to the tutorial. The creative mode seems to work, except when loading a community Claybook.

These are my specs btw :

AMD Phenom II X6 1090T @3.6ghz, 8gbram and a gtx1060 3gb.

I want to applaud you for communicating so directly with the community though! I love the look of this game and can't wait to start playing :).

[sebastian.aaltonen]

Originally posted by MMaRsu | Twitch.tv/mmarsu:

AMD Phenom II X6 1090T @3.6ghz, 8gbram and a gtx1060 3gb.

Could you post a screenshot of the error message?

This bug seems to occur only on Phenom, Sandy and Ivy Bridge processors. Haswell introduced lots of new instructions (such as popcnt, lzcnt). I need to confirm that this is indeed a GPU driver hang and not "illegal instruction". I do not use SSE4/AVX on PC, and I didn't find any lzcnt/popcnt code either (when PC ifdefs are enabled). On consoles we obviously use these new CPU instructions to improve performance.

[MMaRsu]

Sure thing, here it is :

https://imgur.com/a/tA15y7M

Basically that's all I get once I click the tutorial and it loads, the game just ctd.

The editor works just fine.. It's weird right?

[sebastian.aaltonen]

Originally posted by MMaRsu | Twitch.tv/mmarsu:

Sure thing, here it is :

https://imgur.com/a/tA15y7M

Basically that's all I get once I click the tutorial and it loads, the game just ctd.

The editor works just fine.. It's weird right?

I would need the log files mentioned in that screen. Click on (Click here to view directory) and you should see some files. If there's a log file, could you copy & paste the last 10 lines here?

Does the GPU driver also crash? Does your display go off and then back on and you see a dialog like this: https://nvidia.custhelp.com/app/answers/detail/a_id/3335/~/tdr-%28timeout-detection-and-recovery%29-and-collecting-dump-files

If there's no driver crash, then it is likely not GPU related, and could be for example invalid opcode related. In this case the "Half Resolution Volume" doesn't solve your particular issue.