Recommended Posts

So, I decided to run an FPS boosting config. Dxlevel 81 seems to feel better. Maybe it's the lack of paInt on hats. :p

But I finally got myself a Team Spirited Vintage Trophy Belt. Had a regular one and traded with a friend who was happy to do that.

Also awesome beta update.

Gameplay:

Bots:

o Bots now work on Payload maps

+ Added payload to Offline practice

o Spy bots!

Medic:

The Quick-Fix:

o Megaheal (the uber) effect now also applies to the medic

Pyro:

The Detonator:

o Detonation particle effect increased to better match the radius

Soldier:

Reduced rage generation rate with Battalion?s Backup by 50%

Spy:

Fixed a bug that prevented domination lines from being played with the Eternal Reward

Maps:

Added koth_badlands

General:

Added Replay system that allows you to edit and publish movies of your play experiences (full Mac support in the next few days)

Added in-game Coaching system

Added in-game Voting system

Added training for the Demoman, Spy and Engineer

Temporarily enabled crafting and trading

Synced with changes from the official releases

o http://store.steampowered.com/news/5008/

o http://store.steampowered.com/news/5035/

o http://store.steampowered.com/news/5050/

o http://store.steampowered.com/news/5068/

o http://store.steampowered.com/news/5077/

o http://store.steampowered.com/news/5091/

Complete beta update history available here.

Also this is the truth.

Also this just got posted. http://www.teamfortress.com/shogunpack/

shogun_pack.jpg

Cower, peasants! Flee, terrified ronin! Crap in your ancient Japanese bamboo underpants, feudal warlords! For something approaches unlike anything you have ever seen! The Shogun Pack -- a collaboration between Team Fortress 2, the TF community, and Total War: Shogun 2 -- descends upon you like a rising sun! (But in reverse.)

That's right, Japan fans! Unlike other updates, The Shogun Pack represents a three-way partnership of feudal clans to depose a crooked emperor (the emperor being played in this case by "a lack of updates" for this metaphor to work). The awe-inspiring result? Eight all-new, Shogun-themed items for your head-wearing and/or neck-cleaving pleasure. And, in keeping with the three-way theme, you've got three ways to get your hands on them:

1. Pre-order Total War: Shogun 2 from Steam and get all eight items free. (You: "THAT'S INCREDIBLE!")

2. Buy all eight items in Team Fortress 2's Mann Co. Store. (You: "I CAN'T BELIEVE IT! I WON'T BELIEVE IT!")

3. Collect all eight items through in-game item drops or crafting. (You: "SOMEONE CALL AN AMBULANCE! I'M HAVING A HEART ATTACK! FROM JOY!")

