Latest Github Events

[FF_Team]

squeek502 pushed 1 commit to fortressforever/fortressforever:features/pyro-jetpack-wip

• fe8610 squeek502: 'Fade out the beginning of the jetpack when in first-person mode'

View on Github

[FF_Team]

DexterHaslem commented on issue fortressforever/fortressforever#287 ('Feature/kill assists'):

gunna create a PR from fortressforever feature/kill-assists directly so its easier for everyone! yay!

View on Github

[FF_Team]

DexterHaslem closed without merging pull request fortressforever/fortressforever#287 ('Feature/kill assists')

View on Github

[FF_Team]

DexterHaslem created fortressforever/fortressforever:feature/steamworks-server at 2285f9 (+13 new commits)

• e729f8 DexterHaslem: 'managed server that sends commands through steamworks'
• 42ee76 DexterHaslem: 'trim input so superfluous spaces dont screw it'
• d6756d DexterHaslem: 'formatting'
• f3207a DexterHaslem: 'start of ff client sources to talk to local server'
• 79811a DexterHaslem: 'clean shutdown code'
• 7ff409 DexterHaslem: 'less aggressive polling'
• 171d9c DexterHaslem: 'shutdown code that actually works, test msg'
• ddc711 DexterHaslem: 'start of code for actually starting server process'
• e298a8 DexterHaslem: 'ext process handle closing, not really needed but a safety measure'
• 2e0396 DexterHaslem: 'send heartbeats'
• 7cae9f DexterHaslem: 'longer polls and server quit cmd'
• 8fe891 DexterHaslem: 'remove some test code, more heartbeat fixes'
• 2285f9 DexterHaslem: 'rename the current steam api to prevent any confusion, fix clean shutdown'

View on Github

[FF_Team]

DexterHaslem created fortressforever/fortressforever:feature/steamworks-shim at da2228 (+1 new commit)

• da2228 DexterHaslem: 'attempted shimming of steamworks sdk into same process space. doesnt work'

View on Github

[FF_Team]

DexterHaslem created fortressforever/fortressforever-scripts:feature/kill-assists at d4755f (+1 new commit)

• d4755f DexterHaslem: 'script additions to support kill assists'

View on Github

[FF_Team]

fpsmoto commented on commit fortressforever/fortressforever@1fd986:

I believe this also happens when you switch to your knife as a Spy.

View on Github

[FF_Team]

DexterHaslem commented on commit fortressforever/fortressforever@1fd986:

I think any weapon switch also goes crazy and plays twice

View on Github

[FF_Team]

DexterHaslem opened pull request fortressforever/fortressforever#288 ('Feature/kill assists')

View on Github

[FF_Team]

DexterHaslem synchronized pull request fortressforever/fortressforever#288 ('Feature/kill assists')

View on Github

[FF_Team]

DexterHaslem pushed 1 commit to fortressforever/fortressforever:feature/kill-assists

• a9a75a DexterHaslem: 'stick kill assist in killer string right away. fixes alignment issues'

View on Github

[FF_Team]

DexterHaslem opened pull request fortressforever/fortressforever-scripts#59 ('script additions to support kill assists')

View on Github

[FF_Team]

DexterHaslem commented on issue fortressforever/fortressforever#288 ('Feature/kill assists'):

See also fortressforever/fortressforever-scripts#59 for required event script updates

View on Github

[FF_Team]

squeek502 commented on commit fortressforever/fortressforever@1fd986:

Yeah definitely affects weapon deploy sounds too.

View on Github

[FF_Team]

squeek502 created fortressforever/fortressforever:fixes/weapon-local-sounds at f1a27e (+1 new commit)

• f1a27e squeek502: 'Fix local weapon sounds (like deploy sounds) playing twice on high ping. - No need to send the...'

View on Github

[FF_Team]

squeek502 opened pull request fortressforever/fortressforever#289 ('Fix local weapon sounds (like deploy sounds) playing twice on high ping')

View on Github

[FF_Team]

AfterShockFF commented on issue fortressforever/fortressforever#289 ('Fix local weapon sounds (like deploy sounds) playing twice on high ping'):

Would it be simpler to use this https://github.com/fortressforever/fortressforever/blob/beta/game_shared/SoundEmitterSystem.cpp#L1175-1199 ?

View on Github

[FF_Team]

squeek502 commented on issue fortressforever/fortressforever#289 ('Fix local weapon sounds (like deploy sounds) playing twice on high ping'):

Not really the same thing--WeaponSoundLocal is meant to *only* be heard by the local player (viewmodel sounds), so using `CSingleUserRecipientFilter` makes more sense. There's no reason for any server-side stuff except potentially for observers (but that wouldn't have worked before anyway).

View on Github

[FF_Team]

AfterShockFF commented on issue fortressforever/fortressforever#289 ('Fix local weapon sounds (like deploy sounds) playing twice on high ping'):

Ok so the server side sound you removed from WeaponSoundLocal was a bug, and won't have any side effects?

View on Github

[FF_Team]

squeek502 commented on issue fortressforever/fortressforever#289 ('Fix local weapon sounds (like deploy sounds) playing twice on high ping'):

Correct. See the comment above the function:

```
//----------------------------------------------------------------------------
// Purpose: For weapon sounds that only the local player should hear
//----------------------------------------------------------------------------
```

View on Github