#BAR no longer launches - stays at black "Spring" window.
1 messages · Page 1 of 1 (latest)
-uplog
You appear to have some degree of data corruption.Open BAR game folder, delete the pool and pkgs folders and run the launcher again, this will redownload the game content
your config is erroring out, is your hard drive health okay?
Thanks for your response, yes the SSD seems fine as all other games load perfectly on it, I also uninstalled and reinstalled the game on another SSD and the same issue occured.
I deleted the pool and pkgs folder, the game redownloaded but hitting start still causes the same error. It was working perfectly fine just a couple days ago:
Does the file Beyond All Reason/LuaMenu/widgets/chobby/components/configuration.lua exist for you locally? Can you delete it?
Since you said you just updated AMD drivers perhaps try uninstalling and reinstalling the latest version.
lemme check what are the config lines it's bitching about
ok
it's shitting itself on autodetecting your resolution
aaaand i actually can't see your monitor resolutions information in the log either
and that's where it's actually grabbing that information from
so now the question is, why?
it's either drivers, or the way your have connected your screen
@open gale
considering that it worked before
i'm gonna bet on drivers
meanwhile this part looks like this for me
sooo the engine can't see your monitor(s)
for whatever reason
Aha!
This was the problem - I have a VR headset connected to my PC and BAR got confused. It was the only game having the issue and that's why I assumed it was a problem with the config (uninstalled, reinstalled on another SSD, erased all files, etc).
I unplugged my headset, and BAR started up happily.
Thank you @north kernel and @broken pivot !
huh
interesting!
weird that it didn't show any screens though
you can see in my log it shows two
i have two
but oh well
glad you found what's causing this
I know - although the Index does some weird screen-fu with monitor setups.
If anyone else reports the same weird black screen as me, good first place to look.

Good observation, I missed that entirely
I wonder why it can't detect the index's resolution
i wouldn't be surprised if it doesn't report it when it's off
xD
and the engine is confused