MoltenVK VS nix

You could try replacing the wrappers libMoltenVK.dylib found in /Frameworks with the one I’d just uploaded https://github.com/The-Wineskin-Project/MoltenVK/releases/download/v1.2.3/macos-1.2.3-g5cbeaaa-UE4hack-zeroinit-dxvk.tar.xz

Here's the Roguelike third-person shooter Unreal Engine 4 game called Crab Champions that seems to be working thanks to the people who made the UE4 Moltenvk fix (https://github.com/The-Wineskin-Project/MoltenVK/releases).

However, it looks like the latest libMoltenVK (macos-1.2.3-g7b9a415a-UE4hack-Wideline-zeroinit) (huge thanks to Gcenx and nastys/italomandara!) allows the game to work almost perfectly (at least in the few minutes I've been testing).

There’s no need to build MoltenVK from source you can grab prebuilt archives from https://github.com/The-Wineskin-Project/MoltenVK

If this game uses DXVK then try using the following build https://github.com/The-Wineskin-Project/MoltenVK/releases/download/v1.2.0/macos-1.2.0-pr1678-UE4hack-Wideline-zeroinit.tar.xz

You could instead grab an archive from my mirror https://github.com/The-Wineskin-Project/MoltenVK/releases

https://github.com/Gcenx/MoltenVK/releases/tag/v1.1.7 apply these to your crossover and see how it works.

I was testing this version of MoltenVK (Macos_dxvk_patched-1.1.8.tarxz) (https://github.com/Gcenx/MoltenVK/releases/tag/v1.1.8) and I was able to able to get in the game. Before this the game was able to get to the Manu but would just black screen after starting.

The same is true for MoltenVK don’t use the upstream releases/VulkanSDK, instead use https://github.com/Gcenx/MoltenVK

> https://github.com/NixOS/nix/pull/9911#issuecomment-19252073...

As we covered in my last post, NixOS is a amazing Linux distribution for creating stable and declared environments. Now while this is amazing for a desktop setup, it is also perfect for a home-server or home-lab.

(Nix itself is slowly chugging along with Windows via MinGW - https://discourse.nixos.org/t/nix-on-windows/1113/108 and https://github.com/NixOS/nix/issues/1320 , for example.)

Nix is a cross-platform package manager. It uses the nix programming language. Nix and NixOs are often used in the same context, but while the first is a package manager, the latter is a linux distribution based on nix.

Today I want to talk to you about Nixos. What is it? Nixos is a declarative and reproducible OS, partly taking the words used on their own page. What does that mean?

Software developers often want to customize:

1. their home environments: for packages (some reach for brew on MacOS) and configurations (dotfiles, and some reach for stow).

2. their development shells: for build dependencies (compilers, SDKs, libraries), tools (LSP, linters, formatters, debuggers), and services (runtime, database). Some reach for devcontainers here.

3. or even their operating systems: for development, for CI, for deployment, or for personal use.

Nix provision all of the above in the same language, with Nixpkgs, NixOS, home-manager, and devShells such as https://devenv.sh/. What's more, Nix is (https://nixos.org/):

- reproducible: what works on your dev machine also works in CI in prod,

- declarative: you version control and review your configurations and infrastructure as code, at a reasonable level of abstraction,

- reliable: all changes are atomic with easy roll back.

Hopping from one distro to another with a different package manager might require some time to adapt. Using a package manager that can be installed on most distro is one way to help you get to work faster. Flatpak is one of them; other alternative are Snap, Nix or Homebrew. Flatpak is a good starter, and if you have a bunch of free time, I suggest trying Nix.

- it reduces bloat, because you can generate an environment or OS image with only the software needed to run a specific program or service

My guess is that a big efficiency gain would come from the second point, because you don't waste CPU on code that you don't use.

Does this make sense? Has anyone explored this?

[0]: https://nixos.org

1) Setting up the development environment - I currently use devcontainers for most things, but may also dig into nix -> isolated, portable, repeatable development environment 2) Exploring Echo - understand routing, requests, response, etc. 3) Incorporate Templ - integration with Echo, template composition, etc. 4) Integrating TailwindCSS - config for use with Echo/Templ, development cycle, deployment, etc. 5) Add in HTMX - endpoints, template structure, concepts, etc. 6) hyperscript for interactivity - client side interactivity

"Your greatest challenge lies ahead -- and downwards..."

Oh, wait a second, my bad, that's the quote on the box cover for Zork I: (

https://upload.wikimedia.org/wikipedia/en/a/ac/Zork_I_box_ar...

https://en.wikipedia.org/wiki/Zork

)

What you really wanted was a link to where you could download Nix/NixOS -- and/or learn more about it!

Here ya go!

https://nixos.org/

"Your greatest challenge lies ahead -- and downwards..."

:-) :-)

I say all of the above in the spirit of humor -- and as a NixOS user and fan!

(But yes, there is a learning curve to it, so yes, learning Nix/NixOS could be a challenge!)

((But you're a bright person, you have Google and ChatGPT to assist you, and you like challenges!))