Xtext 2.9 RuntimeModule(Xtext 2.9 RuntimeModule)

 这不是一件简单的事情，因为你会遇到100k“字体纹理”的内存问题。 由于您需要100k文本元素，因此您需要管理几个难题。 我也遇到过类似的问题，并将一些技术混合在一起以使其发挥作用。 简单地说，你需要某种LOD（“细节水平”）来完成这项工作。 该设置可能如下所示： 
 
 
 
 使用BufferGeometry构建的THREE.ParticleSystem，其中每个位置都是一个文本位置 
 
 
 一个“高”的TextureAtlas，上面有256个图像，你可以动态分配你周围的图像（4096px x 4096px，256x256px图像） 
 
 
 至少有一个“lowres”TextureAtlas，你有16x16px的图像。 你事先准备好了。 与之前的大小相同，但是您有文本的所有预览图像，每个图像的大小为16x16px。 
 
 
 一个kdtree数据结构，使用nearestneighbour算法来确定相机附近的位置（同样http://threejs.org/examples/#webgl_nearestneighbour ） 
 
 
 子成像模块可以直接在GPU上连续替换高纹理： https ： //github.com/mrdoob/three.js/pull/4661 
 
 
 每个位置的索引，告诉它应该用于显示的TextureAtlas上的哪个位置 
 
 
 你知道我要去哪里。 以下是一些关于我的经历的文档： 
 
 Stackoverflow帖子： 在three.js中显示数千个图像我（开始）解释我在做什么的博客： http ： //blogs.fhnw.ch/threejs/ 
 
 这样，在获得满意的结果之前需要相当长的时间。 使这个更简单的唯一方法是摆脱16x16px预览图像。 但我不建议......或者当然取决于你的设置。 也许你有水平？ 城市？ 或者只显示这些文本的一部分有意义的任何其他结构？ 在处理大事之前，这可能是值得的。 如果您打算真正开展这项工作并按照我所描述的方式实现这一点，我可以帮助您解决一些现有的代码和进一步的解释。 告诉我你要去哪里:) 

This is no simple matter since you'll run into memory issues with 100k "font textures". Since you want 100k text elements you'll have several difficulties to manage. I had a similar problem too once and tossed together a few techniques in order to make it work. Simply put you need some sort of LOD ("Level of Detail") to make that work. That setup might look like following:
 
 
 
A THREE.ParticleSystem built up with BufferGeometry where every position is one text-position
 
 
One "highres" TextureAtlas with 256 images on it which you allocate dynamically with those images that are around you (4096px x 4096px with 256x256px images)
 
 
At least one "lowres" TextureAtlas where you have 16x16px images. You prepare that one beforehand. Same size like previous, but there you have all preview images of your text and every image is 16x16px in size.
 
 
A kdtree data structure to use a nearestneighbour algorithm with to figure out which positions are near the camera (alike http://threejs.org/examples/#webgl_nearestneighbour)
 
 
The sub-imaging module to continually replace highres textures with directly on the GPU: https://github.com/mrdoob/three.js/pull/4661
 
 
An index for every position to tell it which position on the TextureAtlas it should use for display
 
 
You see where I'm going. Here's some docs on my experiences:
 
The Stackoverflow post: Display many thousand images in three.js The blog where I (begun) to explain what I was doing: http://blogs.fhnw.ch/threejs/
 
This way it will take quite some time until you have satisfying results. The only way to make this simpler is to get rid of the 16x16px preview images. But I wouldn't recommend that... Or of course something depending on your setup. Maybe you have levels? towns? Or any other structure where it would make sense to only display a portion of these texts? That might be worth a though before tackling the big thing. If you plan to really work on this and make this happen the way I described I can help you with some already existing code and further explanations. Just tell me where you're heading :)