New Realplayer file out based on new patch today?

[jbmagic]

will there be a new Realplayer file out based on new patch that came out today?

thanks

[3ric]

No, the old one is still good.

[jbmagic]

old one is not good...because the real player position and salary was incorrect on it...

and i tought this new patch 5.1 that he fix yesterday corrected the player positions on the default player file..

just curious is there going to be a realplayer file out now..because jim updated 5.1

thanks

[jetpunk2000]

Originally Posted by jbmagic

old one is not good...because the real player position and salary was incorrect on it...

and i tought this new patch 5.1 that he fix yesterday corrected the player positions on the default player file..

just curious is there going to be a realplayer file out now..because jim updated 5.1

thanks

I believe the player position problem was a coding thing, not a roster file thing, so it should be fine.

[Joe]

yep, that was my understanding as well

[amdaily]

The position issue was a problem with the roster file. The default fictional file was fixed in the patch.

Since the patched real player file is not out yet, what I did was open the old real rosters and copy columns B and C (the names) into the new default roster file and presto - new real roster file with correct positions

[MizzouRah]

Originally Posted by amdaily

The position issue was a problem with the roster file. The default fictional file was fixed in the patch.

Since the patched real player file is not out yet, what I did was open the old real rosters and copy columns B and C (the names) into the new default roster file and presto - new real roster file with correct positions

I'm confused. If I'm using the old real roster file and currently have a dynasty going, do I need to do this and restart? -or- will it fix itself eventually?? Basically, am I screwed in this dynasty?

Todd

[yabanci]

I wouldn't say you're screwed. You might have a couple of rookie cornerbacks playing WLB (DeAngelo Hall the only really significant one) and you'll have some fairly big names becoming free agents at the end of the year when really they signed extensions. I don't even know if the contracts were changed in the new file. If you can live with this, keep going. If not, then you need to restart. But it's not something that will fix itself.

[MizzouRah]

Originally Posted by yabanci

I wouldn't say you're screwed. You might have a couple of rookie cornerbacks playing WLB (DeAngelo Hall the only really significant one) and you'll have some fairly big names becoming free agents at the end of the year when really they signed extensions. I don't even know if the contracts were changed in the new file. If you can live with this, keep going. If not, then you need to restart. But it's not something that will fix itself.

Thanks, I wonder if there is a way to export the file, fix Hall, then re-import like TPB?


Todd

[yabanci]

no, once you start your league, that's it.

[MizzouRah]

Originally Posted by yabanci

no, once you start your league, that's it.

Arrrgghh.. I knew I should have waited before starting a dynasty.

Todd

[jbmagic]

Originally Posted by amdaily

The position issue was a problem with the roster file. The default fictional file was fixed in the patch.

Since the patched real player file is not out yet, what I did was open the old real rosters and copy columns B and C (the names) into the new default roster file and presto - new real roster file with correct positions

did that fix the salary of players that got new extensions this year too?

[Pumpy Tudors]

Errr, was anyone else thinking about that crappy real.com software when seeing the thread title?

[ice4277]

yes