Go to Post If your heart is racing and you feel a little nervous, then you're on the right side of the alliance station wall!;) - David Brinza [more]
Home
Go Back   Chief Delphi > Competition > Rules/Strategy > You Make The Call
CD-Media   CD-Spy  
portal register members calendar search Today's Posts Mark Forums Read FAQ rules

 
 
 
Thread Tools Rate Thread Display Modes
Prev Previous Post   Next Post Next
  #26   Spotlight this post!  
Unread 13-02-2007, 08:49
Tristan Lall's Avatar
Tristan Lall Tristan Lall is offline
Registered User
FRC #0188 (Woburn Robotics)
 
Join Date: Aug 2001
Rookie Year: 1999
Location: Toronto, ON
Posts: 2,484
Tristan Lall has a reputation beyond reputeTristan Lall has a reputation beyond reputeTristan Lall has a reputation beyond reputeTristan Lall has a reputation beyond reputeTristan Lall has a reputation beyond reputeTristan Lall has a reputation beyond reputeTristan Lall has a reputation beyond reputeTristan Lall has a reputation beyond reputeTristan Lall has a reputation beyond reputeTristan Lall has a reputation beyond reputeTristan Lall has a reputation beyond repute
Re: [YMTC]: field of view

Quote:
Originally Posted by dlavery View Post
It is a safety violation, as previously indicated. Q.E.D.
Just to be fair, that Q&A response was posted after all of the arguing above....

Fortunately for gameplay, they did make the distinction between causing a robot to become obscured, and using a device which causes the robot to become obscured, and specified that this applies to blocking the view of opposing drivers only.

The trouble is, this really makes it much more of a gameplay ruling than a safety one—let's say that the red team are a pack of morons and they obscure the view of one of their alliance partners. It seems that that's just as unsafe as if an opponent did the same. Apart from the fact that red team 1's drivers are within yelling distance ("stop it, you morons"), red team 2 has the same conundrum: keep driving (by definition unsafely), or stop and wait for the obstruction to pass (which won't happen if red 1 gets disabled). And I realize that penalizing red 1 also penalizes red 2 and red 3—so that's not an ideal situation either. If only <S01> called for individual disqualifications....

In fact, if this were being enforced on the basis of gameplay, nobody would really care if doing the same stupid thing to your alliance is treated unequally. But for safety, shouldn't there be a solution that can be applied uniformly to whichever team is causing the hazard? As if I haven't belaboured the point enough already, let me just say it: why not describe this as a new gameplay rule, and include it in the next update?

Last edited by Tristan Lall : 13-02-2007 at 08:55. Reason: Clarification.
Reply With Quote
 


Thread Tools
Display Modes Rate This Thread
Rate This Thread:

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
What is the field of view (FOV) of the default lens? Jared Russell Programming 7 26-01-2006 21:54
Camera's Field of View? Greg Marra Programming 1 26-01-2006 13:17
Multiple tetras in field of view Mr. Lim Programming 0 14-02-2005 14:52
YMTC: Redabot Splits the Field Natchez You Make The Call 12 23-01-2005 22:29
YMTC: Redateam uses remote kickoff field Natchez You Make The Call 22 06-01-2005 21:05


All times are GMT -5. The time now is 18:36.

The Chief Delphi Forums are sponsored by Innovation First International, Inc.


Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2017, Jelsoft Enterprises Ltd.
Copyright © Chief Delphi