Upvote Upvoted 63 Downvote Downvoted
1 ⋅⋅ 3 4 5 6 7 8 9
StatusSpec
posted in Projects
151
#151
0 Frags +

I had the crashes until I fixed up MedigunInfo.res
Start there!

I had the crashes until I fixed up MedigunInfo.res
Start there!
152
#152
0 Frags +

Thanks, I'm sure it will be that, but I have no idea how I'm supposed to fix that file. The link is very complicated and codey and I'm a mong.

Thanks, I'm sure it will be that, but I have no idea how I'm supposed to fix that file. The link is very complicated and codey and I'm a mong.
153
#153
0 Frags +

See the "variable" parts added to the SpectatorTournament.res file in that diff? You need to add those parts to your file as well so that it works properly.

@Admirable: I've done some brief testing on your issue and managed to replicated it. I'm blaming it on Valve, since they apparently broke drawing yet again. It was working earlier, right?

See the "variable" parts added to the SpectatorTournament.res file in that diff? You need to add those parts to your file as well so that it works properly.

@Admirable: I've done some brief testing on your issue and managed to replicated it. I'm blaming it on Valve, since they apparently broke drawing yet again. It was working earlier, right?
154
#154
0 Frags +

Yeah as soon as I posted that comment I just checked it again then realised I was replacing the wrong fucking file. I'm such an idiot I astound myself sometimes.

EDIT: Thanks man.

Yeah as soon as I posted that comment I just checked it again then realised I was replacing the wrong fucking file. I'm such an idiot I astound myself sometimes.

EDIT: Thanks man.
155
#155
0 Frags +
thesupremecommanderIt was working earlier, right?

Yeah same files worked fine about 40 days ago.

[quote=thesupremecommander]It was working earlier, right?[/quote]

Yeah same files worked fine about 40 days ago.
156
#156
1 Frags +

StatusSpec 0.17.4 is now available. The only change is an adjustment to drawing which fixes the issues with loadout and status icons not being drawn in the correct location.

Lately, development has slowed due to a lack of ideas to develop, so if you have anything you'd be interested in seeing implemented, please let me know.

[url=https://github.com/fwdcp/StatusSpec/releases/tag/0.17.4]StatusSpec 0.17.4[/url] is now available. The only change is an adjustment to drawing which fixes the issues with loadout and status icons not being drawn in the correct location.

Lately, development has slowed due to a lack of ideas to develop, so if you have anything you'd be interested in seeing implemented, please let me know.
157
#157
2 Frags +

StatusSpec will remain broken indefinitely until the Source SDK is updated. I apologize for any inconvenience.

StatusSpec will remain broken indefinitely until the Source SDK is updated. I apologize for any inconvenience.
158
#158
3 Frags +

StatusSpec 0.18.0 is now available.

The issues introduced with last week's horrific update should all be fixed now. In addition, I have descended into the pits of hell Source and come back with the meaty heart of its glow system. As a result, outlines should be more reliable and more extensible now. This has also allowed me the opportunity to introduce a new feature - projectile outlines!

Feedback and suggestions appreciated as usual.

[url=https://github.com/fwdcp/StatusSpec/releases/tag/0.18.0]StatusSpec 0.18.0[/url] is now available.

The issues introduced with last week's horrific update should all be fixed now. In addition, I have descended into the pits of [s]hell[/s] Source and come back with the meaty heart of its glow system. As a result, outlines should be more reliable and more extensible now. This has also allowed me the opportunity to introduce a new feature - [url=https://github.com/fwdcp/StatusSpec#projectile-outlines]projectile outlines[/url]!

Feedback and suggestions appreciated as usual.
159
#159
0 Frags +

Don't know if I'm missing something but TF2 isn't recognizing this new statusspec folder (including any console commands). The game starts fine, but none of the plugins work; console commands aren't even listed. I'm running in insecure mode.

It seems to be just 0.18.0 that is doing this; I tried starting the game with the previous now broken versions and found that they still crashed the game, which means it's a specific problem with the 0.18.0 folder for me. Are there any additional steps I'm missing in the installation process? Thanks!

Don't know if I'm missing something but TF2 isn't recognizing this new statusspec folder (including any console commands). The game starts fine, but none of the plugins work; console commands aren't even listed. I'm running in insecure mode.

It seems to be just 0.18.0 that is doing this; I tried starting the game with the previous now broken versions and found that they still crashed the game, which means it's a specific problem with the 0.18.0 folder for me. Are there any additional steps I'm missing in the installation process? Thanks!
160
#160
0 Frags +

No, it is the standard installation procedures, and since you managed to successfully crash your game with previous versions, I doubt that is the issue.

Check your console for load errors relating to StatusSpec. That should clue us in to what the issue is.

No, it is the standard installation procedures, and since you managed to successfully crash your game with previous versions, I doubt that is the issue.

Check your console for load errors relating to StatusSpec. That should clue us in to what the issue is.
161
#161
0 Frags +

I've just been updating to the most recent release and trying the various options, I've noticed that using statusspec_killstreaks_enabled 1 will cause my game to crash at a specific point when watching an STV demo.

Edit: my previous loadout/statusicon hud element issue is fixed though! :)

I've just been updating to the most recent release and trying the various options, I've noticed that using statusspec_killstreaks_enabled 1 will cause my game to crash at a specific point when watching an STV demo.

Edit: my previous loadout/statusicon hud element issue is fixed though! :)
162
#162
0 Frags +

