JF make 100
JF Nav
JF Nav
Creation Date: 2002-03-10
So, what is this? It's not JF Scene 5, is it? No, but it's training for it. As you can see, we have a pretty simple scene. A guy, a billboard, a pillar, and a set of chairs. This is a scene that I ripped from Strange Days (one of my favorite movies of all time) VHS with my ASUS GeForce 2 card. It's one of the first videos that I've gotten from it since I don't own a TV or VCR. My neighbor lent me his VCR to grab an important video. I'm having a bit of trouble with my capture stuff. I'm going to mess with it. You know what that means, you should expect JF to be out of commission tomorrow. ^_^ Naw, I think you should expect Page 2. But what about this picture. We don't get to see the goon's face. Well, there's a reason. First off, it's the only picture with the gun in a correct position. Secondly, faces look awful when captured from TV. Thirdly, the background is nice. The picture is pretty small, I captured it at 320x240. It's odd because at 640x480, the capture program drops frames like nothing. But the solution is to compress before I save. The capture+compression program is saying that I have an invalid device. *shrug* So here I am with lo-res pic. But the oddest thing is that when it's not capturing, the picture looks good, but when it captures, it goes into 8-bit mode or something. It looks awful. But then when I compress it later, it looks much better. What is the problem? I think it's a header file giving incorrect color depth. But that should crash any program trying to read it. But now on to the picture. My simplifications are not very good. I just traced his body parts and traced the scenery. But a few interesting things pop out. First off, the floor is a perfect judge of position and orientation. We know that these lines are perfectly parallel and perpendicular. With that we can find the vanishing point, calculate the FoV, and the position of the camera. I like it. I should use that effect in JF. Of course, it won't look natural. You see, look at the lighting, shading, and shadowing. That's a huge part of it, right? The bright floor shining and the pillar is shadowing it, it's wild. Look how soft the shadow is, though. It's more of a darkening spot then a shadow. I doubt that a scene like this will be reproduced pixel for pixel in the next few years. But that's fine. I like real-time low-poly movies. Watching Jav busting heads together makes me smile. It's not even close to getting there, but I squelched out 90% of the memory leaks in AS3D today. That's not very easy. They should all be gone in a week. Then for more functionality. I need multiple Skinned Meshes, non-crashing videos, and better path stability. The skinned meshes ought to work, but they just don't. The videos I can make now crash most of the time and come out upside down and far too slow. Well, see for yourself [229 KB DivX]. Then there's the path system. As you can see in the movie, there's a white line across. That's an infinite number you're seeing. I don't know why, it must be the code somewhere.

I anticipated the Y2k-esque bug - the JF1C Bug - we see no power failures or nuclear meltdowns since JF making of strikes 100 pages. I was thinking about having a non JF1C compliant system, but then I decided to do it right. Of course, I wonder if I ever will have a server that only allows 8.3 names. I was thinking about it with AltSci ThinServer. Simply enough, I'd make the filename jfm12345.htm. But then after a few years, it'd expand past my limit. I'd have to rename it to jf123456.htm. But that's just silly. Who would ever think to put a page up per day for a million days? If it really got into the billions, it'd start using letters like 498rd3F2.htm. Then I'd have 62^8 combinations, plenty really. Actually, probably better would be to use directories. Then I'd have javantea.com/archive/62/JF2234.htm. That would allow infinite files since there are an infinite amount of subdirectories allowed. It's a bit of a hassle, right? A system like this would work, but static files are really extremely messy. Hyperlinks make them easy for users, but not for developers. If you have gigabytes of data, why not go with a database? One file: jfData.asd (ASDF is my own database format perfect for n-dimensional data) would have a double long ID giving room for 2^64 entries. But what about if we want thousands of terrabytes? Quadrillions of entries? Putting the sorting and using problem aside, I'd say that a relative location system would work pretty well. You'd have a distributed network with terrabyte servers worldwide (or even interplanetary if you'd like). One server would reference its direct connections only. The next one down the line would do the same. That way one could look through the data not burdening anyone too much just by asking its neighbors and asking its neighbors to ask their neighbors. Really, this is the modular way that the internet works. It's slightly more complicated seeing that we have IP addresses, ISPs, InterNIC, the backbone of the net, and subnets all over, but that's the basic stuff.

Anyway, enough babble. I need to study! Bemkyo, Bemkyo!
JF Nav
Home Characters Making Of Technical Mail News Links |< First < Prev Next > Latest >|  bandwidth version Goto Scene