With this patch, the main thing is that long tracks will now work (i.e. Targa); without this patch, they won't.

On startup I do not think that any of the mods or long track patches change the Papyrus release file number which should be 1.2.0.2 which was the last update that Papyrus released and should always be used as the base gpl.exe file upon which to build all mods.

Using this patch will make GEM+ create an exe called gplc67.exe which is effectively the 1.3 patched version if you like, but, running this file will still show 1.2.0.2 on the loading screen, but, this file will work with long tracks. Running the raw gpl.exe will never work with the long track patch since GEM+ does not alter this file, it only alters copies of this file which get created for each mod.

Rob

It would have been a good idea to add the version number to the used mainback maybe. So while not ideal (you can exchange main backs) it would give a visual hint

With this patch, the main thing is that long tracks will now work (i.e. Targa); without this patch, they won't.

On startup I do not think that any of the mods or long track patches change the Papyrus release file number which should be 1.2.0.2 which was the last update that Papyrus released and should always be used as the base gpl.exe file upon which to build all mods.

Using this patch will make GEM+ create an exe called gplc67.exe which is effectively the 1.3 patched version if you like, but, running this file will still show 1.2.0.2 on the loading screen, but, this file will work with long tracks. Running the raw gpl.exe will never work with the long track patch since GEM+ does not alter this file, it only alters copies of this file which get created for each mod.

Rob

Thanks for the explanation. My GPL installation is OK and I don't have to fix anything. I can just drive.

With this patch, the main thing is that long tracks will now work (i.e. Targa); without this patch, they won't.

On startup I do not think that any of the mods or long track patches change the Papyrus release file number which should be 1.2.0.2 which was the last update that Papyrus released and should always be used as the base gpl.exe file upon which to build all mods.

Using this patch will make GEM+ create an exe called gplc67.exe which is effectively the 1.3 patched version if you like, but, running this file will still show 1.2.0.2 on the loading screen, but, this file will work with long tracks. Running the raw gpl.exe will never work with the long track patch since GEM+ does not alter this file, it only alters copies of this file which get created for each mod.

Rob

It would have been a good idea to add the version number to the used mainback maybe. So while not ideal (you can exchange main backs) it would give a visual hint

Probably true, but was not my decision. I am pretty sure that it does have handles for a different mainback screen though, so you could use the default for gpl.exe and have a different one for gplc67.exe if I remember rightly.

I do agree though, and especially where stuff might get updated further as well that it would be simple to include a mod version number on the mainback that ships with each mod, or update to each mod, so it is clear which version you have.