Also could you tell me the colour values for the default team coloured outlines?

And is there an example of how to customise the dynamic meters?

Also could you tell me the colour values for the default team coloured outlines?

And is there an example of how to customise the dynamic meters?
163
#163
0 Frags +

Similar to #159, but not quite.

I can't start tf2 in -insecure with statusspec in my custom folder. Without statusspec, I can load tf2 just fine in insecure mode. I tried with an old copy of v 0.14.1 I know has worked for me in the past and it crashes on launch as well. TF2 does not stay open long enough to load console/menus. It launches, shows the "loading" message in the bottom right, and crashes.

Any idea on how I can solve this issue? My custom folder's got PREC and my hud in it - no errors are received on the crash. DX9, 1080p, win 8.1, though I figure that's all irrelevant. The crashes persist loading tf2 in -insecure mode with statusspec in my custom folder, even with NOTHING else in my custom folder.

Similar to #159, but not quite.

I can't start tf2 in -insecure with statusspec in my custom folder. Without statusspec, I can load tf2 just fine in insecure mode. I tried with an old copy of v 0.14.1 I know has worked for me in the past and it crashes on launch as well. TF2 does not stay open long enough to load console/menus. It launches, shows the "loading" message in the bottom right, and crashes.

Any idea on how I can solve this issue? My custom folder's got PREC and my hud in it - no errors are received on the crash. DX9, 1080p, win 8.1, though I figure that's all irrelevant. The crashes persist loading tf2 in -insecure mode with statusspec in my custom folder, even with NOTHING else in my custom folder.
164
#164
1 Frags +
AdmirableI've just been updating to the most recent release and trying the various options, I've noticed that using statusspec_killstreaks_enabled 1 will cause my game to crash at a specific point when watching an STV demo.

Edit: my previous loadout/statusicon hud element issue is fixed though! :)

Was anything else enabled when you crashed? Also, does the demo crash when StatusSpec isn't loaded, and does it crash when StatusSpec is loaded but with no modules enabled?

AdmirableAlso could you tell me the colour values for the default team coloured outlines?

And is there an example of how to customise the dynamic meters?

BLU: rgba(88, 133, 162, 255)
RED: rgba(184, 56, 59, 255)

As for dynamic meters, here's the file I gave to BLoodSire a long time ago:

"Resource/UI/MedigunInfoDynamicMeters.res"
{
	"Medi Gun"
	{
		"fgcolor_override" 	"173 223 255 255"
	}

	"Kritzkrieg"
	{
		"fgcolor_override" 	"246 96 171 255"
	}

	"Quick-Fix"
	{
	}

	"Vaccinator"
	{
	}
}
takramSimilar to #159, but not quite.

I can't start tf2 in -insecure with statusspec in my custom folder. Without statusspec, I can load tf2 just fine in insecure mode. I tried with an old copy of v 0.14.1 I know has worked for me in the past and it crashes on launch as well. TF2 does not stay open long enough to load console/menus. It launches, shows the "loading" message in the bottom right, and crashes.

Any idea on how I can solve this issue? My custom folder's got PREC and my hud in it - no errors are received on the crash. DX9, 1080p, win 8.1, though I figure that's all irrelevant. The crashes persist loading tf2 in -insecure mode with statusspec in my custom folder, even with NOTHING else in my custom folder.

Hm... this might be difficult to diagnose, as I can't replicate any sort of crash.

