<DIV>You mgiht have a problem though with image intensity. The peripheral vision is much more sensative to light changes and movement than that at the fovea. Plus you also mention about movement of the eye. You would be able to focus on the "blurred" image without moving you head and that could be pretty distracting. Also, your head can move a lot faster than that servo mirror could. I suspect you might get some lag time between your sharp image and your ocular focal point. Interesting idea.</DIV>
<DIV> </DIV>
<DIV>Jay<BR><BR><B><I>Marv De Beque <mdebeque@woh.rr.com></I></B> wrote:</DIV>
<BLOCKQUOTE class=replbq style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #1010ff 2px solid"><BR>Here is another thought. Two views are all that are required using two<BR>projectors.<BR><BR>View number 1 is a super wide angle view that spans the complete view area.<BR>Obviously at 1024 by 768 this would make the view very, very pixilated or<BR>low resolution, but that is perfectly fine.<BR><BR>View number 2 is also 1024 by 768, but is a narrow field of view (perhaps 10<BR>to 20 degrees or so). It is aimed by a moveable mirror at the point that<BR>the pilot is looking (head tracking could provide the needed information as<BR>to where to aim). Two mirrors are required, but only one need move. The<BR>moving mirror can be servo controlled and since it is low mass it can swing<BR>the image to the desired spot as rapidly as the pilot moves.<BR><BR>View number 1 represents the peripheral vision. This is the view that the<BR>eye sees outside of the fovea. As you know, you can't read
from your<BR>peripheral vision, so low resolution is fine. To remove sharp contrasts<BR>between pixels, I would defocus the image slightly to create a natural blur.<BR><BR>However, images that strike the fovea can take advantage of the high<BR>resolution image from number 2, which is actually a very narrow angular<BR>section of one's view. You need to expand the view of number 2 a little<BR>beyond the normal eye's viewing angle to allow for eye movement when your<BR>head is not pointed directly at the field of view, but you should have<BR>plenty of resolution to spare for this. This image would be about 3 to 4<BR>times sharper than what you currently see in Falcon 4!<BR><BR>Again, as Mark pointed out, it ain't dirt cheap, but it is easily<BR>technically achievable using ordinary off-the-shelf components and I believe<BR>the results would be spectacular.<BR><BR>Marv<BR><BR><BR><BR><BR>On 10/14/03 12:54 PM, "Mark Doran" <MARK_S_DORAN@HOTMAIL.COM>wrote:<BR><BR>> I think the way
Erwin describes it on his site makes most sense to me. Like<BR>> commercial simulation environments distributed processing makes this problem<BR>> tractable.<BR>> <BR>> I don't have a lot of faith in the availability of head mounted displays<BR>> that have the right resolution, latency and transparency (you want to be<BR>> able to see the physical buttons and lights in your cockpit as you fly,<BR>> right?? ;-) anytime soon at a price I can afford.<BR>> <BR>> However, the prospect of assembling perhaps a dozen computers in a little<BR>> network for managing and rendering multiple view fields of the same "out the<BR>> window" scene is most definitely within reach, not cheap I'll grant you but<BR>> within the bounds of possibility at today's cost points for machines.<BR>> <BR>> The old Fighter Dual had the mode that I would want for Falcon5: a master<BR>> machine that you fly, it has your controllers and all that jazz. Like any<BR>> other
game, that machine can be commanded to show any view but generally you<BR>> want to pick one. To this you slave up to eight other machines (I think it<BR>> was 8) and each is a non-flyable replica of the game running on the master.<BR>> In other words, the jet modeled in the game on the slave is the exact same<BR>> one as that one the master. The slaves can be commanded to show any view in<BR>> the game also. So set up master and slaves to show a different view on each<BR>> one. This actually worked pretty well in Fighter Duel in my experience.<BR>> <BR>> The good part of doing it this way is that the game developer wouldn't have<BR>> to change the way on-screen views are done. The default player will only<BR>> have one master machine and will see the same view types as today. The<BR>> cockpit guy with multiple slaves as well will simply have multiple monitors<BR>> (or projectors) each set to a typical 60 degree slice of view field.<BR>>
Perhaps the only really hard part on the developer (with respect to view<BR>> rendering that is) is making sure that the views supported don't really<BR>> overlap in bad ways...if would be nice for the game engine to think about<BR>> seams in other words.<BR>> <BR>> This sort of approach would have some pretty serious requirements on in-game<BR>> networking support of course. Syncing multiple copies of a prop-job is a<BR>> lot easier than something more sophisticated like an F-16 flying in a<BR>> missile-laden, electronic warfare rich, combat environment. Having on the<BR>> order of 10 clones of the one F-16 trying to stay in sync will require, I<BR>> would imagine, quite a lot of bandwidth. One wonders what the implications<BR>> on bandwidth and latency might be if you want to have more than one pilot<BR>> link for a multiplayer session in this kind of multi-view setup...the mind<BR>> bogles but this would be the ultimate goal I would
say...think: sort of like<BR>> the twin dome sims that MacAir has at it's facility in St Louis.<BR>> <BR>> So much for thoughts on implementation strategy...I'd actually vote for any<BR>> implementation strategy that would work, because... More generally I think<BR>> support for multiple view fields displayed simultaneously is the feature I'd<BR>> say would generate the biggest advance in the state of the art for fast jet<BR>> combat flight sims. Who needs padlock?? ;-)<BR>> <BR>> Cheers,<BR>> <BR>> Mark.<BR>> <BR>> <BR>>> -----Original Message-----<BR>>> From: Inventmd@aol.com [mailto:Inventmd@aol.com]<BR>>> Sent: Monday, October 13, 2003 7:42 PM<BR>>> To: simpits-tech@simpits.org<BR>>> Subject: [simpits-tech] Falcon views 360?<BR>>> <BR>>> With all this talk about Falcon 5.0 coming out, I wonder if it doesn't<BR>> make<BR>>> sense to discuss our wish lists out loud.<BR>>> <BR>>> I
think the biggest detraction from realism of any flight simulation is<BR>> the<BR>>> inability to look at the scenery around you. Whether it be multiple<BR>> monitor<BR>>> support, or headmounted video goggles that pan around cockpit slaved to<BR>> head<BR>>> movements, my two cents is that this issue receive some attention.<BR>>> <BR>>> Perhaps the Falcon community could come to some sort of agreement in terms<BR>> of<BR>>> the ideal algorithm for displaying the environment as close as 360 degrees<BR>> as<BR>>> possible.<BR>>> <BR>>> Perhaps the easiest is the headmounted goggle system with some sort of<BR>>> tracking device. This would be similar to the padlock view but with the<BR>> visual<BR>>> display tracking in Synchrony with head movements rather than panning<BR>> about using<BR>>> the arrow keys.<BR>>> <BR>>> It would be nice to have Falcon support for scalable multiple
monitor<BR>> views.<BR>>> Specifically, support for a minimum of four monitors would be required:<BR>>> front, left, right, above. (And a 5th to check six) Scalability (or zoom)<BR>> would be<BR>>> important so that everything could be adjusted for different monitor sizes<BR>> at<BR>>> different distances (or video projector scenarios). In other words, for<BR>> those<BR>>> with four projectors and large rooms, it might be nice for the left view<BR>>> display to merge and even overlap into the front view display and the<BR>> "above view"<BR>>> display. For those no space and small monitors, one might need to scale<BR>> the<BR>>> picture down to get the appropriate field of view for the monitor position<BR>> --<BR>>> and certainly not overlap.<BR>>> <BR>>> There are some incredibly smart people on this forum-so I figure maybe we<BR>> can<BR>>> get your smarts into the project.<BR>>>
<BR>>> John Li<BR>> _______________________________________________<BR>> Simpits-tech mailing list<BR>> Simpits-tech@simpits.org<BR>> http://www.simpits.org/mailman/listinfo/simpits-tech<BR>> To unsubscribe, please see the instructions at the bottom of the above page.<BR>> Thanks!<BR><BR>_______________________________________________<BR>Simpits-tech mailing list<BR>Simpits-tech@simpits.org<BR>http://www.simpits.org/mailman/listinfo/simpits-tech<BR>To unsubscribe, please see the instructions at the bottom of the above page. Thanks!</BLOCKQUOTE>