KylieNeko

Kylie, who is a Neko

🏳️‍🌈🏳️‍⚧️ Transgender woman. Asexual lesbian. Catgirl. Sometimes makes pizza. Buildy/explorey video gamer. Also doodles sometimes.



New Unity games have a quirk that's nipping me in the bud a lot, so I figured I'd share.

lib_burst_generated.dll

This thing likes to ship with CPU instructions that run on modern CPUs. Okay okay, my CPU is from 2010. I think. Abouts then. Anyways. The thing is, all these games I've run that have this problem run quite cheerfully1 once this file is deleted.2

But most of the games shipping with this enabled do not have any kind of proper CPU detection or error message. They just vaguely crash in the vaguest of ways possible.3

My hardware can run everything I've cared to run on it so far at performance that I am happy enough with.4 And for budget reasons, I'm going to keep on pushing it to go a little bit longer.

But it would be handy if we could figure out something to help the less-technical types. I dunno, something like a first-launch CPU feature detection with a "hey, your hardware isn't supported, if you continue you are Officially On Your Own" type of thing? Cause when I poke around the various forums, the first thing I see when there's a match for my issue is usually Gamer™ "game sucks won't launch ripoff scam" etc type comments.


  1. Acceptable performance in all cases thus far; and honestly, it's the I/O speed to the disk that is more of the problem on my rig.

  2. Several games have since updated with code paths that don't require deleting the file. I don't know if they got a new version of Unity or what, I'm not lurking in the dev communities here, I just know that two of my games I had to manually nudge no longer require that.

  3. And most people don't think to check the Windows Event Logs, or know what they're looking at what they do.5 0xc000001d is an "illegal instruction", and not the only app error that generates here adding to the fun.

  4. And happy enough to point out, if I stream it, that any performance issues that appear are attributable to my aging but still quite viable hardware.

  5. This is actually the foundation of some scams, to have unknowing people look at these logs and see all the errors that are absolutely benign and use that to convince them they are "infected" and need to pay them money and run their scam product etc.


You must log in to comment.