Search the Community

Here's the DR 2.14.0pre2 build for every interested mapper to test. This release focused on DarkRadiant's texturing abilities, the Texture Tool and some of the Surface Inspector algorithms have been completely rewritten. A new model importer UI has been added with the ability to convert FBX models into a format compatible to the game (it can also convert LWO, ASE and OBJ models). The EntityInspector can now deal with more than one selected entities, showing the shared key values in the list. Copy/Paste Textures across angled faces: Texture Tool Rotate Tool (use "R" hotkey to switch) Surface Inspector Harmonise Scale / Linked Scaling Surface Inspector Normalise EntityInspector Multi-Selection Support For more things that have changed or fixed, see the list below. Download Windows Portable x64: https://drive.google.com/file/d/1-wqcqnlz8KOYpts-ap8x313yVaiQm87l/view?usp=sharing Download Windows Installer x64: https://drive.google.com/file/d/1-pSE-517B7Y-T3-VonNv4zLzUMgr-fXt/view?usp=sharing Linux folks need to compile this stuff from source, instructions for various distributions are on the wiki. If you happen to run into a crash, please record a crashdump: How to record a crashdump Changes since 2.13.0 can be seen on the Bugtracker changelog, here's the summary: #5746: Feature: Texture Tool Improvements #5776: Feature: Texture Tool: Add Manipulation Panel to shift/scale/rotate selection #5613: Feature: Show shared keyvalues when multiple entities are selected #5738: Feature: Texture Browser Filter: match multiple words (using 'AND' logic) #5728: Feature: Skin Chooser shows materials of the model #5774: Feature: Surface Inspector: Add buttons to harmonise Horizontal and Vertical scale values #5771: Feature: Improved pasting textures to angled faces sharing an edge #5753: Feature: XY view zoom is centered at cursor #5748: Feature: Texture Tool: Constrain operations to axes by holding down Shift #5128: Feature: Texture Tools: rotate function #5731: Feature: Texture Tool: UI contrast #5721: Feature: Model Conversion UI #5722: Feature: Add FBX model importer #5712: Feature: add IQM format support into lib/picomodel #5705: Improvement: "Replace Selection with exported Model" preserves spawnargs #5659: Improvement: automatically reload exported models #5745: Improvement: Search function: don't start searching while still typing #5791: Improvement: MediaBrowser toolbar: clear filter text when texture is selected through MMB or Texture Browser #5788: Improvement: Merge "Create player start" and "Move player start" options #5785: Improvement: Patch Texture Rotation should take aspect ratio into account #5733: Improvement: Texture Tool: use aspect ratio of material #5740: Improvement: Step-rotating textures through the Surface Inspector should be using the center as pivot #5775: Improvement: Surface Inspector: Option to change horizontal and vertical scale values proportionally #5633: Improvement: Apply textures to surfaces using "normalized" scaling. #5547: Improvement: Normalise button brings texture coordinates closer to 0,0 #2272: Improvement: Prevent Texture Tool "face jump" on rescaling textures #5735: Improvement: Move modifier hints out of the status bar #5767: Improvement: Flip Texture: Prevent huge face UV coordinate translations #5752: Improvement: Double click on list elements should auto-close dialogs #5749: Improvement: Texture Tool: Select items by clicking the UV space they cover #5750: Improvement: Texture Tool: Grid lines are getting too dense when zooming out a lot #5732: Improvement: Texture Tool: intercept keystrokes for grid resizing & snap to grid #5734: Tweak: Surface Inspector vertical shift / vertical scale arrows #5706: Tweak: Surface Inspector's minimum width is too large #5741: Improvement: Model Exporter: warn if Output Format and extension in File Path don't match #5711: Improvement: Change Quake3 map exporter to write "legacy" brush syntax #5710: Fixed: Q3 Legacy BrushDef parser sometime produce some wrong texture rotation #5687: Fixed: "Replace Selection with exported Model" assigns result to Default layer #5408: Fixed: All scene graphs connect to the same undo system, causing interference #5790: Fixed: Remove Floating Layout #5783: Fixed: EntityInspector allows to set an entity's name to an empty value #5723: Fixed: modelDefs folder starts expanded after changing selection #5736: Fixed: Particle Editor: wireframe does not render #4584: Fixed: Drag-select while in texture tool window gets stuck. #5770: Fixed: Some brushes change shape or disappear when rotated or duplicated #5747: Fixed: Texture Tool: drag operation doesn't capture the mouse #5754: Fixed: Ctrl-S does not work when focus is on inputs #5729: Fixed: Autosave filename unhelpfully overwrites 'save copy as' filename #5725: Fixed: Merge Maps: can't hide changed entities/primitives #5708: Fixed: Merge Maps: can't center orthoview/camera on changed entities #5709: Fixed: Merge Maps UI remains if DR is closed while a merge is in progress #5707: Fixed: Merge Maps: "Details" text doesn't use full width of window #5704: Fixed: Brushes colour schemes not saving #5702: Fixed: Fit Texture fields do not allow values below 1.0 #5713: Fixed: PatchDefExporter: do not write trailing white space after shader name #5717: Fixed: LWO2 Model Exporter doesn't write vertex colours #5588: Coding: Separate UI-related and core module interface headers #5780: Coding: Remove IDialogManager references from Map module #5778: Coding: Solution / Build Dependencies Update Changes since 2.14.0pre1 #5810: Fixed: Objective components not correctly renumbered after removing a component #5801: Fixed: Applying a skin to a model entity no longer works under 2.14pre1 #5813: Fixed: Spawnarg types and tooltips not reliably inherited in entityDefs #5814: Feature: Spawnarg type icon not shown for inherited properties #5808: Fixed: Crash when saving map or prefab without a file extension #5807: Fixed: Texture Tool crashes when creating a new brush #5797: Fixed: "Texture tool" grid cannot decrease under 1 #5799: Fixed: Texture Tool: dragged vertices snap to grid even though it's switched off #5800: Fixed: Sound chooser not pre-selecting the inherited value of snd_* keys of an entity #5794: Fixed: User Guide (Local) doesn't work #5792: XY View zooming behaviour improved (if not fixed) Refresh icons for axis flip buttons Separate SurfaceInspector scale rows from other property rows Restore GL_LINEAR_MIPMAP_LINEAR texture filtering Thanks for testing, as always!

