OrbWeaver

That's actually quite hilarious — using your credits to openly list all the unlicensed content you stole from other games. I wonder if the modelling section of the credits says "Thanks to ThePirateBay for providing the cracked copy of 3DS Max we used for all our custom models".

That layout is possible. You need to: Drag the camera view and dock it at the bottom right. Drag the properties panel and dock it at the bottom left. This will leave a vertically split window, with the properties panel and camera view at the bottom, and a single wide XY window at the top. Choose View -> New XY View to create a new XY window, and drag this window to dock at the top right, leaving the default XY window at the left.

XYWnd.cpp no longer exists, it was renamed to OrthoView.cpp. The Visual Studio project will need to be updated to point to the new name otherwise it will try to compile a file which no longer exists.

If there are missing files reported, it's likely the .vcxproj needs to be updated with moved or renamed source files. Unfortunately I'm not in a position to do that (without guessing) because I only build on Linux which uses an entirely separate (CMake) build script. I don't know the cause of the other errors but I would guess they are downstream consequences of not having all the required source files in the build script.

The old-style view layouts no longer exist since the UI has been converted to use fully customisable dock widgets for all major UI elements.

I think we'd need to see the mesh and the UV map as well, in order to properly diagnose this issue. But it's quite likely it is a clamping issue, as LDAsh suggests. I wouldn't be surprised if you have "clamp" in your MTR file. Note that if your texture doesn't use an alpha channel (and it seems this image doesn't), DXT5 is just a waste of space compared to DXT1. Also this image doesn't tile properly and won't look good as a texture even if you solve the clamping issue.

Yes, I'm familiar with this sort of junk-science "analysis" assembled by journalists or random tech companies counting stuff in a database and using it to form some kind of conclusion. Side note: one of the dumbest articles I ever read was some lazy tech journalist trying to decide which Steam games were popular based entirely on the average total play time (in hours and minutes). He concluded that everybody hated "HL2: The Lost Coast" because the average play time was about 15 minutes, without bothering to check that The Lost Coast is actually a short tech demo that can be completed in a few minutes, so obviously people aren't going to rack up hundreds of hours playing it. For example, consider these numbers: So they count "Debian", which is an entire distro with thousands of packages, separately from "the Linux kernel" which is one component of a Linux system and already included in every other Linux distro. Does that mean the 2357 kernel vulnerabilities need to be subtracted from the 3067 Debian vulnerabilities, or have they already done that? Do the Debian vulnerabilities include only the kernel, core packages, or every package in the distribution (including Firefox, Thunderbird etc)? The article doesn't say, and the source data is not available since this is just a second-hand report of an "analysis" done by a random VPN company, not a proper scientific study. In any case, comparing an entire Linux distro with just "Windows" isn't a valid comparison, because a Linux distro includes thousands of third-party packages. In order to make that a fair comparison you'd also need to include Microsoft Office and everything in the Microsoft store under the "Windows" heading. I realise that everybody hated Windows 8, but I'm fairly sure that it didn't somehow magically vanish from history. So they're potentially including a full 16 years of extra vulnerabilities to Debian, by ignoring all versions of Windows released before 2009? Yeah, I'm sure that makes absolutely no difference to the analysis. No shit, Sherlock. They got something right at least. Nobody should be complacent about security, since all modern operating systems and software are affected by vulnerabilities, and need to be kept up-to-date with security patches.

You need to install the darkradiant-plugins-darkmod package.

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?

That's odd, because when I was working on the footsteps years ago, I was definitely adding volume decls to lower the volume of sounds. Perhaps something has changed since then regarding how the code interacts with sound shader keywords. I do recall that there are problems with using sound shaders to increase volume, as others have reported, which is why it's a good idea to make sure your original sound files are fully normalised (volume maximised) before they go into the mod.

Oh I see, that's fine then (at least with regards to my concern about GUI duplication — I have no idea if the switch from text to xData would cause any other problems).

I'm not really up to speed on exactly what goes into an xData file, but do you mean that each readme would include its own copy of the scroll buttons and their required functionality? Because that's definitely the wrong solution to this particular problem from an engineering perspective. If a readme is only intended to include text, then that's all that should appear in the file, not text plus a load of GUI boilerplate which will be identical in every readme and will probably just have to be copy-pasted from somewhere else. It should be up to the game engine to display the text in an appropriate way, including adding a scroll mechanism if it is needed.

While that may be an acceptable solution for you, it is the worst possible way to reduce the volume of sounds. You are introducing serial recompression artifacts for no benefit, and the process is unnecessarily cumbersome if you want to experiment with several different volume levels. Instead, you should just edit (or add) the volume field in the respective .sndshd files, which changes the volume in-game without touching the sound files. For example, "volume -3" will make the sound approximately half as loud. This is a one-line change which is quick and easy to test and does not introduce any compression artifacts.

Language models are a mirror, reflecting the collected works of humanity back at us. Some people look in that mirror, see their own reflection, and conclude "there is a artificial person behind this sheet of glass that looks and behaves exactly like me... our days as humans are numbered!". But it's not true. It's just a reflection. It can't create anything that humans couldn't (or haven't) created to begin with. I have no doubt that one day, artificial human-like intelligence will exist, but it will require a lot more than just a language model remixing stuff on the internet. If you're a cargo cult programmer copy-pasting junk code off Stack Overflow, or a hack blog writer churning out articles with titles like "20 dumb things Trump has said", AI is coming for your job — but that's because your job wasn't worth anything to begin with.

Doesn't reproduce in a developer build from source or the 3.8.0 Ubuntu package, so I guess this is something specific to the FlatPak version.

The relevant code is in CamWnd.cpp (starting with the CamWnd::startCapture method) which makes use of a class called FreezePointer which can be found in the wxutil library. It's not possible to be any more specific than that because I have no idea what would be causing the problem. Presumably it's either (1) a logic error in our code which is being exposed by Wayland handling mouse events in a subtly different way, or (2) a fundamental incompatibility between wxWidgets, GTK and Wayland over which we have no control.

I don't generally use Wayland myself due to the numerous applications which have problems with it, but I tried logging into my Ubuntu GNOME desktop using the Wayland session and I do not see any problems with the view rotation or mouse capturing in DR. Which unfortunately means this will probably only be solved if a developer with a system similar to yours is able to investigate it.

As a workaround, does changing the setting "Freelook mode can be toggled" make any difference to the behaviour? This disables the right-click toggle mode and requires you to hold and drag with the mouse to rotate the view.

On modern Windows you should be able to install the Windows Subsystem for Linux which will make it possible to run many Linux commands on Windows.

I agree. It seems that artist control of specular has been removed for the sake of "cool HDR effects". If a mapper wants to make a texture with zero specular, it should have zero specular in the engine.

Does the bright area appear to move over the texture as you move the camera around, or does it remain in the same place? The defining feature of specular lighting is how it varies based on the positions of the viewer, surface and light source. If the bright area appears to move, then this is specular lighting; if it is fixed in place, it is diffuse lighting. Specular lighting is not defined by brightness. It is possible to have a very bright diffuse texture which will max out to full white under a light source (as in your image), just as it is possible to have a very dull specular texture which is difficult to see even in darkness. From a rendering perspective, there is no real distinction between "intensity" and "color" other than the fact that "intensity" affects RGB channels equally, without changing the apparent hue. There would be no increase in render quality by having a separate intensity value that was tracked and calculated independently of color. However, recent DarkRadiant versions add a slider into the Light Inspector which allows mappers to vary the brightness of one or more lights without having to use the color chooser or risk changing the hue. This is purely a user convenience feature, and does not unlock any new rendering possibilities (the intensity changes are just baked into the RGB color applied to the light entity).

Actually I might be confusing two different things. What the latest LWO exporter fixes is the smoothing angle. Previously this was hard-coded at some weird value slightly less than 90°, but this can now be configured to smooth everything, smooth nothing, or use the Autosmooth Angle setting on the object. I have no idea if explicit smooth groups are supported, or if this is even a thing in Blender.

As far as I know the most up-to-date one is the script I maintain (there is a single tdm_export script which supports both ASE and LWO export). However I haven't specifically tested with the latest Blender 3.4 series, so it's possible that it will need an update. I believe this information is out of date. The problem of LWO losing smoothing information was caused by the Blender exporter itself ignoring object-specific data and enforcing a hard-coded smoothing angle. This is now fixed in my latest version, although the old behaviour is selectable at the time of export if you don't want to deal with object smooth groups. As far as I can recall, when I was testing this, the smoothing options did take effect in the engine (although I couldn't say whether they were 100% mathematically correct).

Would you be able to attach or upload the map (or any other map which shows the same issue, if you don't want to share a WIP)? Even if the map has become corrupted, we ought to be able to handle this more gracefully and perhaps recover whatever data we can read even if some is missing. Under no circumstances should we hard crash regardless of what sort of corruption is in the map file.

This was the relevant SVN change: r9525 | orbweaver | 2021-07-30 21:17:43 +0100 (Fri, 30 Jul 2021) | 11 lines Use correct format for uploading precompressed ATI2 normal maps When the 'ATI2' FOURCC is seen in a precompressed DDS file, use the GL_COMPRESSED_RG_RGTC2 internal format (matching the behaviour of image_useNormalCompression on uncompressed source images). The legacy code was using GL_COMPRESSED_LUMINANCE_ALPHA_LATC2_EXT. This is enough to get plausible looking normal maps with DDS files exported in 3Dc/BC5 format using the GIMP DDS plugin. Not tested with files exported from any other tools; it is conceivable that other FOURCCs might need handling too. Note in particular the comment about this only being tested with the GIMP DDS plugin, and that formats used by other tools might need additional changes.