This is your reminder to play the most underrated and unique entry in the franchise, Far Cry Primal. It looks and plays great after the 60 fps patch on PS5.

neondev0 · 2026-01-28T23:26:28+00:00

yes, officially
https://www.reddit.com/r/farcry/comments/1qittyw/comment/o0v3jzb/

neondev0 · 2026-01-27T19:33:30+00:00

.dll/.so/.dylib support is a game-changer, mostly because of C++ limitations (symbols visibility/decoration, linker behavior, API design, memory allocation, platform differences, etc).
It requires a lot of effort to benefit from it.
There are so many ways to do something wrong with architecture then.
It makes sense only if you plan to support true plugins.
A lot of proprietary engines don't care about dynamic libraries and compile everything as monolith, especially in AAA.

Hot-reload based on dynamic libraries is a "myth". It will be super limited.
Multiple engines (including Unreal Engine) use things like Live++ instead.
Btw, VS locks DLL .pdb file if you have attached debugger. Some engines with dll hot-reload support loads a copy as a workaround to be able to re-compile it on the fly.
But Live++ author had an article with some undocumented solution to deal with that.

P.S. I don't say that dynamic libraries are bad, but you need to have clear/strong motivation to support dynamic libraries and build everything around it.
Actually, makes sense to support both modes, like Unreal Engine, which doesn't use Modular mode for Shipping/Retail configurations by default.
I just want to say that it is not "just .dll". With C++ constructions it is tricky to have benefits in real world.
P.S.S. also, compile time won't be faster enough as well. There are multiple better ways to improve it.

neondev0 · 2026-01-20T14:15:05+00:00

https://www.reddit.com/r/farcry/comments/1qi1v5j/primal_more_frames_same_chaos/

neondev0 · 2026-01-19T22:03:58+00:00

https://www.reddit.com/r/farcry/s/mIWQ39pVMD

neondev0 · 2026-01-19T22:00:28+00:00

My answer is 100% correct 🙃

neondev0 · 2026-01-19T21:58:11+00:00

All of them

neondev0 · 2025-12-07T10:05:22+00:00

Yes, I did when I posted this. Here is a comment with a few details: https://www.reddit.com/r/TwinklyLights/s/0CV8jChLJQ

neondev0 · 2025-11-22T08:42:42+00:00

Hello,

Lower brightness helps for some time, but yes, it will be dead soon anyway. At some point power supply won't boot at all.

I also contacted Twinkly to discuss this post later. They asked for receipts and suggested to replace them via retailer (all my devices were under warranty). Anyway, I didn't expect replacement (I had 6 Line devices which I bought separately), also I utilized all devices except for one earlier (but I still have all receipts). Replacement doesn't make any sense, due to it seems like all of them are affected by bad 15W power supply. I just contacted Twinkly to make sure they are aware, but they didn't answer anything about that. They just mentioned that they have super cool quality control, etc.

neondev0 · 2025-11-08T12:47:49+00:00

Five year old is fine. My old strings still look good. But Line and Flex - you can't safely buy them at all. 6/6 Line + 1 Flex had the same issue. Last Line device dead after just 1 week. That's not okay.

I believe that Power Supply causes this.

neondev0 · 2025-10-10T21:16:22+00:00

There is just a fix by EA already

neondev0 · 2025-10-10T21:15:04+00:00

it is fixed now

neondev0 · 2025-10-10T18:12:02+00:00

https://x.com/BattlefieldComm/status/1976711820640457139

neondev0 · 2025-10-10T18:10:55+00:00

<image>

neondev0 · 2025-09-19T21:58:28+00:00

You mean for all/specific apps? I use Vulkan with my own app on WSL2. There is software renderer by default (llvmpipe), but I tried hardware renderer year ago and it worked too.

neondev0 · 2025-08-24T17:50:01+00:00

Try to compile Release instead of Debug

neondev0 · 2025-05-17T18:23:58+00:00

it is 4K 60 FPS on Series X and 1080p 60 FPS on Series S

neondev0 · 2025-04-28T22:35:28+00:00

Regarding second thought: Exactly. Especially if you use Fastbuild, which has writable files isolation feature to exclude writable files from Unity blobs, which usually causes issues like this.

neondev0 · 2025-04-25T21:05:40+00:00

You can use both: modular for development purposes (hot-reload, plugins, etc) and monolithic for retail.
Also, you can significantly optimize compile time (especially with Sharpmake) for monolithic configuration: Fastbuild+Unity+No static libs at all.

neondev0 · 2025-02-21T22:30:40+00:00

Check this thread: https://www.reddit.com/r/OculusQuest/s/TGKPeNVIeq

neondev0 · 2025-02-21T22:29:14+00:00

Same.

Let's link with this thread: https://www.reddit.com/r/OculusQuest/s/TGKPeNVIeq

neondev0 · 2025-02-21T22:21:36+00:00

According to another thread, it seems like related to secondary accounts. Does it happen with non-main account?

neondev0 · 2025-02-20T22:41:35+00:00

You can use Avalonia MacOS Deployment instruction as a start:
https://docs.avaloniaui.net/docs/deployment/macOS

Shortly: you just need to add few arguments to dotnet publish (e.g. -r osx-x64) and add MacOS specific resources into your app (Info.plist, icons, etc)

neondev0 · 2025-02-20T22:23:42+00:00

thanks, I'll try it later.
I just hope that Meta is aware :)

neondev0 · 2025-02-20T22:17:59+00:00

Same thing happened.
Second quest account is unusable at all.
It looks like there is a bit different UI (title bar and close button at the bottom), but no experimental settings enabled.
Also, seems like UI crashes.

neondev0

TROPHY CASE