Search the Community

I have no ideas actually. If it was caused by interaction itself, then the slowdown should be visible even without shadows. If it was caused by shadows, then it should change when you switch between stencil and shadows, since their code is completely separate. If it was caused by the way inputs are provided, then it should probably work differently with new/old backends. I think without access to this GPU to comment/uncomment all possible chunks of code I won't be able to anything with it. The commit does not have any functional changes, only refactoring, and a big one. It is not something I can simply revert, because without it our progress on shaders side will be slowed down and we'll have many bugs about discrepancy between various modes.

Screenshots from qapitrace, MSAA 2x. MSAA 2x In case it matters, the visible distortion is on frames 1 and 2 as the GL_BACK framebuffer. GL_DEPTH_COMPONENT and GL_STENCIL_INDEX framebuffers look distorted as well. Frame 1 is the first frame to have shaders, glprogs/tonemap.fs and glprogs/tonemap.vs. Frame 2 is the frame I notice on thedarkmod.x64 launch. Frames 0 and 3 GL_BACK framebuffers look ok, but their GL_DEPTH_COMPONENT and GL_STENCIL_INDEX framebuffers look distorted. MSAA off Frame 2 does not have a distorted GL_BACK framebuffer; its GL_DEPTH_COMPONENT and GL_STENCIL_INDEX framebuffers look distorted. Frame 1 GL_BACK framebuffer looks similar to frame 1 when MSAA 2x. (Screenshots MSAA 2x)

I never realised Bill Gates was a member of these forums. Welcome to the community! I hope you enjoy The Dark Mod. Perhaps your Foundation could help pay for the server hosting or fund the development of some new features?

v 0.71 fake spec diffuse light enhancement boosted a bit to be more noticeable added the direct light rimlight boost back in Fake Spec Boost Fake Specs enhance diffuse lighting overall, creating subtle specular shines on things that don't normally have specs, and enhancing stuff that does. When I'm working on them, I'm hyper-focused on them, and notice very subtle amounts. But, regular players are going to be blowing through areas, and won't notice anything that is barely noticeable by me when I'm hyper-focused on them. So, I boosted the amount a bit. The idea isn't for it to be "in your face", but just to add detail that the player might actually notice every now and then as it enhances the scene. Direct Light Rimlight Boost Default TDM shaders have a wonderful effect where the rimlighting in direct light would brighten the more direct line-of-sight the player had with the light source, and the closer the player's eye level was to the surface the light source lit up. When tearing the shaders down and testing each variable to figure out what was doing what, I omitted this, b/c the two parts of it, when tested individually, don't seem like they do much. (one part super-dulls the shine while another part super-brightens). But, going back and looking at default TDM shaders to see what I've missed or did differently, I noticed that when those two var's combine, they create the great rimlight shine boost. So, I added it back in.. but did so by treating rimlight like a two-step light as well. Base rimlight is done, then it's used to create a specular rimlight that gets added into base rimlight.. and then, that all gets added into specular lighting if the surface has a real specular texture map, or diffuse lighting if it doesn't (and shaped by the fake spec map before doing so). So, the nice, bright edge is back on the direct rimlighting... If you're wondering why my rimlighting wraps around more... The normal map intensity has been boosted, making detail pop out more. I don't know I know the normal map adjustment will create more detail to pop out, which means things stick out further and thus get hit by light more. But, other than that, I'm not sure why it wraps more. But, it acts like light bouncing off one pillar onto the backside of the other to extend the rimlight range. I like the effect, so keeping it. glprogs.stages.interaction.071.zip

