I have "r_drawtracers_firstperson 1" in my config, and it suddenly stopped working today.
Here is my autoexec: http://pastebin.com/43B8vgBg
Thanks in advance- it's probably just a stupid error on my part but I couldn't find anything.
r_drawtracers_firstperson not working
posted in
Q/A Help
I have "r_drawtracers_firstperson 1" in my config, and it suddenly stopped working today.
Here is my autoexec: http://pastebin.com/43B8vgBg
Thanks in advance- it's probably just a stupid error on my part but I couldn't find anything.
Here is my autoexec: http://pastebin.com/43B8vgBg
Thanks in advance- it's probably just a stupid error on my part but I couldn't find anything.
i THINK viewmodel_fov can make it so you can't see tracers. i use that to keep the sparks but get rid of the tracers.
i THINK viewmodel_fov can make it so you can't see tracers. i use that to keep the sparks but get rid of the tracers.
Martyi THINK viewmodel_fov can make it so you can't see tracers. i use that to keep the sparks but get rid of the tracers.
iirc they restricted viewmodel_fov to a range that doesn't bug out, that's why they added r_drawtracers_firstperson in the first place
[quote=Marty]i THINK viewmodel_fov can make it so you can't see tracers. i use that to keep the sparks but get rid of the tracers.[/quote]
iirc they restricted viewmodel_fov to a range that doesn't bug out, that's why they added r_drawtracers_firstperson in the first place
iirc they restricted viewmodel_fov to a range that doesn't bug out, that's why they added r_drawtracers_firstperson in the first place
Ive had this same problem for a while and have found no fix for it
It has got to be something in my comanglias config bc when I did the MM stress test I could play with no viewmodels on but I could see the tracers then. When I go back to regular TF2 with no viewmodels I cannot see my tracers.
edit - on second thought it could be related to viewmodel_fov. Since Valve restricts it to something lower than what I have set in my crosshair switcher (even though I have viewmodels off for scattergun) MM reverts it to a lower value, thus revealing the tracers when I enter MM but they go away when I join anything else. So maybe try lowering your viewmodel_fov and see if that helps? I'll test on my end when I get home
Ive had this same problem for a while and have found no fix for it
It has got to be something in my comanglias config bc when I did the MM stress test I could play with no viewmodels on but I could see the tracers then. When I go back to regular TF2 with no viewmodels I cannot see my tracers.
edit - on second thought it could be related to viewmodel_fov. Since Valve restricts it to something lower than what I have set in my crosshair switcher (even though I have viewmodels off for scattergun) MM reverts it to a lower value, thus revealing the tracers when I enter MM but they go away when I join anything else. So maybe try lowering your viewmodel_fov and see if that helps? I'll test on my end when I get home
It has got to be something in my comanglias config bc when I did the MM stress test I could play with no viewmodels on but I could see the tracers then. When I go back to regular TF2 with no viewmodels I cannot see my tracers.
edit - on second thought it could be related to viewmodel_fov. Since Valve restricts it to something lower than what I have set in my crosshair switcher (even though I have viewmodels off for scattergun) MM reverts it to a lower value, thus revealing the tracers when I enter MM but they go away when I join anything else. So maybe try lowering your viewmodel_fov and see if that helps? I'll test on my end when I get home
PertIve had this same problem for a while and have found no fix for it
It has got to be something in my comanglias config bc when I did the MM stress test I could play with no viewmodels on but I could see the tracers then. When I go back to regular TF2 with no viewmodels I cannot see my tracers.
edit - on second thought it could be related to viewmodel_fov. Since Valve restricts it to something lower than what I have set in my crosshair switcher (even though I have viewmodels off for scattergun) MM reverts it to a lower value, thus revealing the tracers when I enter MM but they go away when I join anything else. So maybe try lowering your viewmodel_fov and see if that helps? I'll test on my end when I get home
EDIT: problem solved. It appears it was an issue with broeselhud crosshair switcher. I guess in settings, inputting off_with_muzzleflash allows r_drawtracers_firstperson to work. I'd have to see exactly why, but changing the value from
alias scout_primary "medium; pink; cross; off" to alias scout_primary "medium; pink; cross; off_with_muzzleflash"
fixed it.
[quote=Pert]Ive had this same problem for a while and have found no fix for it
It has got to be something in my comanglias config bc when I did the MM stress test I could play with no viewmodels on but I could see the tracers then. When I go back to regular TF2 with no viewmodels I cannot see my tracers.
edit - on second thought it could be related to viewmodel_fov. Since Valve restricts it to something lower than what I have set in my crosshair switcher (even though I have viewmodels off for scattergun) MM reverts it to a lower value, thus revealing the tracers when I enter MM but they go away when I join anything else. So maybe try lowering your viewmodel_fov and see if that helps? I'll test on my end when I get home[/quote]
EDIT: problem solved. It appears it was an issue with broeselhud crosshair switcher. I guess in settings, inputting off_with_muzzleflash allows r_drawtracers_firstperson to work. I'd have to see exactly why, but changing the value from
alias scout_primary "medium; pink; cross; off" to alias scout_primary "medium; pink; cross; off_with_muzzleflash"
fixed it.
It has got to be something in my comanglias config bc when I did the MM stress test I could play with no viewmodels on but I could see the tracers then. When I go back to regular TF2 with no viewmodels I cannot see my tracers.
edit - on second thought it could be related to viewmodel_fov. Since Valve restricts it to something lower than what I have set in my crosshair switcher (even though I have viewmodels off for scattergun) MM reverts it to a lower value, thus revealing the tracers when I enter MM but they go away when I join anything else. So maybe try lowering your viewmodel_fov and see if that helps? I'll test on my end when I get home[/quote]
EDIT: problem solved. It appears it was an issue with broeselhud crosshair switcher. I guess in settings, inputting off_with_muzzleflash allows r_drawtracers_firstperson to work. I'd have to see exactly why, but changing the value from
alias scout_primary "medium; pink; cross; off" to alias scout_primary "medium; pink; cross; off_with_muzzleflash"
fixed it.
fnmEDIT: problem solved. It appears it was an issue with broeselhud crosshair switcher. I guess in settings, inputting off_with_muzzleflash allows r_drawtracers_firstperson to work. I'd have to see exactly why, but changing the value from
alias scout_primary "medium; pink; cross; off" to alias scout_primary "medium; pink; cross; off_with_muzzleflash"
fixed it.
That works because 'off' means everything off. The crosshair switcher was working as intended. No mystery there.
[quote=fnm]
EDIT: problem solved. It appears it was an issue with broeselhud crosshair switcher. I guess in settings, inputting off_with_muzzleflash allows r_drawtracers_firstperson to work. I'd have to see exactly why, but changing the value from
alias scout_primary "medium; pink; cross; off" to alias scout_primary "medium; pink; cross; off_with_muzzleflash"
fixed it.[/quote]
That works because 'off' means everything off. The crosshair switcher was working as intended. No mystery there.
EDIT: problem solved. It appears it was an issue with broeselhud crosshair switcher. I guess in settings, inputting off_with_muzzleflash allows r_drawtracers_firstperson to work. I'd have to see exactly why, but changing the value from
alias scout_primary "medium; pink; cross; off" to alias scout_primary "medium; pink; cross; off_with_muzzleflash"
fixed it.[/quote]
That works because 'off' means everything off. The crosshair switcher was working as intended. No mystery there.
DanceNumberfnmEDIT: problem solved. It appears it was an issue with broeselhud crosshair switcher. I guess in settings, inputting off_with_muzzleflash allows r_drawtracers_firstperson to work. I'd have to see exactly why, but changing the value from
alias scout_primary "medium; pink; cross; off" to alias scout_primary "medium; pink; cross; off_with_muzzleflash"
fixed it.
That works because 'off' means everything off. The crosshair switcher was working as intended. No mystery there.
awesome, I didnt even know that was a thing with the crosshair switcher
[quote=DanceNumber][quote=fnm]
EDIT: problem solved. It appears it was an issue with broeselhud crosshair switcher. I guess in settings, inputting off_with_muzzleflash allows r_drawtracers_firstperson to work. I'd have to see exactly why, but changing the value from
alias scout_primary "medium; pink; cross; off" to alias scout_primary "medium; pink; cross; off_with_muzzleflash"
fixed it.[/quote]
That works because 'off' means everything off. The crosshair switcher was working as intended. No mystery there.[/quote]
awesome, I didnt even know that was a thing with the crosshair switcher
EDIT: problem solved. It appears it was an issue with broeselhud crosshair switcher. I guess in settings, inputting off_with_muzzleflash allows r_drawtracers_firstperson to work. I'd have to see exactly why, but changing the value from
alias scout_primary "medium; pink; cross; off" to alias scout_primary "medium; pink; cross; off_with_muzzleflash"
fixed it.[/quote]
That works because 'off' means everything off. The crosshair switcher was working as intended. No mystery there.[/quote]
awesome, I didnt even know that was a thing with the crosshair switcher
Please
sign in through STEAM
to post a comment.