[Script request] + Little help with viewmodel
Hello, i need working script for spy(viewmodel on certain weapons, different crosshair, different sensitivity), atm i was using one created via "YetAnotherTF2ConfigGenerator" but since this update my game went nuts and is completly unplayable, this is what happends when i reload any weapon, attack and constantly when im in disguise kit - When im using aussie amby the texture is gold, so it has something to do with viewmodel.
Also i don't know if it's correct subreddit to ask, i can't turn my viewmodel on by any command, i tried r_drawviewmodel 1 and nothing.
Those are scripts i was using:
Im gonna be on reddit for next 3-4 hours to provide any infos needed.
Thanks in advance
Posted Feb 12, 2015, 8:53 PM UTC · edited
Just like all generated configs this is confusing and without explanation. Great.
Now that my grumping is out of the way, we can start by looking at what's bound to your reload key:
current_vis_shootswitchis defined ascurrent_vis_shootswitch_1_2and_3in the switching logic but all three of those are defined as blank aliases. So that doesn't appear to be an issue.You don't have a visible bind for the disguise kit that I can see, so I'll assume it's the same as stock. Which shouldn't cause a problem.
I'll guess that this issue is a graphical one rather than based on the switching code itself. That would suggest the problem lies somewhere in the "Options" portion of your script:
You're attempting to overwrite a number of aliases, which may be fine and may cause issues depending on the server. You appear to be using a custom HUD, and it's possible that some of the settings are interfering with that HUD (like min mode maybe?). I don't have experience with your issue and I'm not necessarily familiar with all of the lines above, so this is probably all the help I can directly give you on this issue.
Edit: Your config.cfg shows that you have
viewmodel_fov "0.100000". That's probably not something you want and could maybe be a cause. Change it to 54, IIRC that's the default. Your viewmodel visibility is constrained by bothviewmodel_fovandr_drawviewmodel.Separate things:
Your script has a ton of issues with quotation marks, including simply using nested quotes (which is probably fine but can cause otherwise avoidable issues on occasion) and using an incorrect (unmatching) number of quotes. It's better to never use nested quotes, there's no situation where they add utility.
Your script attempts to call
cl_crosshair_file ""within an alias multiple times, in my experience this is not functional. To get the default dynamic crosshairs back, you need to make a separate cfg file (like xh_default.cfg for example) and then put the linecl_crosshair_file ""in it. Then replace all instances of it in your other scripts withexec xh_default.You don't need the
spec_commands for your mouse1 and mouse2 binds, shown below:Simply binding directly to
+attackand+attack2is sufficient for those keys to work in spectator. Separatelyspec_previousisn't a valid command, it'sspec_prev.Okay, you solved the graphic glitch, it was the viewmodel_fov fault, when i've set it to viewmodel_fov 54 it works normally, Thanks.
//
I know those scripts were messy but since they worked i was fine with it, today i wan't to clean the mess in them.
About my disguise kit, i'm using default setting with the 1-3 choosing and 6 to switch with red/blue and e lastdisguise;
Im running ToonHUD.
The custom config generator overwrite the +attack, +attack2 and +attack3 so they didn't worked to switch spectator and +attack3 wasn't activating shield/rage on MvM.
im using crosshair only for pistol on spy, on rest it's set to size 0, it by default uses crosshair i choose when im creating the config.
//
Bitw, is there a way to turn off dynamic amby crosshair? In the past it wasn't possible, idk if something changed since then, last time i checked was like in december 2014.
That makes sense, people overlook it all the time when they make attack aliases. You don't need the
spec_commands if you aren't messing with that, though.If that's how you're using the crosshair it makes sense as you wouldn't be able to see the cfg failing to switch to the default dynamic crosshair.
I don't believe so, but AFAIK HUD crosshairs don't grow so you could use a HUD crosshair instead and use the achievement tracker to have the HUD crosshair only show up on your revolver.