I'd say the Tech Support forums are the correct place for rendering issues like this. The DarkRadiant forums are for development and feedback on DR, while the Newbie DarkRadiant Questions thread in the Editing Guild is for general mapping questions. Regarding the silver platter, if I'm not mistaken it contains a reflective stage in its material, which might be conflicting with your mirror. It's not a very noticeable reflection imo, so could derive a new material without that stage and apply it via a skin as a workaround (if nothing else works).

What I was trying to get at that there is no real difference. The end result is the same. The biggest drawback to the "theme" thing is that to create multiple themes, you have to visit almost everything mutliple times - or make one grand swep through things and assign the into multiple themes - at which point you might just as well "tag" them. For me this is semantic hair splitting, regardless on wether you use: * theme A: contains element a, b,c, d * theme B: contains element a, b,x, y or: * element a: tags A, B * element b: tags A, B * element c: tags A * element d: tags A * element x: tags B * element y: tags B The result from a point of getting the search result is the same, search for A and you get the same "set" in both cases. Just the storage is a bit different laid out. You are storing the same information in both cases, and with the over 10000 "things" we have in TDM (possible 15..20000), you need some sort of central storage and editing, anyway, because there is NO WAY you are gonna sort 2000 material shaders into themes, or tag them manually, and then repeat the same for sounds, particles, skins etc. Edit: Searching for "A" is a bit easier with the themes, because you can just "take" everything in the theme. But thats a storage algorithgm difference, and needs not to be visible to the user. The idea here is that a theme works good if the users wants anything in the theme, but breaks down if you add search modifiers. Like "give me everything from theme A but no sounds, and then add every entity from theme B". At this point the user might as well say "give me everything tagged with A except sounds, and every entity tagged with B" and there is no difference in output. Just that parts and mixing themes makes no so much sense as just saying "give me a list of things that match these tags", which essentialy is. The "theming" thus leads the user to believe they get something different, which they don't.

