[ 3 / biz / cgl / ck / diy / fa / ic / jp / lit / sci / vr / vt ] [ index / top / reports ] [ become a patron ] [ status ]
2023-11: Warosu is now out of extended maintenance.

/vr/ - Retro Games

Search:


View post   

>> No.7429518 [DELETED]  [View]
File: 7 KB, 200x200, Ken2006.jpg [View same] [iqdb] [saucenao] [google]
7429518

Reminder that Ken Silverman's Voxlap engine was far more advanced than anything Carmhack could ever have come up with. Ken made a 3D engine with fully destructible environment a decade before Minecraft came out, something "muh Based Carmack" could only dream about and look on enviously.

>> No.7384014 [View]
File: 7 KB, 200x200, Ken2006.jpg [View same] [iqdb] [saucenao] [google]
7384014

>>7384005
>Everything with this system was going fine until we discovered that Ken has some engine flaws in dealing with sprites that use origin based centering. The clipmove() function doesn't work, and neither does hitscan(). These two functions are pretty much essential to doing anything with the engine. I could rewrite them, of course, but that would be a few days to weeks out of our schedule, depending on how many more bugs and design problems crawl out of the woodwork.

>We had waited a few months before switching to the new origin based centering, so I was quite surprised to find such fundamental problems with it. We called up Ken and told him about it, and he said he didn't think anyone was using it, but he really didn't know. We asked him to fix it.

>Tonight I called up Ken because of the group file problems, and because we still don't have a fix for the clipmove() or hitscan() problems. Ken he wasn't going to fix it and we should go back to using the old centering mode. This is totally and completely unacceptable. We've already invested time and effort (need I say money?) into using something, and we're not about to waste more regressing.

>Ken understands algorithms, and he understands graphics. What he doesn't get is how to design SYSTEMS. Everything he does to the engine is a piecemeal enhancement to something that should have been designed right from the beginning. The memory system is a poignant example of this. It is a hack, like most of his code, and not very robust. From what I've disassembled of the group file code (trying to figure out a way to eliminate or replace it), it too demonstrates plentiful opportunities for crashing the system -- pointers being freed without validation, files being closed without verifying the handle, etc.

Navigation
View posts[+24][+48][+96]