Could you check that it doesn't crash when you load into insecure mode without any plugins at all?

[quote=Admirable]I've just been updating to the most recent release and trying the various options, I've noticed that using statusspec_killstreaks_enabled 1 will cause my game to crash at a specific point when watching an STV demo.

Edit: my previous loadout/statusicon hud element issue is fixed though! :)[/quote]
Was anything else enabled when you crashed? Also, does the demo crash when StatusSpec isn't loaded, and does it crash when StatusSpec is loaded but with no modules enabled?

[quote=Admirable]Also could you tell me the colour values for the default team coloured outlines?

And is there an example of how to customise the dynamic meters?[/quote]
BLU: rgba(88, 133, 162, 255)
RED: rgba(184, 56, 59, 255)

As for dynamic meters, here's the file I gave to BLoodSire a long time ago:
[code]"Resource/UI/MedigunInfoDynamicMeters.res"
{
"Medi Gun"
{
"fgcolor_override" "173 223 255 255"
}

"Kritzkrieg"
{
"fgcolor_override" "246 96 171 255"
}

"Quick-Fix"
{
}

"Vaccinator"
{
}
}[/code]

[quote=takram]Similar to #159, but not quite.

I can't start tf2 in -insecure with statusspec in my custom folder. Without statusspec, I can load tf2 just fine in insecure mode. I tried with an old copy of v 0.14.1 I know has worked for me in the past and it crashes on launch as well. TF2 does not stay open long enough to load console/menus. It launches, shows the "loading" message in the bottom right, and crashes.

Any idea on how I can solve this issue? My custom folder's got PREC and my hud in it - no errors are received on the crash. DX9, 1080p, win 8.1, though I figure that's all irrelevant. The crashes persist loading tf2 in -insecure mode with statusspec in my custom folder, even with NOTHING else in my custom folder.[/quote]
Hm... this might be difficult to diagnose, as I can't replicate any sort of crash.

Could you check that it doesn't crash when you load into insecure mode without any plugins at all?
165
#165
0 Frags +
thesupremecommanderCould you check that it doesn't crash when you load into insecure mode without any plugins at all?

insecure mode loads if I have no plugins. It loads if I have all plugins/hud elements (sprites/control points), PREC, hud, but if I have statusspec in my custom folder in insecure mode, I crash.

[quote=thesupremecommander]Could you check that it doesn't crash when you load into insecure mode without any plugins at all?[/quote]

insecure mode loads if I have no plugins. It loads if I have all plugins/hud elements (sprites/control points), PREC, hud, but if I have statusspec in my custom folder in insecure mode, I crash.
166
#166
2 Frags +
thesupremecommanderLately, development has slowed due to a lack of ideas to develop, so if you have anything you'd be interested in seeing implemented, please let me know.

Changing the team names in the same way that we can change the player names might be useful. The scoreboard is shown several times over the course of a map and often shows Red vs Blu, or a joke name, or the name of teams who used the server previously.

[quote=thesupremecommander]Lately, development has slowed due to a lack of ideas to develop, so if you have anything you'd be interested in seeing implemented, please let me know.[/quote]
Changing the team names in the same way that we can change the player names might be useful. The scoreboard is shown several times over the course of a map and often shows Red vs Blu, or a joke name, or the name of teams who used the server previously.
167
#167
1 Frags +

Sort players in spec hud by class rather than server join time.

Sort players in spec hud by class rather than server join time.
168
#168
1 Frags +
GentlemanJonthesupremecommanderLately, development has slowed due to a lack of ideas to develop, so if you have anything you'd be interested in seeing implemented, please let me know.Changing the team names in the same way that we can change the player names might be useful. The scoreboard is shown several times over the course of a map and often shows Red vs Blu, or a joke name, or the name of teams who used the server previously.

You know, I investigated how to do this a long time ago and never found a good way to do it... and now I've discovered a simpler solution that can be implemented much more easily and will probably work.

Expect it soon.

atmoSort players in spec hud by class rather than server join time.

I'll look into this, but I don't think this is possible that easily.

[quote=GentlemanJon][quote=thesupremecommander]Lately, development has slowed due to a lack of ideas to develop, so if you have anything you'd be interested in seeing implemented, please let me know.[/quote]
Changing the team names in the same way that we can change the player names might be useful. The scoreboard is shown several times over the course of a map and often shows Red vs Blu, or a joke name, or the name of teams who used the server previously.[/quote]
You know, I investigated how to do this a long time ago and never found a good way to do it... and now I've discovered a simpler solution that can be implemented much more easily and will probably work.