Also, fllood isn't active on the forums a lot it seems, so maybe another person can give authorisation when @fllood isn't around? Just an idea. I guess I could pm this to fllood. Edit:

Would be interesting to also see a shot of the mission in DR too for mappers to get a better idea of how much there is and how dense (brush, patch and entity counts would be good too). @Baal Have you tried sending a PM to fllood? Simply pinging them with @ only gives them a notification when they log into the forums, while a PM will also get sent to their email.

Looking back at the current poll results, I can't help but feel more and more strongly that if a few knowledgeable enthusiasts produced a more configurable, and more easily configured version with a really idiot's step-by-step guide to setting up, downloading, and installing software, and possibly also how to easily configure a dual boot system that many, many more might take up Linux as their main system and just boot up Windows for some games that won't run under Linux. A step-by-step guide is what I started with the Dark Mod guide on the Wiki - less theory and more do, show, and give examples. I learnt that lesson years ago when I studied a low-level programming book of theory for months before giving up having learned almost nothing but binary, operators, registry operations and so on. Fast forward six months and two simple pages in a monthly computer magazine opened up a whole new world for me with step-by-step examples that a child could follow. It grieves me that there is so much potential wasted.

Hello! I just joined the forums to report an annoying bug. I don't know if it's specific to this map or just a game bug but I have played most of the other missions and this is a first for me. Before i picked up the key to the junkroom i tried to open the door and i got the "needs junkroom key" message on my screen... but that message never went away. I had to complete the mission with that on my screen the entire time, overlaying all the other messages that appear. a reload/restart didnt do anything to solve the problem. A few of the on-screen messages at the beginning didn't make sense to me and were kind of cryptic, like a riddle i didn't get. one of them was something about an alarm? otherwise i liked the mission, pretty challenging and I know i missed some spots. cheers

DarkRadiant 2.13.0 is ready for download. A lot of fixes and improvements made it into this release. Several point files can be selected for display now. DarkRadiant is now capable of comparing maps, both in differential A vs. B comparisons as well as three-way merge scenarios (when both maps share the same ancestor). Windows and Mac Downloads are available on Github: https://github.com/codereader/DarkRadiant/releases/tag/2.13.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.12.0 Feature: Ability to choose from several different pointfiles Feature: Aspect ratio preserving Fit Texture option Feature: ModelSelector: add ability to rescan folders without having to reload all models Feature: Add "Show Material Definition" to ShaderSelector tree views Feature: Paste material-header to surface from clipboard with hotkey. Feature: A way to display editor_usage in the Entity Inspector window Feature: Selection by coords Feature: Three-Way and Differential Map Merge Feature: Map Comparison/Diffing Feature: Git Version Control Integration Plugin Improvement: Show axis when 'R'otating entities Improvement: Improve workflow for adjusting light brightnesses Improvement: Map Loading Performance Improvements Improvement: Refresh entity inspector when reloading defs Improvement: Increase maximum zoom level of 2D views Improvement: "Choose entity..." button for all def_ spawnargs Improvement: CTRL + MMB in orthoview: place camera at height of most recent selection Improvement: Added Documentation for Layer Script Interface Improvement: "Shift textures randomly" shifts all selected faces by the same amount Fixed: Problems with particle preview obstructing the view Fixed: Cannot view or copy from built-in Filters Fixed: Auto-save is slow when animation or particle viewer is playing Fixed: Non uniform light volume scaling not working Fixed: BC5 normal maps cannot be loaded Fixed: Copying a particle in the Particle Editor creates an ___editor list entry which can lead to crashes Fixed: Create Entity window no longer remembers the previous item Fixed: Model exporter: no model is exported if folder path doesn't exist yet Fixed: Non power of 2 textures show up black in Fixed: 'Change game/project' fails to save if a decent-sized .map was loaded Fixed: Reload Defs is messing up the entityDefs Fixed: Crash when using Reloading Defs after placing an Entity Fixed: Entity & Speaker windows don't remember their size Fixed: Restore non-uniform scaling for texture browser. Fixed: Some ASE models do not load Fixed: Prefabs importing miles away Fixed: Path entites rotate 15 degrees, each time when dragged. Fixed: Crash when activating GameConnection Feature "update entities on every change" Fixed: Model previewer not displaying ASE or LWO models Fixed: Crash when selecting an MD5 model in "Create Model..." menu Fixed: Crash when activating the Material Editor in Doom3 game config The list of changes can be found on the our bugtracker changelog. Have fun mapping!

