<!-- MHonArc v2.4.4 -->
<!--X-Subject: Re: [MUD-Dev] The MLI Project -->
<!--X-From-R13: pbqreNvoz.arg -->
<!--X-Date: Mon, 23 Feb 1998 00:20:52 +0000 -->
<!--X-Message-Id: 199802230020.AAA22112#out4,ibm.net -->
<!--X-Content-Type: text/plain -->
<!--X-Reference: 0953.980217#io,com -->
<!--X-Head-End-->
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<html>
<head>
<title>MUD-Dev message, Re: [MUD-Dev] The MLI Project</title>
<!-- meta name="robots" content="noindex,nofollow" -->
<link rev="made" href="mailto:coder#ibm,net">
</head>
<body background="/backgrounds/paperback.gif" bgcolor="#ffffff"
text="#000000" link="#0000FF" alink="#FF0000" vlink="#006000">
<font size="+4" color="#804040">
<strong><em>MUD-Dev<br>mailing list archive</em></strong>
</font>
<br>
[ <a href="../">Other Periods</a>
| <a href="../../">Other mailing lists</a>
| <a href="/search.php3">Search</a>
]
<br clear=all><hr>
<!--X-Body-Begin-->
<!--X-User-Header-->
<!--X-User-Header-End-->
<!--X-TopPNI-->
Date:
[ <a href="msg00553.html">Previous</a>
| <a href="msg00555.html">Next</a>
]
Thread:
[ <a href="msg00515.html">Previous</a>
| <a href="msg00535.html">Next</a>
]
Index:
[ <A HREF="author.html#00554">Author</A>
| <A HREF="#00554">Date</A>
| <A HREF="thread.html#00554">Thread</A>
]
<!--X-TopPNI-End-->
<!--X-MsgBody-->
<!--X-Subject-Header-Begin-->
<H1>Re: [MUD-Dev] The MLI Project</H1>
<HR>
<!--X-Subject-Header-End-->
<!--X-Head-of-Message-->
<UL>
<LI><em>To</em>: <A HREF="mailto:mud-dev#null,net">mud-dev#null,net</A></LI>
<LI><em>Subject</em>: Re: [MUD-Dev] The MLI Project</LI>
<LI><em>From</em>: <A HREF="mailto:coder#ibm,net">coder#ibm,net</A></LI>
<LI><em>Date</em>: Sun, 22 Feb 98 16:04:02 -0800</LI>
<LI><em>Reply-to</em>: <A HREF="mailto:coder#ibm,net">coder#ibm,net</A></LI>
</UL>
<!--X-Head-of-Message-End-->
<!--X-Head-Body-Sep-Begin-->
<HR>
<!--X-Head-Body-Sep-End-->
<!--X-Body-of-Message-->
<PRE>
On 17/02/98 at 08:40 PM, Travis Casey <efindel#polaris,net> said: >On
Monday, 16 February 98, Coder wrote:
>> Quite. Typically you can rely on the opponents having noticiably slowed
>> targetting routines. Blurring your peripheral vision puts some balance
>> back in their favour (not necessarily a Good Thing), as well as tending to
>> reward careful and circumspect play ("I don't know if anybody is there,
>> cause I can't see it too well, so I'd better be a lot more sneaky...")
>> which could be either a Good or Bad Thing.
>The only problem I can see with blurring areas of the screen to simulate
>blurred peripheral vision is that most people can shift the point they're
>focusing their eyes on much faster than most games that I've experienced
>allow you to shift your view.
True. The root intent of the peripheral blurring would not be to aid the
player or to make the game more realistic, but to make the control of
focal point a tactical skill heavily required by the game. (This becomes
especially interesting with near-360 degree views) A similar effect could
be had by restricting the player's view to a small angle, say a 20 degree
cone...
Ever seen the screen saver which apes the spot a flashlight beam wandering
the screen (all the screen is black except for the illuminated circle
which is shown in full detail)? In a way this would be very similar, with
the addition of a proper penumbra etc (an abuse of the term, but it will
do).
>Thus, you're giving the players a
>restriction in how they can look at things that they wouldn't really have
>if they were "in the game."
Yup. I'm attempting neither immersion or "reality".
>> The current tendency is to map the non-focus window's colour pallet to a
>> shadow set (typically grayed versions of the originals). It works
>> reasonably. The advantage of keeping the resolution high is that it still
>> allows the eyeball to carefully watch state changes in non-focal windows.
>> We don't have a GUI which moves focus according to eyeball focal point yet
>> -- tho I'm sure Playboy's research dept would love to see one.
>Even if we did, I have to wonder -- which would take more
>computational effort, showing the whole screen in full detail, or keeping
>track of the user's eye movements and trying to show only the portion
>he/she is looking at in full detail? In an action game, where the player
>may constantly be scanning back and forth look for warning signs of
>danger, it might be possible that doing the entire screen in full detail
>would turn out to be less work.
I note that a major technique of mine in playing Descent and Doom-clones
is constant and regular scanning of the surroundings. As I'm a
keyboard-only player, a friend commented that I had spaghetti fingers
after watching me pirroutte whilst running full tilt down a long corridor.
--
J C Lawrence Internet: claw#null,net
----------(*) Internet: coder#ibm,net
...Honourary Member of Clan McFud -- Teamer's Avenging Monolith...
</PRE>
<!--X-Body-of-Message-End-->
<!--X-MsgBody-End-->
<!--X-Follow-Ups-->
<HR>
<!--X-Follow-Ups-End-->
<!--X-References-->
<UL><LI><STRONG>References</STRONG>:
<UL>
<LI><STRONG><A NAME="00515" HREF="msg00515.html">Re: [MUD-Dev] The MLI Project</A></STRONG>
<UL><LI><EM>From:</EM> Travis Casey <efindel#polaris,net></LI></UL></LI>
</UL></LI></UL>
<!--X-References-End-->
<!--X-BotPNI-->
<UL>
<LI>Prev by Date:
<STRONG><A HREF="msg00553.html">Position sorting</A></STRONG>
</LI>
<LI>Next by Date:
<STRONG><A HREF="msg00555.html">Re: [MUD-Dev] The MLI Project</A></STRONG>
</LI>
<LI>Prev by thread:
<STRONG><A HREF="msg00515.html">Re: [MUD-Dev] The MLI Project</A></STRONG>
</LI>
<LI>Next by thread:
<STRONG><A HREF="msg00535.html">The MLI Project</A></STRONG>
</LI>
<LI>Index(es):
<UL>
<LI><A HREF="index.html#00554"><STRONG>Date</STRONG></A></LI>
<LI><A HREF="thread.html#00554"><STRONG>Thread</STRONG></A></LI>
</UL>
</LI>
</UL>
<!--X-BotPNI-End-->
<!--X-User-Footer-->
<!--X-User-Footer-End-->
<ul><li>Thread context:
<BLOCKQUOTE><UL>
<LI><STRONG>Re: [MUD-Dev] The MLI Project</STRONG>, <EM>(continued)</EM>
<ul compact>
<ul compact>
<ul compact>
<LI><strong><A NAME="00506" HREF="msg00506.html">Re: [MUD-Dev] The MLI Project</A></strong>,
coder <a href="mailto:coder#ibm,net">coder#ibm,net</a>, Tue 17 Feb 1998, 03:23 GMT
<UL>
<LI><strong><A NAME="00509" HREF="msg00509.html">Re: [MUD-Dev] The MLI Project</A></strong>,
Caliban Tiresias Darklock <a href="mailto:caliban#darklock,com">caliban#darklock,com</a>, Tue 17 Feb 1998, 06:19 GMT
<UL>
<LI><strong><A NAME="00517" HREF="msg00517.html">Re: [MUD-Dev] The MLI Project</A></strong>,
Travis Casey <a href="mailto:efindel#polaris,net">efindel#polaris,net</a>, Wed 18 Feb 1998, 04:42 GMT
</LI>
</UL>
</LI>
<LI><strong><A NAME="00515" HREF="msg00515.html">Re: [MUD-Dev] The MLI Project</A></strong>,
Travis Casey <a href="mailto:efindel#polaris,net">efindel#polaris,net</a>, Wed 18 Feb 1998, 04:37 GMT
<UL>
<LI><strong><A NAME="00554" HREF="msg00554.html">Re: [MUD-Dev] The MLI Project</A></strong>,
coder <a href="mailto:coder#ibm,net">coder#ibm,net</a>, Mon 23 Feb 1998, 00:20 GMT
</LI>
</UL>
</LI>
<LI><strong><A NAME="00535" HREF="msg00535.html">The MLI Project</A></strong>,
s001gmu <a href="mailto:s001gmu#nova,wright.edu">s001gmu#nova,wright.edu</a>, Fri 20 Feb 1998, 09:54 GMT
</LI>
</UL>
</LI>
</ul>
<LI><strong><A NAME="00501" HREF="msg00501.html">Re: [MUD-Dev] The MLI Project</A></strong>,
Vadim Tkachenko <a href="mailto:vadimt#4cs,com">vadimt#4cs,com</a>, Mon 16 Feb 1998, 23:31 GMT
<UL>
<LI><strong><A NAME="00520" HREF="msg00520.html">Re: [MUD-Dev] The MLI Project</A></strong>,
Travis Casey <a href="mailto:efindel#polaris,net">efindel#polaris,net</a>, Wed 18 Feb 1998, 04:47 GMT
<UL>
<LI><strong><A NAME="00546" HREF="msg00546.html">Re: [MUD-Dev] The MLI Project</A></strong>,
Stephen Zepp <a href="mailto:zoran#enid,com">zoran#enid,com</a>, Sat 21 Feb 1998, 01:25 GMT
</LI>
</UL>
</LI>
</UL>
</LI>
</ul>
</ul>
</LI>
</UL></BLOCKQUOTE>
</ul>
<hr>
<center>
[ <a href="../">Other Periods</a>
| <a href="../../">Other mailing lists</a>
| <a href="/search.php3">Search</a>
]
</center>
<hr>
</body>
</html>
