![]() WX has more options, but YAL is much simpler. Have patience.Īfter stuff had been downloaded, you can use either WXLauncher, or YAL (Yet Another Launcher) to build up the command line to launch the game itself. It will then download all the various files. If you want the max enjoyment (and lots of downloads), get the FSPort 2014 Media VP. You can also download the improve visuals, new 720p briefings, and so on. But there are a TON of good user campaigns from the FS Community you should try them out out. You will need SOME of the mods, notably, FSport, which are the FS1 and FS2 missions ported into FSOpen engine. (For Steam, it's probably Steam/Steamapps/common/Freespace or Freespace 2)įourth, follow the prompts, and it will prompt you to download the bare minimum of files, and/or the mods. Third, run the installer, and install it into your Freespace or Freespace 2 directory. You will need to install Java first, if you haven't already. ![]() Note: This installer requires Java, but it's for Windows. Second, download FreeSpace Open Installer from What you need to do is NOT that complicated.įirst, you do need to own this game (and Freespace 2 as well, really) That's right, folks, you can play this game with a modern DirectX compatible engine that was open-sourced by Volition a long time ago, called FSOpen! So what should you do? Play it with a MODERN engine! Then, re-run the Software Updater GUI tool.For people who complain that this game doesn't support modern machines. which told me to run `sudo apt -fix-broken install`, so I did that: Once sudo apt update worked again, I had to do this, as quoted from my answer here: sudo apt update Previously, it was showing various Couldn't create temporary file /tmp/ for passing config to apt-key type errors as shown in this question. then once logged back in, sudo apt update worked again! Then, after following those instructions and rebooting from the initramfs menu like this: fsck /dev/mapper/sda4_crypt -y It booted into the initramfs menu instead, as explained by the Q&A I linked to just above. I figured it out because I rebooted to see if that would help my sudo apt update error problem, and my system was unable to boot. So, I had to run this: fsck /dev/mapper/sda4_crypt -y Find the one mounted as your root disk at mount point /. Run df -h first to see what disks you have. So, it turns out I had to run fsck on the root dir. Ls -lad /tmp was fine, showing drwxrwxrwt, as explained in this answer. In my case the problem was my disk had errors. sudo apt-get check doesn't find anything either. sudo apt-get upgrade states that there is nothing that needs to be upgraded. Tried sudo apt-get clean, nothing happened. W: GPG error: bionic InRelease: Couldn't create temporary file /tmp/8dgO for passing config to apt-keyĮ: The repository ' bionic InRelease' is not signed. W: GPG error: bionic-backports InRelease: Couldn't create temporary file /tmp/1d for passing config to apt-keyĮ: The repository ' bionic-backports InRelease' is not signed. ![]() W: GPG error: bionic-updates InRelease: Couldn't create temporary file /tmp/98B6M for passing config to apt-keyĮ: The repository ' bionic-updates InRelease' is not signed. W: GPG error: bionic-security InRelease: Couldn't create temporary file /tmp/ for passing config to apt-keyĮ: The repository ' bionic-security InRelease' is not signed. N: See apt-secure(8) manpage for repository creation and user configuration details. N: Updating from such a repository can't be done securely, and is therefore disabled by default. W: GPG error: xenial InRelease: Couldn't create temporary file /tmp/ for passing config to apt-keyĮ: The repository ' xenial InRelease' is not signed. Get:5 bionic-backports InRelease Ĭouldn't create temporary file /tmp/1d for passing config to apt-keyĬouldn't create temporary file /tmp/8dgO for passing config to apt-key Get:4 bionic-updates InRelease Ĭouldn't create temporary file /tmp/98B6M for passing config to apt-key Get:2 bionic-security InRelease Ĭouldn't create temporary file /tmp/ for passing config to apt-keyĬouldn't create temporary file /tmp/ for passing config to apt-key Tried to do sudo apt-get update, get this response every time I run it: Get:1 xenial InRelease
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |