Search the Community

Shouldn't these (I cannot find them in DR) have a mirror effect applied, like models/darkmod/kitchen/tea_tray_silver2.ase ? I guess this is some brush with texture bc_teatray applied? Although this texture has the mirror effect applied.

Wasn't sure if I should still post this since the mystery was somewhat solved, but just to confirm this case can be found in the wild with FM's other than mine: Yesterday I played Chronicles of Skulduggery 0: To Catch a Thief. There's a door up on a terrace (I can reinstall it and go there to get a viewpos if anyone's interested) which upon picking and opening will cause the light on the back of the wall indoor to slightly shine on the floor outside through the entire wall. Exact same camera position / angle in both images so you can just overlap the two screenshots to see the difference, though if you look at the bottom left ground it's pretty clear what happens once the door is opened. It's still a bit weird: The wall module model should still be casting a shadow, even if the wall brush uses caulk and not shadow caulk. Whatever the case a few FM's out there seem to have this problem, even if it's not an issue the engine or building modules can resolve I wonder if mappers can be better put on notice about it since like me most are likely not aware this is a thing or what causes it. Looked at the first post again and the video attached to it: Definitely seems like the same thing. Most importantly it wasn't doing this in earlier versions which I didn't realize... I'm seeing the clarification by Stgatilov as well which I initially missed, I definitely prefer the performance optimization but now I do wonder if something can also be done about this eventually.

Black Parade is released ! https://www.ttlg.com/forums/showthread.php?t=152429

Of course, it is one of the reasons for the decline of online forums, since the advent of mobile phones. Forums on a mobile are a pain in the ass, but on the other hand, for certain things there are no real alternatives to forums, social networks cannot be with their sequential threads, where it is almost impossible to retrieve answers to a question that is asked. has done days ago. For devs for internal communication, the only thing offered is a collaborative app, such as System D (not to be confused with systemd). FOSS, free and anonymous registration, access further members only by invitation, full encrypted and private. https://www.system-d.org

Core items should cover a good-enough number of moveables in all mission. There normally isn't that much junk and it normally is the same and it is found in the same places: kitchen, bathroom, bedroom... Would mappers complain if all of a sudden a "Stool" is described as a "Stool"? Things change though when a mapper decides a "Brush" becomes "Penelope's Brush". A useless item still, but more power to tell a story through everyday objects. It's all in there already: the "shouldered name" slot in the HUD. It works perfectly fine via script although it would be better to have it built-in. Regardless: no names, no game

Body awareness please. https://forums.thedarkmod.com/index.php?/topic/20013-are-you-gonna-add-this/

I loved it. Awesome game. I faceplanted at the people who asked for quest markers in the Steam forums there... Herr, lass Hirn regnen. The game is so great, and so true to the original, because it doesn't hold your hand. When is the new breed of gamers gonna learn.

Unfortunately many things in this engine are best done on the editor and then called through script, not created directly through script, one of them afaik is triggers. You normally create a trigger by creating a square brush on the editor manually, and give it the trigger_hurt material, so the size and shape comes from that brush, it also creates the physics (a clip model) automatically, then just need to use the script function, entity ent = sys.FindEntity("entity_name"); To get it and use it in the script to do whatever you want. Creating a clip model from script, is probably possible, thou I never did it, so I don't know how... thou I do know how to do it through c++. But I don't think there's any equivalent script functions exposed to the script system, if I'm mistaken please anyone correct me. Perhaps something to recommend in the TDM roadmap?

@MirceaKitsune try something other than caulk on that brush and see if it goes away. Make sure it's not a no shadows or transparent material.

It's not that no: I didn't modify the properties of the default entity or its flame, in this case it's the standard atdm:lamp_oil_wall_lit entity... also I have player shadows enabled, the player as well as other architecture elements cast shadows fine. Walls are the building modules, eg: model models/darkmod/architecture/modules/interior_set01_corner.lwo with skin diamond_wallpaper as a test. This is the closest to the setup I still have: The origin of the light is well beyond the face of the module surface for shadow casting. Though this shouldn't even matter since the light is in the other room and the caulk brush should itself mark this. I think I noticed this on other maps too while playing, but only now saw it obviously enough to realize there's likely an issue somewhere. I remember seeing the glow of a light from another room shining on the floor / ceiling when it shouldn't, though I didn't document it at the time.

So giving it none of those tags, but making the AI invisible, silent, non-solid, and on a team neutral to everyone would not work? Oh well, it was a horrible inelegant idea anyway.