Expect it soon.

[quote=atmo]Sort players in spec hud by class rather than server join time.[/quote]
I'll look into this, but I don't think this is possible that easily.
169
#169
0 Frags +

Something I started but haven't had time to fully finish is forcing FOV, to keep it at 90 when players use something lower.

99% working code is here:
https://github.com/MattMcNam/StatusSpec/commit/83b219a5d8c75aedc1a60bfba7bb08d119fb8d8a

It breaks when you spec a sniper and they zoom in though, haven't had time to detect when a player is zooming/zoomed in since we want to use the smaller fov then.

Not a major issue since most players use 90, but it'd be nice to have, so the code's there if you want to try working on it.

Something I started but haven't had time to fully finish is forcing FOV, to keep it at 90 when players use something lower.

99% working code is here:
https://github.com/MattMcNam/StatusSpec/commit/83b219a5d8c75aedc1a60bfba7bb08d119fb8d8a

It breaks when you spec a sniper and they zoom in though, haven't had time to detect when a player is zooming/zoomed in since we want to use the smaller fov then.

Not a major issue since most players use 90, but it'd be nice to have, so the code's there if you want to try working on it.
170
#170
0 Frags +
takramthesupremecommanderCould you check that it doesn't crash when you load into insecure mode without any plugins at all?
insecure mode loads if I have no plugins. It loads if I have all plugins/hud elements (sprites/control points), PREC, hud, but if I have statusspec in my custom folder in insecure mode, I crash.

Try verifying all of your content, and if that doesn't work, backup your stuff (demos, custom stuff, configs, etc.) and reinstall TF2.

If/when that doesn't solve the issue, we'll need to come up with a better way. Ideally you could compile a debug build yourself and then debug it to find the exact point of the crash, but that would depend on how much you want to solve the problem.

blueeSomething I started but haven't had time to fully finish is forcing FOV, to keep it at 90 when players use something lower.

99% working code is here:
https://github.com/MattMcNam/StatusSpec/commit/83b219a5d8c75aedc1a60bfba7bb08d119fb8d8a

It breaks when you spec a sniper and they zoom in though, haven't had time to detect when a player is zooming/zoomed in since we want to use the smaller fov then.

Not a major issue since most players use 90, but it'd be nice to have, so the code's there if you want to try working on it.

Can you investigate if the sniper zoom FOV changes based on fov_desired (as in a person with a lower fov_desired has a lower FOV when zoomed, and a person with a higher fov_desired has a higher FOV when zoomed)?

I might have a solution for fixing it, but it probably hinges on that detail.

[quote=takram][quote=thesupremecommander]Could you check that it doesn't crash when you load into insecure mode without any plugins at all?[/quote]

insecure mode loads if I have no plugins. It loads if I have all plugins/hud elements (sprites/control points), PREC, hud, but if I have statusspec in my custom folder in insecure mode, I crash.[/quote]
Try verifying all of your content, and if that doesn't work, backup your stuff (demos, custom stuff, configs, etc.) and reinstall TF2.

If/when that doesn't solve the issue, we'll need to come up with a better way. Ideally you could compile a debug build yourself and then debug it to find the exact point of the crash, but that would depend on how much you want to solve the problem.

[quote=bluee]Something I started but haven't had time to fully finish is forcing FOV, to keep it at 90 when players use something lower.

99% working code is here:
https://github.com/MattMcNam/StatusSpec/commit/83b219a5d8c75aedc1a60bfba7bb08d119fb8d8a

It breaks when you spec a sniper and they zoom in though, haven't had time to detect when a player is zooming/zoomed in since we want to use the smaller fov then.

Not a major issue since most players use 90, but it'd be nice to have, so the code's there if you want to try working on it.[/quote]
Can you investigate if the sniper zoom FOV changes based on fov_desired (as in a person with a lower fov_desired has a lower FOV when zoomed, and a person with a higher fov_desired has a higher FOV when zoomed)?

I might have a solution for fixing it, but it probably hinges on that detail.
171
#171
0 Frags +

Is statusspec_playeroutlines_health_adjusted_team_colors working?
When I set it to 1 outlines just disappear :D

Is statusspec_playeroutlines_health_adjusted_team_colors working?
When I set it to 1 outlines just disappear :D
172
#172
0 Frags +
AdmirableIs statusspec_playeroutlines_health_adjusted_team_colors working?
When I set it to 1 outlines just disappear :D

