hldj gets stuck in a constant wrote cfg/hldj_cmd loop

[mistercqnzr]

Hello, I had been using an older version hldj for a long period of time and decided to update it; however once I had installed version 1.5, hldj gets stuck in a constant loop of Host_WriteConfiguration: Wrote cfg/hldj_cmd_[x].cfg where [x] is any letter from a-t, it restarts from there. This constant refreshing causes a split second of video lag (i have a shitcan computer) and makes the game unplayable. I can play sounds but the constant refreshing after every write is too frustrating to tolerate. Not only that but the constant writing floods the dev console with my hldj list, making it a little less useful. I've tried installing every build of hldj available on the site, clearing the leftover hldj files left in the cfg folder each time but it still happens. I've also tried reinstalling tf2, but that doesn't work either.

Has anyone else had this problem? I've found some people who have had it before but their only solution involved a system restore before they reinstalled hldj and i don't really want to commit to that

[Renegade]

If you've tried all the versions up to 1.5.0 I doubt it's anything new in 1.5
There's probably a bind/command/alias somewhere in a script file that is causing problems with the new version or a quirky server setting. Examine all your binds and script files for things that might cause this (especially any HLDJ-related commands) and test on a trusted server (i.e. your own).

It sounds as if hldj_write_cfg is being triggered, which in turn can be triggered by either hldjsf or hldjsd or just about any hldj command (which uses these), so again make sure you don't have some script somewhere that is calling these in an odd way.

[mistercqnzr]

well, it's not a bind. since i didn't really have anything important bound i just did an unbindall/restore defaults and the loop keeps going

i wouldn't even know where to begin to go looking for a script/server setting; i haven't really messed with source engine / extraneous hl2 tools outside hldj

[Renegade]

The best I can advise is to delete and re-install the game completely, then delete and re-install HLDJ. Add the game back to HLDJ and before visiting any server or changing any binds, test it out on your own server.

[mistercqnzr]

I'll be doing that; i'll post here when I've reinstalled everything

[mistercqnzr]

I deleted the G:\Program Files\Steam\steamapps\user\team fortress 2 folder after clearing the local game content, reinstalled it, used a fresh copy of hldj after deleting the old one, and it still gets caught in the loop on the first time running it! I don't know what else I can do.

[mistercqnzr]

so whatever has happened here also affects other source games (despite never having used hldj with them), the same loop happens when i run left4dead as well

edit: experimenting with TF2:

keeping hldj in stop mode, then opened TF2, alt-tabbed out, set hldj to play.

typed exec hldj_init in the console, and the loop begins there.

[mistercqnzr]

next move is going to be deleting everything that uses source i guess

it sucks but it's arguably better than having to back up everything I've done for the last week and a half

[Renegade]

zip up the generated hldj_ configs and your autoexec.cfg, I'll take a look at them, but if it is the game engine screwing up, might want to delete all associated .gcfs as well.

[mistercqnzr]

well i nuked -everything- related to source already; but if the problem resurfaces I'll make sure to do that

[mistercqnzr]

a reinstall didn't fix it, pm sent

[Renegade]

There's no technical difference between your cfg's and those of a fresh install, except maybe 1.5.0 vs. 1.5.02 (1.5.0 is fine though).
You did have some audio in our audio folder though, try testing HLDJ completely vanilla, i.e. no audio. One guess is that there are odd/Unicode characters somewhere in your config or filenames that the game isn't liking. Another random thing you can try is moving HLDJ into a subdirectory on your C drive, I firmly doubt it changes anything, but some users have said it fixed some odd problems.

[mistercqnzr]

it's definitely unicode!

one song used a degree symbol for an o and i overlooked it.

changing it fixed everything.

[Renegade]

congrats