Some time ago, I started writing a VMF map viewer in JavaScript. But I had a problem with my BSP algorithm generating too many vertices.
You'll wait event longer for the end of these lines:
Then I went on to work on another project, and I totally forgot I had this in the first place (Could this be the explanation for HL3 ?).
But 57 pages later, I reopened THAT folder and decided to finally fix it. By porting the original code to JavaScript (
specifically that part). Which makes me wonder how the Source SDK license handles porting the code to another language ...
But after digging into Source engine internals (and also some bits of Quake III code), I finally managed to get the CSG calculation right. While I was at it, I decided to move from a simple web page to using nw.js, which allows me to access directly the filesystem from JavaScript.
Unreadable Dustbowl screenshot:
What's on my todo list:
- Code a native binding for VTFlib, and display textures instead of (ugly?) colors
- Add better support for displacements
- Display sprite entities (parsing FGD files to get this info should not be a problem)
What's not in my todo list:
- Display meshes entities (unless I find an easy way to load mdl files)
- Allow edition of the maps (the real problem here is not making the scene editable, it's writing the map back into a VMF)
- Learn how to map
See you in 6 month !