Horror themed fan mission - exploration of seemingly deserted keep in the middle of swamps. Spiders, undead, darkness. ----------------------------------------------------------------------------------------------------------------------------- This is the story about the fate of my family. My uncle, Ralph Mac Roberts, is the baron of a keep nestled deep within the Rahenaen marshes. It was once an important outpost tasked with guarding one of the few Builder roads that cross the marsh, but after the Inventor`s Guild built a system of nearby dams that flooded the whole land, the road closed and there was no longer anything to watch over anymore. The keep itself needed reinforcement against the raising water level and the trade routes become almost impassable, not only for the carriages but for lone couriers as well. There hadn`t been any messages coming from the keep for over a year and my father was about to assemble a caravan so he could go on an expedition to the keep himself. However, in the middle of the night before he was set to leave, a carrier pigeon landed on his windowsill. My father received the letter and read the apologies from my uncle and his family, excusing their long absence. As a way to make reparations for their extended silence, my uncle invited me to the keep to stay there for a fortnight or so. My uncle had instructed me to leave my horse three leagues away from the keep by the nearest charcoal burning hut and hike the remainder of the road on foot, as the trek through the marsh is treacherous for horses. The weather will be awful this time of year, but my father insists that I should go anyways to ensure that our relatives are okay. These plains become dreadfully deserted - to the point where you more expect to meet the dead than the living. And by the way - I think I`m lost. ----------------------------------------------------------------------------------------------------------------------------- Download link: https://1drv.ms/u/s!Aj1DVS465udZgVkXteBbr6cUxdPH Thanks: to the TDM team for great tools, and all the contributors for their assets, to betatesters: Amadeus, Bienie, Boiler's_hiss, Dragofer, Filizitas, Judith, nbohr1more, s.urfer, again to Amadeus for proofreading and text tweaks, and to all the players for their time! Few screenshots: http://forums.thedarkmod.com/topic/10003-so-what-are-you-working-on-right-now/?p=434716 http://forums.thedarkmod.com/topic/10003-so-what-are-you-working-on-right-now/?p=429558 http://forums.thedarkmod.com/topic/19886-fm-marsh-of-rahena-beta-testing/?p=434507 Enjoy! Walk-through !major spoilers! Finding a way across the marsh area: Getting inside: Bed objective: Light sources: Maps: Enemies: Room objective: Hut objective: Sealed objective: Gold: Key: Bodies:

It is possible to add: Entity spawnarg --- means that this entity should casts shadow even if it's beyond walls according to area/portals. Worldspawn spawnarg --- same meaning as p.1, but applies to all entities in the map. This is OK if the mission is rather up-to-date. The older missions (like before 2.08 maybe) were compiled with older dmap. While I tried to add some compatibility cvar for dmap, it is still likely that fresh dmap will behave differently. You'll have to test the whole map thoroughly, and probably fix dmap-related issues everywhere. On the other hand, adding spawnarg is risk-free, since it does not require fresh dmap. Yes, the major part of the problem is that these caulky walls don't manifest any issues until you carry a light source into specific position. The original game would be buggy only if simple static light is in that position, which is much easier to test. Maybe filter away entities in DarkRadiant and look for visible caulk. I think mappers put caulk on surely-invisible part as an optimization, since otherwise this brush surface would actually be rendered (although only to depth buffer, which is cheap). But some of these surfaces should cast shadow, so it is no clear which can be replaced with caulk and which not. My suggestion is: Create a dedicated thread regarding light/shadow issues. Move the messages from this thread into it too. Analyze cases one by one. It can easily happen that some issues are caused by other things. Decide what to do when we have enough info.

Public release v1.7.6 (with Dark Mod support) is out. Improvements since the final beta 14 are: Fixed a few remaining bugs with zip/pk4 support. Game Versions window now properly displays TDM version. Import window no longer has a vestigial off-screen TDM field (because TDM doesn't need or support importing). Web search option is now disabled if an unknown/unsupported FM is selected. If an FM with an unknown or unsupported game type is selected, the messages in the tab area now no longer refer to Thief 3 ("Mod management is not supported for Thief: Deadly Shadows"). The full changelog can be viewed at the release link. The de facto official AngelLoader thread is here: https://www.ttlg.com/forums/showthread.php?t=149706 Bug reports, feature requests etc. are usually posted there. I'll continue following this thread though. Thanks everyone and enjoy!

Good work! I enjoy short missions because things are nice and focused - you get in, you get out. Also I tend to do better with the loot amounts and I was able to get all the loot without too much trouble, which is rare for me. If I were to make a suggestion though - I found the intro briefing sequence a bit distracting because it was so obvious the narration was pitch-shifted to make a deeper voice. If you felt the original voice wasn't deep enough for your needs, I would either get someone on the forums to record it for you or just leave as is. That's my only real complaint and it's not even about the mission itself, so pretty good first start!

I investigated the topic, and I still think it is too hard. Precomputed visibility is perhaps the best thing for us. So we can split space into cells, and precompute whether cell A and cell B have unoccluded straight line connecting them. We can limit occlusion only by brushes: there is no need to take models/patches into account. Precomputed visibility should be done on per-area basis. When we compute the visibility data for one area, we consider all visportals and all other areas opaque. In other words, we only check for direct visibility within the area. If such information is available, it can be combined with existing visportal&area traversal code. The main problem is how to precompute visibility on per-cell basis. A solution must: Be conservative: you don't want to occasionally see small holes into nowhere Do perfect occluder fusion: otherwise a big house would not occlude most of the stuff behind it. Have sane build times for brush geometry of our scale. This inevitably leads to pretty complex algorithms. If mapper can add a special brush and say "this is major occluder in visarea N", then we can probably (not sure yet) verify that he is correct in saying that, and simply raytrace this occluder during visportal traversal. But realistically... I don't think mappers would really use this tecnhique, except maybe for a very few people/missions.

I created two walls: both have a base brush that is 128 x 128, and 4 units thick. One of the brushes, however, has a little bit of decor that sticks out another 4 units. Later on when I was working on my map, I cloned a model, moved it 128 units, and then changed it's model. However, when changing it from the wall with decor to the wall with no decor, it proceeded to shift itself 2 units forward. I thought maybe it had to do with what grid size I had saved/exported the model as, but adjusting that did nothing. And the models are both aligned together. This is the only model I've had do this. What is causing this?

Thanks for the clarification! I had no idea antiportals were a thing, I can't find an antiportal texture or entity in DarkRadiant so I presume it comes in another form? This means the behavior I'm imagining is already coded in there somewhere: Only change then would be automatically treating every solid brush as an antiportal, of course without having it derender itself only what's behind it... at least that's what I'd initially think, reality is always more complex. Obviously we don't check all world surfaces on the map: Visportal culling acts first so any wall that isn't in an open room doesn't exist from the start, same for surfaces that don't poke into the view frustum and are outside your FOV... if a smart approach is possible we could even check walls in order of distance from the camera so the mask masks itself and even walls covered by other walls are dropped. Only if a front-facing brush surface that wasn't portal-culled pokes into view it's calculated as an occluder; The engine then checks all entities that weren't themselves already culled by portals / frustum and removes those found to be completely covered by a wall's projection. This could be a big success is it could do all of 3 things: Hide models that don't poke beyond the mask, disable lights who's radius box is fully covered by the wall, and close portals that are fully covered by a wall meaning whole rooms can get hidden when their doorway is masked by an occluder. (Anti)portals do all of those things I believe, so it's a matter of somehow getting all surfaces to act as such in an optimal way.

OK, not seeing too many opportunities to improve things yet. The mission is made of mostly model prefabs so there isn't really any excess triangulation due to brush carving. Most of the portals seem to be doing their job but since it's all model geometry all the open doors and windows pose a challenge to help much. Maybe forcing some func_portal closures at the fogged distance might improve things. Speaking of fog, I am seeing a lot of "double-fogged" surfaces. I believe this is happening due to duplicate geometry or transparent geometry. ( See the bright band in center of the screenshot ) : If you can isolate this extra geometry and make it into entities then you can set those entities with a "noFog" flag to prevent them from fogging. This presumes the geometry is transparent though.

I am pleased to announce the release of our new fan mission, The Hare in the Snare: Part 1 Mission type: City Missions + Inn/Tavern Description: People are being abducted off the streets and a Watch Captain requires the services of a thief to help him find out why. Download link (v1.0.2-release): https://drive.google.com/file/d/1HYvM_u56wDB16uIlb7qgS_q3P24V69MO/view?usp=sharing Credits: Mapping and original characters: @Frost_Salamander Story, readables, custom models, voices and cinematics: @Kerry000 Menu title track produced and mixed by @JackFarmer with selected gigagooga sound samples Beta testers: @Cambridge Spy @Zerg Rush @Amadeus @Acolytesix @Lzocast @wesp5 @nbohr1more @Kerry000 @ate0ate @Wellingtoncrab @prjames Additional thanks: @Dragofer, @nbohr1moreand @peter_spyfor technical help @Springheel for the modules and tutorials @kingsalfor allowing @Kerry000to abuse his manbeast everyone else on Discord and the TDM forums who offered assistance Requirements and notes: This mission requires TDM 2.09. Earlier versions will probably work but you might see one or two missing models. You may experience some FPS drops in some areas with lower-end hardware. Mid-range and above should be fine. If you have issues, I highly recommend you use shadow maps instead of stencil (settings -> advanced -> shadows implementation). It makes a big difference. For 'Hard' and 'Expert' the light gem sensitivity has been increased by '1' (meaning easier for AI to detect you). Screenshots:

Thanks for the replies, gonna try those spoiler Tags again now for my short review (oh well it inserted one above my text now and I can't seem to delete it on mobile - this text editor is strange)

Just finished this mission and wow I gotta say in great honor to Grayman and of course the rest of the team picking it up, this was something I've never seen before in any other TDM mission, especially visually wise. I am so happy that grayson gave green light for other experienced mappers to finish his last mission. And what came out of this is really something special. I'll put my review in spoiler tags since I'm now referring to critical mission details. Edit - How do I put spoiler text here on mobile?? [spoiler] test [/spoiler][SPOILER] test [/SPOILER] [spoiler[spoiler [sfah

I'd like to better understand what you want. The design of dragging bodies is to hold frob (key down) to drag and release frob (key up) to let go. That way it's impossible to walk away while unintentionally dragging a body. Plus, it's quick to grab and move several body limbs in rapid succession. This is thought to provide a better experience, especially for new players. Towards the beginning of this thread, I created a "tdm_frobhold_drag_body_behavior" cvar. https://forums.thedarkmod.com/index.php?/topic/22198-feature-proposal-frob-to-use-world-item/&do=findComment&comment=487580 "tdm_frobhold_drag_body_behavior", default:"1" Which drag body behavior? 1 --- on frob key up, drop body (limb). 0 --- on second frob, drop body (limb), TDM v2.11 (and prior) behavior. That cvar was removed shortly afterwards, because it was said that it wasn't needed. With that cvar set to 0, a second frob would be required to let go of the body. Is that the behavior that you want? If so, I can add that cvar back. Also, I saw elsewhere that you want the ability to revert back to the old way. If you mean that all of the controls match TDM 2.11, that can be done with "tdm_frobhold_delay 0" and there will be a menu setting to disable it as well.

OK, here you go: [ 30%] Linking CXX shared module libradiantcore.so cd /home/thebigh/Games/DarkRadiant/radiantcore && /usr/bin/cmake -E cmake_link_script CMakeFiles/radiantcore.dir/link.txt --verbose=1 /usr/bin/c++ -fPIC -pthread -O3 -DNDEBUG -Wl,-z,defs -shared -o libradiantcore.so CMakeFiles/radiantcore.dir/brush/Brush.cpp.o CMakeFiles/radiantcore.dir/brush/BrushModule.cpp.o CMakeFiles/radiantcore.dir/brush/BrushNode.cpp.o CMakeFiles/radiantcore.dir/brush/csg/CSG.cpp.o CMakeFiles/radiantcore.dir/brush/export/CollisionModel.cpp.o CMakeFiles/radiantcore.dir/brush/Face.cpp.o CMakeFiles/radiantcore.dir/brush/FaceInstance.cpp.o CMakeFiles/radiantcore.dir/brush/FacePlane.cpp.o CMakeFiles/radiantcore.dir/brush/FixedWinding.cpp.o CMakeFiles/radiantcore.dir/brush/TexDef.cpp.o CMakeFiles/radiantcore.dir/brush/TextureMatrix.cpp.o CMakeFiles/radiantcore.dir/brush/TextureProjection.cpp.o CMakeFiles/radiantcore.dir/brush/Winding.cpp.o CMakeFiles/radiantcore.dir/camera/Camera.cpp.o CMakeFiles/radiantcore.dir/camera/CameraManager.cpp.o CMakeFiles/radiantcore.dir/clipper/BrushByPlaneClipper.cpp.o CMakeFiles/radiantcore.dir/clipper/Clipper.cpp.o CMakeFiles/radiantcore.dir/clipper/ClipPoint.cpp.o CMakeFiles/radiantcore.dir/clipper/SplitAlgorithm.cpp.o CMakeFiles/radiantcore.dir/commandsystem/CommandSystem.cpp.o CMakeFiles/radiantcore.dir/eclass/Doom3EntityClass.cpp.o CMakeFiles/radiantcore.dir/eclass/EClassColourManager.cpp.o CMakeFiles/radiantcore.dir/eclass/EClassManager.cpp.o CMakeFiles/radiantcore.dir/entity/AngleKey.cpp.o CMakeFiles/radiantcore.dir/entity/curve/CurveCatmullRom.cpp.o CMakeFiles/radiantcore.dir/entity/curve/Curve.cpp.o CMakeFiles/radiantcore.dir/entity/curve/CurveEditInstance.cpp.o CMakeFiles/radiantcore.dir/entity/curve/CurveNURBS.cpp.o CMakeFiles/radiantcore.dir/entity/Doom3Entity.cpp.o CMakeFiles/radiantcore.dir/entity/doom3group/Doom3Group.cpp.o CMakeFiles/radiantcore.dir/entity/doom3group/Doom3GroupNode.cpp.o CMakeFiles/radiantcore.dir/entity/eclassmodel/EclassModelNode.cpp.o CMakeFiles/radiantcore.dir/entity/EntityModule.cpp.o CMakeFiles/radiantcore.dir/entity/EntityNode.cpp.o CMakeFiles/radiantcore.dir/entity/EntitySettings.cpp.o CMakeFiles/radiantcore.dir/entity/generic/GenericEntity.cpp.o CMakeFiles/radiantcore.dir/entity/generic/GenericEntityNode.cpp.o CMakeFiles/radiantcore.dir/entity/KeyValue.cpp.o CMakeFiles/radiantcore.dir/entity/KeyValueObserver.cpp.o CMakeFiles/radiantcore.dir/entity/light/Light.cpp.o CMakeFiles/radiantcore.dir/entity/light/LightNode.cpp.o CMakeFiles/radiantcore.dir/entity/light/Renderables.cpp.o CMakeFiles/radiantcore.dir/entity/ModelKey.cpp.o CMakeFiles/radiantcore.dir/entity/NameKeyObserver.cpp.o CMakeFiles/radiantcore.dir/entity/NamespaceManager.cpp.o CMakeFiles/radiantcore.dir/entity/RotationKey.cpp.o CMakeFiles/radiantcore.dir/entity/RotationMatrix.cpp.o CMakeFiles/radiantcore.dir/entity/ShaderParms.cpp.o CMakeFiles/radiantcore.dir/entity/speaker/SpeakerNode.cpp.o CMakeFiles/radiantcore.dir/entity/speaker/SpeakerRenderables.cpp.o CMakeFiles/radiantcore.dir/entity/target/TargetableNode.cpp.o CMakeFiles/radiantcore.dir/entity/target/TargetKeyCollection.cpp.o CMakeFiles/radiantcore.dir/entity/target/TargetKey.cpp.o CMakeFiles/radiantcore.dir/entity/target/TargetLineNode.cpp.o CMakeFiles/radiantcore.dir/entity/target/TargetManager.cpp.o CMakeFiles/radiantcore.dir/filetypes/FileTypeRegistry.cpp.o CMakeFiles/radiantcore.dir/filters/BasicFilterSystem.cpp.o CMakeFiles/radiantcore.dir/filters/XMLFilter.cpp.o CMakeFiles/radiantcore.dir/filters/XmlFilterEventAdapter.cpp.o CMakeFiles/radiantcore.dir/fonts/FontLoader.cpp.o CMakeFiles/radiantcore.dir/fonts/FontManager.cpp.o CMakeFiles/radiantcore.dir/fonts/GlyphInfo.cpp.o CMakeFiles/radiantcore.dir/fonts/GlyphSet.cpp.o CMakeFiles/radiantcore.dir/grid/GridManager.cpp.o CMakeFiles/radiantcore.dir/imagefile/BMPLoader.cpp.o CMakeFiles/radiantcore.dir/imagefile/dds.cpp.o CMakeFiles/radiantcore.dir/imagefile/ddslib.cpp.o CMakeFiles/radiantcore.dir/imagefile/ImageLoader.cpp.o CMakeFiles/radiantcore.dir/imagefile/JPEGLoader.cpp.o CMakeFiles/radiantcore.dir/imagefile/PNGLoader.cpp.o CMakeFiles/radiantcore.dir/imagefile/TGALoader.cpp.o CMakeFiles/radiantcore.dir/layers/LayerInfoFileModule.cpp.o CMakeFiles/radiantcore.dir/layers/LayerManager.cpp.o CMakeFiles/radiantcore.dir/layers/LayerModule.cpp.o CMakeFiles/radiantcore.dir/log/COutRedirector.cpp.o CMakeFiles/radiantcore.dir/log/LogFile.cpp.o CMakeFiles/radiantcore.dir/log/LogStreamBuf.cpp.o CMakeFiles/radiantcore.dir/log/LogStream.cpp.o CMakeFiles/radiantcore.dir/log/LogWriter.cpp.o CMakeFiles/radiantcore.dir/log/StringLogDevice.cpp.o CMakeFiles/radiantcore.dir/map/aas/AasFileManager.cpp.o CMakeFiles/radiantcore.dir/map/aas/Doom3AasFile.cpp.o CMakeFiles/radiantcore.dir/map/aas/Doom3AasFileLoader.cpp.o CMakeFiles/radiantcore.dir/map/aas/Doom3AasFileSettings.cpp.o CMakeFiles/radiantcore.dir/map/algorithm/Export.cpp.o CMakeFiles/radiantcore.dir/map/algorithm/Import.cpp.o CMakeFiles/radiantcore.dir/map/algorithm/MapExporter.cpp.o CMakeFiles/radiantcore.dir/map/algorithm/MapImporter.cpp.o CMakeFiles/radiantcore.dir/map/algorithm/Models.cpp.o CMakeFiles/radiantcore.dir/map/algorithm/Skins.cpp.o CMakeFiles/radiantcore.dir/map/ArchivedMapResource.cpp.o CMakeFiles/radiantcore.dir/map/CounterManager.cpp.o CMakeFiles/radiantcore.dir/map/EditingStopwatch.cpp.o CMakeFiles/radiantcore.dir/map/EditingStopwatchInfoFileModule.cpp.o CMakeFiles/radiantcore.dir/map/format/Doom3MapFormat.cpp.o CMakeFiles/radiantcore.dir/map/format/Doom3MapReader.cpp.o CMakeFiles/radiantcore.dir/map/format/Doom3MapWriter.cpp.o CMakeFiles/radiantcore.dir/map/format/Doom3PrefabFormat.cpp.o CMakeFiles/radiantcore.dir/map/format/MapFormatManager.cpp.o CMakeFiles/radiantcore.dir/map/format/portable/PortableMapFormat.cpp.o CMakeFiles/radiantcore.dir/map/format/portable/PortableMapReader.cpp.o CMakeFiles/radiantcore.dir/map/format/portable/PortableMapWriter.cpp.o CMakeFiles/radiantcore.dir/map/format/primitiveparsers/BrushDef3.cpp.o CMakeFiles/radiantcore.dir/map/format/primitiveparsers/BrushDef.cpp.o CMakeFiles/radiantcore.dir/map/format/primitiveparsers/Patch.cpp.o CMakeFiles/radiantcore.dir/map/format/primitiveparsers/PatchDef2.cpp.o CMakeFiles/radiantcore.dir/map/format/primitiveparsers/PatchDef3.cpp.o CMakeFiles/radiantcore.dir/map/format/Quake3MapFormat.cpp.o CMakeFiles/radiantcore.dir/map/format/Quake3MapReader.cpp.o CMakeFiles/radiantcore.dir/map/format/Quake4MapFormat.cpp.o CMakeFiles/radiantcore.dir/map/format/Quake4MapReader.cpp.o CMakeFiles/radiantcore.dir/map/infofile/InfoFile.cpp.o CMakeFiles/radiantcore.dir/map/infofile/InfoFileExporter.cpp.o CMakeFiles/radiantcore.dir/map/infofile/InfoFileManager.cpp.o CMakeFiles/radiantcore.dir/map/Map.cpp.o CMakeFiles/radiantcore.dir/map/MapFileManager.cpp.o CMakeFiles/radiantcore.dir/map/MapModules.cpp.o CMakeFiles/radiantcore.dir/map/MapPosition.cpp.o CMakeFiles/radiantcore.dir/map/MapPositionManager.cpp.o CMakeFiles/radiantcore.dir/map/MapPropertyInfoFileModule.cpp.o CMakeFiles/radiantcore.dir/map/MapResource.cpp.o CMakeFiles/radiantcore.dir/map/MapResourceLoader.cpp.o CMakeFiles/radiantcore.dir/map/MapResourceManager.cpp.o CMakeFiles/radiantcore.dir/map/mru/MRU.cpp.o CMakeFiles/radiantcore.dir/map/namespace/ComplexName.cpp.o CMakeFiles/radiantcore.dir/map/namespace/Namespace.cpp.o CMakeFiles/radiantcore.dir/map/namespace/NamespaceFactory.cpp.o CMakeFiles/radiantcore.dir/map/PointFile.cpp.o CMakeFiles/radiantcore.dir/map/RegionManager.cpp.o CMakeFiles/radiantcore.dir/map/RootNode.cpp.o CMakeFiles/radiantcore.dir/model/export/AseExporter.cpp.o CMakeFiles/radiantcore.dir/model/export/Lwo2Chunk.cpp.o CMakeFiles/radiantcore.dir/model/export/Lwo2Exporter.cpp.o CMakeFiles/radiantcore.dir/model/export/ModelExporter.cpp.o CMakeFiles/radiantcore.dir/model/export/ModelScalePreserver.cpp.o CMakeFiles/radiantcore.dir/model/export/PatchSurface.cpp.o CMakeFiles/radiantcore.dir/model/export/ScaledModelExporter.cpp.o CMakeFiles/radiantcore.dir/model/export/WavefrontExporter.cpp.o CMakeFiles/radiantcore.dir/model/md5/MD5AnimationCache.cpp.o CMakeFiles/radiantcore.dir/model/md5/MD5Anim.cpp.o CMakeFiles/radiantcore.dir/model/md5/MD5Model.cpp.o CMakeFiles/radiantcore.dir/model/md5/MD5ModelLoader.cpp.o CMakeFiles/radiantcore.dir/model/md5/MD5ModelNode.cpp.o CMakeFiles/radiantcore.dir/model/md5/MD5Module.cpp.o CMakeFiles/radiantcore.dir/model/md5/MD5Skeleton.cpp.o CMakeFiles/radiantcore.dir/model/md5/MD5Surface.cpp.o CMakeFiles/radiantcore.dir/model/ModelCache.cpp.o CMakeFiles/radiantcore.dir/model/ModelFormatManager.cpp.o CMakeFiles/radiantcore.dir/model/NullModel.cpp.o CMakeFiles/radiantcore.dir/model/NullModelNode.cpp.o CMakeFiles/radiantcore.dir/model/picomodel/PicoModelLoader.cpp.o CMakeFiles/radiantcore.dir/model/picomodel/PicoModelModule.cpp.o CMakeFiles/radiantcore.dir/model/picomodel/StaticModel.cpp.o CMakeFiles/radiantcore.dir/model/picomodel/StaticModelNode.cpp.o CMakeFiles/radiantcore.dir/model/picomodel/StaticModelSurface.cpp.o CMakeFiles/radiantcore.dir/model/picomodel/lib/lwo/clip.c.o CMakeFiles/radiantcore.dir/model/picomodel/lib/lwo/envelope.c.o CMakeFiles/radiantcore.dir/model/picomodel/lib/lwo/list.c.o CMakeFiles/radiantcore.dir/model/picomodel/lib/lwo/lwio.c.o CMakeFiles/radiantcore.dir/model/picomodel/lib/lwo/lwo2.c.o CMakeFiles/radiantcore.dir/model/picomodel/lib/lwo/lwob.c.o CMakeFiles/radiantcore.dir/model/picomodel/lib/lwo/pntspols.c.o CMakeFiles/radiantcore.dir/model/picomodel/lib/lwo/surface.c.o CMakeFiles/radiantcore.dir/model/picomodel/lib/lwo/vecmath.c.o CMakeFiles/radiantcore.dir/model/picomodel/lib/lwo/vmap.c.o CMakeFiles/radiantcore.dir/model/picomodel/lib/picointernal.c.o CMakeFiles/radiantcore.dir/model/picomodel/lib/picomodel.c.o CMakeFiles/radiantcore.dir/model/picomodel/lib/picomodules.c.o CMakeFiles/radiantcore.dir/model/picomodel/lib/pm_3ds.c.o CMakeFiles/radiantcore.dir/model/picomodel/lib/pm_ase.c.o CMakeFiles/radiantcore.dir/model/picomodel/lib/pm_fm.c.o CMakeFiles/radiantcore.dir/model/picomodel/lib/pm_lwo.c.o CMakeFiles/radiantcore.dir/model/picomodel/lib/pm_md2.c.o CMakeFiles/radiantcore.dir/model/picomodel/lib/pm_md3.c.o CMakeFiles/radiantcore.dir/model/picomodel/lib/pm_mdc.c.o CMakeFiles/radiantcore.dir/model/picomodel/lib/pm_ms3d.c.o CMakeFiles/radiantcore.dir/model/picomodel/lib/pm_obj.c.o CMakeFiles/radiantcore.dir/model/picomodel/lib/pm_terrain.c.o CMakeFiles/radiantcore.dir/modulesystem/ModuleLoader.cpp.o CMakeFiles/radiantcore.dir/modulesystem/ModuleRegistry.cpp.o CMakeFiles/radiantcore.dir/particles/ParticleDef.cpp.o CMakeFiles/radiantcore.dir/particles/ParticleNode.cpp.o CMakeFiles/radiantcore.dir/particles/ParticleParameter.cpp.o CMakeFiles/radiantcore.dir/particles/ParticlesManager.cpp.o CMakeFiles/radiantcore.dir/particles/RenderableParticleBunch.cpp.o CMakeFiles/radiantcore.dir/particles/RenderableParticle.cpp.o CMakeFiles/radiantcore.dir/particles/RenderableParticleStage.cpp.o CMakeFiles/radiantcore.dir/particles/StageDef.cpp.o CMakeFiles/radiantcore.dir/patch/algorithm/General.cpp.o CMakeFiles/radiantcore.dir/patch/algorithm/Prefab.cpp.o CMakeFiles/radiantcore.dir/patch/Patch.cpp.o CMakeFiles/radiantcore.dir/patch/PatchModule.cpp.o CMakeFiles/radiantcore.dir/patch/PatchNode.cpp.o CMakeFiles/radiantcore.dir/patch/PatchRenderables.cpp.o CMakeFiles/radiantcore.dir/patch/PatchTesselation.cpp.o CMakeFiles/radiantcore.dir/precompiled.cpp.o CMakeFiles/radiantcore.dir/Radiant.cpp.o CMakeFiles/radiantcore.dir/rendersystem/backend/GLProgramFactory.cpp.o CMakeFiles/radiantcore.dir/rendersystem/backend/glprogram/GenericVFPProgram.cpp.o CMakeFiles/radiantcore.dir/rendersystem/backend/glprogram/GLSLBumpProgram.cpp.o CMakeFiles/radiantcore.dir/rendersystem/backend/glprogram/GLSLDepthFillProgram.cpp.o CMakeFiles/radiantcore.dir/rendersystem/backend/OpenGLShader.cpp.o CMakeFiles/radiantcore.dir/rendersystem/backend/OpenGLShaderPass.cpp.o CMakeFiles/radiantcore.dir/rendersystem/debug/SpacePartitionRenderer.cpp.o CMakeFiles/radiantcore.dir/rendersystem/GLFont.cpp.o CMakeFiles/radiantcore.dir/rendersystem/OpenGLModule.cpp.o CMakeFiles/radiantcore.dir/rendersystem/OpenGLRenderSystem.cpp.o CMakeFiles/radiantcore.dir/rendersystem/RenderSystemFactory.cpp.o CMakeFiles/radiantcore.dir/rendersystem/SharedOpenGLContextModule.cpp.o CMakeFiles/radiantcore.dir/scenegraph/Octree.cpp.o CMakeFiles/radiantcore.dir/scenegraph/SceneGraph.cpp.o CMakeFiles/radiantcore.dir/scenegraph/SceneGraphFactory.cpp.o CMakeFiles/radiantcore.dir/selection/algorithm/Curves.cpp.o CMakeFiles/radiantcore.dir/selection/algorithm/Entity.cpp.o CMakeFiles/radiantcore.dir/selection/algorithm/General.cpp.o CMakeFiles/radiantcore.dir/selection/algorithm/Group.cpp.o CMakeFiles/radiantcore.dir/selection/algorithm/GroupCycle.cpp.o CMakeFiles/radiantcore.dir/selection/algorithm/Patch.cpp.o CMakeFiles/radiantcore.dir/selection/algorithm/Planes.cpp.o CMakeFiles/radiantcore.dir/selection/algorithm/Primitives.cpp.o CMakeFiles/radiantcore.dir/selection/algorithm/Shader.cpp.o CMakeFiles/radiantcore.dir/selection/algorithm/Transformation.cpp.o CMakeFiles/radiantcore.dir/selection/clipboard/Clipboard.cpp.o CMakeFiles/radiantcore.dir/selection/group/SelectionGroupInfoFileModule.cpp.o CMakeFiles/radiantcore.dir/selection/group/SelectionGroupManager.cpp.o CMakeFiles/radiantcore.dir/selection/group/SelectionGroupModule.cpp.o CMakeFiles/radiantcore.dir/selection/ManipulationPivot.cpp.o CMakeFiles/radiantcore.dir/selection/manipulators/DragManipulator.cpp.o CMakeFiles/radiantcore.dir/selection/manipulators/ManipulatorBase.cpp.o CMakeFiles/radiantcore.dir/selection/manipulators/ManipulatorComponents.cpp.o CMakeFiles/radiantcore.dir/selection/manipulators/ModelScaleManipulator.cpp.o CMakeFiles/radiantcore.dir/selection/manipulators/RotateManipulator.cpp.o CMakeFiles/radiantcore.dir/selection/manipulators/ScaleManipulator.cpp.o CMakeFiles/radiantcore.dir/selection/manipulators/TranslateManipulator.cpp.o CMakeFiles/radiantcore.dir/selection/RadiantSelectionSystem.cpp.o CMakeFiles/radiantcore.dir/selection/SelectedNodeList.cpp.o CMakeFiles/radiantcore.dir/selection/selectionset/SelectionSet.cpp.o CMakeFiles/radiantcore.dir/selection/selectionset/SelectionSetInfoFileModule.cpp.o CMakeFiles/radiantcore.dir/selection/selectionset/SelectionSetManager.cpp.o CMakeFiles/radiantcore.dir/selection/selectionset/SelectionSetModule.cpp.o CMakeFiles/radiantcore.dir/selection/SelectionTestWalkers.cpp.o CMakeFiles/radiantcore.dir/selection/shaderclipboard/ClosestTexturableFinder.cpp.o CMakeFiles/radiantcore.dir/selection/shaderclipboard/ShaderClipboard.cpp.o CMakeFiles/radiantcore.dir/selection/shaderclipboard/Texturable.cpp.o CMakeFiles/radiantcore.dir/selection/TransformationVisitors.cpp.o CMakeFiles/radiantcore.dir/settings/ColourScheme.cpp.o CMakeFiles/radiantcore.dir/settings/ColourSchemeManager.cpp.o CMakeFiles/radiantcore.dir/settings/Game.cpp.o CMakeFiles/radiantcore.dir/settings/GameManager.cpp.o CMakeFiles/radiantcore.dir/settings/LanguageManager.cpp.o CMakeFiles/radiantcore.dir/settings/PreferencePage.cpp.o CMakeFiles/radiantcore.dir/settings/PreferenceSystem.cpp.o CMakeFiles/radiantcore.dir/shaders/CameraCubeMapDecl.cpp.o CMakeFiles/radiantcore.dir/shaders/CShader.cpp.o CMakeFiles/radiantcore.dir/shaders/Doom3ShaderLayer.cpp.o CMakeFiles/radiantcore.dir/shaders/Doom3ShaderSystem.cpp.o CMakeFiles/radiantcore.dir/shaders/MapExpression.cpp.o CMakeFiles/radiantcore.dir/shaders/ShaderExpression.cpp.o CMakeFiles/radiantcore.dir/shaders/ShaderLibrary.cpp.o CMakeFiles/radiantcore.dir/shaders/ShaderTemplate.cpp.o CMakeFiles/radiantcore.dir/shaders/TableDefinition.cpp.o CMakeFiles/radiantcore.dir/shaders/textures/GLTextureManager.cpp.o CMakeFiles/radiantcore.dir/shaders/textures/TextureManipulator.cpp.o CMakeFiles/radiantcore.dir/skins/Doom3SkinCache.cpp.o CMakeFiles/radiantcore.dir/undo/UndoSystem.cpp.o CMakeFiles/radiantcore.dir/vfs/DeflatedInputStream.cpp.o CMakeFiles/radiantcore.dir/vfs/DirectoryArchive.cpp.o CMakeFiles/radiantcore.dir/vfs/Doom3FileSystem.cpp.o CMakeFiles/radiantcore.dir/vfs/Doom3FileSystemModule.cpp.o CMakeFiles/radiantcore.dir/vfs/ZipArchive.cpp.o CMakeFiles/radiantcore.dir/xmlregistry/RegistryTree.cpp.o CMakeFiles/radiantcore.dir/xmlregistry/XMLRegistry.cpp.o -Wl,-rpath,/home/thebigh/Games/DarkRadiant/libs/wxutil:/home/thebigh/Games/DarkRadiant/libs/xmlutil:/home/thebigh/Games/DarkRadiant/libs/scene:/home/thebigh/Games/DarkRadiant/libs/math: ../libs/wxutil/libwxutil.so ../libs/module/libmodule.a -ljpeg -lpng12 ../libs/xmlutil/libxmlutil.so -lxml2 ../libs/scene/libscenegraph.so ../libs/math/libmath.so -L/usr/lib/x86_64-linux-gnu -pthread -lwx_baseu-3.0 -lwx_gtk3u_core-3.0 -lwx_gtk3u_stc-3.0 -lwx_gtk3u_adv-3.0 -lwx_gtk3u_gl-3.0 -lwx_gtk3u_xrc-3.0 -lsigc-2.0 -lftgl -lGLEW -lGLU -lGL -ldl /usr/bin/ld: CMakeFiles/radiantcore.dir/vfs/DeflatedInputStream.cpp.o: in function `archive::DeflatedInputStream::~DeflatedInputStream()': DeflatedInputStream.cpp:(.text+0x1b): undefined reference to `inflateEnd' /usr/bin/ld: CMakeFiles/radiantcore.dir/vfs/DeflatedInputStream.cpp.o: in function `archive::DeflatedInputStream::read(unsigned char*, unsigned long)': DeflatedInputStream.cpp:(.text+0xaa): undefined reference to `inflate' /usr/bin/ld: DeflatedInputStream.cpp:(.text+0xca): undefined reference to `inflate' /usr/bin/ld: CMakeFiles/radiantcore.dir/vfs/DeflatedInputStream.cpp.o: in function `archive::DeflatedInputStream::DeflatedInputStream(InputStream&)': DeflatedInputStream.cpp:(.text+0x149): undefined reference to `inflateInit2_' collect2: error: ld returned 1 exit status make[2]: *** [radiantcore/CMakeFiles/radiantcore.dir/build.make:4154: radiantcore/libradiantcore.so] Error 1 make[2]: Leaving directory '/home/thebigh/Games/DarkRadiant' make[1]: *** [CMakeFiles/Makefile2:787: radiantcore/CMakeFiles/radiantcore.dir/all] Error 2 make[1]: Leaving directory '/home/thebigh/Games/DarkRadiant' make: *** [Makefile:130: all] Error 2

Not so long ago I found what could make a pretty good profile picture and decided to try it out on these new forums. But I couldn't find a button anywhere that would let me change it. I asked on Discord and it seems Spooks also couldn't find anything anywhere. So I logged into an old alternative account and, lo and behold, that account has a button. This is on the first screen I get when I: 1) click on my account name in the top-right of the browser -> 2) click on 'profile'. Compared to my actual account: Are you also missing this button on your account? It'd be very much appreciated if that functionality could be restored to any of the affected accounts.