View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
0000189Medieval EngineersBugpublic2022-04-09 19:432022-04-11 14:26
Reporterfairfaxthemoose Assigned Toequinox  
PrioritynormalSeveritycrashReproducibilityhave not tried
Status closedResolutionfixed 
PlatformWindows 
Fixed in Version0.7.3.968CF8 
Summary0000189: Immediate crash from structural integrity stress overload
Description

Across a period of 3 hours on 2 different worlds in over 15 attempts (re-logs post crash)

Maxing out the structural stress causing a collapse immediately crashes game

Stone is able to crash game with much less effort, a smaller part breaking off will crash
Wood supports can crash but its less likely and takes more fractures/parts unlike stone which is consistent

So far only noticed it on singular and double splits but as mentioned above it can be caused by literally a single stone block fragmenting

This has happened on everything from building a wall, making an aqueduct style bridge, making a free standing single arch bridge, and experimenting with stress on basic 1x1x14 vertical columns

Steps To Reproduce

A

  1. Build up a tower/column of stone blocks to the maximum stress threshold (should be 14-15)
  2. Take it over the threshold causing a break

B

  1. Build up a tower/column of stone blocks to the maximum stress threshold but then "overclock" the load bearing ability by flaring out the tower at the base on the same level as the red stress as to even it out (Should be about 3-4 blocks over the normal threshold)
  2. Take it over the threshold causing a break

C

  1. Build 2 normal towers to the max stress threshold
    2, Bridge the towers as to create a "bridge"
  2. Take one side of the bridge over the threshold OR remove a block from under one of the towers causing a break
TagsNo tags attached.

Relationships

duplicate of 0000193 resolvedequinox [DS] Crash: System.AccessViolationException - UpdateMotionType  

Activities

equinox

2022-04-11 14:26

administrator   #~0000136

Seems to be fixed by 0000193 (not yet released)

Issue History

Date Modified Username Field Change
2022-04-09 19:43 fairfaxthemoose New Issue
2022-04-11 14:26 equinox Assigned To => equinox
2022-04-11 14:26 equinox Status new => closed
2022-04-11 14:26 equinox Resolution open => fixed
2022-04-11 14:26 equinox Fixed in Version => 0.7.3.968CF8
2022-04-11 14:26 equinox Note Added: 0000136
2022-04-11 14:26 equinox Relationship added duplicate of 0000193