Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem














Streighr->Straight will be changed :'D
The game's check for the **'F' direct edit** is a **physical raycast check** performed against the block's 3D geometry when a player looks at it.
Definition
Geometry
'F' Edit Status
Root Cause (Based on Model)
**Corner**
Complex, but likely has a flat, accessible screen face.
**Works**
The raycast hits the screen surface correctly.
**Ramp**
Slanted, angled face.
**Fails**
The raycast hits the screen at an **angle too oblique** to satisfy the game's internal threshold for direct interaction.
**Straight**
Flat face, but part of a custom mod series.
**Fails**
The screen mesh in the **`LCDWallTwoSidedStreight.mwm`** model is likely **recessed, too thin, or misaligned** with the block's outer collision box, causing the raycast to hit the surrounding structure instead of the intended screen surface.
Summary of Conclusions
----------------------
Here is why the provided evidence supports the conclusion:
### 1\. The XML Confirms the _Potential_ for 'F'
All three definitions use the exact same critical tags that grant the _capability_ for both the 'K' (Terminal) and 'F' (Direct Edit) shortcuts:
* **`<Definition xsi:type="MyObjectBuilder_TextPanelDefinition">`**
* **`<TypeId>TextPanel</TypeId>`**
Since the **Corner** definition (which works) uses these tags, and the **Ramp** and **Straight** definitions (which fail) also use these tags, the issue cannot be fixed by changing any of the listed XML properties. The problem must occur _after_ the game loads the block's C# behavior.