DarkRadiant 2.7.0 has been released, this thread is out of date: Here's the DR 2.7.0pre5 build for motivated mappers to test. It's a maintenance build for the most part, but it contains a few smaller improvements. As usual, a bit of refactoring and improvement has been happening under the hood, but this shouldn't have any negative impact. Especially, I would be interested if installation works, as I've moved forward to Visual Studio 2019 for this build. OrbWeaver has been working on a DarkRadiant user guide which is continuously expanded and available on the website https://www.darkradiant.net/userguide (also accessible through the About > User Guide menu option). Windows Installer x64: https://drive.google.com/open?id=1ePE5oYYBq_2AcoNtQSBFGjXTBWk3fuWe Windows Portable x64: https://drive.google.com/open?id=1hCO5nxhcmm5jQipRPa8lBNrzstfdj-AR Linux folks need to compile this stuff from source, instructions for various distributions are on the wiki. If you happen to run into a crash, please record a crashdump: How to record a crashdump Changes since 2.6.0 can be seen on the Bugtracker changelog, important stuff includes so far: #5071: General: Upgrade VC++ projects to VS2019 #4889: Feature: A method to deprecate models without breaking existing maps #4873: Feature: Game/Project Setup should show recently used custom paths in the mission drop down list #5021: Fixed: DR gets unhandled exception on start up #4792: Fixed: Rotation of x-oriented particles in Particle Editor is different than in-game #5054: Fixed: Highlighted vertices of hidden brushes will move when moving highlighted vertices of visible brushes. #4904: Fixed: Unmaximised DarkRadiant not remembering main window size and location #4966: Fixed: Reload Models option in Create Model dialog window doesn't update the model #4999: Fixed: Problem with satisfying readable objective "when closed" #4859: Fixed: DR thinks an entity name of the form "Cylinder01" is the same as "Cylinder1" #4885: Fixed: Syntax error in "Test for missing targets" script #4880: Fixed: Bad normals produced by .ASE exporter #4876: Fixed: No confirmation dialogue box when exporting combined models #4861: Fixed: Undo/Redo Does Not Restore Light Color #4874: Fixed: Compile error with gcc-7 (and gcc-8) #4841: Fixed: Blend export script fails #4840: Fixed: Mouse Binding settings for Aux1 do not work Changes since 2.7.0pre1 #5078: Fixed: Search feature in TreeView controls seems to be broken #5081: General: Updated Xcode project, DR compiles again in macOS #5077: Fixed: Compilation failed in Ubuntu 19.10 Changes since 2.7.0pre2 #5104: Fixed: Exporting bell_hand.lwo as ASE is producing an invalid model, which will fail to dmap #5101: Fixed: Model exporter doesn't remember last export location #5092: Fixed: Buttons to change spawnargs can affect entities that aren't currently selected #5091: Feature: Add "Choose Skin" button when editing model spawnarg of an existing entity #5095: Fixed: Search box persists for some seconds after closing window or shifting focus #5094: Fixed: Choose Skin dialog will crash in 2.7.0pre2 #5093: Fixed: When no GL context is present, OpenGLModule::assertNoErrors() runs into an endless loop until your memory runs out #5086: Fixed: In DR 2.7.0 pre2: S/R interface issues with adding stims or responses #5087: Fixed: Connecting lines to targeted entities don't show up if 'Default' layer was hidden #5082: Fixed: Layers window: first click after opening isn't registered properly Changes since 2.7.0pre3 #5095: Even more fixed: Search box persists for some seconds after closing window or shifting focus #5112: Feature: Let the 'Matching skins' folder start in expanded state when showing the SkinChooser #5113: Fixed: 'Choose skin' from model spawnarg: hitting cancel sets model spawnarg as skin #5114: Fixed: Model selection: materials/verts/polys display always refers to previously selected model #5117: Fixed: Entities with non-existent classnames are shown white instead of blue in orthoview Changes since 2.7.0pre4 #5088: Fixed: Hitting cancel in 'Create Speaker' still creates a speaker And an untracked change to make the Entity Inspector columns resizable. Thanks for testing, as always!