PLAYERS * Volumetric lights appeared late before the previous beta, so the quality of volumetrics in 2.10 was rather poor, and the dithering pattern was very annoying to look at. The feature received a lot more development, and now adheres to the standards of modern rendering. The dithering pattern is gone, performance should be much better, and now you won't miss volumetrics even if you prefer to play with stencil shadows all the time! (thread) * Thanks to a certain "AI-heavy" mission, the game code has received major optimizations. It is most noticeable in low performance conditions, when game modelling takes a lot of CPU time. Previously the game could easily descend into the "spiral of death" with FPS falling below 5, now it is way harder due to better scheduling of AI thinking. There is a variety of other game code optimizations which make our lives slightly better. * New version includes several optimizations for shadows, mostly stencil shadows. A long-standing inefficiency of stencil shadows with antialiasing is fixed, new tile-based optimization is added for soft stencil shadows (thread), small lights with large meshes work faster due to BVH efforts (thread). On the side of shadow maps, the rules for distributing the resolution budget are changed: small distant lights no longer steal precious bandwidth for themselves. * There are several improvements on gameplay side as well. The core mechanics of blackjacking enemies has received subtle, yet helpful improvements (thread). Now you can grab many close pieces of loot by holding down the frob button, instead of picking up each item individually. There are several improvements to crouching, making it more responsive (thanks to @Daft Mugi). The in-game downloader now supports "sort by release date" ordering. * There were a ton of small bugfixes for issues like: bow stuck after load, wrong strafe-walk sound, crash when saving shortly after the death of an elemental, melee combat crash, issues with leaning onto doors, missing fracture sounds after loading a save, X-ray glitch in the first frame, toggling solidity/visibility, lightgem on game load, etc. MAPPERS * The engine now supports OBJ model format. This format is much more popular than ASE and LWO. The engine loading code is very lightweight: it will use your model exactly is as, and load it very quickly. The OBJ format is preferred for large meshes due for faster loading times. The only possible downside is somewhat larger download size compared to LWO, although not much and not always (thread). * Renderer should deal with large meshes much faster, thanks to BVH optimizations. Recall that idTech4 was made for very low-poly models. When renderer frontend sees a "surface" in a model, it always treats this surface as an atomic piece, doing all computations for all of its vertices and triangles. This is very good for low-poly models, can heavily drag performance down with large meshes, as several recent missions noticed during beta. The BVH data structure breaks every surface into smaller chunks, allowing renderer to quickly cull away whole chunks. This makes a big difference in case of large meshes (e.g. terrain) lit by many small lights (thread). * You no longer have to write frob-highlight stages in materials, since they are added implicitly. The problem with these stages was that were very easy to forget, which resulted in no highlight on frobable items. Also it increased cognitive load and scared mappers away. While writing frobstages is no longer necessary, the old stages work just fine. So mappers can still customize frob-highlighting if they really want to (thread). * It is now legal to override a single decl of core game in your mission. Recall that "decl" means a material, a skin, an entityDef, a particle, etc. Note that overriding a whole file from core game always worked as expected, but overriding a single decl from a file did not work reliably before (despite the common belief that it should). * The major cleaning of shaders resulted in some changes in lighting model. The aim was to make TDM lighting closer to the standard Phong model, and make it more logical in general. The changes should rarely make a big difference, aside from probably stronger specular (thread). * Added error-reporting to the GUI scripting engine. Implementing GUI scripts is very hard, error-prone, and confusing. Aside from surprising differences in Doom 3 GUI behavior compared to e.g. Javascript in DOM, a lot of confusion was caused by total lack of any error handling whatsoever! In the new version, all possible errors should result in easy-to-understand console warnings, so writing correct GUI is much easier. Also, we fixed a few features, and added a few new ones to the GUI engine (thread). * dmap command received minor improvements. Yet another big rewrite happened for T-junctions fixing code, since it took tremendous amount of time on one mission. Also a few precision improvements were made. * Other small fixes and additions: added script functions getAnimRate / setAnimRate for tweaking animations added script function setObjectiveNotification for silent objective change added script function getCurInvItemCount for interaction with inventory added script variable "AI_ENEMY_TACTILE" to the base AI scriptobject, which is true whenever the AI is in tactile range of an enemy added spawnarg absence_alert_increase for loot items as a proper substitute for absence_alert, giving control over how much an AI gets alerted if that piece goes missing added spawnargs allow_idle_anims / allow_random_headturning for customization during a running mission, useful i.e. for cutscenes AIs notice broken fracture entities trigger_multiple now works on stationary AIs almost doubled tracemodel limits, raising the restrictive limits for making collision meshes for moveable items door movers can now call "used_action_script" whenever something like a key, lockpick or other item is used on them, if they have the spawnarg "call_used_action_script" "1". ASSETS * Many new assets from capable creators in our community have been incorporated into the core assets. These include: Loot assets: Detailed coins and ingots with accompanying lore. Link Ancient loot items suitable for museums, collectors and ancient sites, first seen in the Volta series. A tiling treasure hoard texture for those with unimagineable wealth. 6 detailed book skins including 3 that are lootable, a first for TDM. Link Security assets Highly detailed standing and wall safes - with or without an accompanying combination lock. Link The combination "safe lock" is now part of core assets and can be operated by either scrolling or frobbing. Mappers no longer need to track down this asset and include it with their FM files as a custom asset. Wall-mounted locks in the style of those commonly found in the original Thief games. Camgoyle sentry, a magical stone guardian based on the security camera shooting magical projectiles at the player, first seen in Written in Stone. The prefab also includes a power source pedestal. Link Fully useable audiograph for playing recorded sounds, first seen in the Accountant and Shadow of Northdale missions. A new full-featured scriptobject makes them easy to implement and control via spawnargs. Wiki Furniture assets Posh upholstered armchairs and sofas for the wealthiest nobles. Link A new high-detail grandfather clock with a working scriptobject and a mantle clock. Link A gothic-style cabinet. Link Office assets Including bundled stacks of paper, blueprints, a letter, crumpled paper, waste bins, an end table and an ornate table. Nautical assets Full-scale modular ship prefabs with interiors, allowing anyone to assemble a ship for a nautical mission in a matter of seconds. 1 merchant galleon and 2 smaller sailing ships are available. Link Link Link A large galleon ship wreck in 2 pieces for those sailors who have met an unfortunate end. Decorative assets An impressive multi-tiered wall fountain, first seen in the mansion in Noble Affairs. A new pair of marble lion statues. Link A standing stone menir with carved symbols on it, ideal for pagan missions. Link Stone pedestal with purple cloth for presenting valuable items. Textures High-resolution cobblestone textures for detailing the streets of TDM. Link Starry wallpaper. Lamps A set of 6 bronze vintage lamps has been added for particulary posh establishments. Link Thief-style charge post streetlamp. A new open-top carriage, the barouche. Link Miscellaneous other models, including: wall planter, 7 small "foliage" herbs, 2 mine carts, 6 shop signs, equippable feather duster and 5 decor plates * We fixed all loading warnings on all existing assets. This became possible after creating an automatic map generator which forces the engine to load all assets from every group. All the references to missing files are fixed too, which means a variety of assets have become available: Old noblewoman skin, plain mage robes skin, moor helmet, electrical arcs, stone window decals (5178), yellow banner skin (5563), wine barrel (Link), grass particles (5689), lampion lights and more graffiti decals. PROGRAMMING Under the hood, we updated third-party libraries, and moved to Visual Studio 2022. The "Debug With Inlines" configuration was split into "Debug Editable" (with hot-reload support) and "Debug Fast" (fastest debuggable). Marking the final step in transition to tdm_installer, the old tdm_update program is finally removed, with TDM packaging code extracted to standalone program.

