Kerry000

Hi @datiswous. Yes,, I would love to continue with the next part. The HitS story is quite a tale that would take place over several missions, and it is entirely my own fault that the next part is not complete. @Frost_Salamanderwas the lead on HitS and he's still very active here, as you know, but my life got upended shortly after we released Hare in the Snare and I was unable to continue assisting him. He, on the other hand, kindly set it aside as a courtesy to me, as a project we'd only work on together. I am unfortunately not yet in a position to dedicate the time the next mission needs right now, but I have indicated that I'd likely be able to get involved again some time next year. Thank you for asking about it. It is still close to my heart. As are the recurring characters in the plot.

I'm guessing you haven't heard of the human critical flicker fusion threshold when tracking detail? No matter. First, let me explain how a refresh mismatch on a monitor causes judder: 29.97 is the standard the world over and you don't get judder with accelerating pans, or if you follow the 7-second-rule, and it absolutely is related to a refresh rate mismatch. 30 fps is still 30 images per second, or an image every 33 milliseconds. That is not slow at all, and it's still the framerate for big budget movies. There's a reason that judder can be bad on one monitor and yet look really smooth on another one. For example, the Hare in the Snare intro had no judder on my old 60Hz monitor, but on my 180Hz screen the judder is very noticeable. Here's an exact scenario where a monitor's refresh mismatch alone causes judder: Source: A film shot at 60fps Display: A monitor fixed at 90Hz Result: The video player uses a 2:1 pulldown to fit the 60 frames into 90 refresh cycles --> This leads to uneven timing, otherwise known as a refresh mismatch --> And this can still happen with a film shot at a high 90fps and displayed on a 60Hz monitor, for example --> Because the video player has to squeeze or stretch the footage to match the refresh rate, which means some frames get played twice if the footage was a lower fps, and some frames get dropped completely if the footage was a higher fps. As for how the brain can cause judder: Source: A film shot at 60fps Display: A monitor with a native 60Hz refresh rate Condition: The pan speed is near or above the critical flicker fusion threshold for tracking detail Have you ever seen footage of helicopter blades that appear to spin slowly or spin backwards? Or a wheel on a car or an old wagon? That happens in real life too. If you put a spotlight on a fan and spin it at different speeds, you'll get to a point where you see the blades look like they're spinning backwards, or spinning slowly. That's the human brain filling in the gaps wrong. And it does the same thing when watching a pan across a scene. This is all documented science, you can look it up. That said, the whole point of my post was not to explain WHY judder happens, but to say that we can use 60fps in our videos, and that I have tested it inside TDM and it works.

TL;DR: 60fps is where it's at. Avoid 29.97fps if your video includes pans at a constant rate. The engine handles 60fps just fine. Hello everyone, I decided to try a change of framerate on the intro for the Hare in the Snare FM in order to minimize the judder that's been annoying me ever since I saw it in someone's playthrough video on YT last week. That's the jittering effect you see when a high-contrast scene pans across the screen at a constant rate, without heavy motion blur. This judder is also prevalent in the excellent intro video in Volta 3 by @kingsal. It's caused by a combination of your monitor's refresh rate misaligning with the precise framerate of a video, and the human brain's habit of creating an image where it expects the next frame to be (the human eye has an equivalent "refresh rate" of around 120 to 200Hz, so they say). Anyway, long story short, I've been experimenting with 60fps instead, and it works really well. Just be sure to keep the bitrate under 8Mb/s for compatibility with any users running older hardware. The wiki still recommends the standard framerate of 29.97, but I think that should be updated. 29.97 is not good for slow pans (the "camera" moving across the screen) at a steady rate. Also, for what it's worth, don't bother with 48kHz audio. 44.1kHz at 128kb/s is more than enough for a briefing video. @kingsal, feel free to chime in, but I 'd suggest that a change of framerate to 60fps to your briefing video would eliminate the judder completely. The nature of TDM is such that our videos are pretty much always going to be high-contrast in a flat-shaded, comic style. And that's where judder always ruins the day. A higher framerate fixes it. Until people start making 3D or realistic AI videos for their FMs, that is. Although changing to a realistic style via AI would be a real shame, IMO.

For someone like myself who's creating assets, readables, voiceovers etc. in collaboration with a mapper working on the map file, I personally really enjoyed the convenience of GitHub. As someone who's never used Git for project management before, I got the hang of the basics pretty quickly. Essentially what is advantageous for me is that I can work on my own branch, adding new textures or models or xdata for the readables etc. without interfering in the mapper's work. I just update my branch with his progress as time goes on, and he then merges my branch into his main repository whenever I make progress on my side. The process has been pretty seamless for us. I enjoy that I can just merge my branch with the main repository and then immediately run TDM (and DMAP) to then see all my additions in place in the latest update of the work-in-progress FM. Saves us having to transfer files to one another just to test our work, and also keeps the whole thing safe in an online repository if one us makes a mess of things on our local computers.