Wiki series: A to Z Scripting For a long time, scripting has been something of an elusive topic in TDM. Those who were already familiar with programming would analyse existing scripted setups in TDM, gradually deducing how things are done around here. Those with no prior knowledge had a handful of basic tutorials to look at, but they only went so far. As a result, a lot of basic scripting questions have been asked and answered on these forums over the years. Here is my offering: the A to Z Scripting series, aiming to cover all things scripting in TDM. It should cater to anyone, from absolute beginners to more knowledgeable users looking to familiarise themselves with TDM's methods for employing scripts. Special thanks go to Obsttorte for providing feedback on the entire guide, as well as Kingsal for providing some material to work with. (Don't mind the timestamps, this thread has been stitched together on Dec 27 2020 from another discussion.)

I was referring to D3W advice in general, not the specific text you posted. I've seen several forum posts on D3W and I think even these forums where people have repeated the "fact" that Doom 3 has a problem with more than 3 lights hitting a surface, and advised mappers to cut up brushes to make sure they never see a cyan surface in the r_showLightCount view, even though this was a waste of time that made no difference to frame rates back when I was doing it on a Radeon 9800 XT in 2006. I suspect that the "3 light limit" comes from the descriptive text in the explanation of r_showLightCount: 1. Black= No light hitting the surface. 2. Red= 1 light hitting the surface (this is excellent). 3. Green= 2 lights hitting a surface (this is great). 4. Blue = 3 lights hitting a surface (This is getting bad. You need to keep these areas small, but it is ok to have a number of smaller areas in a room that are blue). 5. Cyan, pink, or white= 4+ lights hitting a surface this is bad and you should only have this in very small, isolated areas. It would be easy to interpret these descriptions as implying that something bad happens between 2 lights ("this is great") and 3 lights ("this is getting bad"), even no there is no such limit and these textual descriptions were (as far as I can tell) just off-the-cuff phrases that never actually reflected any empirical performance testing. There is no such limit for maximum lights, because light count is just one of many factors influencing performance, along with poly count, shadow count, shadow mesh complexity, number of shadow-casting lights, number and size of open/closed visportals and many other things. Giving suggested limits for particular scene elements is counter productive because these limits tend to get enshrined in documents and forum posts and propagated through time as a sort of "cargo cult", where people believe that as long as they have fewer than a certain number of lights or polygons then their scene will be fast to render, even though there may be many cases where having more lights/polygons would be fine if other elements of the scene are simpler, and vice versa. The only meaningful way to address performance is based on empirical testing, with guided optimisations based on this data. For example, if you have a scene that is particularly slow to render, and you find that you have a large surface hit by 20 different lights and they all cast shadows, this might be the thing to optimised, whereas in another scene you might find that you have 10 million polygons in view due to a reflection surface and too many open visportals, and these are the things you need to fix. But in no case does this mean that if you stick to 19 different lights and only 9 million polygons, you will never have a problem with performance. No need to get defensive; I wasn't criticising you, just pointing out that some of that old advice from D3W and other forums isn't particularly accurate and shouldn't be relied upon by today's mappers, particularly when it asserts particular numeric limits that quickly become obsolete due to the evolution of hardware, and might not have been correct to begin with. Nothing wrong with looking at light counts in conjunction with other items (but you must also consider the area of the over-lit polygons, not just the count, and consider the effect of light scissoring which considerably restricts the actual area that is illuminated based on the size of the light, even if that light hits a large polygon), provided you don't become attached to certain fixed "ideal light counts" which are just too crude a measure to be useful. Overall my advice with light count and everything else (polygons, shadows etc) is: Minimise everything as far as you possibly can without compromising the artistic intent. Use in-game diagnostics and statistics as a guide, without being hung up on particular numeric thresholds and values. Test on a variety of hardware (especially mediocre hardware) if you can, to avoid producing a map which only runs well on your super high-end rig.

