This demonstration has been reserved:Karmacharger 8:59 PM 7/28/2016 (PDT)
Hey Wind, i have a question. I plan on buying another PC with expensive specs. So i can render two clips at the same time. The question is, is there a way to speed up Srcdemo2 render? because the srcdemo2 render time is unacceptably long and it's getting my nerves. When i render one clip, i can't play games, well technically i can, but i feel like my PC will explode or bluescreen while playing game and rendering srcdemo2. So having two PC render one clip each, would speed up the video progress. Also, can a processor like i7 or amd a10 makes the Srcdemo2 render faster? or it doesn't matter? Karmacharger 9:16 PM 7/31/2016 (PDT)
Alright, here's my second PC specs:
Mainboard : Gigabyte H170-Gaming 3
Chipset : Intel
Processor : Intel P6 @ 3408 MHz
Physical Memory : 32768 MB
Video Card : NVIDIA GeForce GTX 970
Hard Disk : Samsun SSD 750 EVO 250G SCSI Disk Device (250GB)
Hard Disk : WD WD30EZRZ-00Z5HB0 SCSI Disk Device (3001GB)
Operating System : Windows 7 Ultimate Professional Media Center 6.01.7601 Service Pack 1 (64-bit)
DirectX : Version 11.00
I'm rendering at host_framerate 1500, and yes it's still pretty slow. If there's a way to increase the render speed, that would be great. Looking forward to your reply Karmacharger 8:39 PM 8/4/2016 (PDT)
This is probably not what you want to hear, but I don't have a good answer. The biggest limiting factor is Valve's Source Recorder itself. The way is does thing is really inefficient. It doesn't pre-render frames while writing to disk, it writes frames in the most inefficient image format ever (.tga files), and it doesn't support outputting files across multiple disks.
SrcDemo2 already makes rendering much faster by avoiding having to wait for most frames to be written to disk. If you were to try rendering a host_framerate 1500 demo without SrcDemo2, good luck (and you will need a lot of disk space). So you're already gaining a lot of speed with SrcDemo2.
I have never formally benchmarked it, but my hunch is that the bulk of the non-Valve-Source-Recorder-induced inefficiency is in the transmission of picture frame data from the game to SrcDemo2. On Windows, the picture data has to go through from the game to the Windows kernel's filesystem layer and then back to userspace to SrcDemo2. This takes lots of context switches on the CPU. On Windows, this process is handled through the Dokan library, which isn't really fast, and neither are the Java binding library for it that SrcDemo2 uses. I suspect the OS X and Linux version of SrcDemo2, which work using the FUSE library instead of Dokan, are a lot faster, because FUSE is much more widely used than Dokan and I suspect much more optimized. It also has tunables which I actually understand (configurable minimum block sizes) that AFAIK don't exist on Dokan. So, if you have the will to do it, you could try rendering demos with Linux and see if that's any faster.
That being said, if my hunch is correct about the bottleneck being the time it takes for the frame data to go from userspace to kernelspace and back to userspace, then your problem is the CPU and the time it takes to do context switches. "Intel P6" (you didn't specify the precise model number) is ~2 CPU generations old. I suspect a core i5/i7 would provide a big boost. Before spending more money on a new CPU, you can verify that the CPU is the bottleneck by trying to overclock or underclock your existing CPU. If you notice that the rendering speed increases or decreases proportionally to how much you overclocked or underclocked the CPU, then you are sure that the bottleneck is the CPU.
You could also reduce the host_framerate. 1500 is a bit pushing it. Try 900 and see if you can tell any difference in the output frames. Even 450 is probably good enough for weapon demonstrations (technically, even 24 is).
Lastly, also consider just using two computers. You could set up your other computer as a rendering station, and your new computer as your gaming computer. You can put the demo files on a shared folder that both can read. You can create a "renderer" steam account so that both computers can have TF2 running at the same time. This doesn't speed up rendering, but it frees your main computer so you can keep playing. (EDIT: looks like you have done that already)
Hope this helps~ — Wind 16:48, 7 August 2016 (PDT)
Wow valve, that spy one is so lazy. Is good, please upload~ — Wind 16:48, 7 August 2016 (PDT)
Yes, they didn't even try. Recently all big TF2 YouTubers has been roasting Valve's laziness, and the way they release new content without asking the community first whether it's a good idea to buff/nerf this weapon or not, but no, they just went for it. They buffed the Sydney Sleeper, that thing is already a monster, why would everyone in the right mind to buff it? That kinda explained Valve didn't even play their own game. But after they screwed up in the Meet Your Match update, they posted in the blog two times saying they are listening to us. Well hopefully they done the right thing. Karmacharger 1:56 PM 8/8/2016 (PDT)
Oh by the way, thanks for the reply to my srcdemo2 render related question. It's fine, it's not really a big deal. Yes i have two PCs, one render a clip, another one render another clip. Karmacharger 2:03 PM 8/8/2016 (PDT)
Alright, i need to go back to my channel and make some videos for my own. I'll be right back after 3-4 videos. Also Wind, i lost the password for the Wiki youtube channel, mind send it to me in Steam? Thanks Karmacharger 12:31 AM 8/10/2016 (PDT)
Forgot to mention: At the last clip, instead if muting the sentry empty sound, i reduced the volume for that particular sound from 100% to 30%. If i mute it completely, it might confuse new players in some ways. Karmacharger 6:45 PM 8/10/2016 (PDT)
That's fine. Is good, please upload~ — Wind 16:12, 14 August 2016 (PDT)
One missed hit on the pyro. Rest is good — Wind 18:41, 26 June 2016 (PDT)
https://www.youtube.com/watch?v=ysoOQ7TeGlM alright hopefully it's good. I also re-rendered the Claidheamh Mór and Bushwacka with only showing the rocket damage, i uploaded both videos to the wiki channel, i don't think i should show you here, it's the same, just without the rest of the damage type clips. Well yeah, review once a month isn't enough. You can check twice a week, that wouldn't be too bad. Karmacharger 1:43 PM 7/3/2016 (PDT)
Is good, please upload~ — Wind 18:31, 4 July 2016 (PDT)
This demonstration has been reserved:Vp999 (talk) 02:16, 6 July 2016 (PDT)
Increased holster and deploy time and increased range
Honorbound changed. Deals 50 self damage on holster if no kill was made. Cannot be holstered if player is below 50 life and no kill was made.
100% life restore on kill changed to 50% health gain on kill that can result in overheal
No random crits
My third try to make a demonstration. I am SkullCake, I changed my name and I made a new account. This will be my account now. Here is the video. I hope it's good. -Vp999 (talk) 04:25, 6 July 2016 (PDT)
If you want, we can merge your two accounts so that edits are still preserved under the same account.
Regarding the demonstration:
Inconsistency between soldier/demo clips: the soldier one doesn't show what happens if you try to holster the weapon while being at 50 HP, but the demo one does. It should be demonstrated for both classes (I think that would be the first weapon like this for the Soldier).
Slight framerate drop when making towards the medic at 0:48.
The video doesn't demonstrate the large melee range. The current demo doesn't either but it should have... Check the Eyelander demo for an example of how to demonstrate this. Should be demonstrated for both classes.
The rest is good~ — Wind 17:19, 10 July 2016 (PDT)
I have one more problem... the big yellow damage numbers doesn't work anymore... -Vp999 (talk) 00:39, 11 July 2016 (PDT)
Not sure what you mean; the big yellow damage numbers do show up in the video.
Your video is perfect, just one thing to change: the demonstration of extended melee range for the Soldier should come after the other soldier-related clips (i.e. just before the Demoman loadout view at 1:23). — Wind 16:29, 17 July 2016 (PDT)
I changed what you said, and I also changed the demoman bit to match Soldier's demonstration then melee range. I hope that this is good. -Vp999 (talk) 00:03, 18 July 2016 (PDT)
Good job, the quality is 10/10. But still has a few issues though.
Let's take a look:
1. At 0:44, right scene. There is a sudden frame cut or stop, whatever you call it. But you know what i'm saying
Just one. Congratulation, you just need to re-record that particular scene, and show me the fixed version. I'm not the person who approve videos here, so wait for Windpower for him to review your video. Karmacharger 9:10 PM 7/17/2016 (PDT)
It's not exactly at 0:44, it's just a bit later when you're almost right against the back wall. Should be easy to fix hopefully. Rest is all good~ — Wind 16:29, 17 July 2016 (PDT)