I’m perfectly ok sitting though those videos the first run of the game… After that I really hate them and they get in the freakin way, espestally when you can’t skip them.
Is there a command-line tag to skip/disable the those videos? Right now its really annoying that right-click joining still requires me to sit through all those videos. Maybe when the game doesn’t crash (GL error) so often this won’t be as bad.
To disable Startup Videos from playing
Go to C:\Program Files (x86)\Steam\steamapps\common\brink\base\video\assets
(or where ever Steam is installed)
Rename pubdevlegal_splash.bik to something like pubdevlegal_splash.bik.BAK
It seems that you need to set it in the launch options to work.
+set com_bootLogo 0
Bear in mind that renaming your videos folder will prompt Steam to reacquire several GB of Bink videos each time you update. For this reason it’s not recommended.
[QUOTE=murka;299257]It seems that you need to set it in the launch options to work.
+set com_bootLogo 0[/QUOTE]
Perfect!!! that worked thank you.
I tried the other way first then when I seen this option I went back to revert my file too see there is another one there. Must have released an update, hopefully the game will be stable for me.
How about the between match videos? It’s annoying having to ‘press any key’ then mousing over to the skip button to skip voiceover screen. I’d like to be able to go straight to the next map when i’m in freeplay especially.
[QUOTE=wolf blitzer;299179]or this might be easier
com_bootLogo “0”[/QUOTE]
That did not seem to work for me, but this did…
seta g_skipIntro “1”
Your game window may minimise, but click on it in the task bar and you will be back in business…
[QUOTE=Bandwidth_Bandito;307048]That did not seem to work for me, but this did…
seta g_skipIntro “1”
Your game window may minimise, but click on it in the task bar and you will be back in business…[/QUOTE]
g_skipIntro is not a real command in brink. You are creating it as a variable that does nothing by using the “seta” command. When you type g_skipIntro in the console it tells you it’s an unknown command.
What might have happened is that you used the “seta com_bootlogo 0” and it didn’t take until the next restart.
Yep you’re right, but I seemed sure I restarted a few times with no skipping of the intros until I entered that ol’ etqw setting and by coincidence com_bootlogo must have finally kicked in. LOL! There seemed to have been a (dare I say it) lag between putting things in the autoexec.cfg and their taking affect. But this may have just been a classic case of me trying to change too many things too quickly.
MOOKA!