![]() |
Re: Week 1 Analysis
Main observation:
The game is significantly different than anyone's predictions I heard before this week. As almost everyone else mentioned, this is a ridiculously penalty heavy game, and I think that's hurting more than a little bit. I sincerely hope we see a Tuesday rule update that addresses the concerns brought up in this thread. |
Re: Week 1 Analysis
Man, I could go to town on what happened at Palmetto
This has to be the worst scouting I've ever seen. EVER. You can't trust the FIRST rankings AT ALL this year. Teams like 4451 got absolutely awful schedules, but were the best assisting bot out on the field, and one of the most consistent low and high goal scorers. They weren't picked at all. I'll be honest, our robot was having a lot of issues, I don't think we (1648) deserved to be picked at all, but team 3571, coached by a certain world championship winning drive coach, and one of the best trussers and best intakes in the field, was also left out of eliminations. We saw teams in elims that had no business being there, there were teams that didn't understand game rules in elims here. Defense may win a lot of matches, but when teams as good as 4451, 3571, and 4452 get overlooked because the FIRST rankings show they were on weak alliances all day, there is a problem. I seriously hope 3571 gets polled in FRC Top 25, that's how good I felt their intake and shots were throughout the day. I have had enough of week 1 ref issues now. Last year, we lost in quarterfinals because of a ref not calling a pyramid contact, but calling a human player stepping behind the line. I swallowed that one up as having scouting mistakes and having a weaker robot and lucky schedule. This time, I was absolutely livid after watching many matches end in high scores because of unnecessary tech foul calls. When my human player is in no immediate danger of hitting a robot, and barely extends over that yellow tape for a fraction of a second to in bound the ball, I don't think G40 should apply to that. We racked up 150 foul points in a match by ourselves because this ref was too focused on watching millimeter portrustions of hands over the yellow tape*. FIRST, PLEASE FIX THIS! THESE TECH FOULS ARE RIDICULOUS AND I ASSURE YOU AREN'T PREVENTING ANY DANGEROUS SITUATIONS. I'm glad we don't compete again until week 5, I think it's going to take me a couple of weeks to calm down and refocus on how to improve. *1024 and 5130, we apologize for incurring so many foul points and making a winnable match into a loss. |
Re: Week 1 Analysis
Here's my opinion:
Penalties: G40's penalty should be reduced if the alliance at fault gained no advantage by running afoul of it. G12 may need to be reworked to become like the pinning rule, to where you can posses the opponents ball for five seconds if the ball was acquired without the use of an active mechanism on the robot, but you must get X distance away from their ball before you can attempt to posses it again. That way if the opposing human player drops their ball in your robot you don't get the "death penalty" for it. EDIT: Also, the robot may not distance itself from the ball by launching it via a mechanism on the robot. Defense: Defense is always part of the game, but I doubt this is quite what the GDC envisioned when they made a game all about the concept of assists. Pushing matches tend to be the least damaging type of effective defense played, and what they tend to break (transmissions, motors, wheels) are more readily replaceable than all the frame bends and tweaks that usually result from these high speed ramming maneuvers I've seen. Usually once the frame is bent, the robot is never quite right again. tl;dr push and bump, don't ram. Though, would be interesting to put shock watches on some of these robots, and see how hard some of these hits are. |
Re: Week 1 Analysis
Quote:
|
Re: Week 1 Analysis
Quote:
|
Re: Week 1 Analysis
Quote:
|
Re: Week 1 Analysis
Quote:
|
Re: Week 1 Analysis
Quote:
|
Re: Week 1 Analysis
Quote:
|
Re: Week 1 Analysis
Quote:
|
Re: Week 1 Analysis
Quote:
|
Re: Week 1 Analysis
Quote:
|
Re: Week 1 Analysis
Quote:
|
Re: Week 1 Analysis
What fun being the Week 1 guinea pigs was. Our pairings were absolutely dreadful this year at WAAMV. We were often paired with unreliable teams, of which had confused drivers and didn't communicate. Our event's game breaking problem? An FMS that failed at least 5 times over the course of the last two days, causing mass robot DC's, and not to mention that fact that the field broke down several times. In the end, we leveled out at 6-6 for Qualifiers, and loosing our Semifinal Games.
Drive Issues Our ability to shoot was somewhat hindered by our team having ONE driver manning all the controls, which led to multi-tasking being a nil topic. We were easily able to be shoved around, (even though we're on traction wheels) and the fact that we couldn't set up our launcher WHILE driving led to wasted time being stationary. By next event we're going to install a 360 Gamepad onto our drive station, so I can load the launcher while our driver focuses on ball acquisition, and getting our butts to the goal.Autonomous We were pretty reliable on our Autonomous, missing about 4 or 5 out of 12 balls we loaded. We ended up being 4th on autonomous score, which led other teams to be interested in us once it came to alliance selection. Our code's rundown is Mast - 1 Sec - Drive 30% (2.7 Sec) - 3 Sec - Launch(.25 Sec) x3Elimination During Quarters, we were paired with 1294 (Top Gun) and 4579 (RoboEagles). 1294's bot was the best loading bot at our district, with a backboard that rebounds into the holding area, and let us get some quick assist points out. We were facing an alliance containing 2990, a robot that near-severely damaged our spinner. 2990 was their destined shooting bot, and as such, 1294 and 4579 pressed on them hard as soon as their assists counted. 1294 kept bashing them to the point that they got under them, causing 2990 to, technically, ENTER 1294's robot. That gave us 50 Foul Points. At that point, 3220 bashed 1294, toppling 2990 and giving US even MORE Foul Points.As this is MY first year, I'm quite pleased with our performance. Because this is our team's 5th year, the last of our founding members have left us for better lands. As such, we have 8 members with 1+ years of experience. The rest of us (15+ Members) are Rookies and Freshmen. It's like back to square one. May luck bless us at Event Two. To all of you guys, good luck! |
Re: Week 1 Analysis
I wanted to comment how I feel the bar may impact ref'ing. As a ref for a week two event, I feel like there are two ways I could handle keeping score for an alliance. *Note: refs do not have the ability to undo ending a cycle*
A.) Have a itchy scoring finger: This ensures the second a ball is through the goal, and *scored,* the next cycle can begin. But what if that bar hits the ball back into play. Now a new cycle is started, and the first ball was never scored. The ref now is to blame. B.) Patience is key: Not wanting to mess up, you will always have to make sure the ball is completely scored before ending a cycle. This means the ball crosses the plane, wait a second. The ball hits the bar, wait a second. Ball bounces around on the bar for a bit, wait two seconds. Finally, the ball falls off the bar, END CYCLE. While its true that no field fault occurred, it came at the expense of play time for an alliance. Either way, this bar will be playing psychological games with refs, something I am not looking forward to. Hopefully it will be more clear when on the field, but from the videos, it was never 100% when the ball would be accepted or not. |
Re: Week 1 Analysis
Quote:
They should just remove the tape and extend the safety zone all the way to the edge of the field. |
Re: Week 1 Analysis
Quote:
|
Re: Week 1 Analysis
Quote:
|
Re: Week 1 Analysis
Quote:
|
Re: Week 1 Analysis
Quote:
I understand why G40 exists, but I don't think calling it every single time there is some portrusion is in the spirit of the rule. The initial team update added the rule because there were robots extending past the field perimeter when intaking the ball, so to keep human players safe, we need to have some saftey zone. When there is no robot extending past the field perimeter, and our human player wants to have some sort of accuracy when loading our robot, we shouldn't be penalized if we extend an inch into the zone. Especially if our player is in no immediate danger. Maybe we can define a "robot interaction zone" just like we did in 2005, but without pressure plates. |
Re: Week 1 Analysis
Quote:
http://www.youtube.com/watch?v=iUi8ZEie7uw |
Quote:
The green dots represent the number of assists. You are talking about the rank number or the team number. |
Re: Week 1 Analysis
Quote:
<Proposed G21> ROBOTS may not extend outside the HUMAN PLAYER BARRIER. (Note: the HP barrier is the 20" wide zone above the field perimeter pipes) <Proposed G40> TEAMS may not extend any body part into the FIELD during the MATCH. G41 (no HP/robot contact, no HP/Ball/Robot contact) remains as is. This would make the HP barrier a "transition zone" where either robots or HP's could reach, but there could be no contact between them. You still couldn't lay a ball directly into a robot. |
Re: Week 1 Analysis
Quote:
|
Re: Week 1 Analysis
Quote:
"6061 is highly weldable, for example using tungsten inert gas welding (TIG) or metal inert gas welding (MIG). Typically, after welding, the properties near the weld are those of 6061-O, a loss of strength of around 80%. The material can be re-heat-treated to restore -T4 or -T6 temper for the whole piece. After welding, the material can naturally age and restore some of its strength as well. Nevertheless, the Alcoa Structural Handbook recommends the design strength of the material adjacent to the weld to be taken as 11,000 psi without proper heat treatment after the weld." That compares to 35ksi yield strength of properly heat treated 6061-T6. Teams that use welded aluminum construction need to realize that your welded joints are now incredibly weak. And that's if the welding has been done with perfect technique (certified welder with years of experience). High school grade workmanship will be way worse. |
Re: Week 1 Analysis
Quote:
Great technique by the human player. We'll be using this as a training video. |
Re: Week 1 Analysis
GTR West Q49. The blue alliance just executed a beautiful strategy with 3 weak robots and succeeded in 2 31pt cycles.
|
Re: Week 1 Analysis
Quote:
|
Re: Week 1 Analysis
Quote:
Thanks for the link |
Re: Week 1 Analysis
Quote:
|
Re: Week 1 Analysis
Just watched a rather amazing match at GTR.
Match 59: 1310 facing off against 610 (&Company) 1310 beats 610 by a score of 161/160 to clinch the number 1 seed. :yikes: |
Re: Week 1 Analysis
Quote:
|
Re: Week 1 Analysis
Quote:
|
Re: Week 1 Analysis
![]() |
Re: Week 1 Analysis
Quote:
12.4% of winning alliances would not have won without penalty points? That's insanely high. If I am reading this correct and that is only the qualification matches being taken into account, I would be interested in seeing that same statistic for the eliminations. |
Re: Week 1 Analysis
Quote:
Quote:
For comparison, it was 3.9% of (all) matches last year. |
Re: Week 1 Analysis
Quote:
|
Re: Week 1 Analysis
Quote:
At any rate, I point it out not to take anything away from you guys' win (based on that video it's difficult to imagine a world in which you didn't win, defense or not), but mostly just because it's another important conclusion to be drawn. There's a big reason why this game is so physical, and that match proves it. |
Re: Week 1 Analysis
Quote:
|
Re: Week 1 Analysis
Quote:
|
Re: Week 1 Analysis
What continues to baffle me is when human players throw the ball onto the field without even attempting to get the ball into one of their robots. The next 15 or more seconds are spent trying to recover the ball which should have never been lost in the first place.
Things for teams to learn from Week 1 1) If you can't do scoring in auto 90% of time or better then don't shoot!! 2) Teach your human players how to put a ball into a robot fast and reliably without crossing into the field and occurring a penalty. 3) Be humble- This is a role playing game just like sports. Somebody needs to play 1st base and somebody needs to be in the outfield, the outfield is just as important. If you can't do something, just realize that and make out of what you have!! 4) Know the rules!!!! |
Re: Week 1 Analysis
At the MAR events it looks like refs are pausing matches in the middle of teleop to discuss and assess penalties and assists...?
|
Re: Week 1 Analysis
Quote:
http://youtu.be/iUi8ZEie7uw Quick cycles are the key. The third team on this alliance was dead...imagine what would have been possible with an auto contribution and some defensive play from 346. They were a capable bot - played into semi finals if memory serves. |
Re: Week 1 Analysis
Carnage. Who's going to want to do a 3rd event before states?
|
Re: Week 1 Analysis
Quote:
However, there wasn't any actual defense being played on the inbounding robot or the catcher; I doubt you would ever be able to easily line up like that. |
Re: Week 1 Analysis
Quote:
|
Re: Week 1 Analysis
Quote:
|
Re: Week 1 Analysis
Quote:
|
Re: Week 1 Analysis
Quote:
|
Re: Week 1 Analysis
Quote:
|
Re: Week 1 Analysis
Quote:
I'll talk to our business team and we should be getting pictures up soon on our website! |
Re: Week 1 Analysis
Quote:
Here's the data you're looking for: http://www.chiefdelphi.com/forums/fr...p?events=MICEN |
Re: Week 1 Analysis
1 Attachment(s)
Quote:
|
Re: Week 1 Analysis
Quote:
|
Re: Week 1 Analysis
Quote:
If so, 25% of the points scored in the elims were fouls. |
Re: Week 1 Analysis
Quote:
At least at Hatboro, matches were being paused quite a bit. With a game like this, I think its a good thing to get it right instead of just letting the alliance go, unable to score. Again though, Why can't we just insert the balls where they left the field?? Its much simpler then having to track down the nearest HP and run halfway across the field. Quote:
|
Re: Week 1 Analysis
Quote:
#1, 7, 8. So, QF 1-1, 3-2 and 4-2. Another note: .25 of red alliance's points were penalties (260 pts), while .29 of blue alliance's points were penalties (370 pts), almost 50% more penalty points than red recieved. Additionally, the proportion of blue's penalty points to red's teleop/hybrid points is .47, and for the other alliance is .29. Higher-numbered alliances seem to have played much cleaner this week. |
Re: Week 1 Analysis
Quote:
|
Re: Week 1 Analysis
Quote:
|
Re: Week 1 Analysis
Quote:
|
Re: Week 1 Analysis
Quote:
-Assists being attributed within the same century they occur -The pedestals lighting up prior to the heat death of the universe -Dead Ball cards being enforced better than county ordinances in the Old West -Real time scoring functioning better than square wheels At what point would FIRST decide to make changes to rules that may affect strategies of a very select few in order to better administer the game they designed? I can't answer that question. |
Re: Week 1 Analysis
Quote:
And even then, you can still push it into the 1pt goal. |
Re: Week 1 Analysis
I'm actually somewhat confused about all these HP fouls....that never happened in the matches that 4901 played in at Palmetto.
|
Re: Week 1 Analysis
Quote:
The game is, IMO, broken because of the overused penalties, delayed scoring, incorrect scoring, lack of rule knowledge by referees, 2003-style defense gameplay and obscure field issues. Anything they can do to make the game "less broken" is good. There's weird field stuff happening too. I've watched goofy timing display stuff on the webcasts, as well as delays between when a ball is scored and the assist lights go off and pedestal lights go on. Also, I've seen a few more timing issues with the hot goals (8 seconds left, 2 seconds right). Does anybody know how they're scoring these? |
Re: Week 1 Analysis
Quote:
G20 ROBOTS must be in compliance with Section 4.6: BUMPER Rules throughout the MATCH. Violation: DISABLED Hopefully FIRST fixes the bug that does not allow the head ref to disable from his scoring tablet as currently he has to run to the driver station to e-stop (disable) the robot. |
Re: Week 1 Analysis
All this hype over aggressive defense this year is astounding. How did so many teams not anticipate this aspect of the game? This is especially important when some teams build weighted chassis battering rams as robots. I know my team wont have a problem, our entire robot is double extrusion and welded steel ::ouch:: ;)
|
Re: Week 1 Analysis
Quote:
|
Re: Week 1 Analysis
Quote:
Also, I've heard the referee data input stations are time consuming to navigate thereby causing massive delays in attributing assist, fouls, and scores. |
Re: Week 1 Analysis
Quote:
Assuming you're talking about Mt. Olive, the incident involved a match stopped out of safety concerns (I'm almost certain based off the timestamp of a picture I have of why-it'll be posted to CD-media soon). For a short period of time, the match was going to be resumed, hence why the fouls that would be incurred were being discussed. Assists were never a question in the event I believe you're talking of. Eventually, it was determined the match would be reset. Overall, it was a hectic game for week one. Being that the last 4 games have had some form of a protected zone, teams did not expect the defense that happened. The biggest issue to me is that field crew/reset is a position this year that doesn't require any sort of game knowledge or training. I have more of an issue with that than Refs having to keep track of posessions* and usual ref stuff; it's just too much to add on ensuring field reset does the right thing. *I'm differentiating posessions from assists. |
Re: Week 1 Analysis
I didn't attend a week 1 regional, and I have read quite a bit about the damage caused and rough defense, but with this in mind, how did this years kitbot hold up? The frame is definitely weaker than last years so I wasn't sure how it would do.
|
Re: Week 1 Analysis
Quote:
|
Re: Week 1 Analysis
Quote:
|
Re: Week 1 Analysis
I think that an appreciable portion (but certainly not all) of the "missed assists" that teams are complaining about is due to the very definition of ASSIST. In the heat of the match, it is easy to forget that robots must be in unique zones to get the ASSIST. This distinction never has an effect on single assists and rarely (if ever) has any effect on double assists. However, it takes a conscious effort by the alliance to achieve the triple assist.
Remember everyone POSSESSION =/= ASSIST. |
Re: Week 1 Analysis
Quote:
|
Re: Week 1 Analysis
I didn't see any robots tipped at GTRW, despite 1310 coming close a couple of times. I would guess that this is an artifact of the game generating mostly low-CG designs.
|
Re: Week 1 Analysis
I don't have a problem with whats being called a foul or a tech foul, but I do a have a problem when refs are calling such a small amount of them.
I feel as though there should be a ref watching each individual robot for fouls. |
Re: Week 1 Analysis
Quote:
Where would you get the volunteers? |
Re: Week 1 Analysis
Quote:
|
Re: Week 1 Analysis
Quote:
But with that said, I would rather a foul be double called and cleared up by a coach who was keeping track of fouls, than the foul never getting called. |
Re: Week 1 Analysis
Quote:
|
Re: Week 1 Analysis
This has already been said, but I'll say it again from first-hand experience: scoring in autonomous is of extremely high importance. Especially if you face a good/heavy defensive team, if you miss your auto shots it will take you half the match to get the auto balls in the goals before you can start cycling.
Also...make sure your autonomous balls don't collide midair... |
Quote:
|
During our time at our first competition, we broke several things such as very expensive pneumatic cylinders, pickup system, and bearings from other robots ramming into us and using there pickup as an attack
|
Re: Week 1 Analysis
Quote:
We made a weird choice this year, and decided that minimal weight, rather than the 120 lbs, was ideal. We not only felt like moving quickly (to get away from defense and collisions) was the way to go, but that having more mass would make it more likely that we would absorb collisions, rather than bounce away from them. Even so, we might be replacing some of our frame tubing with thicker stuff, depending on how early rounds go in Utah. Here's hoping that things smooth out before then... |
Re: Week 1 Analysis
I can't be the only one that hearkens from the olden days of FRC (my rookie year was 2003). I like this return to the violent defense of yesteryear. Intentionally breaking robots should still be a no-no.
I took one look at this years game and immediately knew violent defense was going to be a thing, and consequently ROBOTs (and especially MECHANISMs that extend beyond the FRAME PERIMETER) would need to be built to withstand a beating. With BUMPERs nowadays though, you don't see nearly as much in the way of bent frames like you used to back in 03/04. 4343 ran an AM14U kit chassis with some added stiffening measures through 14 matches of rough play this weekend at GTRW and it seems to have held up just fine. I suspect many of the elites tested the robustness of their intakes by crashing their Ultimate Ascent bot (or another past robot) into it at full speed. I haven't seen any of the stronger teams have an intake I would consider 'fragile'. |
Re: Week 1 Analysis
Quote:
|
Re: Week 1 Analysis
Week 1 analysis from a CSA
1. This game is the roughest game I have ever been apart of. (The carnage that is imposed on robots is quite different than recent years of FRC). 2. Lots and lots of CRIO reboots due to impact. (check all your connections on Thursday and make sure they have slack,slack and are tightly in.) Tons of teams lost comms after a hit by one, two, or even three robots. Flakey connections will not cut it this year. It can be the difference between a loss or win quite literally because you are rebooting for at least 30 secs of the match. 3. If you get into a pushing match with 6 cims behind you may trip a breaker so be weary of that. Robot/Game analysis. 1. Penalties need to be lessened and rules hopefully should be uniform from tournament to tournament.(Matches decided by penalties always taste bad.) The amount of discrepancy between tournaments is staggering this year, but fixable in the long run of weeks. 2. The refs have the hardest job in FRC this year. They have to take care of at least three different actions while trying to make sure that robots are not committing fouls. This is just too much on them this year. I hope to see this changed so that they can make the right calls. (aka more personnel to help) 3. I for the first time do not envy anyone playing in districts or 3 regionals this year. The amount of punishment I thought the robots took last year was incredible. At this point in the game the amount of hard hits and robots falling apart is way more than I would have ever imaged for only the first week of competition. Many teams play at least 2 or more events before championships I saw great teams fall apart in the final rounds of eliminations due to the nature of the game. If this state of play keeps up they may not have much left by State or even world championships. 4. The game forces even the best scorers to actively play defence between each transfer of the ball. This allows for an almost seamless transfer of control and play. That being said, this is where the majority of the problems start between congestion, guarding, penalties, and just straight up hard defence. After watching the shut down D that was played when 188 had a chance to to win by 610 was smart. It's easy to get stuck in the mode of score, score, score. Something I love about this game when teams work together to pull a plan off. That takes a ton of moxie and coordination. Question: how do your think they fix the pedistool problem? That one makes me the most uneasy. TL:DR All in all teams be safe out there. Do what you can to ensure your robot will survive this current game. |
Re: Week 1 Analysis
Quote:
In 04, it was a TIG welded 1" box tube with 1/8" walls. In 04 at the Wonderland invitational, which we won (thanks 1241, 1114), we took a full speed frame to frame collision in auto that bent the frame by about 2" until it touched our wheel. A few minutes with a sawzall to remove the offending piece of frame (it happened to be part of our ball herder and not a necessary structural piece) and we were back in business. |
Re: Week 1 Analysis
As a queuer, I didn't get to see ALL of the carnage and craziness that was going on, but boy did I sure hear about it. Talking to the GSDE refs at Lunch on Saturday, even they were saying they NEED 8 Refs (there are 6 including Head Ref), the additional 2 refs solely watching for penalties or scores, with the current team handling the other.
This game has so much potential when played at high levels if some things are just cleared up, like G40, the bar (whether fixed or left as is), among others. |
Re: Week 1 Analysis
Week One competitions was fun but I have a couple questions on rule?
Are G28 and G29 going to be enforce better at Week two competitions? Is there anyway to challenge any calls right after a match? Are refs going to step up their fouls? Battle-bots? Comments; FRC 4954 have broke 2 pistons, a pick up system, and multiple barring. We were a shooter and multiple Week One robots that had fast drivetrains and the uncompleted scorers play very physical defense on us. This feels like battle-bots. |
Re: Week 1 Analysis
Quote:
I know our team's not located too close to yours, but next time we're at a competition together and you need a hand, definitely let us know! I hope you can get that stuff repaired in the next few weeks. Your team and 5113 are going to have great rookie seasons! Best of luck at Clifton! |
Re: Week 1 Analysis
Quote:
|
Re: Week 1 Analysis
Doing our competitions at Hatboro-Horsham, all defensive robots violated rules G28 and G29. Are the refs going to call that during the next competition. G29 says that robot alliances can not pin any robots for more than 5 seconds and "a robot is considered pinned until the ROBOTS have separated by at lest six feet". Also the pinning robot has to wait 3 seconds to pin again. A lot of scorers was pinned over 5 seconds and the pinner did not get out of the 6 six radius. G28 explains even though there is a part that a robot can bring out to 20 inches but that "thing" cannot damage a robot part that is inside the frame.
|
Re: Week 1 Analysis
Quote:
|
Re: Week 1 Analysis
Quote:
|
Re: Week 1 Analysis
Quote:
|
Re: Week 1 Analysis
Quote:
The match was stopped mysteriously and the ref's grouped together for quite some time near the entangled robots. Once the discussion was over it was decided that the match would resume. I have never once heard or seen a match being stopped for any reason the refs decide or resumed. If it was a safety issue a G3 probably should have been called on all participating robots. We then proceeded to question the resuming of the stopped match. It was then debated for sometime of what should be done and it was eventually decided that it would be restarted and not resumed... ![]() Another interesting item was that on Saturday drivers were told at the drivers meeting that gloves were required and fouls would be given for NOT using them during field robot loading/unloading. I still haven't found that rule. I do not know if any were assessed, but we didn't attempt to find out. We normally use them anyway. |
Re: Week 1 Analysis
The head ref at Hatboro would frequently pause matches to fix podium issues, then resume them. It happened about every two or three matches.
|
Re: Week 1 Analysis
Quote:
Quote:
|
Re: Week 1 Analysis
Quote:
Just to be clear...I'm not blaming the refs. I agree with the sentiments of many others in that they have WAY too much to try to do to possibly watch everything that's happening. I appreciate the job the refs have to do and I know that they are trying the best they can in a very difficult job this year. Separate scorers would help which would allow the refs to focus more on what the robots are doing. I do think that technical fouls are much too large for the amount they are being called. |
| All times are GMT -5. The time now is 10:53. |
Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2017, Jelsoft Enterprises Ltd.
Copyright © Chief Delphi