If I was an experienced gamer on here (which I'm not), or a betting person.....I'd almost swear the fatigue/rotation %ages are more inline with giving equal distribution to a position.

For example: With a WR starting as RB1 in a game, he carried 10 times in half one of a game, RB2 had 9 carries. Both disappeared in Q3 and only came off the bench mid-late 4th. If you read the settings correctly, a 25% fatigue level should take a player out of the game early....but he should rotate back in quickly as a result ?

Speed and ball carry matter most, then acceleration for on field results. High avoid fumble is necessary for RB's getting 15+ touches. A WR will be successful at RB provided he has good RB skills, not because of his weight

I've been reading a lot that ball carry is the new secret ingredient in 4.6. Any benefit in getting a good RB with speed, acceleration, ball carry and avoid fumble, converting him to WR to lose 20 lbs and gain even more speed, then continue playing him as a RB since he's even faster now? (Hope that makes sense)

The benefit is solely the few points of speed you would gain but there is supposed to be a penalty for playing players out of position. It's not enough to negatively impact a WR at RB from the looks of it however

From what I've seen from the most dominant teams in my favorite league that seems to be the case - no out of position penalties whatsoever.

A WR is punished in 4.6 for playing out of position at RB. However, the punishment isn't enough to keep me from playing WRs at RB. If you want to drop your fatigue setting, why not put your best players on the field?

The data tracked in the "out of position" spreadsheet found at this link shows there's no advantage to playing a WR at RB: https://bigdata.myfootballnow.com/forums/1/61?page=1#275

As others have indicated, skills matter — especially ball carry and avoid fumble. Route running is a factor on tosses. It's looking like acceleration might help on some plays but hurt on others, where the RB needs to let blockers get into position.

The only advantage of playing a WR at RB is the 2-3 points of speed you gain by having a lighter weight player, but it's important to remember the speed curve in 4.6 translates to virtually no distinction between 80 and 90 speed. In other words, a player's success as a runner depends on his skills, not the position you list for him.

EDIT:

Play selection is the No. 1 factor in whether you are successful at running the ball. The run blocking ability (including acceleration and strength) of your OL and TE and FB and WRs are also a factor.

I've yet to see a WR be "punished" from playing OOP....with high speed/accel & avoid fumble. My team avgs about 3 penalties per game....broken down, 95% of those are from the OL....and my OL rotation is 60%.

There might be an "argument" to be made on players playing OOP who are not in the same "grouping".

I'm playing in a very competitive league, and asked permission to start a DB as a RB,,,,,if it's given the green light....I'll put a penny to a pound that my penalties wlll not increase as a result of the change of OOP.

The "penalty" is against a player's performance, not a yellow flag

I was thinking about the game engine penalizing their performance playing OOP, not actual called penalties. However, now that you mention it I'd think your DB as an RB could get called for more false starts etc. if his discipline or experience playing running back was really low.

You have to be tactful, too. You want a high strength WR running the ball but also you'd be a fool and would injure your WR quickly if you implemented him like a battering ram on inside runs from the 3-1-1, 2-2-1 and 2RB/3TE sets. In tight vs. a stacked d-line = a bad idea.

Otherwise, keep on rockin' in the free world.