#All units are invisible
1 messages · Page 1 of 1 (latest)
Your CPU/GPU is quite old, not sure if the game will work for you. You can try updating your GPU drivers to the last AMD ones released for your card:
https://www.amd.com/en/support/downloads/drivers.html/graphics/radeon-hd/radeon-hd-6000-series/amd-radeon-hd-6850.html
Try the Crimson Edition 16.2.1 Beta drivers (your logs indicate you are using older drivers, v 15.301.1901.0)
15.3 is the latest. The application "Crimson Edition" is a different version number. 🙁
Can somone put a good log in here? I want to compare. I downloaded the git repo and can maybe figure out the code thats the problem.
All my other machines (much newer) are "work" machines.
#1462555663069876336 message
I have an invisible units issue as well. It happens to me only on specific maps. I wanted to practice for the next Apprentice League, and loaded up Pools of Ilys, where this issue showed up:
I'm on Arch Linux, Nvidia graphics (4070Ti), and a Ryzen 9 7900X.
I tried the appimage from the website, the AUR package (also appimage), as well as the flatpak version. I backed up and moved the .local/state/Beyond All Reason directory for a fresh download of everything, and nothing worked.
This firsts happened to me on Tundra_V2, when I wanted to play the sixth scenario. A couple of days ago, I tried it again, and the units were still invisible, except for a handful of unit types.
@sterile rune This looks like what I was observing on ZK's first scenario, a handful of units invisible in a semi-consistent manner on Nvidia/Linux. It seemed to not be lua related. A log with /debuggl enabled may help look into this further.
It is a common problem, always on certain maps.
I have had this frequently on industrial revolution
And the combo
Linux+AMD+Nvidia
You say "frequently." Does this mean it does work sometimes?
Does happen to me on that map as well!
I say that for some reason it works sometimes, but I don't understand how or why
you use linux?
When I observed it, it tended to occur on first game launched after startup, but not any subsequent games, until another full restart of the game.
I don't observe it at all, ever, on my AMD/Linux system, this seems unique to Nvidia/Linux
no, it happens to me in random situation.
Halfway through the evening, I was watching some Rotato, and on a specific map, it started doing this.
The map was:
mescaline v2
I think the very first time I played on Tundra_V2, in the Back from the Dead scenario, it did work. But ever since restarting the scenario, I could never see my units there again.
But not all units had that issue on that map. On Pools of Ilys, I can't see any units.
yor current driver version?
590.48.01-15
580.126.09
#⭐|main message
grrrr time to start learning how to get out all the debug logs
@north tapir this problem affects more users than we think
Linux+Nvidia?
correct. AMD cpu
Same
But CPU... Idk if the CPU has something to do with the problem
Driver version?
Running on xorg too
The command to reload is
/luaui reload
But don't help a lot
ye gave it a go and nothing changed
I have a fucked up two monitor setup, but this has happened to me on a single monitor too
The only way is a total reboot for now
, have nothing to do with monitoring settings
I'm running these for some other games, but I wonder if they can mess with BAR
Idk what it is...
Nvidia card?
Maybe it is hardware specific
I am not sure about that. BAR always starts on my secondary monitor because it's the 0 x-coordinate monitor and it ignores the setting when I boot. I have to manually select "borderless" the first time I enter a scenario so it actually swaps BAR to the correct monitor, and that transfer is not pretty
But I think it's related to the Linux drivers
I've managed to make very weird things happen by trying to move and resize BAR on my setup
so I'm not ruling anything out at this point
4070 ti is the card though
Well ... I can't help you a lot.
I have the same issue, but no solution for now
sometimes it's not even all units, it just like randomly all maces are invisible with no shadow
Yes I know...
I can also confirm the map dependent behavior. Tundra V2 and Pools of Ilys 1.1.2 trigger it consistently from testing maps mentioned above
Also, I get this warning at the start of every match (regardless if the invisibility bug is happening). Not sure if it's related
Industrial revolution seems fine to me O.o
for what its worth I get this all the time too, had it again today on Pentos V1, it happens to me every time on this map
I concur, also happens on one or two monitors
Linux + Nvidia?
I think AMD CPU.. but not 100 % sure
in fact, Spider who's post we're replying to said he is AMD GPU
Yes, this may have been a mistake. I think the AMD gfx all-units-invisible is a different issue from the Nvidia gfx sometimes-units-are-invisible issue.
I'm doing a bit of confusion at this point
Just need to key myself good at zooming out and then controlling the icons of units (;
Can I have TLDR what I need to run to see it?
I'm on Linux with NVIDIA GPU (CPU brand is irrelevant here)
I reproduce mine the following way:
- Start match on Pools of Ilys
I don't know why you have this invis units, im playing this game since 5 year's on Manjaro/KDE on my Intel i7-6700k with my 2080Ti nvidia and i never had invisible units, no matter which map i played... maybe its related to your graphic presets in bar?
I've gone through all the default presets, and changed most settings manually, going through a lot of restarting, and none of those had an influence on the invis units.
It's also weird that some people report it happening sometimes, while I have it every time.
I'm on X11 as well.
I playing this regularly for year's.... never had invis units
Ah, Intel CPU. All reports I've seen so far have an AMD CPU, including myself.
Though ivand says it's irrelevant, so that might be a coincidence.
I have MSAA disabled btw, you need also to restart the client for certained effects like Anti Aliasing... keep that in mind
going through a lot of restarting
Yeah, those were the restarts I mentioned here.
Are you facing this invis units on All That Glitters also?

There was recently another Linux bug, which was related to AMD GPU's... where the engine had problem's with certain shader effects... it only occured with water effects...
I think your problem might be related to water... but i could be wrong...
Lots of water maps work perfectly fine for me though.
Im good in finding errors, but this problem is filled in dark fog yet... i mean there might me a lot stuff to change... to finally find the culprit... Did you have disable Resizable BAR in Bios?
Not sure, let me check!
Resizable BAR is a UEFI Bios feature for newer GPU's... since im still on legacy bios and i don't have this problems... maybe...
Mine is enabled.
It gives around 2%-7% avg fps in certain games... but i would try to disable it, when its related to this problem... up to you.
You are my hero and savior.
Behold. Visible commander on Ilys.
Cool im glad i could help... im also active in Manjaro Linux Forum and help user's with their Distro's 🙂
@fluid marten @stone lotus @dawn zodiac @north tapir @shadow viper You guys could also try to disable Resizable BAR in your Bios to see if its fix your invis unit's.
Thank you very much for that.
Very cool of you.
Yes, units are still visible when doing that.
WDYM "still", weren't they invisible before?
Oh it was just fixed. I turned off resizable bar in my BIOS, like Kobold suggested, and that worked, as seen in that screenshot.
I am tundraing out of my mind right now. Excellent work people
Happy unit visibility day!
BAR is popular enough to have custom bios settings but not popular enough for them to work with linux 😔
Now I'll never be able to resize my BAR window again. 
It is hilarious that a setting that literally has "BAR" in it was the culprit. 
So you could also fix it with my suggestion to disable Resizable BAR?
correct
I also verified with the /luarules disable
(though I don't understand what that is debugging)
I think /luarules disable was meant to make the units visible while they were invisible. Ivand was unaware it was already fixed, and suggested testing that, I think.
I might re-enable resizable bar tomorrow and try the /luarules disable thing to gather more info.
I can do that now
From my understanding, is spider740 using WinSlop 11 and he also has this problem with invis units or not? Lets see if this is a Linux Only problem or maybe Microslop is also affected.
stand by for the resizening
Yeah, @dawn zodiac's logs say Windows. Yo Spider, do you still have this issue? Two of us could fix it by disabling resizable bar in our BIOS settings!
Interestingly Tundra_v2 was still ok with resizeable BAR immediately after reboot, but Pools of Ilys is fubar as usual
I vaguely remember Tundra_V2 working for me the first time I ever loaded it, but then it stopped working after a reload.
Im not wondering that this bug is unreliable... since Resizable BAR is accelerating the speed to loead Texture's faster into the VRAM... only a clean power shutdown, would reset the situation to default.
As long your VRAM/RAM not cleaned, its hard to predict when this error occured or not.
Map: Pools of Ilys
Resizeable BAR on
First image with normal settings, second image with /luarules disable after /cheat
no visible difference
After that single skirmish with Pools of Ilys now Tundra_v2 is invisible again
Map: Tundra V2
Resizeable BAR on
First image normal settings, second image with /luarules disable
That's enough data I'm switching it back off
With Resize BAR off I did the same thing after restart:
-> Launch skirmish on Tundra_V2 and build two mexes (no problems)
-> Launch skirmish on Pools of Ilys (no problems)
I so far have failed to find the ability to enable/disable resizable BAR in my laptop's bios.
Which Laptop are you using?
Mine was very obvious on literally the front page (not real screenshot but some random google image)
MSI Thin 15 B13VE-1697CA 2024
If you have a Nvidia GPU you can also disable R-BAR in your Distro btw.
the hallucinator and this random video from 4 years ago says you might find it under advanced/pcie/pci sub-system settings, though this BIOS version is not the same
@north tapir You have a Nvidia GPU or not? https://wiki.archlinux.org/title/Improving_performance NVreg_EnableResizableBar=1 is the suggested... so with 0 instead 1 it should be disabled
but yeah probably what kobold said
Yeah, mine doesn't look like that. Looks like this:
Yeah Laptop Bioses/UEFI's looks total different compared to PC's.
`/etc/modprobe.d/nvidia-rebar.conf
options nvidia NVreg_EnableResizableBar=0`
Then regenerate the initramfs so the option is applied when the NVIDIA kernel module is loaded early during boot.
A full power cycle (shutdown and power off) may be required for PCIe BAR resizing to take effect.
TBH im clueless what they mean with regenerate the initramfs... i think thats happening automatical in background after a reboot or not? Sometimes i think this Arch Wiki's are gatekeeping and a little bid hard to understand.
Since you're changing which kernel modules are to be loaded, the initramfs, which is what is initially loaded into RAM at boot, needs to be updated.
Yeah that's what im expecting after reading this... idk if this is a language barrier problem since im not a native english speaker, but i don't understand what exactly mean: regenerate the initramfs... how does it work. Do we have to do another set off command's? Where is the clear advice? For me they always speak in a gatekeeper language when i read this Arch wiki's... making things looks more complicated as it actually be the case.
Clicking on that leads you to a page explaining how to do it. You use mkinitcpio for that.
Yeah i'm using sudo mkinitcpio -P for year's, when im editing certain system files, merging .pacnew files etc. and that's what i'm talking about... instead clearly writing that command in the guide or giving a hot link and pointing straight to mkinitcpio. This guys writing sometimes guide's which relying on insider information and for me its confusing/unclear (gatekeeping). if you not aware that regenerate initramfs means to execute sudo mkinitcpio -P, you are lost... and fuck i'm even a tech nerd.
That's true, the wording could be more exact, given that they say "regenerate" on one page, and then don't use that word in the title of the section they link to. But ctrl+f'ing for regenerate does point you there.
Anyway, to summarize
Recent discoveries:
- For multiple people (including myself), disabling resizable bar in the BIOS settings has fixed the issue seemingly entirely.
- Using
/luarules disable, however, did not solve the issue.
