Ys: The Oath in Felghana

Ys: The Oath in Felghana

[Solved?] Weird buildbot issue
I've just ♥♥♥♥♥♥ an issue with the buildbot-which usually only runs the first time you install the game. I just noticed yesterday that this ys game has a configuration app. I ran that, bumped up the resolution and a few other graphics options. But, for some reason, after I did that, every time I start the game or the config app, I get the "do you want the following program to make changes" permission thing with the buildbot_winslave04,
program location: "C:\Program Files (x86)\Steam\bin\steamservice.exe" /installscript "C:\Program Files (x86)\Steam\steamapps\common\Ys The Oath in Felghana\runasadmin.vdf" 207320
If I click no the desired app loads up (game/config). If I click yes it does the following:

Performing first time setup
Installing: configuration tool (step 1 of 2)
(after which it brings up the configuration screen, upon clicking ok or cancel then the buildbot does)
Performing first time setup
Installing: configuration tool (step 2 of 2)
(bringing the same configuration screen up again. Exiting that will run the desired app (either the game or-if I ran the config app-the config screen for a third time.))

I tried reinstalling, deleting the ys the oath in felghana folder, restarting comp, verifying game cache. Nothing worked. I then deleted the installscript.vdf located inside the main folder. That stopped the buildbot thing. Verifying the game cache puts it back in. This kind of bothers me and I'm wondering what really happened, even though deleting the file seems to be an easy workaround. Anyone have any idea what's up?
En son Brandarwi tarafından düzenlendi; 6 Ağu 2013 @ 20:32
< >
7 yorumdan 1 ile 7 arası gösteriliyor
I'm having the exact same issue. Anyone else experiencing this?
Ok, I managed to solve the problem affecting me. I needed to manually add a registry entry in

HKEY_LOCAL_MACHINE\\Software\\Valve\\Steam\\Apps\\207320

Name: ConfigTool
Type: DWORD
Value: 1

For some reason this entry wasn't being created automatically.
I tried what you said, it didn't change anything. There was also already a registry of name Installed type DWORD value 1. Comparing Oath (207320) to Origin (207350), I can't find any difference between them that I can see (as only Oath has this buildbot problem), I think that's weird.
Ok, I don't know why, but here's what I did exactly that made this buildbot thing stop, without deleting the installscript.vdf. I renamed the config.exe in oath folder, then copied the origin config.exe to oath's. I ran that. Then I switched it back to oath's config.exe (by renaming origin and then the renamed oath back), and ran it. Then I deleted all 3 config (the renamed origin, the oath config, and oath config dx9) and verified the game cache to redownload the config.exe. Then the buildbot stopped weirding out.
İlk olarak Bryff tarafından gönderildi:
Ok, I don't know why, but here's what I did exactly that made this buildbot thing stop, without deleting the installscript.vdf. I renamed the config.exe in oath folder, then copied the origin config.exe to oath's. I ran that. Then I switched it back to oath's config.exe (by renaming origin and then the renamed oath back), and ran it. Then I deleted all 3 config (the renamed origin, the oath config, and oath config dx9) and verified the game cache to redownload the config.exe. Then the buildbot stopped weirding out.

No effect for me. I still have the same issue you did. However when the buildbot pop up opens I can click No and nothing unusual seems to happen. I can play, run the config, have changes/game save and everything. Really weird. I never encountered this problem on my XP machine, wonder why it's happening to me on my 7 Machine.
Same problem here. I got those config tool windows popping up 2 times each loading. I didn't get it when i first play & finish this game in December 2012 / January 2013.

The above solution didn't solve anything.
En son Harest tarafından düzenlendi; 6 Ağu 2013 @ 12:31
I had a similar problem but the configuration utility was popping up TWICE every time I launched the game. The registry fix worked for me.
< >
7 yorumdan 1 ile 7 arası gösteriliyor
Sayfa başına: 1530 50

Gönderilme Tarihi: 22 Tem 2013 @ 15:31
İleti: 7