In case anyone else is wondering, or simply doesn't like reading screen shots of text, this is apparently a real report:
I don't understand this item listed under Long-Term Goals:
Build PureDarwin on BSD/linux.
Does this mean porting their not-yet-created desktop environment to a BSD variant and Linux? Are they planning to abandon the Darwin kernel, or do they intend to maintain their DE on three different kernel/library stacks?
This might be an unpopular opinion, but I feel Tears of the Kingdom is overrated. Yes, it has some welcome quality-of-life improvements, and yes, it has more content than its predecessor, but I find the characters less interesting, the environments less inspired, and the encounters more repetitive. Every time I pick it up again, I get bored within a couple hours and go back to another play-through of Breath of the Wild.
I would vote for Baldur's Gate 3 over TotK without hesitation.
Resource and memory management were completely rewritten in order to use allocated video memory more efficiently:
Note: Defragmentation is currently disabled on Intel's ANV driver, see #4434. The dxvk.enableMemoryDefrag config option can be set to enable or disable this feature via the the Configuration file.
While technically not required, the new memory management works best on drivers that support both VK_EXT_memory_budget and VK_KHR_maintenance5. The Driver Support page was updated accordingly.
Support for emulated cursors was implemented for the D3D9 cursor API, which allows games to set an arbitrary image as the mouse cursor. This fixes an issue in Dungeon Siege 2 (#3020) and makes the cursor appear correctly in Act of War and various older D3D8 games. (PR #4302)
Unreal Engine 3 games using D3D9 have a quirk in that they pass a seemingly uninitialized value as the mipmap LOD bias. In order to avoid creating more Vulkan sampler objects than the driver supports, previous versions of DXVK would round the LOD bias to a multiple of 0.5, which could introduce visual inaccuracies. As a more correct soluition, DXVK will now destroy unused Vulkan samplers on the fly and use the correct LOD bias.
Note: The aforementioned workaround was never needed or used in the D3D11 implementation, it only affected D3D9.
In order to reduce system memory pressure and improve stability in 32-bit games, creating, uploading and discarding resources is now throttled if the amount of temporary staging memory allocations exceed a certain threshold. This fixes crashes in Total War: Rome II and a number of other games. Additionally, large DYNAMIC textures commonly used for video playback will no longer use a staging buffer.
The d3d11.maxDynamicImageBufferSize and d3d11.maxImplicitDiscardSize options were removed accordingly; affected games such as Total War: Warhammer III and Ryse: Son of Rome should now perform well by default, without excessive memory usage.
Note: These changes negatively affect CPU-bound performance in a number of games, including Shadow Warrior 2.
SEQUENTIAL swap effects are now implemented for DXGI swap chains, which allows games to read previously presented backbuffers. This fixes an issue wherein savegame thumbnails would appear black in certain visual novels. (https://github.com/ValveSoftware/Proton/issues/7017)EvaluateAttributeSnapped.VK_EXT_pageable_device_local_memory is now used to enable better driver-side memory management.I read his message. He didn't seem grumpy or frustrated to me; just encouraging folks to use a certain style that's already in wide use, for reduced noise and better consistency.
Please unblock challenges.cloudflare.com to proceed
(grumble, unblock, reload)
Verify you are human
(click)
...spin...spin......spin...
Verify you are human
(click)
...spin...spin......spin...
Verify you are human
(click)
...spin...spin......spin...
Verify you are human
(click)
...spin...spin......spin...
Verify you are human
(click)
...spin...spin......spin...
I hope they're using this time to learn lessons from their Starfield flop and gather the talent and budget needed to improve upon Skyrim. A modern engine probably wouldn't hurt.
However, my expectations are very low at this point.
Not quite as important as the right to repair, but close in spirit: I would love to see a legal requirement for shut-down online games to release the server specs needed for the community to replace/maintain them.
Edit: And data export for existing players, so our game progress can be reconstructed on community servers, of course.
Threads? How disappointing. The White House would do better to operate its own fediverse presence.
The second comment on the page sums up what I was going to point out:
I'd be careful making assumptions like this ; the same was true of exploits like Spectre until people managed to get it efficiently running in Javascript in a browser (which did not take very long after the spectre paper was released). Don't assume that because the initial PoC is time consuming and requires a bunch of access that it won't be refined into something much less demanding in short order.
Let's not panic, but let's not get complacent, either.
The notion that creating a half-decent application is quick and easy enough that I would be willing to transform their idea into reality for free.
Once again, a bad thing disguised in a "protect the children" narrative.
https://www.eff.org/deeplinks/2024/02/dont-fall-latest-changes-dangerous-kids-online-safety-act
I sincerely hope that believing reddit to be representative of the C++ community is not a widely shared notion.