Latest Github Events

[FF_Team]

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

• eb76d8 squeek502: 'Give jetpack particles a bit more spread and a bit less alpha'

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 :+1:

View on Github

[FF_Team]

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

View on Github

[FF_Team]

squeek502 pushed 2 commits to fortressforever/fortressforever:beta

• f1a27e squeek502: 'Fix local weapon sounds (like deploy sounds) playing twice on high ping. - No need to send the...'
• cf60db squeek502: 'Merge pull request #289 from fortressforever/fixes/weapon-local-sounds. Fix local weapon sounds...'

View on Github

[FF_Team]

DexterHaslem commented on commit fortressforever/fortressforever@cf60db:

nice work!

View on Github

[FF_Team]

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

• f0707b DexterHaslem: 'run assist damage tracking through GetDeathScorer(). makes sure assists from buildables and junk go...'

View on Github

[FF_Team]

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

View on Github

[FF_Team]

squeek502 created fortressforever/fortressforever:fixes/sourcetv-sendproxy at 914059 (+2 new commits)

• 3c6ebc squeek502: 'Fix SendProxy_OnlyToObservers not sending data to SourceTV. - This was stopping fields in a...'
• 914059 squeek502: 'Re-enable hud_keystate for SourceTV demos now that it will work'

View on Github

[FF_Team]

squeek502 opened pull request fortressforever/fortressforever#290 ('Fix certain fields not getting saved in SourceTV demos')

View on Github

[FF_Team]

AfterShockFF commented on issue fortressforever/fortressforever#290 ('Fix certain fields not getting saved in SourceTV demos'):

Whats m_flNextClassSpecificSkill needed for, is that to display the overpressure hud bar? I wonder if we could round that to 8 bits rather than 32, since 256 segments on screen is probably fine. Similarly can we squeeze flHitTime down at all?

I know it seems like potentially over optimising but...

View on Github

[FF_Team]

squeek502 commented on issue fortressforever/fortressforever#290 ('Fix certain fields not getting saved in SourceTV demos'):

Yes, `m_flNextClassSpecificSkill` is for overpressure (the cooldown also shows on the AC viewmodel).

You're right that those floats seem like they can be optimized. Here's some potentially similar fields; I couldn't actually find many examples of `curtime` fields:

```
//...

View on Github

[FF_Team]

squeek502 commented on issue fortressforever/fortressforever#290 ('Fix certain fields not getting saved in SourceTV demos'):

Just realized that there's also a `SendPropTime` function:

```c++
// basecombatweapon_shared.cpp
SendPropTime( SENDINFO( m_flNextPrimaryAttack ) ),
SendPropTime( SENDINFO( m_flNextSecondaryAttack ) ),
```

What it looks like (I'm not really sure what -1 bits does or...

View on Github

[FF_Team]

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

Looks like logging assists to file is not implemented yet. Here's our discussion about it from a while back:

```
Ryan Liptak: do assists get logged as well?
Dexter Haslem: in console? yea i just added to end of the other messages
Dexter Haslem: (assisted by %s). etc
Ryan Liptak: i mean...

View on Github

[FF_Team]

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

oops. I forgot entirely about that logging obviously. Assists on new line? would changing the kill line break any existing parsers

View on Github

[FF_Team]

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

> would changing the kill line break any existing parsers

Yes, almost certainly. Assists on their own line probably isn't ideal, but at least it'd be backwards compatible. Note that, if assists are on their own line, it'd still be possible to associate assists with specific kills, because it'll...

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

• ca35df DexterHaslem: 'its me ur pal FFGameRules(). its me your pal vc2005 too stupid to figure out the inheritancein....'

View on Github

[FF_Team]

squeek502 synchronized pull request fortressforever/fortressforever#290 ('Fix certain fields not getting saved in SourceTV demos')

View on Github

[FF_Team]

squeek502 pushed 1 commit to fortressforever/fortressforever:fixes/sourcetv-sendproxy

• 060c93 squeek502: 'Use SendPropTime instead of SendPropFloat in DT_FFPlayerObserver'

View on Github

[FF_Team]

squeek502 commented on issue fortressforever/fortressforever-scripts#58 ('WIP: Pyro revamp (scripts side)'):

@AfterShockFF make sure that this is up-to-date. Looks like some IC stuff (like increased clip size) has not been pushed yet.

Reminder to me/anyone else: The class description text/hints/etc will need to be updated.

View on Github