Upvote Upvoted 1 Downvote Downvoted
The Curse of %wintext%
posted in Q/A Help
1
#1
0 Frags +

So I'm derping around in Lawena, and realize I've gone to far for the clip I want. I open up demoui, set it to a tick about 1000 back, and click go to. It does it's usual loading thing, then it plays of bunch of REALLY loud TF2 sounds and shows me this crap:
%wintext death screen%
For whatever reason, I can use the goto command to go as far forward and as many times in that direction as I want, but whenever I use the goto command on a tick in the past, it shows me this screen.
The only way to go back is to disconnect from the demo altogether and go to the tick I wanted. This, understandably, can get very aggravating.
I've tried using snd_restart in the console with absolutely no change.
It's also not the HUD itself, I've tried this is minimal HUD (kill notices) and with both yaHUD and OMP Hud.
Could someone please help me fix this?

UPDATE: I've tested this thing again, and it only does this with certain demos. I'm not sure how that's possible.
UPDATE2: So I tested it out, and it seems that this error only happens when using demos that were recorded on custom maps such as tr_walkway and pl_morrigan_alley, but have no effect on valve maps such as cp_process. That'd be fine, except that there's a lot of really good custom maps that I want to play on.

So I'm derping around in Lawena, and realize I've gone to far for the clip I want. I open up demoui, set it to a tick about 1000 back, and click go to. It does it's usual loading thing, then it plays of bunch of REALLY loud TF2 sounds and shows me this crap:
[url=postimg.org/image/i2zlxtrpb/]%wintext death screen%[/url]
For whatever reason, I can use the goto command to go as far forward and as many times in that direction as I want, but whenever I use the goto command on a tick in the past, it shows me this screen.
The only way to go back is to disconnect from the demo altogether and go to the tick I wanted. This, understandably, can get very aggravating.
I've tried using snd_restart in the console with absolutely no change.
It's also not the HUD itself, I've tried this is minimal HUD (kill notices) and with both yaHUD and OMP Hud.
Could someone please help me fix this?

UPDATE: I've tested this thing again, and it only does this with certain demos. I'm not sure how that's possible.
UPDATE2: So I tested it out, and it seems that this error only happens when using demos that were recorded on custom maps such as tr_walkway and pl_morrigan_alley, but have no effect on valve maps such as cp_process. That'd be fine, except that there's a lot of really good custom maps that I want to play on.
2
#2
2 Frags +

Close and re-open demoui then hit resume. Fixes it for me

Close and re-open demoui then hit resume. Fixes it for me
3
#3
1 Frags +

That's normal, just resume the demo and it will play normally.

That's normal, just resume the demo and it will play normally.
4
#4
0 Frags +

Well it worked. But why does this happen? What changed recently that caused this to pop up?
(It's still a little bit aggravating, because I can't use the keybinds I have for demo_pause and resume, but that just means it will take a few seconds longer.)

Well it worked. But why does this happen? What changed recently that caused this to pop up?
(It's still a little bit aggravating, because I can't use the keybinds I have for demo_pause and resume, but that just means it will take a few seconds longer.)
5
#5
0 Frags +

Not sure if related, but this used to happen to a ton of HUD elements a long time ago if mat_antialias was changed via a cfg on game launch IIRC. Since Lawena/Demo Buddy do that, stuff breaks. I don't think it was ever fixed.

Not sure if related, but this used to happen to a ton of HUD elements a long time ago if mat_antialias was changed via a cfg on game launch IIRC. Since Lawena/Demo Buddy do that, stuff breaks. I don't think it was ever fixed.
Please sign in through STEAM to post a comment.