![]() |
Re: The Not So-Secret Secret End-Game
It just seems incredibly strange that half the game name is a complete lie
|
Re: The Not So-Secret Secret End-Game
Quote:
|
Re: The Not So-Secret Secret End-Game
Quote:
Honestly, I think everyone in this thread should back away from the caffeine, get some sleep, and ask themselves tomorrow if they really think the above is something the GDC would actually say. |
Re: The Not So-Secret Secret End-Game
Quote:
|
Re: The Not So-Secret Secret End-Game
Quote:
|
Re: The Not So-Secret Secret End-Game
Quote:
|
Re: The Not So-Secret Secret End-Game
Quote:
There is no sport to pull aerial from and doesn't really seem to be a major part of the game. |
Re: The Not So-Secret Secret End-Game
Quote:
I think you're being seriously naive if you don't think the GDC would do something to combat the effect that Ri3D's have on the robots we see at competition. EDIT: Just to be clear, I don't necessarily think this will happen. I think its a significant possibility. There have been enough clues, things that seem just a little out of place. Maybe the changing game hint was intentional. That truss is way stronger than it needs to be for its stated purpose. "Aerial" Assist having essentially no "Aerial" component. The first FIRST game in 14+ years to be devoid of an endgame. Aerial Assist as is, the minimum competitive robot, and the elite competitive robot are very similar in design. |
Re: The Not So-Secret Secret End-Game
At first I was thinking this was just a conspiracy theory cooked up by those veterans who were disappointed that the game was forcing them to collaborate with other teams.
However.... the more I read the other comments, the more I'm open to the possibility that FRC could change things up mid-build season. The one factor that gives me pause is the proliferation of the Ri3Ds this year. If FIRST is looking to force more innovative approaches, introducing an end-game mid-way would be a way to do that. One other point that hasn't been mentioned yet is that changing requirements mid-stream is extremely common in the real-world. It is pretty much how most of the software projects I've worked on pan out. It is very good skill to learn how to adapt and improvise. Frustrating -- you bet. But it can also be extremely rewarding when the team pulls it together at the last minute. ant |
Re: The Not So-Secret Secret End-Game
Quote:
Just a thought |
Re: The Not So-Secret Secret End-Game
Quote:
|
Re: The Not So-Secret Secret End-Game
The fact that you have to go back to 1998 before you hit a game that didn't feature an endgame makes me think this is easily a possibility. FIRST is all about replicating a realistic engineering environment and what better way to do that than with a last minute wrench in the system.
|
Re: The Not So-Secret Secret End-Game
Quote:
|
Re: The Not So-Secret Secret End-Game
Quote:
Ultimate Ascent's game design contributed, and I think Ri3D exacerbated, a limited diversity in 2013 robot designs. I think this is a negative thing. Changing the game after kickoff would be one way for them to attempt to bring some diversity back, as some teams will choose to not attempt to change their design, while some will. |
Re: The Not So-Secret Secret End-Game
Quote:
1. FIRST needs to keep growing. Rookie teams are the lifeblood of FRC. The autonomous +5 points for just getting from the starting zone to the end zone gives rookie teams a success. Your team and my team will find a way to move, shoot and score in the "hot zone" during auto. We kicked around camera, lazy susan turret and are working on several ideas for a shooter. Again, this part of the game buoys up the rookie teams giving them points for moving. Judging from our own team's experience, just getting the robot to move and do SOMETHING in auto. was a major accomplishment given the relative STEM inexperience and lack of longer term STEM systems in our school. One man's opinion only. 2. The multiple passing point system is an extension of the cooperative game from 2012. It is also something that FIRST has been gradually working on since we've been "in the game". The biggest obstacles for us are deciding how we will pass the ball and if we will get multiple points for 2-3 passing and concentrate on the lower versus upper shooting targets. Adding an elevator system is another system that has the potential of breaking down during the game and complicates both construction, and driver training. Our jury's still out but as of this afternoon, we want to be consistent enough to score and consistent enough to add to the team aspects of this game. Flame me if you want. I've got big shoulders and certainly can learn from all responses. As posted above, the truss IS a destractor only unless FIRST changes the rules and offers points for doing more with it. 10 points for popping the ball over the bar is not something we want to be trying to do during the shortened game time. It would be cool, and we'll probably build a prototype to gather and shoot. Again, it is consistency of scoring points and team work that we want to sharpen up. For us it's about doing the picking in the finals rather than getting picked. Fancy engineering is great if you've got the facilities and financial backing. Keeping it simple and to the goals of the game is how smaller, less funded teams operate. I'm thinking FIRST may have had this in mind too. This game is not as complicated as our first game in 2010. That's a good thing. As a teacher, I want my students to work the problem rather than having the problem work them. Great thread though....I'm quite interested to see how y'all work the problem, if you deal with the truss, or just stay the course, keep it real and score lots of points in partnership with others on the course. Again...I am NOT an engineer but a mere AP Human Geo, AP Government, AP Economics instructor. I truly want to get your thoughts on this. Your thoughts can only make all of our teams better. See some of y'all at the Dallas Regional? Steve Miller Team 3355-Purple Vipers |
| All times are GMT -5. The time now is 03:46. |
Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2017, Jelsoft Enterprises Ltd.
Copyright © Chief Delphi