Can't use spoiler tags, so here's the file I'm using for beta4.

[update] Spoke to Marcus @AMD UK on the phone and as it turns out a number of complaints have been made against "Spyre". My AMD forum account has been unbarred and my Ip address unblocked!!! Bought a new gfx card for xmas, been having issues with mainly the driver So I though a good place to look for support and polity vent etc - or so I thought My second post got flamed by some smart arse fanboy and then promptly locked, to which I reported the posted asking why it had been locked.. and then my account on there got deleted and my Ip blocked (untill the isp dhcp refreshed etc) so I cant login even with a different account name. I have emailed AMD directly about this as I did nothing wrong according the t&c's and I got no warning Pm or email from the forum mods. Now I've been over at the nVidia forums a long while back when I had the 8800GTX when I was equally frustrated when posting about the driver issue with thief etc, but at no point did a thread get locked or worse my account deleted. I don't have loyalty to AMD or nVidia but depending on the answer I get from AMD next week this card maybe going back and AMD will be added to the list of manufactures I will never buy anything from again. So whats the moral of this story, well take your pick.. [update] found cached copies of 1 of my posts Cached AMD frum link Cached AMD forum link2

@Zerg Rush: Any further clues or suggestions or strategy should be wrapped in spoiler tags, please.

I was surprised to find nothing about HRTF on this site so I decided to make a thread about what it is, how it improves your TDM experience and how you can get it. For Germans: Quasi den gleichen Thread gibt es auf Deutsch hier: http://www.hardwareluxx.de/community/f267/guide-openal-soft-mit-hrtf-als-ersatz-fuer-openal-vorteil-3d-sound-fuer-headphones-1013497.html What is HRTF? To put it simply: Our brain can determine the position of sounds so accurately because depending on where the sound comes from it goes through different zones of our head where the sound is unnoticeably changed but it's enough for the brain to put it into 3d space. HRTF is a technique to improve positional audio in games by filtering the audio signal the same way it would be changed when passing through our heads. This way the positioning is spot-on and feels very real. I have some demo videos on Youtube if you are in doubt it works: https://www.youtube.com/watch?v=MVqFbu4gsqs&index=8&list=PL_0EBFw_May-IAaplRFVS5n2-9p3pPR_4 Please note that HRTF suffers greatly under audio compression and is much better in real life! What do I need for HRTF? In this topic I will only talk about OpenAL Soft HRTF because this is the only way at the moment to get HRTF from TDM. You need: - Headphones! (in theory HRTF would work with speakers as well but there are no datasets for speakers) - OpenAL Soft version >= 1.14 (the way how HRTF can be used changed between versions, I will only talk about the latest version, 1.17.1 here) That's it! No specific sound card required or anything. It is however very easy to mess up the setup so that HRTF doesn't work. Follow the guide closely to make sure it works. How do I set it up? Windows 32 Bit: - Download current build of OpenAL Soft - move soft_oal.dll from bin\Win32 as "OpenAL32.dll" to C:\Windows\system32 Windows 64 Bit: - warning: Due to the architecture of Windows the 32/64 bit numbers are confusing. My tutorial is correct, don't be confused! - Download current build of OpenAL Soft - move soft_oal.dll from bin\Win32 as "OpenAL32.dll" to C:\Windows\SysWOW64 (for 32 bit games) - move soft_oal.dll from bin\Win64 as "OpenAL32.dll" to C:\Windows\system32 (for 64 bit games) Final steps for both Windows versions: - move standard HRTF datasets (default*.mhr) from hrtf to %appdata%\openal\hrtf - remove OpenAL32.dll/wrap_oal.dll from the game folder if existing - Copy all text from alsoftrc.sample, create alsoft.ini in %appdata%, paste the text from alsoftrc.sample into alsoft.ini and change "#hrtf = auto" to "hrtf = true" (remove "#"!) - make sure your audio sample rate is 44,1kHz or 48kHz - turn on OpenAL in Darkmod.cfg (seta s_useOpenAL "1") - set TDM to stereo sound - To make sure it works run put this in a .bat file and run it from the TDM folder: Check openallog.txt if HRTF is enabled. Linux: - Make sure your OpenAL Soft version is >= 1.14 - Depending on the distribution and OpenAL Soft install you may need to install the HRTF datasets manually: - Download current build of OpenAL Soft and move default*.mhr from hrtf to ~/.local/share/openal/hrtf - Download alsoftrc.sample and save to ~/.alsoftrc - In ~/.alsoftrc change "#hrtf = auto" to "hrtf = true" (remove "#"!) - set TDM to stereo sound Advanced users: There is a way to improve the positioning even more: Because the default HRTF datasets are made for an "average" head they may not be optimal for you. You can create your own by following this guide: https://www.reddit.com/r/oculus/comments/1fzonq/psa_for_games_using_openal_including_minecraft/cagd3lb PS: This also works with Thief 1&2 running on NewDark but you have to enforce a frequency of 44,100 kHz in alsoft.ini for it to work because Thief's sounds are in 22,050 khz. PPS: In order to spread the awareness of HRTF I license this forum post under CC-BY so you can repost it anywhere when giving credit to me.

