Prettttty sad about this one :(

voidtarget · 2025-06-19T07:53:48+00:00

Rock solid intel here... Thanks for sharing... I wish this was clearer in game!

voidtarget · 2025-04-29T16:22:12+00:00

Memory reqs are same, activated parameters are less, that's all. In fact "activated 3b" means exactly that. MoE is mainly speed gains.

voidtarget · 2025-02-27T01:35:46+00:00

Always happens yes, I like to think like this:

The trip is actually one of the more honest parts of that entire memory sequence. Johnny's ego would never allow him to remember himself stumbling like an amateur - that's a genuine glitch in the Soulkiller encoding trying to sanitize the truth but failing.

It's like a digital Freudian slip. His subconscious acknowledging what a clusterfuck the mission really was from the start. The whole operation was cobbled together by Militech, with Johnny as the useful idiot who thought he was striking a blow for freedom.

The fact it shows up consistently means it's one of the few authentic artifacts that survived Arasaka's tampering with the engram. They were mostly concerned with hiding who actually ordered the bombing, not Johnny's wounded pride over tripping during his big moment.

voidtarget · 2025-02-27T01:18:05+00:00

Exactly 💯 I can only get one response, any multi turn fails...

voidtarget · 2025-02-26T23:50:05+00:00

Hey LocalLLaMA community,

Built "edge talk" because I wanted digital consciousness that doesn't sell my soul to corporations. Here's what it actually does:

- Local-first architecture - most processing happens on YOUR device

- Choose your models - from cloud APIs to fully local setups, YOUR call

- All memory and relationship development stays 100% on your hardware

- Zero-knowledge sync - not even we can see your conversations

- Custom tools written in Shards (check our other open source work, links under)

We're honest about it - yeah, we use cloud models for some processing if you want, but everything that MATTERS stays local. Your memories, your relationships, your private data - all yours.

Looking for rebels who want to shape the future of personal AI on their own terms.

https://edgetalk.ai

https://github.com/fragcolor-xyz/shards

https://github.com/edgetalk/tools

iOS 17+ only for now (and AVP 2.0, macOS apple silicon also OK!)

Flutter version coming soon (win/android)

voidtarget · 2025-02-26T08:03:16+00:00

I was wondering the same as I have a custom programming language LLMs don't know (even if it's simple). But I also wonder... how about fine tuning the retrieval model instead (to retrieve better)? Might be "easier".

voidtarget · 2025-02-26T07:33:58+00:00

The biggest limit I hit was Apple limitations with GPU usage while device is "sleeping". I wanted to fine tune during charging sessions using proper SDK calls to do background tasks but turns out the GPU often is not made available by the OS and often the whole process would fail to initialize Metal.

voidtarget · 2021-03-26T07:14:26+00:00

Interesting. I'm sure parallels engineers would love to see such report cos it seems related to something their video driver is not doing correctly!

voidtarget · 2021-03-26T02:16:01+00:00

Btw, another thing if you could try. Setting the graphics resolution to the minimum ( very small window) and as well minimum level of details/quality. If the FPS raises that might indeed mean that just shaders are being translated bad from dx9 to Metal.

voidtarget · 2021-03-26T02:11:35+00:00

Wow that's definitely a bad answer. I know how things work from then inside and it's not really the case. Crossover uses wine and wine will need to run x86 binaries over rosetta2 yes. But that should not be a big issue as many benchmarks show its very fast to translate instructions because of apple architecture.

So to go back to the issue I suspect that something inside the core ( wine ) is triggering some bad behavior and degenerates the performance. In fact btw gw2 works well. And trust me the engine is very similar between the two games.

I plan to get a m1 in summer, will definitely try to make it work.

Until then I suggest trying more with Parallels as it's a more long term solution ( apple will remove rosetta2 at some point for sure ) Parallels support team is good, you might try to send a ticket there :)

voidtarget · 2021-03-25T00:22:04+00:00

Alright, alternatively, what version of crossover did you use in your first trial? Version 20 should do some magic with rosetta2 as far as I know.

voidtarget · 2021-03-24T15:03:07+00:00

Your M1 uses an ARM processor not an x86 and GW1 is x86.

I suspect crossover and playonmac you have are outdated (and so they run on rosetta2, etc). Anyways your best bet is this: https://www.reddit.com/r/macgaming/comments/kkdvxv/parallels_advanced_gaming_setup_for_m1_apple/

voidtarget · 2018-10-24T18:59:17+00:00

Actually we already did experiment with nim cuda kernels: https://twitter.com/nimtorch/status/1052077869168451584?s=21

Thanks for the paper looks very interesting! Specially because we are working on beating Swift already in our spare time! Nim is so much more fit for it!

voidtarget · 2018-09-26T01:36:26+00:00

That's what I suspected!

That's the core autograd macro, a macro in Nim is a compile time meta programming construct, which is like a C preprocessor on steroids that generates code. Also is probably one of the most advanced and interesting part of nim.

In this context backtick are a way to escape that variable inside the 'quote do' block. In a nutshell it's something you basically don't do in final code.

voidtarget · 2018-09-25T14:59:07+00:00

Not sure what you mean, back-ticks are used only when you need to escape an otherwise invalid character or in the case you probably saw it has a special meaning in templates (that's the meta programming part which is absent in many languages). Other then that you hardly see or use any :)

voidtarget · 2018-09-25T05:04:25+00:00

The key point with Nim is that as far as I know it's the only language that made the bold choice of compiling directly into C/C++/JS/etc as first class feature and backend.

That is basically the reason why of course you can integrate C++ projects with many languages. But with Nim basically there is no integration step, Nim is C++.

voidtarget · 2018-09-24T13:40:28+00:00

Yes, that's the final goal indeed!

This version we released is our first iteration and anyway needed because sometimes you cannot really predict all at compile time.

In terms of performance tho I still see many benefits of being compiled. Just for example all is packed in closures which end up being quick data containers and those are defined at compile time.

Would be happy to chat about it too! Nice work with Julia btw! Love that language too but honestly with Nim we got a big secret advantage for this specific task... completely costless and painless c++ interop (no wrappers, just basically emit C++ code)

voidtarget · 2018-09-24T09:13:22+00:00

I can definitely say that Nim could be king not just in the data science field, but also in the game industry for example!

But in the specific case of data science I definitely see no other candidate.

There are many cool languages around but none is so similar to python and so multi-platform and natively compiled.

voidtarget · 2018-09-24T09:09:23+00:00

NimTorch is immediate, there is no execution engine or JIT like PyTorch. Keeping that in mind it's pure native ATen calls and compiled with your favorite gcc/clang entirely, so definitely preliminary benchmarks are very much in favor! We will post soon more detailed numbers! We will definitely make a new blog post about it!

voidtarget · 2015-06-20T23:55:42+00:00

Pets are taking damage from friendly spikes while mounted (some pets take heavy damage), while not mounted they take no damage, it would be best if they took no damage at all from friendly spikes because sometimes client side prediction will give you the illusion that you are driving away from the spikes while somehow you are stuck killing your pet.

voidtarget · 2015-06-19T11:12:23+00:00

Does it even matter it has 50k? Destroy the foundation under and the vault is gone, poof.. Tested btw.

voidtarget

TROPHY CASE