Hard Light Productions Forums

Modding, Mission Design, and Coding => FS2 Open Coding - The Source Code Project (SCP) => Topic started by: SirKnightly on July 11, 2017, 12:50:27 pm

Title: Release: 3.8.0-RC3
Post by: SirKnightly on July 11, 2017, 12:50:27 pm

Major changes in this version: (chronologically ordered)

• Support for APNG animations: APNG (https://en.wikipedia.org/wiki/APNG) is a variant of the established PNG format which allows to store animations instead of single frames in a PNG file. This change allows to use these animation files in FSO which significantly improves usability for modders since they no longer have to store all individual frames as separate images.
• Physically-Based Rendering (PBR): This upgrade of our rendering engine allows to use PBR (https://en.wikipedia.org/wiki/Physically_based_rendering) assets to make models look more realistic and allow more artistic freedom for modders since they have more control over how a model looks. This also added support for HDR lighting which should improve the overall graphics experience.
• SDL2 usage on all platforms: SDL is a library for abstracting away the differences between different platforms. We now use SDL2 for all platforms which reduces the amount of platform-specific code tremendously and should result in better usability on all platforms. This was a major change that has been in development for several years. Here are a few key features that were added:
  
  • Pilot and configuration data is now stored in the correct location across all platforms (this allows to run FSO on Windows from the Program Files directory without administrator rights)
  • All platforms now use the ini files for storing settings. This fixes a lot of issues with the registry on Windows.
  • Better support for input devices. Since SDL handles keyboard, mouse and joystick input we now have better support on newer OS versions. Note: This does not mean that we support multiple joysticks (yet). There is ongoing development effort to support this but this release does not have that yet.
• CMake build system generation: This isn't relevant for players but we are now using CMake (https://en.wikipedia.org/wiki/CMake) for handling compiling our builds. This improves cross-platform support and allows to implement advanced compilation features across multiple platforms. Modders will like the new "FastDebug" builds which are like the previous "Debug" builds but are compiled with all the optimizations of normal Release builds. That should make modding a lot easier since you can now debug your mod with almost the same performance as a Release build.
• Improved shield effects: Rendering of the shields is now handled by special shaders which improves the overall quality of the effects and allows more freedom for future effects.
• Native particle systems: Particles have always been supported by FSO but the effects that could be created by them were very limited. There were some attempts to fix this by using Lua scripting for more advanced features but that suffered from performance issues. With these new particle systems that feature has been integrated directly into the engine which should improve performance and allow for better effects in the future.
• TrueType Font support: TrueType (https://en.wikipedia.org/wiki/TrueType) fonts improve the text rendering capabilities of FSO by allowing to use freely scaleable font faces instead of the previous bitmap fonts.
• Use OpenGL Core Profile for rendering: This is another major graphical upgrade which adds support for the OpenGL Core profile across all platforms (this was also made possible by the SDL2 integration). This upgrade allows us to use more modern rendering techniques and is especially useful for our Linux users who use the open-source Mesa drivers since our shaders failed to compile with those drivers. Now everyone will be able to enjoy the new graphical features added in this and previous releases. This also made some internal changes to how we handle rendering which improves the usability of our rendering engine within our code.
• Use FFmpeg for video & audio decoding: FFmpeg (https://www.ffmpeg.org/) is a multi-media library which exposes functionality for decoding video and audio files to their raw form so that we can use that data. Thanks to this library we can now play 1080p cutscenes without any stuttering or frame-timing issues. It also allows to use more advanced audio and video codecs such as H.264 for video or Opus for audio.

This list is taken from our GitHub wiki (https://github.com/scp-fs2open/fs2open.github.com/wiki/History-and-Release-Timeline).


Important!!
As always, you need OpenAL installed.  Linux and OS X come with it but Windows users will need to get Creative's OpenAL installer (http://scp.indiegames.us/builds/oalinst.zip). Alternatively, if Creative's OpenAL doesn't work with your hardware, you can use OpenAL Soft (http://kcat.strangesoft.net/openal.html#download).

Hidden Text: TrackIR Users • Show

Important!!
An external DLL is required for FSO to use TrackIR functions.  The following DLL is simply unpacked in to your main FreeSpace2 root dir.
TrackIR is only supported on Windows.
TrackIR SCP DLL (http://www.mediafire.com/download.php?4zw024zrh44etse) (Mirror (http://scp.fsmods.net/builds/scptrackir.zip)) (Mirror (http://scp.indiegames.us/builds/scptrackir.zip))

Launchers, if you don't have one already:
All platforms:  wxLauncher 0.12.x Test Build (http://www.hard-light.net/forums/index.php?topic=89162) (ongoing project for a unified launcher, you should upgrade to the latest RC/test build if you have not yet)
Important: For best compatibility with FSO 3.8 you should use at least wxLauncher 0.12.

Hidden Text: Alternative Launchers • Show

Windows:  Launcher 5.5g (http://scp.fsmods.net/files/Launcher55g.zip) (Mirror (http://scp.indiegames.us/builds/Launcher55g.zip)) (Mirror (http://www.mediafire.com/?wdvzn7hhhzh418m)) Not compatible with Windows 8+, use wxLauncher above
OS X:  Soulstorm's OS X Launcher 3.0 (http://www.hard-light.net/forums/index.php/topic,51391.0.html)
Linux:  YAL (http://www.hard-light.net/forums/index.php/topic,53206.0.html) or by hand (http://www.hard-light.net/wiki/index.php/Fs2_open_on_Linux/Graphics_Settings) or whatever you can figure out.

Known issues:

• Github issues (https://github.com/scp-fs2open/fs2open.github.com/issues) and pending pull requests (https://github.com/scp-fs2open/fs2open.github.com/pulls)
• See the list of Fix for next release (http://scp.indiegames.us/mantis/search.php?project_id=1&status_id%5B%5D=10&status_id%5B%5D=20&status_id%5B%5D=30&status_id%5B%5D=40&status_id%5B%5D=50&priority_id%5B%5D=40&priority_id%5B%5D=50&priority_id%5B%5D=60&sticky_issues=on&sortby=last_updated&dir=DESC&per_page=200&hide_status_id=-2) bugs - mark a bug as an elevated priority (high, urgent, immediate) to get it included in that filter.

Firefox and/or NoScript download issues, or Chrome "Deceptive Site" pages:

• Please read the following post on how to address direct download link issues (http://www.hard-light.net/forums/index.php?topic=93709.msg1851868#msg1851868)

(http://scp.indiegames.us/img/windows-icon.png) Windows (32/64-bit)
Compiled by Appveyor (http://www.appveyor.com/) on Windows Server 2012 R2 64-bit, Visual Studio Community 2015 with Update 3

32-bit: fs2_open_3_8_0_RC3-builds-Win32.zip (https://github.com/scp-fs2open/fs2open.github.com/releases/download/release_3_8_0_RC3/fs2_open_3_8_0_RC3-builds-Win32.zip)
This one is based on the SSE2 Optimizations from the MSVC Compiler.

64-bit: fs2_open_3_8_0_RC3-builds-Win64.zip (https://github.com/scp-fs2open/fs2open.github.com/releases/download/release_3_8_0_RC3/fs2_open_3_8_0_RC3-builds-Win64.zip)
WARNING: 64-bit builds are still experimental. These builds have been tested but there may still be issues that are not present in the 32-bit builds. Make sure you read the installation instructions below.
Installation: If you use the 64-bit executables you have to make sure that you install all files from the zip file and that there are no remaining 32-bit DLLs left in your FSO directory. Some users have installed the 32-bit OpenAL DLLs directly into your FSO directory which is a common cause for errors. If the launcher fails to use the 64-bit executable this is the first thing you should check.

Hidden Text: Alternative builds • Show

32-bit AVX: fs2_open_3_8_0_RC3-builds-Win32-AVX.zip (https://github.com/scp-fs2open/fs2open.github.com/releases/download/release_3_8_0_RC3/fs2_open_3_8_0_RC3-builds-Win32-AVX.zip)
This one is based on the AVX Optimizations from the MSVC Compiler (fastest build if your CPU supports AVX instructions).

64-bit AVX: fs2_open_3_8_0_RC3-builds-Win64-AVX.zip (https://github.com/scp-fs2open/fs2open.github.com/releases/download/release_3_8_0_RC3/fs2_open_3_8_0_RC3-builds-Win64-AVX.zip)
WARNING: 64-bit builds are still experimental.
This one is based on the AVX Optimizations from the MSVC Compiler.

What are those SSE, SSE2 and AVX builds I keep seeing everywhere?
Your answer is in this topic. (http://www.hard-light.net/forums/index.php?topic=65628.0)

(http://scp.indiegames.us/img/mac-icon.png) OS X Universal (32/64-bit Intel)
Compiled on OS X 10.11.4, Xcode 7.3 (Apple LLVM version cross-reference (https://gist.github.com/yamaya/2924292))

fs2_open_3_8_0_RC3-builds-MacOSX.tar.gz (https://github.com/scp-fs2open/fs2open.github.com/releases/download/release_3_8_0_RC3/fs2_open_3_8_0_RC3-builds-MacOSX.tar.gz)

(http://scp.indiegames.us/img/linux-icon.png) Linux 64-bit
Compiled on Ubuntu 14.04.4 LTS 64-bit, GCC 5
fs2_open_3_8_0_RC3-builds-Linux.tar.gz (https://github.com/scp-fs2open/fs2open.github.com/releases/download/release_3_8_0_RC3/fs2_open_3_8_0_RC3-builds-Linux.tar.gz)

These builds use a mechanism called AppImage (http://appimage.org/) which should allow these builds to run on most Linux distributions. However, we recommend that you compile your own builds which will result in less issues.
Alternatively, if there is a package in your software repository then you should use that. If you are the maintainer of such a package for a distribution then let us know and we will include that here.

Hidden Text: Other Platforms, Source Code • Show

Source Code Export
Source Code (https://api.github.com/repos/scp-fs2open/fs2open.github.com/tarball/release_3_8_0_RC3)

Title: Re: Release: 3.8.0-RC3
Post by: Lykurgos88 on July 12, 2017, 11:08:32 am

A quick run with RC3:

1) I'm sorry to report that the SDL2 related auto-center bug for joysticks (where joystick becomes "limp" after 1 mission) is still existing with RC3.

2) Capship explosions still do not trigger force feedback effects. Most of the other FF effects still work.

Title: Re: Release: 3.8.0-RC3
Post by: Trivial Psychic on July 12, 2017, 08:22:56 pm

May I suggest on future RC threads that a section of the release info include what fixes have been added since the previous RC, rather than just the entire list of 3.8.0 additions?

Title: Re: Release: 3.8.0-RC3
Post by: m!m on July 15, 2017, 06:23:25 am

Including a changelog automatically is rather hard to do. You can take a look at all the merged changes and the associated issues by using the 3.8 Milestone page (https://github.com/scp-fs2open/fs2open.github.com/milestone/2?closed=1) on GitHub,

Title: Re: Release: 3.8.0-RC3
Post by: Zacam on July 25, 2017, 12:58:33 am

For users of Firefox and NoScript:

If you are having issues with the download links going to a different page about a security warning, that's a Google/NoScript Cross Site Problem.

However, you can alleviate that and enable the ability to download directly forth the scp-fs2open github directly or links pointed there as follows:

Go to NoScript Options menu, then Advanced, then XSS tab. In the input box with the other URI's present, add the following 2 lines:
"https://github-production-release-asset-([a-z(1-9)]*).s3.amazonaws.com/*" (minus the quotes)
"https://github.com/scp-fs2open/fs2open.github.com/releases/download/*" (also minus the quotes, this one is likely redundant, but I'd rather cover the bases)

And you should be able to refresh and download the builds directly from their links here or on GitHub.

For Google  Chrome users receiving a "Deceptive Site" page from amazonaws, you can select "Details" at the bottom and click "visit this unsafe site", but I also urge that you select "report a detection problem" as well so that the false report can be corrected.