Wont Start

[Weston1]

I just got the game and installed it and everything, but it wont start. I'll click play game and it'll tell me barony is running for a few seconds and then say im not playing anything. I tried uninstalling and reinstalling the game. On google it says to delete "default.cfg" but i dont have that. What can I do?

[5 Bears On Patrol]

Same here.

[Goma]

Having the same issue here as well. Just bought the game during the Autumn sale. Went to try and run it for the first time and on my friends list it briefly shows me as "playing" the game but then quickly returns to a normal state.

There is no "default.cfg" in the game folder. My drivers are up to date.

Halp!

[mistersneak]

Hey guys, sorry to hear you're having trouble! That sucks!
Would you please try deleting your local content and reinstalling the game? Also can you please confirm what OS you're running on - in case a reinstall doesn't solve it this might help us track down the issue.

[Goma]

I deleted the local content then reinstalled the game. Problem still persists.

I am running Windows 7 Home Premium
GPU: NVIDIA GeForce GTX 770 (Driver Version: 376.09, released November 28, 2016)
CPU: Intel i7-4930K

I also tried with the previous driver version. Same result.

If you need any more details let me know.

[Addictgamer]

Yes, please post the contents of log.txt from Barony's install dir.

[Weston1]

What is log.txt?

[Addictgamer]

To access the game's directory: In your Steam library, right click on Barony and select properties, then click on the "Local Files" tab and hit "BROWSE LOCAL FILES..."

Paste the contents of the file "log.txt" located in that directory.

[Weston1]

I don't have a file with ".txt" after it just "log" and in it is:

[22-55-26] successfully loaded language file 'lang/en.txt'
[22-55-30] initializing SDL...
[22-55-30] initializing FMOD...
[22-55-31] initializing SDL_net...
[22-55-31] initializing SDL_image...
[22-55-31] setting display mode to 960x600...
[22-55-36] display changed successfully.
[22-55-36] loading engine resources...
[22-55-36] loading sprites...
[22-55-37] loading models...
[22-55-40] generating poly models...
[22-55-53] loading tiles...
[22-55-55] loading sounds...
[22-56-07] running main loop.
[22-56-12] changing video mode.
[22-56-12] setting display mode to 1366x709...
[22-56-12] display changed successfully.
[22-57-02] closing engine...
[22-57-02] removing engine timer...
[22-57-02] freeing engine resources...
[22-57-02] freeing map data...
[22-57-02] freeing textures...
[22-57-02] freeing sprites...
[22-57-02] freeing models...
[22-57-02] freeing sounds...
[22-57-02] shutting down SDL and its subsystems...
[22-57-02] storing user stats to Steam...
[22-57-02] success

[Addictgamer]

It looks like the game started and ran just fine. Is this a left-over log file -- have you ever successfuly run Barony before?

[Goma]

I browsed through the game folder and did not find "log.txt"

For science reasons I attempted to run "barony.exe" and it gave me the error:

"The program can't start because api-ms-win-crt-runtime-l1-1-0.dll is missing from your computer. Try reinstalling the program to fix this problem."

I have also checked windows update to make sure I wasn't missing any important updates.

Hope this info helps!

[Addictgamer]

That dll can be found here:
https://support.microsoft.com/en-us/kb/2999226

[Goma]

Yeah, I just googled and found it a minute ago. I applied the update and the game appears to work just fine! Woot.

[zanetheinsane]

I am having the same issue. I have played Barony fine in the past but I went to start it up and th game shows as running under my steam profile but immediately goes away. No log.txt file is generated. I've just updated my Radeon drivers to the latest version 16.9.2

Running Windows 8.1 x64 with a Radeon 7850.

Uninstalled and reinstalled the game multiple times.

[Addictgamer]

What happens if you execute barony.exe directly, as opposed to through the Steam interface?

[Koledin]

Same to me, if i execute barony. exe directly it tells me that api-ms-win-crt-runtime-l1-1-0.dll is missing...