[dangarion]

So we've got a league (The RWBL). Some users patched OOTP10 (because leagues they were in required it) and now the commish can't do their exports.

Then the commish patched and now he can't do people who didn't patch exports...

It used to be patches in same version OOTP never caused this problem... What happened?

Not to mention the fact that both versions of OOTP (Mac and Windows) didn't get their patch released at the same time.

I realize the "solution" is that the people playing now have to install a patched and non patched version of the game, but honestly do you think that is realistic? Our league is now on hold till this stuff gets straightened out.

[stevew]

Originally Posted by dangarion

So we've got a league (The RWBL). Some users patched OOTP10 (because leagues they were in required it) and now the commish can't do their exports.

Then the commish patched and now he can't do people who didn't patch exports...

It used to be patches in same version OOTP never caused this problem... What happened?

Not to mention the fact that both versions of OOTP (Mac and Windows) didn't get their patch released at the same time.

I realize the "solution" is that the people playing now have to install a patched and non patched version of the game, but honestly do you think that is realistic? Our league is now on hold till this stuff gets straightened out.

I haven't patched yet, ftr. But to have to put a whole league on hold is very poor form.

[Stu]

Originally Posted by dangarion

So we've got a league (The RWBL). Some users patched OOTP10 (because leagues they were in required it) and now the commish can't do their exports.

Then the commish patched and now he can't do people who didn't patch exports...

It used to be patches in same version OOTP never caused this problem... What happened?

Not to mention the fact that both versions of OOTP (Mac and Windows) didn't get their patch released at the same time.

I realize the "solution" is that the people playing now have to install a patched and non patched version of the game, but honestly do you think that is realistic? Our league is now on hold till this stuff gets straightened out.

I've been running my league since v2006 and I don't think exports from different patch levels have ever been compatible unless it was a very minor patch.

I don't think it's technically possible to fix this since the patch adds new features which might need to be exported such as the new pitching rotation options and locking pitchers into a role.

[dangarion]

Originally Posted by Stu

I've been running my league since v2006 and I don't think exports from different patch levels have ever been compatible unless it was a very minor patch.

I don't think it's technically possible to fix this since the patch adds new features which might need to be exported such as the new pitching rotation options and locking pitchers into a role.

They were able to do it from the 6.12 to 6.5 transition... Which was a major overhaul of the lineup system.

[Alan T]

Posted this elsewhere, but putting it here in case it helps others:


Guide for online users to run two versions of OOTP at once

1) If you have already upgraded your OOTPX but your league is not going to yet, you first need to re-download the old version so you have it available:

Originally Posted by Andreas Raht

PC patch: http://www.ootpdevfiles.com/ootp/10....otp10patch.exe

Download the patch and run the ootp10patch.exe once it is fully downloaded.


2) During the patch install, it will ask where you want to install the patch. do NOT install it in the default location or where you currently have OOTPX installed. Instead pick a temporary folder to "install" the patch to. All this does is pretty much extract the patch to that temporary folder.


3) Once the patch extraction has completed, open up that temporary folder in windows explorer. You will find three folders and ootp10.exe Rename that ootp10.exe to be called something like ootp10-2-18.exe and then copy only that file (do not copy the three folders) to your normal OOTP10 Program folder. (In default windows installs, this is often: C:\Program Files\Out of the Park Developments\OOTP Baseball 10

4) Now in your Normal OOTP Baseball 10 folder, you should have two executables. You should have ootp10.exe (which is the 10.4.29 version) and you should have ootp10-2-18.exe (which is the 10.2.16 version)

5) For your online league that has not upgraded, you have to launch ootp10-2-18.exe for that file to import/export/etc. For your online league that has upgraded, run the normal ootp10.exe file instead.


Not the most pain free thing in the world, but took me all of 3 minutes to set up. Hopefully it helps those of you in a bind until the patch issues are worked out.

[kq76]

Originally Posted by dangarion

They were able to do it from the 6.12 to 6.5 transition... Which was a major overhaul of the lineup system.

Not entirely. According to the feature list, 6.12 could import into 6.5, but it didn't work the other way around. There was also the issue that depending on the version you were running you'd get different player demands so you could go from one version to the other to get the best deal from that player which wasn't exactly fair. Besides, I'd say that was pretty much touted as a feature or at least not a deterrent to buying the expansion pack. Either way, I don't think you could point it out as typical representative of how it normally works. And I don't know, maybe successive patches normally are compatible, but without really looking at it that doesn't strike as the case.

[dangarion]

Originally Posted by kq76

Not entirely. According to the feature list, 6.12 could import into 6.5, but it didn't work the other way around. There was also the issue that depending on the version you were running you'd get different player demands so you could go from one version to the other to get the best deal from that player which wasn't exactly fair. Besides, I'd say that was pretty much touted as a feature or at least not a deterrent to buying the expansion pack. Either way, I don't think you could point it out as typical representative of how it normally works. And I don't know, maybe successive patches normally are compatible, but without really looking at it that doesn't strike as the case.

Consecutive patches were compatible back in 6. But either way, I've got my point across that there needs to be more communication regarding this stuff in the future.