The Hare in the Snare's videos are both 1080p with VBR (2 pass) encoding, at 30fps. I set the target bitrate to 3 Mbps (max 5) for both. Getting their total size down to 66Mb for 3 mins worth of video at 1080p illustrates the merits of sticking to the traditional (old) visual style. You're right that the intro we created could not have been done via GUI animations and it was actually heavily dumbed down and filtered in post to give it an almost monochrome "Thief" feel, but in hindsight the outro (debrief) video we did with static screenshots was the better of the two. It took 1/10th the amount of time to create. The trouble with trying to do that via GUI animation, however, is the creation of unique and artistic imagery. Even though our outro is static, much of the imagery required manually setting the scenes with inactive AI's and introducing cinematic camera angles, then cleaning up in post. I am sure it could be done with a GUI-based "movie maker", but boy are you going to spend forever creating a pool of reusable GUI assets that will soon become "same old". For what it's worth, my suggestion would be to first improve the implementation of in-game videos by making it more reliable. For the Hare in the Snare debrief we ended up filing two bug reports (though we have not yet had the time to provide @stgatilov with a test case) and we actually ended up creating our own unique scripts and GUI files to make it work properly. We also need to allow audio files to be played directly from the .mp4 (only the intro currently does this) to prevent the audio going out of sync when the Uncapped FPS setting is off. Finally, there needs to be a tutorial to show mappers how to do it with cinematic screenshots compiled into a dynamic video sequence. We would see more video work if people had a basic understanding of how to create them with all the free compositing and editing software available today, in combination with stylized screenshots. I personally think that would be a gentler learning curve than a GUI animation system. Video size, however, is really not an issue if you understand how to manage bitrate. There is no need for an 11Mbps bitrate on any TDM video. Not even Blu-ray requires that much. For stylized and dynamic screenshot sequences in .mp4 format, I don't see why anyone would need more than 5Mbps at 1080p, unless they were going for full colour with rapidly changing frames. But in the case of Hare in the Snare, variable framerates or drastic compression were not required at all. Those videos were longer and more detailed than 99% of FM's, yet were also a much smaller size than most.

Okay, thank you @Tarhiel, That means you missed two story-related secrets...

@Gerberox, Yes, it was mentioned twice...

Hi @Tarhiel, Thank you for taking the time to reply in such detail. I'll gladly answer the questions you've raised. You said you found 3 out of 5 secrets. May I ask which ones you found? Thank you again for your kind words. We worked very hard on the readables in order to make them engaging for the player.

@Spyrano and @JackFarmer, Thank you both for the kind words and rest assured that we are hard at work on part 2. We're really glad to hear that you're looking forward to it @Tarhiel, Thank you for the glowing review, we truly appreciate it. Would you mind answering something for me so that we can gauge our development of the characters? Who did you want to kill in the mission? Did you want to kill them because of their involvement in the darker side of the plot, or do you usually enjoy killing characters in-game? It's important for us to create strong emotions in the player about certain characters whose stories are going to evolve along with the main plot.

Hello @SeriousToni, To which footlocker are you referring? Captain Williams? We have not encountered this issue, so a little more info would be helpful. Are you saying the lockpicking function does not activate, or that the lockpicking itself is too difficult? Do you hear the usual lockpicking sound and see the small latch moving?

Hello @vozka, Thank you for your feedback and the kind support. We appreciate the compliments Regarding your other comment....

Hi @MrMunkeepants, Glad you enjoyed the mission. Regarding the other entrance... The coal shortage in Bridgeport is a major plot point of the planned Hare in the Snare series, so the short answer is yes, there is much more to come.

Hello @MrMunkeepants (lol), Here you go...

Hi @Xolvix, I took the screenshots on my home PC, which is not new hardware. This FM is absolutely playable and was tested on various configurations (including an old laptop) during the beta phase. You might experience some frame drops here and there in the outdoor areas, but that's not unusual in any game. My recommendation would be to try it out and see what settings work best for you. My personal shadow settings for the screenshots were as follows: Shadows Implementation: Stencil Soft Shadow Quality: High Shadow Softness: Low (slider almost all the way to the left)

A really nice compliment. Thank you very much, @Silverflame3 Part 2 is already underway, and both the characters you mention are an important part of it

Hi @Bienie, Thank you for the great feedback. We think alike in terms of tight, detailed FM's so I'm glad you enjoyed it. The small oversights like clipping models and scaled textures are something we might look at in time. Regarding your other comments: Yes, Hales does not speak in the mission. The standard female voices are far too silly for someone like Hales, and in the absence of a female voice actor for TDM we chose to make her the strong silent type. Hales is all business, no nonsense. Having her ignore greetings made by the other staff etc. fits well with her character. Thanks again for playing @kin, thank you kindly. We're glad to hear that. @datiswous, not quite sure where that "purse" is, but I can see from the screenshot that it is not a coin purse. It looks to be one of those tobacco pouches, possibly? And if you get stuck trying to find a way into the manor, see the spoiler about it above (there are 2 ways in).

Got it, thank you

@OrbWeaverGetting the following error when installing your .ase export script (the other two import scripts installed okay). This is in Blender v2.80 and using the correct version (for 2.80) from the page you linked...

It was this one: https://github.com/DarklightGames/io_export_ase But I am so switching to yours from now on!

Tadaa! Thank you @peter_spy and everyone else who helped ( @HMart) This is from peter_spy's test:

Understood, and thank you again. So, @peter_spysolved the problem in the interim. It was a few bad lines in the .ase (the programmer that wrote the plugin for Blender included things like "who cares" in his definitions, lol) but we have now got it all to work. I had already ensured the model was triangulated and exported with correct UV's.

Okay, thank you. Sorry, I have no experience with DR. I suspect it's an issue that occurs when converting the fbx to either an ase or a lwo. We've now tried it with a lwo converted from the fbx in Lightwave, and as a ase converted from the fbx in Blender. It looks great in the editor, but then never runs in-game. The textures work (@peter_spy tried them on a different mesh), it's just the model. Something must be getting lost during the conversion from fbx

Got you. Thanks again for the help. Have just decided to use ASE model, rather than .lwo, in order to simplify the whole process.

@OrbWeaver, does the material name in the modeling application need to include the folder path, or just the name itself? (ie. redbrick_with_mortar versus textures/darkmod/stone/brick/redbrick_with_mortar) EDIT: Never mind, I figured it out