Is there a way to tell the light sources apart? I was looking over the default TDM shaders again (now that I have a better understanding of what's doing what), and there's a variable called "R2f" in interaction.common.fs that shapes light to make it seem like lamps cast more light downwards than upwards (b/c their glass / metal hoods block some light). But, it looks odd on torches, candles, sconces, etc that would shoot more light upwards and less down due to their implement blocking light downwards. I can use modify the R2f function to make it shoot upwards or downwards.. that was easy enough. But, if I can't build logic into the shader to differentiate light sources, I don't know which should get upwards & which should get downwards.... Here's some picks as example from Coercion... A lamp looks better with light shaped downwards... ... not upwards ... But, a candle looks better with light shaped upwards... ... not downwards ... However, without being able to tell the light sources apart, the shader can't tell how to shape the light to benefit. Original shaders used R2f as-is, and it blended well enough I guess to not be noticeable. But, I'd really like to leverage it for nicer lighting. Do light objects have some flag that could get piped through as a uniform to the shaders? (edit) I should also mention... fireplaces look better without any R2f shaping. So, an ideal variable would be able to tell me if light should get shaped up, down, or not at all. Is there something like that?

DarkRadiant 2.11.0 is ready for download. Next to bug fixes and GUI improvements (also to the recently added TDM Game Connection plugin) this build enables users to manage their favourite resources like materials, entities, sound shaders. The search function of resource trees has been improved too. It's recommended to prefer this version over any previous release. See the pre-release testing thread for a few feature highlights. Windows and Mac Downloads are available on Github: https://github.com/codereader/DarkRadiant/releases/tag/2.11.0 and of course linked from the website https://www.darkradiant.net Thanks go out to all who helped testing this release! Please report any bugs or feature requests here in these forums, following these guidelines: Bugs (including steps for reproduction) can go directly on the tracker. When unsure about a bug/issue, feel free to ask. If you run into a crash, please record a crashdump: Crashdump Instructions Feature requests should be suggested (and possibly discussed) here in these forums before they may be added to the tracker. Changes since 2.10.0 Feature: Managing favorite resources like entities, textures and sound shaders Feature: Extended/improved the search feature of resource browsers Feature: List model definitions in Model Chooser Feature: Initial GUI improvements to game connection plugin Fixed: Collapsing a brush while undoing cannot be undone Fixed: Skin Chooser starts with expanded All Skins root folder Fixed: Projected lights don't rotate around their origin anymore Fixed: Default scale & natural function producing stretched results Fixed: Script dialogs don't scale when window is resized Fixed: Material parser doesn't recognise materials with no whitespace between name and block Fixed: Treeview search box can overlap with the search result Improved: Prefab Chooser preview has better initial view origin and angles Improved: Imported prefabs are now created at the cursor Improved: Added option for "ai_see" spawnarg to Light Inspector The list of changes can be found on the our bugtracker changelog. Have fun mapping!

The problem with a "theme" system (I think) is that it's forcing the assets into categories they may not fit well into or that don't make sense; or I mean it's forcing the mapper to think in terms of discrete "categories" at all, when that may not be most effective. Whereas a tagging system doesn't impose any "system"... Tags are completely open-ended, and could be at any level of scale or heirarchy -- you could have: bathroom-furniture, made-of-wood, Victorian, X-author's set, good for triggers, items for a bookshelf, architectural, magic, etc, etc... as tags, but not all of those categories make sense as discrete themes with other co-themes at the same level. I guess this is a longwinded say tagging more intuitively lets you target what you want without imposing a structure you have to wedge it into ... just a totally open field of tags from any walk of life. Edit: This is not to say tags should be arbitrarily specific. There should be tags of general categories too of course; even these will be the backbone of the system. But the whole point is tagging allows multiple layers, so you can use the general category tags to start your search, then ween it down with increasingly specific tag sets, whatever is best for the asset set. Some asset sets, or especially combinations, will categorize differently than others, and tagging is ok with that. Edit2: The image I have in my mind anyway is like a photo-collection tagged collection. There's an opening page with a tag cloud with the most common basic tags (general category) the largest in size and minor ones smaller, which you click on and then you get a browser with that set of textures. Then on the left hand bar will be all the tag-combinations within that set (other tags textures in the set are carrying; then in parentheses maybe the number of AND-textures it'd filter down to / OR-new textures they'd bring in), the major tags again larger or highlighted somehow, which if you click one of those new tags, it'd filter the browser to show the AND set. And maybe there's also an option so you could have an OR set and get both (or even select a new OR set from the full tag cloud), which adds new textures into the browser window, and also new sets of tags in the left-bar (the new tags carried by one or more textures in the new set). Also there's a place you could back out of a tag to cut that subset out. So you could open up & winnow down the set as you desire. It ends up a kind of way to browse through the whole collection by navigating through tag AND/OR combinations. Also there's a search bar where you could type in a tag at any time also.

Now I'll admit: I could word things I bring up in a less hasty or panicked matter. I'll admit, I get anxious when I read about the various terrible things reality serves up like a heaping platter of "nope" almost daily. I'm a bit coarse in my language. But one of the things that attracted me to this forum is that not only does it focus on The Dark Mod, which is inspired by the original Thief Trilogy, which I adored growing up but could never get because I was too young at the time, and also because Springheel is rather pro-free-speech, something many forums don't allow or severely limit nowadays in fear of being "CANCELLED". I'll admit I used to be far left, and pro-cancelling whatever offended me. But over the years my literally autistic self matured (mostly) and learned that screeching at people to shut up because you don't like their opinion on how to stop legitimately bad things in the world when ssometimes, freedom does, indeed, need to be defended with force. And, as such, I gradually became more center left. I still consider myself a liberal in the classic sense, a strong supporter of secularism, and a violent opposed of authoritarianism and theocracy and the normalization of ties with theocracies and authoritarian states. I'm very thankful that Springheel allows for his platform to allow us to discuss and theorize about the news of the world, withoutbeing moderated by ban-happy mods. So, when you come here and start acting shifty and saying basically either I go and the forums start shutting up about what you don't like, or else you, as a Fan Mission creator (something I wish I could do but for multiple reasons can't) will leave the forums, especially when you could just ignore any threads I start, makes me dislike you as being a childish, weaselly suckup who takes advantage of The Dark Mod's low amount of developers to try and unspokenly blackmail the forums into censoring itself when you could just not participate in my threads.

I will update this list as we go, re-arranging info based on severity - Ongoing privacy concerns The trade-offs between privacy and features is not a simple black-and-white decision, even Windows 8 has an “Advertising ID” that follows you around. Ars Technica revealed that, even with all of the Win10 security settings on Off, Win10 still sends some data to the Micro$oft Mothership. The simple fact is that Microsoft hasn’t told us what data it’s collecting. With the release of Windows 10, Micro$oft have stepped up there 'illegal' data capture of private user data - http://forums.thedarkmod.com/topic/17379-microoft-data-slurp-now-not-just-limited-to-win10/?hl=windows M$ is now via the latest update, monitoring how long your Win10 session's are and how long you use various apps - http://betanews.com/2016/01/04/why-is-microsoft-monitoring-how-long-you-use-windows-10. At release ALL Win10 (home-to-enterprise) users could not disable telemetry, but as of the latest update now enterprise user's only now have that option - http://www.zdnet.com/article/windows-10-telemetry-time-for-level-playing-field/ But it seems some enterprising user has created a tool for home/pro users - http://winaero.com/blog/how-to-disable-telemetry-and-data-collection-in-windows-10/. But the article points out that tere is some telemetry being sent back to M$ in Win7/8 - http://forums.thedarkmod.com/topic/17379-microoft-data-slurp-now-not-just-limited-to-win10/?hl=windows Another renamed service that needs to be disabled - http://www.forbes.com/sites/gordonkelly/2015/11/24/windows-10-automatic-spying-begins-again/ Another example of fresh install, on a PC that wasn't used for 8hrs - http://betanews.com/2016/02/06/windows-10-phones-home-a-lot-even-with-all-reporting-and-telemetry-disabled/ More and more tools are coming out for Win 10 to try and block all or most of the telemetry traffic, here one I have come across - DisableWinTracking Advertising it wasn't in at launch but there are reports of 'recommended' apps appearing in the start menu, WTF! -http://www.digitaltrends.com/computing/windows-10-start-menu-advert/ Stability and Compatibility I tested the retail version, its IMHO its still not stable enough to considered a daily OS. I tested on release and wasn't impressed. I found if I enabled (fairly modest) whitelist outbound blocking on my internet router, Win10's internet responsiveness would fall through the floor. All browsers would takes ages to resolve sites and the OS itself would actually become lumpy/laggy. Broken Video drivers, its so widespread that even a few on here have been affected - http://forums.thedarkmod.com/topic/17665-windows-10-why-you-shouldnt-upgrade/?p=384905 The Graphical user interface M$ white-washing of the interface in Win8 and office 2013 and have refused to learn from user feedback. Forced updates Not being able to control what gets installed on "MY PC", is a massive NO! NO! Patching remains Windows 10’s Achilles’ heel, all Windows 10 Home machines, and Windows 10 Pro machines that aren’t hiding behind an update server (such as WSUS or WUB) will get all patches applied according to Microsoft’s time scale. All three of the first Cumulative Update patches have had problems with reboot cycles. KB3081424 on Aug. 5, KB3081436 on Aug. 12, and KB3081438 on Aug. 14 all crashed a bunch of Windows 10 systems. The installer stops mid-installation, flashes an error message, rolls back, and reboots. Then you guessed it -- the forced installer kicks in and crashes Windows again. Rinse, lather, repeat. Getting out of the mess involves editing the registry. We haven’t yet seen how Micro$oft will recover from a really bad update, the experience to date with the three Cumulative Updates does not instil confidence. We don’t know if Microsoft will start documenting its patches again. We don’t know if much effort will be directed at fixing and improving the Microsoft-supplied Universal apps. Windows 10 installer takes a look at your system and based on the hardware and software it finds, assigns your request to a bucket of similar upgrade requests. The guys running the upgrade system, prioritize your request based on their assessment of how likely your system is to bomb out on an upgrade. Key apps, such as Mail and Edge, STILL aren’t ready yet Some of Windows 10’s key apps simply half baked. Mail has a nasty habit of putting notifications in the upper-left corner and leaving them hanging forever. There’s no combined Inbox, so if you have multiple accounts you have to jump from Inbox to Inbox. And it crashes hard -- for a lot of people. Edge, the new browser, similarly has all sorts of rough "edges". There are no extensions yet, thus no AdBlocker. Changing the search engine is tortuous, moving tabs onto the desktop and back again doesn’t work and you can’t pin tabs. In short use what ever mail/browser you wrere using on previous OS. Not much in the way of Universal apps Don't believe the marketing bollox about all of those wonderful Universal apps in Windows 10, whether it’s on a desktop, notebook, phone, Raspberry Pi, it ain't happening. The Windows Store is still by and large a wasteland, with crap apps galore. Win10’s Tablet Mode broken First, there’s the menu on the left that tucks away the entries on the left side of the Start menu. It collapses fine, but when it’s collapsed it rarely shows any more tiles than when it’s not collapsed. What’s the point, eh? Universal app windows have that pesky taskbar permanently tacked on the bottom, while the window bar at the top auto-hides. Edge, when running full screen, doesn’t support any of the old Metro IE swipe commands. You can’t swipe through running apps. The apps themselves? The irony is M$ Office on the iPad is better than M$ Office on Windows 10. OneDrive regression This concern applies only if you use OneDrive in Windows 8.1, and if you put a lot of stuff in OneDrive. For those of you using OneDrive in Windows 7 (and Windows 8), there’s no change in behavior with Win10. But if you’re accustomed to seeing all of your OneDrive files in Windows 8.1’s File Explorer, you’ll be in for a bit of a shock. Windows 10 makes you choose which OneDrive folders you want to be able to see in File Explorer. Once you’ve made that choice, the other folders aren’t accessible in File Explorer. The only way to see what files you have in OneDrive is by venturing to the OneDrive website. Missing Media Center and DVD player For those people that run Windows Media Center, its gone in Windows 10 PC. Instead Micro$oft wants you to use/buy an Xbox. Ain’t broke, don’t fix it The old adage comes from experience and it’s as applicable now as it ever was. If you’re using Windows 7/8/8.1, and it’s properly patched up and working for you, and you’ve stopped using Internet Explorer, you really have to consider whether it’s worth the effort to upgrade to Windows 10. Carefully consider whether the warning signs listed here. Still to many questions For example, when you upgrade a “genuine” Win7, Win8 or Win8.1 machine to Win10 and run the upgrade in place, Micro$oft records a hardware ID that says, “this machine has valid license” At that point, you can install either Win7 or Win10 on that machine, and your license will be validated. Its believed that the only version of Win10 that you can disable ALL telemetry and fully control Windows update in, is the enterprise version. Smells like Teen Spirit desperation Microsoft Marketing chief Chris Capossela explained that users who choose Windows 7 do so “at your own risk, at your own peril.” It is particularly myopic to rubbish one of your own products that way. Put simply Capossela is a complete cock, Windows 7 is no less secure than Windows 10 (it will be supported until 2020 and Windows 8.1 2023) and is no less compatible with new hardware and software. Also at the moment Win7 has a bigger market share, so easier work for developers. Micro$oft has bad been caught forcing the upgrade on some users, http://www.theregister.co.uk/2015/10/15/pushy_windows_10/ and http://www.fudzilla.com/news/39479-microsoft-raises-the-upgrade-pressure As this is a very bad and its only getting worse, another link to the forced upgrade/update issue - http://forums.thedarkmod.com/topic/17665-windows-10-why-you-shouldnt-upgrade/?p=385115 Nagware being rolled out the business machine - http://www.theregister.co.uk/2016/01/14/get_windows_10_business_pcs/ Now blocking support for the latest CPU in windows 7/8 - http://www.techpowerup.com/219316/no-enterprise-support-for-older-windows-versions-on-the-latest-processors-microsoft.html More marketing desperation Malware - KB3035583 http://news.softpedia.com/news/microsoft-updates-infamous-get-windows-10-patch-kb3035583-502117.shtml Compatibility issues If you have any old games that use really old forms of DRM or SafeDISC your fresh out of luck - http://www.geek.com/games/windows-10-doesnt-run-games-with-securom-and-safedisc-drm-1631383/ Various apps and games (even The Darkmod) has had issue's running on Windows 10, see - http://forums.thedarkmod.com/topic/17310-windows-10-support-thread/?hl=win10 and http://forums.thedarkmod.com/topic/17551-gamma-broken-in-windows-10/?hl=win10&do=findComment&comment=381800 Upgrade NagwareMicrosoft is still coming up with way to try and force users to upgrade from 7/8/8.1 - if you like me want to block 7 prevent this crap checkout GWX control panel or Never10 16. M$ deliberatly blocking the installation of some applications http://news.softpedia.com/news/Microsoft-Blocks-Classic-Shell-in-Windows-10-Build-9879-465429.shtml 17. Windows 10 installing UNWANTED Windows Store apps without user consent https://www.ghacks.net/2018/07/02/windows-10-installing-unwanted-store-apps/

DarkRadiant 3.0.0 is ready for download. It took a while, but DarkRadiant 3.0.0 is finally available. Most of the time has been spent on improving DarkRadiant's renderer, which now features shadow mapping support of up to 6 lights. It's still not matching the engine's output (especially in terms of performance), but it should be faster and much more helpful than it was before. The effort that has been put into the renderer rewrite plus the bigger changes in the previous few releases make the jump to the next major version feel more than justified. Besides of that, a lot of non-renderer issues have been resolved in this release too, next to some fine usability improvements. For more things that have changed or fixed, see the list below. Windows and Mac Downloads are available on Github: https://github.com/codereader/DarkRadiant/releases/tag/3.0.0 and of course linked from the website https://www.darkradiant.net Thanks go out to all who helped testing this release! And I'll gladly repeat myself, by thanking all the awesome people who keep using DarkRadiant to create Fan Missions - they are the main reason for me to keep going. Please report any bugs or feature requests here in these forums, following these guidelines: Bugs (including steps for reproduction) can go directly on the tracker. When unsure about a bug/issue, feel free to ask. If you run into a crash, please record a crashdump: Crashdump Instructions Feature requests should be suggested (and possibly discussed) here in these forums before they may be added to the tracker. Changes since 2.14.0 Feature: Realtime shadow mode Feature: Allow way to hide some entities in Create Entity list Feature: MD5 Animation Viewer: show current frame & total frames Feature: MD5 Animation Viewer: jump to frame Feature: DarkRadiant warns about missing .darkradiant file on load Feature: Ability to center 3D camera on selected entity Feature: Cut functionality to complement copy and paste Feature: Save user settings by application version Fixed: Free Rotation not working anymore, can only rotate along 3 axes Fixed: DR crash with combination of mouse buttons pressed Fixed: Git Sync Exception: too many redirects or authentication replays Fixed: Missing brushes when opening alphalabs1 from vanilla Doom 3 PK4s Fixed: Selected Skin not showing in ModelSelector Fixed: Reload Defs takes longer every time Fixed: ForceShadows materials are not casting shadows Fixed: Objective GUI doesn't display properly in some places Fixed: Crash on loading certain maps Fixed: Vertex colours do not show on models in lighting mode Fixed: Entity inspector shows inherited spawnargs of previous selection Fixed: DR overwrite order for defs is different from TDM's Fixed: X/Y and Camera View bindings don't save properly Fixed: Material Preview rendering Fixed: "Replace Selection with exported Model" sets classname to "func_static". Fixed: Map -> Edit Package Info (darkmod.txt)... crashes DarkRadiant Fixed: Rotating a func_static result to random stretch textures Fixed: DR crashes when syncing with remote Git repository Fixed: Switching visibility of Github repo from public to private causes crash Fixed: Dockable window layout doesn't save new floating XY views Fixed: "Choose skin..." button on custom model spawnargs shows skins for main model spawnarg Fixed: Entity inspector considers inherited colors black Fixed: ReloadDefs moves def_attached light crystals to entity origin Fixed: Option to filter skins out of search results in the Choose Model dialogue Fixed: .lin files can't be opened if different case than .map name Fixed: Model chooser radio box selection issue Fixed: Changing multiple lights between omni/projected resets colours to black Improvement: Allow absolute paths for snapshots Improvement: Light diamonds and Speaker radii are transparent Improvement: Unify Declaration Parsers Improvement: Add "Create Particle" to right-click orthoview drop-down menu Improvement: Revisit Interaction Shader to get closer to the TDM looks Improvement: Entity inspector should recognise spawnargs beginning with "sprS_" as def spawnargs Improvement: UI for worldspawn-to-entity conversion Improvement: classname field should always be read-only, to force use of the "Choose entity class" button Coding: Update solution and build dependencies to Visual Studio 2022 The list of changes can be found on the our bugtracker changelog. Have fun mapping!

DarkRadiant 3.1.0 is ready for download. What's new: The Texture Tool got its Free Scale operator now, allowing you to fit the texture with the mouse instead of having to type in the percentages. A lot of work went into the Declaration handling (EntityDef, Skins, Materials, Particles, etc.), which is now much more robust and more conformant to how the game is doing things (at least until TDM 2.10). The Material Editor got a plethora of issues resolved Improved the Model Export dialog and options For more things that have changed or fixed, see the list below. Windows and Mac Downloads are available on Github: https://github.com/codereader/DarkRadiant/releases/tag/3.1.0 and of course linked from the website https://www.darkradiant.net Thanks go out to all who helped testing this release! And I'll gladly repeat myself, by thanking all the awesome people who keep using DarkRadiant to create Fan Missions - they are the main reason for me to keep going. Please report any bugs or feature requests here in these forums, following these guidelines: Bugs (including steps for reproduction) can go directly on the tracker. When unsure about a bug/issue, feel free to ask. If you run into a crash, please record a crashdump: Crashdump Instructions Feature requests should be suggested (and possibly discussed) here in these forums before they may be added to the tracker. Changes since 3.0.0 Feature: DR doesn't consider wildcards in skins Feature: Reload Images eature: Texture Tool free scale Feature: Add "Show Definition" to all ResourceTreeView instances Fixed: "Reload Defs" doesn't remove entities that have been commented out Fixed: 'Reload Sounds' doesn't load new FM sound shader definitions Fixed: Reload Defs is not sufficient for reloading modelDefs Fixed: Models are reset to origin after reloadDecls Fixed: Skin Chooser doesn't preselect non-matching skins Fixed: Moving speakers deletes distance spawnargs if they're the same as in shader Fixed: Unable to select func_emitter with particle attached Fixed: Particle Editor Preview lacks vertex colours in lighting mode Fixed: Particle effects still visible when hidden via layers or filter Fixed: Entities referring to modelDefs should use the "idle" pose where possible Fixed: DR does not parse materials in def files Fixed: Modifier Hint Popup can crash when hitting Ctrl/Alt/Shift keys during shutdown Fixed: Insignificant digits displayed in Surface Inspector shift/scale/rotate values Improvement: Skin Chooser: show in which .skin file the skin is defined Improvement: Declaration Block Parsing overhauled Improvement: Python Interface for IDeclarationManagerImprovement: leave player start entity selected after placemen Improvement: Let Map Info show materials used by models Improvement: Renaming Declarations causes problems when saving it later Improvement: Light Texture Preview should display editor images if present Improvement: Remove comments about particle generator in .prt files Material Editor: New Material is locked if the default unnamed name is already in use Material Editor: allow to delete materials Material Editor: image browser's "cancel" button rewrites the material source text Material Editor: does not save manual edits to source text Material Editor: should show .mtr the material is defined in Material Editor: after "Reload Images", image previews are only updated when selecting a different material Material Editor: suboptimal preview for cubeMap materials Material Editor: preview object doesn't have smooth shading Material Editor: preview doesn't take "scale" into account in Textured Mode Material Editor: blend add stages are rendered separately in preview in lighting mode Material Editor: test frob highlight button not working Material Editor: doesn't remember settings from previous session Material Editor: image thumbnails use "scale" keyword from previously selected material Material Editor: frob highlight stage not updated correctly when changing diffusemap Material Editor: using Escape to close ignores unsaved changes Material Editor: Global Settings should be preselected Material Editor: some declaration text is lost while editing#6047: Material Editor: clicking "cancel" when selecting a light classname clears the classname field Material Editor: new materials always sorted last Material Editor: filter for image browser Material Editor: can't unlock editing on materials in "Other Materials" folder Material Editor: tries to save materials in DarkRadiant folder if no FM is installed Material Editor: allow to change preview backgroun Material Editor: preview renders shadows for noshadows materials 'Export selected as Collision Model' doesn't auto-create path folder and throws error Model exporter: manually enter export origin Model exporter: export origin choice should use a radio button Model exporter: only 1 entity's model is reloaded Model exporter: "Use entity origin as export origin" still uses map origin Model exporter: rename "Center Objects around Origin" The list of changes can be found on the our bugtracker changelog. Have fun mapping!

Beyond trying older versions like 2.06 or 2.05, I will request that you try the latest Dev Build: I believe that some shaders have been restructured to remove requirements around bindless textures and AZDO behaviors since 2.10

Hello all. Since I'm new to these forums, first a little intro. I've been engrossed in DM editing for about a month now and thanks to the excellent tutorials find it fairly smooth sailing, tho' at times mindbendingly complicated. I've done Doom and Q2 editing in the past so have a bit of related experience and the The A-Z beginners guide was perfect for the job. I've never done Thief editing but have always loved the game - in fact I was replaying the original T2 for the nth time when I came across the Dark Mod. Now my little problem. I've been copy/pasting scrips found in tutorials and fms to create new materials, learning higgledy piggledy about the effects of changing some variables. I've now gotten some projected lights shaders to work so can start experimenting with that, too. However, tho' my shaders show up in Dark Radiant under my_fm folder and I can apply them, after dmapping Dark Mod will then hang when I press 'attack' to start the mission. After I rename lights.mtr to e.g. lights.bak so Dark Mod can't find it the problem vanishes, Dark Mod starts up and my projected shader is working just fine. Danged if I can figure out what I'm doing wrong! Here's my setup. I have everything in my_fm folder immediately under Doom3, set up as A-Z directs me. I have lights.mtr in the materials subfolder. An example definition is: lights/my_fm/textures/lights/win31_l { qer_editorimage textures/my_fm/lights/win31_l_ed lightFalloffImage makeintensity( lights/spot01) { forcehighquality map textures/my_fm/lights/win31_l colored zeroClamp } } "win31_l" isn't defined elsewhere, in some other materials.mtr Thanks for any help canopus

Hmm... another build fail In file included from /home/thebigh/Games/DarkRadiant/radiantcore/shaders/TableDefinition.cpp:1: /home/thebigh/Games/DarkRadiant/radiantcore/shaders/TableDefinition.h:15:1: error: expected class-name before ‘{’ token 15 | { | ^ make[2]: *** [radiantcore/CMakeFiles/radiantcore.dir/build.make:3469: radiantcore/CMakeFiles/radiantcore.dir/shaders/TableDefinition.cpp.o] Error 1 make[1]: *** [CMakeFiles/Makefile2:838: radiantcore/CMakeFiles/radiantcore.dir/all] Error 2 make: *** [Makefile:130: all] Error 2

v 0.52 move few more light calc's to vertex-side brought "fake spec map" back, but using it to modify spec dot before adding spec dot to light dot (b/c both mul by diffuse texture then ) ~~~~~~~~~~~~~~ The u_cubic branch light attenuation calculations in ambient.fs & common.fs are pure math until they run into texture pulls that have to get done fragment-side. So, moved their calc's over to vertex-side, passing result from vs to fs as var_CubicAttenuation. Non-cubic light falloff & projection are texture pulls that have to occur fragment-side, so they stay where they are. Also moved the specular map check (IE: if params.specularColor.rgb is not pure black) over to vertex-side after testing to see if it's set by the time it hits vertex shader. It is, so can perform the test there, and create a basic var to pass to fs shaders instead of having to do the test over and over for each pixel. Minor changes. Just offloads processing of these from per-pixel to per-vertex. ~~~~~~~~~~~~~~~ Played a mission or two using spec dot added to light dot w/o fake spec map, and it was annoying. Without some kind of "noise" to modify the specular shine on surfaces, the shine is constant and looks awkward on some things. So, brought back the fake spec map if the texture doesn't have a real spec map. But, this time just multiplying the spec dot float by a single channel of the fake spec map (since fake spec map is grayscale anyways), and then adding spec dot to light dot before mul'ing that by diffuse texture. Sort of splitting the difference, basically. ~~~~~~~~~~~~~~ I'm getting weird artifacts on certain textures, still. I thought it was something I did. So, I loaded all the original TDM 2.09 shaders back in, and double-checked.. still getting them... (pic below has the interaction.common.fs non-cubic branch "totalColor" x10 to make it easier to see.) The things clear-up as I move towards things... I piped variables through, and it seems to be the normal map... pic below has RawN piped straight through.... Again, the artifacts clear up when I move closer to stuff... It only impacts some textures. Not sure what's up. Again, this is using the 2.09 original shaders. Feels like a mip-map thing? Like the mip-map levels aren't interpolating well? Maybe it's a driver issue on my end (I'm running TDM on an Intel integrated HD 4600, and Intel doesn't exactly crank out updated drivers for their integrated chips very often). I don't know. glprogs.stages.interaction.052.zip

The idea came from a suggestion a friend made this morning. Where you have two 'leafs' (locations, zones, rooms, etc) each with thier own info_location speaker (IL) separated by a info_location_separator (ILS). Leaf 1 is play 'sound A' and leaf 2 is playing 'sound B' but the problem is there is no sound overlap. So my friends idea was to get the ILS to play both Sound A & B, and the mapper would set a distance of say 1-3 meters. And the ILS would only play both sounds when the Vizportal its sitting in/on is open. I tried to simulate the effect I want by placing 2x speakers in the VP location, but for some reason the info_location speakers in 1.08 don't loop reliably.

I did a few fixes in experimental (and probably dead) shaders which generated nontrivial warnings. All the remaining warnings fall into the same category: WARNING:Validation for program ambientInteraction failed: Validation Failed: Sampler error: Samplers of different types use the same texture image unit. - or - A sampler's texture unit is out of range (greater than max allowed or negative). I recall some stuff like that discussed: basically, OpenGL requires to bind correct textures in order to link shader (weird). Not sure I want to fix that. No ideas why new backend does not work though.

You can try my alternative footstep sounds package which addressed the things you described together with a lot of other footstep sounds both for player and AI if you want to. https://forums.thedarkmod.com/index.php?/topic/17631-new-footstep-sounds/

Mods can this moved again? @Acolytesix- can you make sure you post in the beta thread instead of this one please (this one is public, the beta thread is only for logged-in forum members): https://forums.thedarkmod.com/index.php?/topic/21822-beta-testing-high-expectations/

Changelog of 2.10 development: dev16202-9175 * Major changes in security camera (5528, 4731, Wiki). * Entity limit removed raised to 64K (5439, announcement). * Added secrets tracking system for mappers to use (5549, Wiki). * Integrated Sotha's "automaton" AI from Ulysses into core assets. * Menu: improved the main page and the "new game" page to make it easier for new players. * Menu: ask for confirmation on game restart, fixed menu music setting. * Menu: show checkboxes near objectives after mission is failed (5049). * Fixed rare crash in script-generated frobs (5542). * Added idPlayer::GetObjectiveVisible script event (5543). * Fixed rare collision bug causing lags (5439, r9157). * Debug visualization no longer blocks SMP performance improvements (5468). * Fixed script-generated game saves by disabling screenshot due to SMP. * Added missing frob highlight to plaster materials (4487). * Removed missing material reference in skin "wench/purple_bodice". * Minor fixes to mirroring: puddle, bc_teatray. Known problems: Volta 1, Volta 2, and Snowed Inn don't start due to broken menu. dev16215-9224 * More work on security camera (5528, Wiki) --- not finished yet. * Massive changes in dmap to make it faster (5562, 5488, announcement). * Fixed vertices merging in dmap which could cause sparklies (5486). * OpenAL (sound) upgraded to 1.21.1, fixing bsinc resampler (5564). * Added first implementation of tooltips in settings menu (2626). dev16225-9284 * Map loading optimizations: texture storage, parallel image loading, models loading (5591). * Fixed map not starting after prior error + removed 5 seconds delay at the end of loading (5118). * Removed mandatory snapping from dmap, fixing thin objects like ropes (5486). * Improved precision of windings in dmap compilation (5580). * SIMD code cleanup: enabled AVX on Linux, disabled denormals (4550). * Dropped visportals are now further classified as "leaky" and generic ones (5353, wiki). * Fixed creation of script threads with object method call (4713). * Added cvar s_alReverbGain to tone down EFX reverb (5587). * r_materialOverride fixed with Frontend Acceleration. * Fixed when player is in the void with "r_useLightAreaCulling 0". * Minor fixes in menu tooltips. * Fixed GL debug groups on AMD (5280). * Changes in FPS counter, which make displayed value more stable when com_showFpsAvg is large. dev16238-9330 * Frob highlight replaced with frob outline (5427) --- not finished yet. * Linux platform-specific code now uses GLFW for window, GL-init and input handling (5510, 5293, testing). * Windows build can change desktop resolution once again; also made "borderless" mode default (5510). * New dmap diagnostics for location separators and location entities (5354). * Dmap leak pointfiles are much shorter now (5592). * FFmpeg video formats further restricted to mp4+h264+aac and roq (4845, announcement). * Fixed occasional crash at the end of RunScript AI task, happening e.g. in WS3 mission (5538). * Debug cvars r_lockSurfaces and r_maxTri improved. * Upgraded GLFW to 3.3.4. * Added generic hash map in the code; fixed race condition in shader loading during map start (5597). * Refactoring of Clear methods in code (5593). * Added slider in menu for reverb cvar s_alReverbGain (5587). * Menu tooltip improvements. * Experimental: localization system now accepts string placeholders (5261). dev16256-9358 * Implemented new object manipulation and body dragging physics (5599 announcement). * Extracted static geometry into its own VBO in VertexCache, fixing performance regression since 2.07 (5598). * Added weapons to inventory grid (5601). * Fixed in-game mission downloader warning when downloading localization pack (5551). * Fixed in-game mission downloader warning when FM is not available on the chosen mirror (5551). * Disabled bindless textures by default because it does not work on modern AMD GPUs. * Reduced lower limit on texture units to 32, probably fixing the "Too few!" startup error on bad GL drivers. * Allow choosing adaptive VSync in setting menu. * Fullscreen options in menu: borderless goes first + block resolution when borderless is selected. * Interaction table performance optimization when loading from savefile. * Changed number of contacts in physics to 32 everywhere + minor filling optimization (3871). * Save missions.tdminfo immediately after FM download finishes. * Better logging of FM downloads under LC_MAINMENU & LT_INFO (5551). * Saint Lucia FM: adjusted mission loading GUI to display tip for about 20% of loading time (5118). dev16269-9407 * Reimplemented frob-highlighting of surfaces (5427). * Removed TDM version display in the main menu. * Replaced r_glProfiling and r_logSmpTimings with Tracy profiler library. * Better handling of position-independent executable setting on Linux. * Improved third-party libs usage: fixed OpenAL build on GCC10, fixed rebuilding libs with GCC different from 5. dev16325-9462 * PNG image format is now supported in materials, PCX support removed (5665). * Major refactoring of image formats in: SEED, screenshots of all kind. DevIL library removed (5665). * Rough prototype of .srt subtitles in briefing video (2454). * Fixed stack overflow crash if CPU-resident image is defaulted e.g. when not found (5665). * Mission statistics now show number of game loads. * Silenced "missing vertex or index cache" console warning. * Calling "set" in GUI script with not enough arguments now results in Error instead of crash (5323). * Debug cvar r_skipFog expanded to filter out boundaries. * r_immediateRenderingEmulate = 1 by default, probably fixing debug visualization for people using deprecated GL profile. * Fixed GPL header in source code files. dev16330-9508 * Extended support of subtitles to both briefing video and in-game sounds (2454: BEWARE interface will change!) * Support updating the currently installed mission in in-game downloader (5661). * Supported hide_distance for particle emitters and geometry of light entities (5668). * JPG and PNG images are no longer compressed by pk4/zip (they are already compressed by themselves). * Fixed entity arguments broken in event system after entity limit removal (5439). The bug crashed Snowed Inn on startup. * Refactored entity think code, optimized away thinking of frobable entities. * Added con_nowrap cvar: it caps lengthy lines in game console instead of wrapping them to the next line. * Added a ton of trace scopes in game, dmap, and loading (enabled by com_enableTracing 1 and Tracy connection). * Minor fixes: parallelSky, r_showViewEntities, image_preload 0, r_singleModelName. Known problems: GUI is not drawn in-game until paper is frob-highlighted. dev16335-9550 * Added hot-reload support: LOD settings, _color and shaderParms, noshadows, angle, targets, frobmovers + rotate/translate, bound entities (5683). * Fixed error on respawning an AI (5683). * Added con_fontSize cvar, which allows making console font smaller, also enabled mipmapping. * Refactored shaders loading, which fixes SMP-specific crash on AMD drivers (5012). * Non-bound lights are turned off when they are hidden e.g. using LOD (post). * Fixed noshadows_lod_N not working sometimes (5691). * Fixed GUI rendering on parchments --- known problem from previous build. * Fixed color banding in lockpick success/failure highlights. * Changing tdm_lod_bias has immediate effect without restart. * Small fix towards loading RGTC normal maps from DDS. * Removed old broken code for entities binding/unbinding (5414). * Some showPrimitives fixes. * Automation: fixed bug with astronomical timer for game controls (not used anywhere yet). dev16342-9552 * Merged branch with major changes in main menu GUI (5323, thread). Known problems: All the missions from the list do not work as expected in main menu: custom background is missing, empty briefing page is shown, in rare cases even briefing/debriefing video can disappear. This will be properly fixed only when 2.10 is released. Right now you can download fixed pk4 file by direct link from the same page --- fixed version should work as expected. dev16350-9577 * Support "set X on head" spawnarg for attached heads (post). * Fixed lockpicking getting stuck if you go away (5715). * Hopefully fixed random flickering when frob-highlighting objects with stencil shadows enabled. * Fast and deterministic normal maps compression on CPU (5716). * Optimized OGG files loading. * Optimized TGA files loading. * Continued work on X-ray support. * Continued work on subtitles support (2454). * Added new models and prefabs by @Wellingtoncrab. * Added material textures/darkmod/window/wooden_frame01/wooden_frame01_dark. * Probably fixed reloadModels for .lwo files. dev16358-9588 * Fixed crashes in image loading on AMD driver (5591). * Fixed occasional crashes in TGA loading optimization (5716). * Generate mipmaps for non-DDS textures in software, see cvar image_mipmapMode. * Frob outline disabled by default, see r_frobOutline (thread). * Tweaked render order ("sort last") for particle materials. * Continued work on subtitles (2454). * Removed [cleanup] button in mod selection menu (thread). dev16368-9627 (*) * Major changes in frob highlight/outline: translucency, alpha test, shine-through (5427). * Restored geometric frob outline under r_frobOutline 2 (5427, post). * Fixed bug breaking GL core profile, which usually caused black menu on AMD (post). * (WIP) Volumetric light effect. * Renderer's "safe mode" changed to windowed 800 x 600 (post). * Cap volume parameter in sound shader by 1.5 (4627). * Lockpicking sound no longer affected by EFX reverb. * Some changes in time handling, fixed timescale on uncapped FPS (5324, 4698). * Reduced pause on game start from 1.0 to 0.1 seconds (5314). * Minor dmap (aas) acceleration (5562). * Minor optimizations in models / sounds loading. * Don't drop held item after bumping dead/unconscious AIs (3516). * Tweaked render order ("sort last") for particle materials, reverting some. * Some changes in randomization (5763). * Minor fix in game console. * Adjusted stlucia.pk4 to avoid tdm_installer analysis... unsuccessfully. * Changed integration of doctest unit tests. Known problems: some maps broken with "clip model outside world bounds" warning spam. dev16390-9648 * Fixed "clip model outside world bounds" warning spam on some maps (post). * Fixed sparklies on hard geometric frob outline with bloom (5427). * DDS textures can be used in image programs, although they should not (5781). * Fixed spotlights/projected lights illuminating objects outside their frustum (5529). * Continued work on volumetric light shader: LOD, stencil, etc. (5816). * Allow xray shader in GUI overlays, fixed rare crash. * Do not spam warnings when index cache is not ready yet, e.g. during noclip on large map. * Minor fix of game console behavior. * (WIP) Changed frustum of spotlights when near != 0 (5815). * Fixed AlertDuration of security camera (5528). * Fixed normalmaps: flagstones_mossy_01 (5777), flagstones_gravel (5760), ash_001 and ash01_crumb_edge (5784), blocks_large_mildew (5786), ornament_shield_white_eagleandpallets (5803). * Added material for rough_grey_blocks (5789). * Added missing "torn" skins for all paintings. * Commented out additional camera screen materials (5676). beta210-01 (rev 16399-9702) * Projected lights: restored TDM 2.07 behavior, fix lighting outside frustum (5815). * Fixed light frustum precision (4888). * Major changes in volumetric lights (5816). * Continued work on security camera (5528). * X-ray improvements. * Fixed severe slowdown with soft stencil shadows and antialiasing. * Allow lifting ragdolls above ground, unless they have "ground_when_dragged" (5599). * Fixed mirrors getting black under "image_useTexStorage 1" (topic). * Added script events: vecRotate, getCalibratedLightgemValue, setSolid, getEntityFlag. * Take entity orientation account in flinderization offsets. * Removed "emitter_size" spawnarg. * Fixed r_showLights. * Refactor shaders: extracted common code to includes. beta210-02 (rev 16411-9731) * Fixed dbghelp.dll issue which blocked running TDM on fresh Windows 7 (issue). * Fixed rare depth fighting when SSAO is on. * Fixed OpenGL error with shadow maps when no light fallbacks to stencil implementation. * Fixed envshot command (5796). * Restored materials and prefabs for multiple camera GUIs. * X-ray: supported "suppressInSubview" spawnarg on lights (also affects other subviews like mirrors) * Added X-ray related assets: materials, visible/invisible skins. * Added script events: getLocationPoint, pointIsInBounds, getTraceSurfType. * Preserve opacity towards AIs and restore frobability in script event setSolid. * Func_emitters can now be bound without the particle flickering rapidly. * Fixed "condump unwrap". * Added display case models without glass to allow them to have breakable glass. * Added forcescreenaspect + hcenter GUI keywords for aspect-ratio-independent images. * Removed a few subtitles lines which were for testing only. * Internal typeinfo changes. beta210-03 (rev 16421-9771) * Reverted to 2.09 frob-highlight: no outline, use material frob stages. * Added three new frob outline presets by @kingsal and @nbohr1more. * Changed the way volumetric lights are set up (see wiki page). * Volumetric lights respect noshadows and don't affect lightgem. * Added script events: getHealth, setHealth, setSolid,projectDecal; fixed getLocationPoint. * Added script event getEnemy and canSee to security camera. * Add Epifire's flinder models to the security cameras. * Fixed subtitles going sticky on save/load. * Slightly reduced subtitles font size, added semi-transparent black background. * Added subtitles to Saint Lucia mission. * Fixed dmap issue in generating unoptimized collision maps for patch-only entities (5859). * Elemental no longer has 8 legs, wasting time in inverse kinematics. * Some optimizations in frontend: fix disabled optimization, avoid vertex data copy. * Added r_useInteractionTriCulling -1 mode to move some CPU load to GPU. * Fixed lamp cubemap light textures. * Fixed language switches broken by new main menu GUI. * Fixed occasional spam about slow jobs (threshold is now 100 ms instead of 10 ms). * Corrected OpenGL usage of clipping planes in shadow map generation. * Console printing is now threadsafe, which could crash Frontend Acceleration. * Improvements in system console on Windows. * Allow all SIMD code supported by compiler on Elbrus CPU. beta210-04 (rev 16441-9798) * Security camera now supports AI detection, also fixed volumetric lights. * Fixed save/load for volumetric lights, supported scrolling light materials. * Fixed scrolling light textures (5860). * Fixed uncompressed normal maps and backface lighting (5862). * stain01bwet material now works as it always did, no depth fighting (5325). * Skip X-ray rendering when it is already within subview. * Removed parchment from message about secrets (5549). * Fixed and upscaled droppuddle texture (5870). * Extended tooltips in video settings menu. * Fixed randomization of gui::random_value on game load. * A bit more subtitles in Saint Lucia mission. * Fixed 1280 x 960 resolution in 4:3. * Fixed rare graphic bug in some debug tools. * Small optimization in frontend: reuse index array for interaction. beta210-05 (rev 16457-9815) * Fixed bright lines on the boundary of light volume on AMD drivers (5876). * Fixed secret counter increased multiple times on single-count entities (5549). * Security camera: "sweepWaitSoundOffset" spawnarg controls snd_end timing. * Security camera: snd_sparks and snd_death can be used simultaneously. * Security camera: split "seeAI" spawnarg into "seeAI", "seeAnimals", "seeBodies". * Fixed the xray model stuck in place when shouldered. * Improved player GUI for taking damage. * Added spawnarg "animal_patrol_wait" to allow animals that move continuously (post). * Portal sky scissor optimization. * A bit of cleaning in source code conan dependencies (5839). * Fixed hover highlight on Restart Game button in settings menu. * Volumetric lights refactoring. beta210-06 (rev 16472-9845) * Fixed saving/loading of suppressInSubview for X-ray. * Fixed language setting being ignored on restart (post). * Reimplemented rotation in new grabber code, rotating heavy objects is easy now (post). * Fixed weird spots sticking on screen sometimes when bloom is on (post). * Fixed seeAI setting for security camera towards AIs on hostile teams; updated editor descriptions. * Fixed one more bug causing tdm_installer to analyze installation. * image_downsize no longer affects loading screens and other GUIs. * Fixed lighting with "image_useNormalCompression 0". * Added editor description for nodrop spawnarg. * Reorganized mapper tool prefabs, fixed Epifire's wall-mounted security camera prefab. * Removed non-working 16-bit color option from the menu settings. * Improved EFX in New Job mission (5594). * Fixed issue in Saint Lucia mission: all voiceovers being played on mission restart (4828). * Some more corrections to subtitles in Saint Lucia mission. beta210-07 (rev 16474-9850) * Set r_useMultiDrawIndirect to 0, fixing NaN flickering on AMD drivers. * Fixed X-ray combined with Render Scale. beta210-08 (rev16475-9853) * Fixed crash on index cache resize with now default "r_useMultiDrawIndirect 0". Changelog of earlier versions can be found here.

sure - I would only ask that you follow the thread to make sure you don't report stuff that has already been mentioned: https://forums.thedarkmod.com/index.php?/topic/21822-beta-testing-high-expectations/