Leaderboard

Here is another update to the English Stone font's DAT file used for subtitles and some readables: fontImage_24.dat This supercedes the Jan 30th update. As agreed, now all character spacings - as given by xSkip - are preserved (from this file in TDM 2.11). Exception: the Jan 30th repair of garbage metadata for "<" and ">" remains, including xSkip repair. ASCII Characters (lower 128). The earlier Jan 30th post summaries those ASCII characters that needed metadata changes to avoid adjoining stray marks. (The detail report below updates newer reversions and minor revisions.) ANSI Characters (upper 128). An analysis was also made of the status of the Stone 28 pt font's characters in the upper codepoint range of 128-255. This could be of interest if the subtitle system was some day expanded to include European languages, and continues to use the historic codepage method. The analysis also prompted some additional DAT tweaks now. Broadly, implementation of the upper-range characters (standard or TDM-specific, as defined in the TDM wiki's I18N - Character mapping I18N) is incomplete for Stone 24 pt. The status is: 43% (55 chars) Good as is. 9% (12 chars) Good enough after DAT tweak included in this update. 6% (7 chars) Missing and shown as hollow box. 30% (38 chars) Missing accent/diacritic. 7% (9 chars) Otherwise weird. But often suggestive of glyph work started but not completed. In addition, 7 chars within categories (3-5) were "improved", but are still not good. To really solve categories (3-5) requires DSS bitmap surgery (and corresponding DAT adjustments), which is beyond the scope of planned work. DAT tweaks of ANSI characters (like with ASCII) were careful to avoid changes to xSkip. Tweaks can be further grouped by problem solved.... In category (2): - (4 chars) Char is clipped, with stray mark from adjoining character on other side. - (7 chars) Stray mark, without char clipping. As improvements in categories (3-5): - (3 chars) Stray mark, without char clipping - (4 chars) Out of valid range on top edge A categorized itemization about treatment of specific problems and characters, with further details, is here: Information about methods, including new tools, to conduct this analysis and tweaking will be forthcoming, mostly after the 2.12 release.

I agree, it had to happen with the move towards ultra reality . I suspect the comming years will be quite interresting

I think the writing is on the wall. Advanced upscaling will be adopted as widely as possible as the free performance band-aid for the gaming industry. The majority of players will probably run it automatically without even noticing. Recently we've seen rumors of Microsoft working on a Windows upscaler (which may be similar to AMD's RSR in that the game developers don't need to touch it) and Sony may include an NPU in a PlayStation 5 Pro for their own bespoke console-level upscaling solution (not an FSR 3/4, although those can be supported). The irony would be if Nvidia ended up killing the demand for gaming GPUs faster by marketing DLSS so hard, that there's less "need" for new and top-end GPUs. But they won't care because they prefer to chase more lucrative markets like AI, datacenter, automotive. I say "faster" because there is some point in the future when additional hardware can't push the boundaries of graphics, or faster hardware can't be created. We'll see an evolution of Unreal Engine 5's photorealism approach, adoption of 8K resolution, possibly 16K for VR, and a push to the 240-1000 FPS range. Generated frames could be used for a free doubling if not quadrupling of FPS to hit those high numbers, and upscaling tends to work better when your input/target resolution are already very high. For VR specifically, foveated rendering can slash hardware requirements, possibly by 80% or more if the implementation is good enough. On the hardware side, there's still free lunch to be had with a few additional node shrinks. Stacked L2/L3 cache could be extremely beneficial, think the 3D V-Cache version of Infinity Cache (Nvidia has gone with big L2 with Lovelace). We don't see adoption of High Bandwidth Memory in consumer GPUs because it is in such high demand for AI/enterprise products, but there's no technical reason it can't be used. We will see the blossoming of mega APUs this decade.

View > Camera > Next / Previous leak spot

well the fsr3 mod from nukem gave the old 2080 ti a massive boost. i can play it at high with medium raytracing now at 117 fps . there is some minimal ghosting in some scenes with framegen on but overall its very good looking. at 4k i suspect things would look very different fps wise.

Generally speaking, solid + opaque materials like wood or stone will seal, while nonsolid ones like materials meant for dirt decals won't. Some exceptions, for example caulk is a popular solid + invisible sealant, unlike i.e. all the nodraw and nodrawsolids which won't seal. Another thing that helps a lot is to use a large grid size like 8 or 16 units sealing geometry. This way you can more easily align parts and see gaps. Details can be done with smaller brushes or with patches. All of your detail pieces should be entities instead of worldspawn due to compiler reasons. This has the extra benefit that you can use the "All entities" filter to hide entities and only see your sealing worldspawn geometry.

There's also a menu button to move the 3d view to the currently selected leak/lin.

*looks at Shadows of Northdale folder* ... Yeah screw it, what's another 5-10 mb among friends? Especially when the assets look so damn cool!

Are you aware of the pointfile feature? Dmap writes these .lin files into the maps directory. Display them with File->Pointfile and look for red lines that visualize problems like leaks and visportal problems. Which faces of a brush are sealing depends on the material assigned to the face. I don't know exactly which ones seal and which don't.

It very much is. I've been goofing around in DR for a decade, on and off, and about two years ago I said to myself "that's it, I'm gonna actually make a mission for once". (And then about a year ago I started making this one.) So yea, my drive to do this hasn't dwindled, it has only gotten stronger. I've always loved making maps for games, and I still very much do. If I told you, I'd have to kill you. I actually wanted to make that book readable, and have some kind of interesting recipes in there, but I just couldn't think of anything... If I ever think of something, I'll do that.