when i do a search, it give me some results, I click on a result and exspect to get taken to the post it specifies - but no..... I get taken to the first post of the bloody thread it is in..ggrrr

It's interesting because I recently read a thread on the Doomworld forums on people's opinions of single-segmenting maps in classic Doom/Doom 2. In other words, playing a map from start to finish without using saves - if you die, you have to replay the entire map. The general consensus was that saves are useful, however there was some merit in there being extra tension and challenge knowing that death couldn't be rewound easily by reloading a save. On the other hand (and speaking as an adult), people have to work and often have limited time for gaming. Having to replay a long map because you died can be quite off-putting and takes the joy out of a game if it happens often enough. Savegames keep the tempo going, keeps the feeling of progress going. Also someone pointed out that starting a map from scratch after a death is kinda like using saves anyway, just a single save at the beginning. You're just being tedious by denying the use of saves in this case. Dunno where I'm going with this. Trying to be diplomatic and say I can see all sides to the discussion.

Regarding the sound: Instead of creating a speaker via script, you could create the speaker in a seperate (e.g. where the start-weapons and items are stored) and move it to the player position, when you need the sound. When the sound should stop, you could move it back to its former location. That way, you can have the speaker on repeat all the time or you could handle it like you would any other speaker. Regarding the speed potion: By the way: If you are searching for somethin in the forums, I would recommend to use google with a "site:forums.thedarkomod.com" before the term you are searching for. This limits the google search to the forums and the google algorithm is way better than the search function of the forum itself. In this case it was the second hit of the search.

Another wiki topic added: Your Mission - From Beta Testing to Release and Beyond with links from the endings of: A - Z Beginner Full Guide Page 6 How to pack your Mission The material here will be largely obvious to old hands, but worth stating explicitly for the benefit of newcomers. From the Introduction: This article elaborates typical steps for beta-testing a mission beyond its packaging, namely: distribution, forum presence, and testing. This process continues to Final Release and any updates. Consider this a follow-on to - * A - Z Beginner Full Guide; and * How to Pack your Mission, which fully describes the vital process of packaging and testing a .PK4 archive.

The compilation guide refers to the master branch, since the command git clone git://github.com/codereader/DarkRadiant.git will check out master. I wasn't aware that you're on Linux, because the snapshot builds above won't apply to you, it's for Windows x64 only. You'll have to build from source to test anything in between releases.

So normally I use the compilation guide to build from source, does that install DR stable, or production? If I want a snapshot of the latest source, where do I download that? Btw. I use Linux (Manjaro - Arch based distro)

In order to thank the team (and other mappers) for their relentless efforts in contributing, I hereby give the community.... Ulysses: Genesis A FM By Sotha Story: Read & listen it in game. Link: https://drive.google.com/file/d/0BwR0ORZU5sraTlJ6ZHlYZ1pJRVE/edit?usp=sharing http://www4.zippysha...95436/file.html Other: Spoilers: When discussing, please use spoiler tags, like this: [spoiler] Hidden text. [/spoiler] Mirrors: Could someone put this on TDM ingame downloader? Thanks!