Auto PackageInfo Converter

[Tharon]

As an effort to keep the old Steam client, some users on a now locked thread helped developing a method to convert the packageinfo.vdf file from the old format to the new. This will fix the old steam client hang at the start.

This is a new, automated version of the packageinfoconverter V1.

I've also included a button for automatically create a steam.cfg and a desktop link with the necessary parameters to avoid steam auto-updating itself.

Download : https://drive.google.com/file/d/1qcwn3zhMAbXoRfA17MCYNYweaD9ToWUQ/view?usp=sharing
Virus Total check : https://www.virustotal.com/gui/url/c49cf6a1379e74108773cba2e49b846653e5da87e82e171809c28e8a0e72e348/detection

[my wife left me]

Thank you very much Tharon!

[Pepper]

Incredible, thank you

[[bin]zwieda]

Thanks a lot!

[tintingaroo]

Been working through the process with the tool.
Can it open and close Steam for us?

I'm thinking, after paths to clients is set:

a)
Case 1:
It detects OLD Steam running -> [NEW] a button that closes old Steam & launches new Steam.

Case 2:
It detects NO Steam running -> [NEW] a button to launch new Steam.

Case 3 stays as it is.

b) After fully loading, user closes new client.

c) Start PackageInfo conversion button

d) When completed -> [NEW] Button that gives option to quit tool and start old Steam

[tintingaroo]

Also who wrote the overview? I like their writing, they did a nice job.

[Tharon]

I was working on something like that, but detect when Steam have fully loaded is tricky.
Also force Steam to close can cause a number of issues. There are a lot of reports of users with uninstalled games because they didn't close Steam properly.

[m4dEngi]

Originally posted by Tharon:

I was working on something like that, but detect when Steam have fully loaded is tricky.

Can be done using steamworks api: Check if client process is active -> Initialize API -> Call BLogedOn on IClient/ISteamUser (usually that should be enough)

[Tharon]

Isn't reliable. When BlogedON starts to returns true, the client is still not fully loaded.
Adding the possibile issues on forcing steam to close, the effort to make the tool full automatic isn't worth the hassle.

[Xykreilon]

Anyone found a workaround for things like TF2 not working with the old client yet?
I can still use the old client just fine. But, I can't play TF2 if I use it :/ I have to switch to the new client when I want to play it

[Tharon]

A workaround is possible but isn't simple.
Someone must build a "dummy" SteamAPI who act as a compatibility layer between the SteamAPI shipped with TF2 and the old Steam.

I don't suggest to even try it because such a thing can easily trigger a VAC ban.

[Valoşi]

Originally posted by Xykreilon:

Anyone found a workaround for things like TF2 not working with the old client yet?
I can still use the old client just fine. But, I can't play TF2 if I use it :/ I have to switch to the new client when I want to play it

I had the same problem with Creativerse after it switched to the Unity engine. The quick and dirty solution I came up with was to install mobile Steam in a separate directory from classic Steam (in my case, it's on a completely diffrent drive for safety). ONLY install the games that aren't compatible with classic Steam on the modern version. Then, set it to small mode, showing only those games installed.

It'll still lag some, but not nearly as bad and is much safer to use for those of us who are affected medically by the mobile phone layout of the new UI. And you'll still be able to use classic Steam for everything else.


Incidentally, Tharon: Occasionally, I'll get a major hiccup with PackageInfo Converter and it'll give me a wrong version error on every copy of packageinfo.vdf I have on-hand. I've found the only way to fix it seems to be reinstalling classic Steam and running through my oldest copies of the VDF until one clicks.

Do you know of any reason this might happen? I could understand needing to use an older VDF copy or having to reinstall for the backup VDF, but it's strange that I sometimes have to do both before I can get it to work. And this happens whether or not I delete the appinfo.vdf file (I've tried both scenarios).

[Tharon]

If you get a wrong version error this mean that the file is already in the old format (and there is no need to convert it).
If the files doesn't work in steam, even if in the correct format, then you can discard it because it will never work.

Old vdf files only works sometimes, because Steam will try to update the file leading to corruption at various levels. If the file is recent it can work, but in some occasion it can give problems like CPU spikes, strange network traffic and Steam can became slow to respond or games have difficult to launch. If any of thouse occours then the file must be replaced with a newer.
This usually happen if the user add games in their Steam account.

To be safe, always convert the file from a new, fresh version acquired from the new Steam installation.

There is no need to delete appinfo.vdf or reinstall Steam. You only need to get the up to date file from the new Steam client and convert it. The Auto Package info converter do it automatically, you only need to have both client installed and follow the instruction when asked to launch or close the new client.

[Valoşi]

I hadn't even thought of harvesting a copy from the newer client. That's probably why I've had problems that sometimes required a reinstall. The next time Steam messes up the file, I'll grab from the other version instead.

[Yobbo]

Any workarounds for Origin games bought in Steam? The game can't be launched unless both clients are active, and old steam tries to update the game every time I launch. Upon completion it gives me an error saying "An error occurred while updating *game* (missing executable)". I'm hoping there is a safer workaround considering it's not a VAC protected valve game like TF2. Thoughts?

[Tharon]

Origin integration was made after the release of the new UI, so maybe there is something required that is missing in the old client.

I don't think there is an easy workaround for this incompatibility. Unfortunately (or fortunately) i don't have any Origin games on Steam, so i can't do any test.