Confirmed broken, I haven't had a chance to look into a possible fix. It might be permanently broken.

[quote=Admirable]Is statusspec_playeroutlines_health_adjusted_team_colors working?
When I set it to 1 outlines just disappear :D[/quote]
Confirmed broken, I haven't had a chance to look into a possible fix. It might be permanently broken.
173
#173
2 Frags +

It looks like Valve has decided to break everything. This may be unrecoverable without an SDK update from Valve.

It looks like Valve has decided to break everything. This may be unrecoverable without an SDK update from Valve.
174
#174
0 Frags +

I've managed to fix quite a few of the issues that have cropped up. VGUI stuff is still broken, though, and as a result medigun info and some other modules are broken.

I hope to make a minor release soon which adds features and fixes everything else.

I've managed to fix quite a few of the issues that have cropped up. VGUI stuff is still broken, though, and as a result medigun info and some other modules are broken.

I hope to make a minor release soon which adds features and fixes everything else.
175
#175
1 Frags +

Well, it appears that Valve has reverted all of the changes that they've made, so this plugin is back up and running again!

StatusSpec 0.19.0 has just been released and includes a whole lot of changes. Read the changelog on GitHub and ask questions about anything you're confused about.

Well, it appears that Valve has reverted all of the changes that they've made, so this plugin is back up and running again!

[url=https://github.com/fwdcp/StatusSpec/releases/tag/0.19.0]StatusSpec 0.19.0[/url] has just been released and includes a whole lot of changes. Read the changelog on GitHub and ask questions about anything you're confused about.
176
#176
1 Frags +

Thanks for your work!

Thanks for your work!
177
#177
5 Frags +

StatusSpec 0.20.0 is now available. Since 0.19.0, several changes have been made. It's recommended that people read the README to familiarize themselves with the changes (including changes from 0.19.1 and 0.19.2, which were released but not commented on here).

Over the past five months, StatusSpec has released 31 different versions within 469 different commits and now has 15 modules of functionality built in. I'd like to take a moment to thank everyone who's been involved, including bluee (for being a major influence with AdvSpec and offering a lot of help along the way), GentlemanJon (for working with me and making both of our plugins better), the production teams (for helping me to identify issues and to suggest new functionality), everyone who's taken the time to download the plugin and try it out for themselves (for helping me figure out how to make it better and more robust), and the general audience of competitive casts and the TF2 competitive community at large (which inspires me to work several hours a week to maintain and improve this plugin), and everyone else I've forgotten to specifically mention. Thank you for your support!

[url=https://github.com/fwdcp/StatusSpec/releases/tag/0.20.0]StatusSpec 0.20.0[/url] is now available. Since 0.19.0, several changes have been made. It's recommended that people read the README to familiarize themselves with the changes (including changes from 0.19.1 and 0.19.2, which were released but not commented on here).

Over the past five months, StatusSpec has released 31 different versions within 469 different commits and now has 15 modules of functionality built in. I'd like to take a moment to thank everyone who's been involved, including bluee (for being a major influence with AdvSpec and offering a lot of help along the way), GentlemanJon (for working with me and making both of our plugins better), the production teams (for helping me to identify issues and to suggest new functionality), everyone who's taken the time to download the plugin and try it out for themselves (for helping me figure out how to make it better and more robust), and the general audience of competitive casts and the TF2 competitive community at large (which inspires me to work several hours a week to maintain and improve this plugin), and everyone else I've forgotten to specifically mention. Thank you for your support!
178
#178
1 Frags +

StatusSpec 0.20.1 is now available, with some fixes and minor feature changes.

[url=https://github.com/fwdcp/StatusSpec/releases/tag/0.20.1]StatusSpec 0.20.1[/url] is now available, with some fixes and minor feature changes.
179
#179
0 Frags +

thesupremecommander best commander! Thanks for all your work to improve the aesthetics of TF2 casting.

thesupremecommander best commander! Thanks for all your work to improve the aesthetics of TF2 casting.
180
#180
0 Frags +

Camera Tools: might want to specify in the readme that it only accepts numbers as <team> <position> rather than red/blu or soldier/medic. I tried to do that like a noob.

Camera Tools: might want to specify in the readme that it only accepts numbers as <team> <position> rather than red/blu or soldier/medic. I tried to do that like a noob.
1 ⋅⋅ 3 4 5 6 7 8 9
Please sign in through STEAM to post a comment.