|
|
|
![]() |
|
|||||||
|
||||||||
![]() |
|
|
Thread Tools |
Rating:
|
Display Modes |
|
|
|
#1
|
|||
|
|||
|
Re: Propose possible fixes for high goals
Quote:
Quote:
This isn't really a big deal. In every sporting event there are challenges. They don't stop a baseball game because it is windy, batters just try to keep the ball low to avoid the wind. Same in football, soccer, or any sport played outside... Adjust your shot, modify your strategy, play the game you were given. |
|
#2
|
||||
|
||||
|
Re: Propose possible fixes for high goals
I think it's totally fair. It's just all part of the design challenge. It probably is hard to change the trajectory of a catapult and do all the math associated with it, but that's one of the reasons why we didn't design a catapult.
|
|
#3
|
||||
|
||||
|
Re: Propose possible fixes for high goals
If nothing is going to be changed about the bar, then things need to change about how cycles are ended. Refs should be able to undo cycles since the ball is literally bouncing out of the goal after it appears to be scored. Maybe have another set of lights on the human barrier station so if the cycle is undone, the human players can't inbound until those lights are lit as well. As a ref, I will not want to cause a field fault due to unscoring balls, but I also want to make sure that the next cycle is started as soon as possible. Honestly, this bar seems more unfair to refs, than to the robots.
|
|
#4
|
||||
|
||||
|
Re: Propose possible fixes for high goals
Even if the bar was deemed unfair by the GDC itself, nothing would be done about it, and it's not mainly because of money. The main problem is that in the week one events, the teams who participated had to deal with the bar. Changing that bar is not fair to them. If they had to deal with it, it's more fair that everyone else has to deal with it as well. They had to adjust and so do we, simple as that.
|
|
#5
|
||||
|
||||
|
Re: Propose possible fixes for high goals
Quote:
![]() |
|
#6
|
||||
|
||||
|
Re: Propose possible fixes for high goals
Quote:
|
|
#7
|
||||
|
||||
|
Re: Propose possible fixes for high goals
It's not a rule, it's a field element.
|
|
#8
|
||||
|
||||
|
Re: Propose possible fixes for high goals
FIRST has changed field elements before also... this whole discussion sounds remarkably like the discussion early in 2012 when basketballs wouldn't roll out from under the bridges.
Then, FIRST made a change to the way they attached the polycarb ball ramps to the underside of the bridge assembly (if I remember correctly). |
|
#9
|
||||
|
||||
|
Re: Propose possible fixes for high goals
They've changed the field before too. Remember in 2012 they changed the polycarb under the bridges after balls would get stuck under them, so only certain robots could pick them up. I'm pretty sure this was between week 1 and week 2.
|
|
#10
|
||||
|
||||
|
Re: Propose possible fixes for high goals
Honestly if it becomes a larger issue, more than refs trying to keep score and what have you, they could probably just use cardboard... I don't think it had made that big of an impact YET.
|
|
#11
|
|||||
|
|||||
|
Re: Propose possible fixes for high goals
Is having to replay a match a big impact? A match in eliminations?
|
|
#12
|
||||
|
||||
|
Re: Propose possible fixes for high goals
Maybe instead of a metal bars it should be chain (of a sturdier variety than 2013 chain) with pool noodle around it.
|
|
#13
|
||||
|
||||
|
Re: Propose possible fixes for high goals
Quote:
This bounce potential may negatively impact my team's shot - but that doesn't change the fact that it would still be more unfair to modify now than to continue to work as is...We may modify our approach and make it a non-issue, but that is why we don't register for week one events! |
|
#14
|
||||
|
||||
|
Re: Propose possible fixes for high goals
Quote:
|
|
#15
|
|||
|
|||
|
Re: Propose possible fixes for high goals
Why?
What about it isn't what was provided when the game was released? In 2013 adding the cord to tie the chains together was done, but was it needed? In 2012 the polycarbonate was changed, but was it needed? In both cases I'd say no, but lots of teams would argue. In 2012, if a ball went under the bridge all you had to do was drop the opposite side. In 2013, if your disc bounced out you could not throw the thing as fast as physically possible. I don't understand why teams are upset about this. It seems to me that everyone is a little grumpy because they spent six weeks on a project and it doesn't work as well as they wanted it to. But, the same problem happens in real life too... |
![]() |
| Thread Tools | |
| Display Modes | Rate This Thread |
|
|