Linked LOD?
- Dominant language
- C++
- Stars
- 3.3k
- Forks
- 353
- Avg merge
- 3d 16h
- Merged PRs (30d)
- 1
Description
**Description**
I played with linked_proxy and LOD, turning subsurfed cube to strong decimated versions.
I tested all the possible ways I think:
- In linked_proxy, if you LOD a linked object proxy, they get deleted from Armory LOD automatically after you open the linked object.
- Creating LOD objects in the original blend, then linking them into linked_proxy file doesn't show them in Krom.
- Doing both LODs in blend file and linked_proxy

results in the older version (cube instead of subsurfed cube) showing at LOD or the disappearance in Krom.
**Expected behavior**
See the LOD versions in Krom.
Further goal: keeping heavy meshes in blend files and the LOD versions in linked_proxy with Krom reading the original mesh only when needed according to LOD distance, NOT in the linked_proxy blend file viewport. Possible?
**System**
Blender: 2.8
Armory: 2019.11
OS: Win
Graphics card: GTX970
**Test File**
https://github.com/armory3d/armory_examples/tree/master/linked_proxy
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with the linked_proxy example in armory_examples and reproduce the LOD cases described using Blender 2.8 and Armory 2019.11. Compare the linked object, original blend, and Krom results to determine why LOD objects disappear, fail to load, or show the older mesh. Done means the expected LOD versions appear in Krom while heavy original meshes remain out of the linked_proxy viewport.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- blender
- Domain
- computer-graphics, game-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 28/100