Pick any one of the three to get your items! Heck, pick ALL three! (Don't actually do this. -Legal Dept.) Whatever your choice, be sure to check out The Shogun Pack!

How do you do other configs? Also, did you get a big increase in FPS? And does the game still look good? :p

No, the game ends up looking like crap since like 90% of the lighting tech is disabled.

True, the game doesn't look particularly pretty, since everything gains a matte appearance, but my average FPS went up to 100ish from 60.

Don't forget the 66 tick hard-limit that Source has either.

34 of those frames will be repeats.

I thought the 66-tick limit was updates from the server per second, which has little to do with what is drawn in a frame. Even with the 66-tick limit, those other 34 frames can be interpolation and prediction between the 66-tick limit, which would not be repeats.

I thought the 66-tick limit was updates from the server per second, which has little to do with what is drawn in a frame. Even with the 66-tick limit, those other 34 frames can be interpolation and prediction between the 66-tick limit, which would not be repeats.

The tickrate is the number of times the gameworld iterates per second, if the world has not iterated then the render result will be the same.

The tickrate is the number of times the gameworld iterates per second, if the world has not iterated then the render result will be the same.

I may be wrong with the following, but your are honestly the first person I have ever seen claim that TF2 in particular is limited to 66 game-world iterations per second (or FPS, for a simpler term, since anything over 66 is wasted according to you).

Everything I have ever heard about tickrate relates to Source engine networking and has little to do with client-side FPS. From what I understand of Source, all tickrate does, is set the rate that the server and client will communicate updates. Which means the server will only send updates to the client 66 times per second, but it does not mean the client will only draw 66 different frames per second, it only means that the other frames it does draw per second will be interpolation + prediction between updates/ticks.

Also, didn't they update the orange box engine awhile ago (which includes TF2 and what not) to support up to 100 tickrate, not a max of 66?

I've honestly never thought about how often Source "thinks", reading up on the tickrate (from the VDC) claims that the tickrate defines how often the server thinks, but on the client defines how often it monitors input state.

Edit: And of course the reading input stage of part of the engine "thinking", meaning that between the ticks nothing can actually happen. Then again it also claims L4D1/1 only think 30 times a second, but that seems wrong.

I may be wrong with the following, but your are honestly the first person I have ever seen claim that TF2 in particular is limited to 66 game-world iterations per second (or FPS, for a simpler term, since anything over 66 is wasted according to you).

Everything I have ever heard about tickrate relates to Source engine networking and has little to do with client-side FPS. From what I understand of Source, all tickrate does, is set the rate that the server and client will communicate updates. Which means the server will only send updates to the client 66 times per second, but it does not mean the client will only draw 66 different frames per second, it only means that the other frames it does draw per second will be interpolation + prediction between updates/ticks.

Also, didn't they update the orange box engine awhile ago (which includes TF2 and what not) to support up to 100 tickrate, not a max of 66?

Every game engine has a tickrate, both on the client and server. What you're thinking about is the _updaterate, _cmdrate and rate convars, which set the number of requests, submissions and allocated bandwidth to use used when communicating with a remote server.

By my understanding, without a tickrate we would encounter issues such as with running DOS games via emulation, where the gameworld runs at superspeed and requires CPU throttling.

And no, the current trunk of Source aka Source 15/"Orange Box engine" confers the 66-tick limitation (This wasn't present pre-OB), this caused some angsty teen drama over at the CS:S Beta forums. But in the end, locking to 66-tick allowed for the beta devteam to tweak and optimise small issues like inconsistant rate of fire.

I usually have VSync off for increased performance.

Anyway I went back to Dx9.

Any game I've played in the last 5-7 years that runs at around 60 FPS or more on my system shows terrible screen tearing unless I enable vertical synchronization. I've turned it on in every game I've played for many years, 60 FPS or not. I've never had any issues from doing this.

...

By my understanding, without a tickrate we would encounter issues such as with running DOS games via emulation, where the gameworld runs at superspeed and requires CPU throttling.

...

Half-Life 1 does this to an extent (it has a limit, of 300fps, so while it's capped it still thinks far too often)

There's also the opposite end of the spectrum, where the game thinks too slowly, leaving it feeling sluggish or jittery (S.T.A.L.K.E.R. did this, while GTA4 avoided it pretty well)

Half-Life 1 does this to an extent (it has a limit, of 300fps, so while it's capped it still thinks far too often)

...

I'll adjust this slightly, all Valve games using Source (or GldSrc) have an internal engine limit of 300fps (Which I found out with my new computer, which is capable of hitting 300fps in any of the Source games I tried)

Will the items ever stop? I can't enjoy this game anymore, which is really sad because it was one of my favorites.

I doubt they will but I don't let that bother me anymore. If I want to play Team Fortress 2, I'll play it for what it is: a fun team-based game. I don't care if people have different weapons and items as long as they aren't insanely more powerful than anything I have.

Well now I have 1 Vintage hat for each class, the objective I was attempting to achieve. Most of them are ones I like too :D

Olde Baker Boy, Tyrant's Helm, Rubber Glove, Tricorne, Toque, Engineer's Cap, Gatsby, Trophy Belt (TS'd), Fedora + Camera Beard.

:D

I'll adjust this slightly, all Valve games using Source (or GldSrc) have an internal engine limit of 300fps (Which I found out with my new computer, which is capable of hitting 300fps in any of the Source games I tried)

That can be changed if you set fps_max as a launch parameter IIRC.

Next Team Fortress 2 video will meet the Medic

The next TF2 video will star the Medic, according to a fan who recently visited Valve?s offices. While wandering around Valve HQ the visitor got to see a preview version of the next TF2 short film and reported back to fans on the Steam forums, saying that the video is almost finished, it?s coming out soon, and it?s going to be one of the best TF2 videos yet.

You can read forumite Political Gamer?s report in full on the Steam Forums. While he was there he met Valve CEO Gabe Newell, saw Dota 2 in action and watched an unfinished version of the new TF2 video, Meet the Medic.

He says ?I have seen it and its 100% real. It?s about 80-90% done. Its one of the best ?Meet the? videos yet? and adds that ?it will be released ?soon.?

Source

Yay :yes:

Also there was an update today for both the beta and the full game.

Team Fortress 2

  • Updated honor-bound weapons so they can be holstered within a second of touching a supply cabinet
  • Updated the Blighted Beak with creator submitted fixes
  • Fixed a clipping problem
  • Made it paintable
  • Updated the Hero's Hachimaki to be tradeable

Undocumented changes

  • Removed team colours from the Blighted Beak

Team Fortress 2 Beta

Gameplay

  • Scout
  • Sun-on-a-Stick base damage lowered slightly but guarantees crits against burning players instead of minicrits
  • Fan o' War
  • Marking someone for death now lasts 15 seconds (from 10 seconds)
  • Soldier
  • Concheror damage-to-health conversion increased to 35% (from 20%)
  • General
  • Added missing Shogun Pack models
  • Fixed client crash caused by missing Shogun Pack models
  • Added missing strings for class-specific duels
  • Updated the Blighted Beak with creator submitted fixes
  • Fixed a clipping problem
  • Made it paintable
  • Replay:
  • Added "replay_printsessioninfo <full path>" command for server admins to monitor session files, aid in debugging problems

This topic is now closed to further replies.
  • Posts

    • My father still uses a programme written in dbase3. Still manages to work with a little help from dosbox. 
    • Microsoft hides these secret Windows 11 performance boost settings available on every PC by Sayan Sen Windows enthusiasts often look for ways to extract as much performance out of their systems as possible, and it's often the case that they try and do so while trying to minimize the heat and power consumption. This is especially relevant in the case of mobile Windows PCs since laptops and notebooks tend to get hot and management of that heat and power is harder in such a form factor. As such users often turn to techniques like under-volting which can be used to squeeze out the maximum capabilities of a chip while also maintaining lowered power levels. There are official apps from AMD and Intel with the likes of Ryzen Master and XTU (Extreme Tuning Utility). While these are quite handy, most enthusiasts probably prefer to dig into the BIOS and play around with settings there like Curve Optimizer on Ryzen, which lets users set various frequency-voltage scaling values. These are essentially called P-States. If you are not familiar with them, Processor Power Management is done through Advanced Configuration and Power Interface (ACPI) P-states and C-states. While P-states or performance pwoer states handle CPU voltage-frequency scaling, C-states deal with CPU sleep states so that some of the CPU functions, which are not necessary at that moment, can be disabled. The P-states and C-states work together to make the processor run more efficiently. It helps the OS and apps determine which cores can be parked and which should be boosted. Of course not every user is an enthusiast or knows the technicalities and integrities of how things like overclocking or undervolting work. Thankfully for them Windows itself offers something pretty cool, though it is hidden by default on all systems. By default, Windows only has two P-States, "Minimum Processor State" and "Maximum Processor State." However, this can be changed with a Registry trick to expand the options under a secret "Processor performance boost mode" dropdown. This essentially enables the HWP or hardware P-States available on a device, and these are not controlled just by the OS itself as the underlying hardware gets involved too. In total there are five Processor Performance Boost Mode profiles that control how Windows requests and allows CPU turbo/boost behavior under the different power policies. They are: Disabled: In this mode, processor boosting is effectively turned off. The CPU will avoid entering turbo or boost frequencies and instead operate closer to its base frequency ceiling. This can significantly reduce power consumption and heat output, but at the cost of reduced burst performance and responsiveness in short workloads. Enabled: This is the standard behavior where boost functionality is allowed under normal conditions. The processor can opportunistically increase frequency when workload demands it, balancing performance gains with power and thermal constraints as managed by the system. Aggressive: Aggressive mode favors performance more heavily, allowing the CPU to enter higher boost states more readily and sustain them longer. This should in theory improve responsiveness under bursty or heavy workloads but increases power draw and thermal output compared to the default enabled behavior. Efficient Enabled: This mode still allows boosting, but with a stronger bias toward energy efficiency. The system attempts to use boost more selectively, avoiding unnecessary frequency spikes when the performance gain is marginal. Efficient Aggressive: This is a hybrid approach where boost is still performance-responsive, but the system continuously weighs efficiency more heavily than in Aggressive mode. It aims to deliver noticeable performance improvements while reducing wasted power in less demanding scenarios. Here's how to enable the Processor performance boost mode: Open Registry Editor: Press Win+R, type regedit, and click OK. Go to: HKLM\SYSTEM\CurrentControlSet\Control\Power\PowerSettings\54533251-82be-4824-96c1-47b60b740d00\be337238-0d82-4146-a960-4f3749d470c7 (where HKLM stands for HKEY_LOCAL_MACHINE_) Modify the value of Attributes from 1 to 2 (you can find modify option by right-clicking) After that, exit Registry, you should now be able to see the new "Processor performance boost mode" dropdown menu: As you can see there are now five new P-States or CPPC states or power profile available that help define the boost mode processor setting on your PC. Wrapping it up here's a quick run-down of the settings as defined by Microsoft itself. Setting Description Disabled The corresponding P-state-based behaviour is disabled. Collaborative Processor Performance Control (CPPC) behaviour is disabled. Enabled The corresponding P-state-based behaviour is enabled. CPPC behaviour is Efficient Enabled. Aggressive The corresponding P-state-based behaviour is enabled. CPPC behaviour is Aggressive. Efficient Enabled The corresponding P-state-based behaviour is Efficient. CPPC behaviour is Efficient Enabled. Efficient Aggressive The corresponding P-state-based behaviour is Efficient. CPPC behaviour is Aggressive. Aggressive At Guaranteed Windows calculates the desired extra performance above the guaranteed performance level, and asks the processor to deliver that specific performance level. Efficient Aggressive At Guaranteed Windows always asks the processor to deliver the highest possible performance above the guaranteed performance level. In the next part we shall be comparing these settings to explore how much of a benefit or regression they can provide in terms of performance and power efficiency. If you decide to change the values on your system and are experiencing problems like crashes or an overheating PC, make sure to revert the steps back to the original state.
    • I think he means you haven't reviewed previous UFC games. Of course it doesn't matter... Every time you just report on something that involves the President even if just simply what happened you guys usually get accused of being anti-Trump. We live in fun times.
  • Recent Achievements

    • One Month Later
      Leroy Jethro Gibbs earned a badge
      One Month Later
    • Conversation Starter
      flexorcist earned a badge
      Conversation Starter
    • One Month Later
      AndreaB earned a badge
      One Month Later
    • One Month Later
      agatameier earned a badge
      One Month Later
    • Week One Done
      agatameier earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      518
    2. 2
      +Edouard
      198
    3. 3
      PsYcHoKiLLa
      147
    4. 4
      ATLien_0
      93
    5. 5
      Steven P.
      77
  • Tell a friend

    Love Neowin? Tell a friend!