|
||||
| ||||
|
|||||||
| OOTP 17 - General Discussions Everything about the latest Out of the Park Baseball - officially licensed by MLB.com and the MLBPA. |
![]() |
|
|
Thread Tools |
|
|
#1 |
|
Major Leagues
Join Date: Jul 2013
Posts: 455
|
Online league issues after switching to 17? Could use some help
Hey everyone,
I did some searches and have not found a solution so I thought I would post here to find some help. The league I commish just switched to 17 and so far members have been able to successfully: - Install file from download from the forums and get it working - Export successfully The problem has been if they try to download the file from in game (I get the same problem if I try) where it comes up with "Error: Could not unpack files from archive". Hoping someone can give some tips. Thank you. |
|
|
|
|
|
#2 |
|
Minors (Rookie Ball)
Join Date: Dec 2012
Posts: 42
|
Did you ever figure out a fix. I have the same issue
|
|
|
|
|
|
#3 |
|
Minors (Double A)
Join Date: Feb 2004
Posts: 140
|
We just upgraded the FOBL from 15 to 17, and one quirk that I found is that in 15, our FOBL.lg file export would be named FOBL.tar.gz (which was actually different from what we had in previous versions, FOBL.lg.gar.gz; we would rename it manually).
In 17, the file was being generated as fobl.tar.gz -- all lowercase. Our upper-case file name didn't seem to work anymore for importing. So, maybe double-check the file name and case sensitivity? |
|
|
|
|
|
#4 |
|
Hall Of Famer
Join Date: Aug 2009
Location: NJ, US
Posts: 2,006
|
Was anything other than case sensitivity found to be the issue?
Just upgraded our league from v16 --> v17. Had each GM import the league from 16 to 17 on their machine and then update in-game to download the latest file on the server. 7 teams have successfully done this but one is getting the "Error: Could not unpack files from archive" when they attempt to update in-game. Anyone have any info as to what the issue may be? |
|
|
|
|
|
#5 | |
|
Hall Of Famer
Join Date: Aug 2009
Location: NJ, US
Posts: 2,006
|
Quote:
As I said I had the GMs import the league from v16 --> v17 and then update in-game. When this GM imported the process took just a couple minutes, much too quick. I asked a bunch of questions and the GM poked around and suddenly realized when he went to select the world.dat file (in the import process) he accidentally got into the 'auto-save' folder where there is a world.dat file. He choose that file and the import appeared to go fine. Well, it went quickly because only the .dat files are there to import and not all the .txt files in the other folders. But when this import finished he could log in and superficially everything looked fine, his roster looked fine. When he then tried to update in game the league saved and the download happened very quickly (didn't actually happen) and then he got the 'unable to extract' error because the file didn't download. So importing the auto-save/world.dat file worked to an extent but obviously everything wasn't there. So yea, not likely to run into this type of user error but you never know. |
|
|
|
|
![]() |
| Bookmarks |
|
|