Jump to content

Search the Community

Showing results for tags 'linux'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Vintagestory Discussion
    • News
    • Discussion
    • Suggestions
    • Questions
    • Multiplayer
    • Bugs (archived)
  • Creative endeavors
    • Builds
    • Videos, Art or Screenshots
    • Story
  • Vintage Story Modding
    • Mod Releases
    • Modpack Releases
    • Mods & Mod Development
  • Off Topic
    • Other Games
    • General Offtopic

Categories

  • News
  • Community Spotlight and Events
  • Stories

Product Groups

  • Game Account & Game Servers
  • Game Server

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


About Me

Found 8 results

  1. In this thread I explain how to install, configure, play, mod and update Vintage Story on Steam Deck. Introduction Video game company Valve recently came up with an affordable PC Linux handheld device called Steam Deck. I received mine a while ago, and of course being a fan of the game I installed Vintage Story on it. Vintage Story is not on Steam, but it is a Linux game and it works nicely on Steam Deck as a non-steam game. Just to be clear, I don't really intend to advertise anything here. I thought if you come here from the search engine, I'll show you how to install and use it on this particular form factor and share my experiences. Demo clips My apologies for poor quality, it's a 1080p webcam but struggling to focus from up close. However most details should be visible. Clumsy but getting hang of it. deck1.mp4 Performance overlay in multiplayer game. deck2.mp4 Installing Thanks to the Linux Flatpak package available for Vintage Story, installation and updating the game is very easy. The whole process should take no more than a few minutes. Press STEAM button, choose Power then choose Switch to Desktop. You will be in desktop mode. Use the right touchpad to move the mouse, and press it to left click. Alternatively you can use the touch screen. Click the Start Menu. From the System category, click Discover application. Click the search box in top left, and press STEAM + X to pull up the virtual keyboard. Type Vintage Story, press RT to Enter, then press B to hide the keyboard. From the list on the right, choose Vintage Story item. Press the Install button to download and install it. After a few moments, it should be complete. Click the Start Menu. From the Games category, right click (press left touchpad) Vintage Story entry and select Add to Steam. Steam Desktop UI dialog window should show up. Vintage Story item should be on the list, select it. If it's not on the list, click Browse and navigate to /var/lib/flatpak/exports/share/applications and open at.vintagestory.VintageStory.desktop. Press Add Selected Programs. (Optional) You can use SteamGrid utility to download and set a matching library thumbnail from SteamGridDB for the game. Refer to its instructions on how to use it, you'll need to generate a SteamGridDB API key. Logout or click Return to Gaming Mode from the desktop. That's it! Vintage Story should be in your Non-Steam category in your Steam library now. Here's how it looks like on my Deck UI, with a nice graphic imported from SteamGridDB. Configuring and Performance Before you launch it, make sure to download a community layout named Vintage Story [Mark 1]. As of Vintage Story v1.16.5, it has an important workaround for mouse wheel registering two scrolls instead of one. First, enable Fullscreen and V-Sync. Also don't use FPS limiter in game options - use the one built into Steam Deck performance options. Everything else is up to you. For 60 FPS, my recommended quality preset for Multiplayer mode is Medium. It should use around 9-12 Watts of power, depending on your screen brightness. Battery should last for 4 hours of 60 FPS gameplay, even more so if you reduce the framerate to 30 FPS. I recommend using Low preset for smooth gameplay in Single Player mode. In my experience Single Player mode is more resource intensive, probably due to a fact that in addition to the game client, it additionally hosts a server in the background that performs CPU intensive tasks such as chunk generation and so on. Controls Here are controls for the game as mapped in the community controller layout Vintage Story [Mark 1], working with the default control configuration inside the game. Right touchpad or Right joystick - Mouse R2 or press right touchpad, or press right joystick - Left mouse button L2 - Right mouse button Left touchpad vertical swipe - Mouse wheel Left joystick - WASD (Walk) A - Space (Jump) B - Escape (Menu, closing windows) Y - C (Character sheet) X - E (Inventory) R1, L2 - cycle though 0-9 keyboard keys (Change hotbar items) L4 - Ctrl (Sprint) R4 - Shift (Sneak) L5 - Left Alt (Lock/Unlock mouse cursor) View - M (Map) View Long Press - F6 (Show/Hide Minimap) Menu - H (Survival Guide) Menu Long Press - J (Journal) D-Pad Up - Q (Drop one item) D-Pad Up Long Press - Ctrl+Q (Drop all items) D-Pad Right - X (Flip left/right hand contents) D-Pad Right Long Press - F (Select Tool Mode) D-Pad Down - G (Sit) D-Pad Down Long Press - F5 (Switch camera mode) D-Pad Left - Tab (Show/Hide chat dialog) D-Pad Left Long Press - T (Type in chat) You can modify it to tailor it to your preferences. You can also enable gyroscope mouse aiming in Steam controller settings if you desire. Just remember that if you want to share your scheme, avoid changing default game controls. Modding In Desktop mode, open the Dolphin file manager, in the top right corner of the window press the hamburger menu icon and choose Show hidden files. From your Home location, navigate to .var/app/at.vintagestory.VintageStory/config/VintagestoryData/Mods. You shall place any mod files here. Mods not working or crash when connecting to modded servers Some mods work well with Windows and Linux, but not Linux Flatpak version of Vintage Story. The common reason for that is mod developers reference libraries in a way that can't work on this rather exotic setup. Thankfully, this particular problem is often easy to fix. You need to contact mod developers and make them sure they're referencing libraries in a compatible way. See links below for details. https://github.com/G3rste/petai/issues/24 https://github.com/G3rste/petai/pull/25 https://www.reddit.com/r/VintageStory/comments/y6rtp2/issues_with_mods_using_netstandard_library_on/ If you experience any other problems, please let me know. Updating and Downgrading To update Vintage Story to the most recent stable version, you'll need to go back to Discover app in the Desktop Mode, go to the Updates section and click the Update button. That's it, nothing else is required. Downgrading to older versions is a bit more complicated, but doable. You just need to set up an account password to be able to use "sudo" command and then type two first commands from the Downgrading section from Flatpak Tips and Tricks page, as such: flatpak remote-info --log flathub at.vintagestory.VintageStory sudo flatpak update --commit=<paste-commit-id-here> at.vintagestory.VintageStory Known Issues for ≤ 1.16.5 Steam Input invokes mouse wheel up/down 2 times, resulting in scrolling by 2 items/lines, not by one. Game sometimes hangs on exit, user needs to force exit a few times from Steam UI to terminate it. Slight frametime jitter regardless of used video options. Closing thoughts Vintage Story works and plays nice on Steam Deck with no major issues, except for the mouse wheel issue for skipping inventory items on bottom bar, but it was already worked around with a controller mapping hack. Smooth and stable gameplay, you can map all the essential controls you need. If you use Discord to voice chat, you can also install it the same way, run in Steam and switch between VS and Discord seamlessly. You can also map Push-To-Talk key if you need it. That's it! Let me know what you think. Also, my first post on this forum. Thanks Tyron et al for this amazing game.
  2. Easy Red 2 is the game for who knows what he wants from a World War 2 Game: Simulation in weapons and movements, historical accuracy in battles, huge maps with a lot of deployed units, vehicles dominating the battlefields and a realistic combat approach. https://www.corvostudio.it/easyred2.html https://www.youtube.com/watch?v=p8C7B_9gNs0
  3. As we have a decent number of Linux users in the community, I would be great to collect the experience, for which distros/configurations it could be managed to run VintageStory. Please share in the comments your working VS linux configuration in the following way: Distro / Kernel release : Ubuntu Studio 16.04 LTS / 4.4.0-127-lowlatency Mono / .NET package version : mono-complete 4.2.1.102+dfsg2-7ubuntu4 Graphics driver version : NVIDIA binary driver 384.130 (proprietary) Works for client, mp server or both : client + multiplayer server Installation method used : server.sh Hacks (if needed) : server.sh needs at least wget version 1.17.9 (not in the standard repo of Ubuntu 16.04) Update as of 8th of March 2020: From a bug report it looks like mono 4.2.1 is not sufficent any more, even for a server only!
  4. Hi! I just bought the game because I saw itchio was doing Creator Day again, the thing is that I installed it but there was a problem, there was no sound (openal was installed), looking through the Linux distro/configurations topic I saw that there is a aur package, and looking it through pamac I saw that there is a flatpak package. My suggestion is to show the flatpak version when downloading the game as an alternative as it's easy to install and at least for me, it just works. Thanks.
  5. Hello, I would like to start off by saying that I have never used the install.sh script included with the Linux Tarball of VintageStory. Also, the developers state, here on this website, that Linux requires a lot of manual tweaks. That's sort of true I guess. Here's the process I go through to install the game. Step 1a) For Debian-based distributions: install Mono. You can follow the instructions to install Mono by clicking here. I know the Ubuntu and Arch Linux process, so if needed, I can walk people through the steps on those distributions of Linux. On Ubuntu, it is (unfortunately) more involved, and requires a decent understanding of APT repositories. However, you get the benefit of having access to the mono build coming directly from the mono-project itself. Step 1b) On Arch (and it's derivatives), mono can be found in the repositories, so pacman is the only tool you'll need. sudo pacman -S mono Step 2a) On Debian-based distributions, download the Linux (Full) tarball from your Vintage Story account to ~/.local/bin Next open a terminal and change directory into the directory you installed it to: cd ~/.local/bin/ Finally, extract the tarball in place: tar -xvf vs_archive_<version>.tar.gz and move into the newly extracted vintagestory directory: cd ./vintagestory Step 2b) On Arch-based distributions, just install Vintage Story with the AUR. If you aren't using an AUR manager such as `yay` or `trizen`, here is the manual method. First you'll want to get the AUR package using git: git clone https://aur.archlinux.org/vintagestory.git then you can change directory into the newly downloaded vintagestory directory with the cd command. Finally, you can just install it with: makepkg -si If for any reason the AUR method doesn't work, you can just fall back to using the Debian-based instructions in step 2a and continue to steps 3; otherwise, go to step 5. Step 3) Edit the Vintagestory.desktop file. You only need to edit 4 lines. First you may want to get rid of the ${Version} variables, but you don't have to do this. Then you'll want to edit the last two lines by updating the path to explicit values (where <usrname> needs to be replaced with your Linux user's username (i.e. in my case, I replace <usrname> with deblad): # The commented out values are the old values that come with the game. #Name=Vintage Story ${VERSION} #Name[de]=Vintage Story ${VERSION} Name=Vintage Story Name[de]=Vintage Story ... #Path=${APPDATA}/${INST_DIR} #ICON=${APPDATA}/${INST_DIR}/assets/gameicon.xpm Path=/home/<usrname>/.local/share/vintagestory Icon=/home/<usrname>/.local/share/vintagestory/assets/gameicon.xpm Notice that the only changes we made were super simple ones. All you do is replace the ${APPDATA}/${INST_DIR} with the path that we extracted the tarball to in step 2. Step 4) Copy (or move) the newly edited Vintagestory.desktop file to your ~/.local/share/applications directory. Notice that it is one directory above your current working directory so you can just use the command, cp Vintagestory.desktop ../applications Step 5) Enjoy the game. You can find the application in the applications menu of your desktop. If you got all paths correct, you'll see the icon and the game will just work - provided that you installed mono. That's it. 5 Simple Steps. Honestly, they could be simpler if the game devs would adopt this method to install the game on Linux. I honestly hope they do Updated on 4 November 2021.
  6. I would like to create a flatpak package for Vintage Story. Flatpak is an application packaging system for Linux. Flathub is the most prominent app store that distributes flatpak packages. By submitting the package to Flathub, I will add another, IMO simpler, way for Linux users to run the Vintage Story client. I want to ask for your approval before doing this. First, whether you are OK with me creating and submitting a flatpak package. Second, whether you give permission for Flathub to redistribute your game. The usual way Flathub works is that people download the application from Flathub. In this case, where I think your game is considered to be generally non-redistributable, Flathub will need explicit permission to redistribute your game. In case you do not give permission for Flathub to distribute your game, flatpak has the ability to download files at installation time. When someone installs the package, flatpak can automatically download the game files from https://cdn.vintagestory.at/. I believe this will work because the download links don't seem to require any authentication, though this may cause problems if you ever decide to rename the files.
  7. Preface: I am relatively new to Linux, so I am not sure if this is an issue I may have inadvertently caused in the past. ### System specs: OS: Linux Mint 19.2 Cinnamon Processor: AMD Ryzen 5 2600 Memory: 16 GB (listed as 15.7 GB in System Info) Graphics Card: AMD Radeon RX 580 EDIT: Forgot to mention this, but I am running the Food Spoilage update (v1.10-rc.1), although I've encountered this issue on the latest stable version of Vintage Story (v1.9.14). I've encountered a strange bug that I have yet to see addressed elsewhere on the forums. I am able to run the game just fine through the Linux terminal with Mono(1): the main issue is when I attempt to generate a new world in Singleplayer. When I attempt to generate a new world there―using the Realistic Climate band and 384 block height limit settings―I am taken to the world generation screen as normal, but there is no apparent indication of when the loading screen begins filling up (Exhibit A): I have attempted generating worlds using different game settings (Patchy Climate and Creative World), but the same result happens. I looked into the Linux terminal and found something interesting while attempting to generate my worlds (Realistic Climate Bands, 384 block world height): 17:25:37 [Client Fatal] Newtonsoft.Json.JsonReaderException: Unexpected character encountered while parsing value: _. Path '', line 0, position 0. at Newtonsoft.Json.JsonTextReader.ParseValue () [0x002cc] in <5753133c467642479854e5d6c1dc2798>:0 at Newtonsoft.Json.JsonTextReader.Read () [0x0004c] in <5753133c467642479854e5d6c1dc2798>:0 at Newtonsoft.Json.JsonReader.ReadAndMoveToContent () [0x00000] in <5753133c467642479854e5d6c1dc2798>:0 at Newtonsoft.Json.Serialization.JsonSerializerInternalReader.ReadForType (Newtonsoft.Json.JsonReader reader, Newtonsoft.Json.Serialization.JsonContract contract, System.Boolean hasConverter) [0x0003f] in <5753133c467642479854e5d6c1dc2798>:0 at Newtonsoft.Json.Serialization.JsonSerializerInternalReader.Deserialize (Newtonsoft.Json.JsonReader reader, System.Type objectType, System.Boolean checkAdditionalContent) [0x000d9] in <5753133c467642479854e5d6c1dc2798>:0 at Newtonsoft.Json.JsonSerializer.DeserializeInternal (Newtonsoft.Json.JsonReader reader, System.Type objectType) [0x00053] in <5753133c467642479854e5d6c1dc2798>:0 at Newtonsoft.Json.JsonSerializer.Deserialize (Newtonsoft.Json.JsonReader reader, System.Type objectType) [0x00000] in <5753133c467642479854e5d6c1dc2798>:0 at Newtonsoft.Json.JsonConvert.DeserializeObject (System.String value, System.Type type, Newtonsoft.Json.JsonSerializerSettings settings) [0x0002d] in <5753133c467642479854e5d6c1dc2798>:0 at Newtonsoft.Json.JsonConvert.DeserializeObject[T] (System.String value, Newtonsoft.Json.JsonSerializerSettings settings) [0x00000] in <5753133c467642479854e5d6c1dc2798>:0 at Newtonsoft.Json.JsonConvert.DeserializeObject[T] (System.String value) [0x00000] in <5753133c467642479854e5d6c1dc2798>:0 at Vintagestory.Server.PlayerDataManager.LoadList[T] (System.String name) [0x00023] in <ae33bd11df074a09b126fdde258fcc24>:0 at Vintagestory.Server.PlayerDataManager.Load () [0x0002c] in <ae33bd11df074a09b126fdde258fcc24>:0 at Vintagestory.Server.PlayerDataManager..ctor (Vintagestory.Server.ServerMain server) [0x0000d] in <ae33bd11df074a09b126fdde258fcc24>:0 at Vintagestory.Server.ServerMain..ctor (Vintagestory.Common.StartServerArgs serverargs, System.String[] cmdlineArgsRaw, Vintagestory.Server.ServerCommandLineArgs progArgs) [0x00355] in <ae33bd11df074a09b126fdde258fcc24>:0 at _HQkmz7DQLMYQ8vrWVKY4vJm3UIF._cbC6oAuIIyrWllhAsBZZ1p8dOzk () [0x0003f] in <9121d65540b840bc89082a9014d8ea71>:0 I've checked the other generation attempts and they all seem to have similar errors: (Patchy Climate, 256 block world height) 17:29:32 [Client Fatal] Newtonsoft.Json.JsonReaderException: Unexpected character encountered while parsing value: _. Path '', line 0, position 0. at Newtonsoft.Json.JsonTextReader.ParseValue () [0x002cc] in <5753133c467642479854e5d6c1dc2798>:0 at Newtonsoft.Json.JsonTextReader.Read () [0x0004c] in <5753133c467642479854e5d6c1dc2798>:0 at Newtonsoft.Json.JsonReader.ReadAndMoveToContent () [0x00000] in <5753133c467642479854e5d6c1dc2798>:0 at Newtonsoft.Json.Serialization.JsonSerializerInternalReader.ReadForType (Newtonsoft.Json.JsonReader reader, Newtonsoft.Json.Serialization.JsonContract contract, System.Boolean hasConverter) [0x0003f] in <5753133c467642479854e5d6c1dc2798>:0 at Newtonsoft.Json.Serialization.JsonSerializerInternalReader.Deserialize (Newtonsoft.Json.JsonReader reader, System.Type objectType, System.Boolean checkAdditionalContent) [0x000d9] in <5753133c467642479854e5d6c1dc2798>:0 at Newtonsoft.Json.JsonSerializer.DeserializeInternal (Newtonsoft.Json.JsonReader reader, System.Type objectType) [0x00053] in <5753133c467642479854e5d6c1dc2798>:0 at Newtonsoft.Json.JsonSerializer.Deserialize (Newtonsoft.Json.JsonReader reader, System.Type objectType) [0x00000] in <5753133c467642479854e5d6c1dc2798>:0 at Newtonsoft.Json.JsonConvert.DeserializeObject (System.String value, System.Type type, Newtonsoft.Json.JsonSerializerSettings settings) [0x0002d] in <5753133c467642479854e5d6c1dc2798>:0 at Newtonsoft.Json.JsonConvert.DeserializeObject[T] (System.String value, Newtonsoft.Json.JsonSerializerSettings settings) [0x00000] in <5753133c467642479854e5d6c1dc2798>:0 at Newtonsoft.Json.JsonConvert.DeserializeObject[T] (System.String value) [0x00000] in <5753133c467642479854e5d6c1dc2798>:0 at Vintagestory.Server.PlayerDataManager.LoadList[T] (System.String name) [0x00023] in <ae33bd11df074a09b126fdde258fcc24>:0 at Vintagestory.Server.PlayerDataManager.Load () [0x0002c] in <ae33bd11df074a09b126fdde258fcc24>:0 at Vintagestory.Server.PlayerDataManager..ctor (Vintagestory.Server.ServerMain server) [0x0000d] in <ae33bd11df074a09b126fdde258fcc24>:0 at Vintagestory.Server.ServerMain..ctor (Vintagestory.Common.StartServerArgs serverargs, System.String[] cmdlineArgsRaw, Vintagestory.Server.ServerCommandLineArgs progArgs) [0x00355] in <ae33bd11df074a09b126fdde258fcc24>:0 at _HQkmz7DQLMYQ8vrWVKY4vJm3UIF._cbC6oAuIIyrWllhAsBZZ1p8dOzk () [0x0003f] in <9121d65540b840bc89082a9014d8ea71>:0 (Creative World, 256 block world height) 17:29:50 [Client Fatal] Newtonsoft.Json.JsonReaderException: Unexpected character encountered while parsing value: _. Path '', line 0, position 0. at Newtonsoft.Json.JsonTextReader.ParseValue () [0x002cc] in <5753133c467642479854e5d6c1dc2798>:0 at Newtonsoft.Json.JsonTextReader.Read () [0x0004c] in <5753133c467642479854e5d6c1dc2798>:0 at Newtonsoft.Json.JsonReader.ReadAndMoveToContent () [0x00000] in <5753133c467642479854e5d6c1dc2798>:0 at Newtonsoft.Json.Serialization.JsonSerializerInternalReader.ReadForType (Newtonsoft.Json.JsonReader reader, Newtonsoft.Json.Serialization.JsonContract contract, System.Boolean hasConverter) [0x0003f] in <5753133c467642479854e5d6c1dc2798>:0 at Newtonsoft.Json.Serialization.JsonSerializerInternalReader.Deserialize (Newtonsoft.Json.JsonReader reader, System.Type objectType, System.Boolean checkAdditionalContent) [0x000d9] in <5753133c467642479854e5d6c1dc2798>:0 at Newtonsoft.Json.JsonSerializer.DeserializeInternal (Newtonsoft.Json.JsonReader reader, System.Type objectType) [0x00053] in <5753133c467642479854e5d6c1dc2798>:0 at Newtonsoft.Json.JsonSerializer.Deserialize (Newtonsoft.Json.JsonReader reader, System.Type objectType) [0x00000] in <5753133c467642479854e5d6c1dc2798>:0 at Newtonsoft.Json.JsonConvert.DeserializeObject (System.String value, System.Type type, Newtonsoft.Json.JsonSerializerSettings settings) [0x0002d] in <5753133c467642479854e5d6c1dc2798>:0 at Newtonsoft.Json.JsonConvert.DeserializeObject[T] (System.String value, Newtonsoft.Json.JsonSerializerSettings settings) [0x00000] in <5753133c467642479854e5d6c1dc2798>:0 at Newtonsoft.Json.JsonConvert.DeserializeObject[T] (System.String value) [0x00000] in <5753133c467642479854e5d6c1dc2798>:0 at Vintagestory.Server.PlayerDataManager.LoadList[T] (System.String name) [0x00023] in <ae33bd11df074a09b126fdde258fcc24>:0 at Vintagestory.Server.PlayerDataManager.Load () [0x0002c] in <ae33bd11df074a09b126fdde258fcc24>:0 at Vintagestory.Server.PlayerDataManager..ctor (Vintagestory.Server.ServerMain server) [0x0000d] in <ae33bd11df074a09b126fdde258fcc24>:0 at Vintagestory.Server.ServerMain..ctor (Vintagestory.Common.StartServerArgs serverargs, System.String[] cmdlineArgsRaw, Vintagestory.Server.ServerCommandLineArgs progArgs) [0x00355] in <ae33bd11df074a09b126fdde258fcc24>:0 at _HQkmz7DQLMYQ8vrWVKY4vJm3UIF._cbC6oAuIIyrWllhAsBZZ1p8dOzk () [0x0003f] in <9121d65540b840bc89082a9014d8ea71>:0 Parsing through the text as best I can, it seems that error is the result of this "Newtonsoft.Json" suffering a reader exception: specifically, "Unexpected character encountered while parsing value: _. Path '', line 0, position 0." I looked into my vintagestory folder to see if I can somehow fix this myself and discovered a "Newtonsoft.Json.dll" file within ~/vintagestory/Lib. I removed the .dll file, but that resulted in the game not starting up at all through the command terminal. I'm somewhat reminded of a fix I discovered while trying to start up Civilization VI where a certain file had to be edited just to start the game up, so I'm considering my next option to rename the .dll file to "Newtonsoft.json.dll" instead; I'll report back on this in a bit. Irrespective of this, I'm not sure why this is happening. To be safe, I attempted to completely uninstall Mono and reinstall it to see if I had installed it incorrectly, but the generation issue still occurs. EDIT: Renaming the "Newtonsoft.Json.dll" to "Newtonsoft.json.dll" caused the game to not start up at all, instead providing an error on the Linux terminal. Figured it would happen since its extension is a .dll, but I had to try. ### (1) A separate issue, but I couldn't run "install.sh" through the terminal. However, as a relatively new Linux user, I realize that perhaps using the "mono" command may not be appropriate for programs with the ".sh" extension―I simply have not taken the time to look into this one yet.
  8. Hi, I would like to report a problem with the 1.6.9 for linux. When the mouse is free to change the direction of the camera, clicking will reset it to a specific state, does not matter where I was looking. This does not apply when the inventory or any other sub-window are opened and the camera rotation is locked. Bye!
×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.