Upon looking to this further I’m not sure if it actually works as I understood it to, due to the way group services are handled currently in Mastodon. Clearly there is some sort of flag in Activitypub on group accounts to indicate to other apps that it is a group account, because e.g. https://lemmy.ml/c/climatejustice@chirp.social works and you can follow it but the same link substituting /c/ for /u/ does not work. And for normal user accounts, the inverse is true.
However, aside from that flag, my understanding is they are essentially just user accounts that boost any posts from followers that mention the account handle, which causes the boosted post to show in the feed for all followers of the account. Since that account isn’t actually posting the posts that it boosts, I guess it makes sense that activity wouldn’t be visible in Lemmy, where boosts don’t exist. Following this logic no posts would be displayed, and that’s what is observed. Initially I thought this was because no one on the instance had followed the group yet, because e.g. https://lemmy.world/c/BlackMastodon@chirp.social does show posts while https://lemmy.ml/c/BlackMastodon@chirp.social does not. The same group on a.gup.pe also shows more posts on https://lemmy.ml/c/BlackMastodon@a.gup.pe.
It’s hard for me to make sense of what’s going on here (especially as I don’t microblog or use Mastodon personally) because clearly the Mastodon content is federating through the lemmy instance, but I’ve only been able to observe a subset of it and I haven’t been able to figure out the parameters that have caused some posts to be visible in Lemmy but not others.
Kinda sorta required if you want to stream assets from storage, an approach taken by many modern games. Might not be absolutely necessary depending on your setup / game settings. BG3 also said SSD required but there’s a “Slow HDD Mode” in the settings anyway, which I believe just shifts more of the streaming burden to RAM/VRAM. If you played on a HDD without enabling it, I guess you’d expect to see inconsistent pop-in as individual assets try to stream in faster than your storage can read. But playing with it enabled might also cause performance drop if your RAM/VRAM was already close to full utilization with the setting disabled