FarLight is primarily an early-stage interactive application and rendering engine for Windows. Currently not much is implemented, but I plan to do more convenient features and user-friendly design and in the future 😄.
Visual Studio 2017 or 2019 is recommended with C/C++17 MSVC compiler preinstalled. FarLight is officially untested on other development environments but they can be used because of premake5 support. Main development is running under Visual Studio 2019 and Windows system.
You can clone the repository to a local destination using git:
git clone --recursive https://github.com/NewBediver/FarLight.git
Make sure that you do a --recursive clone to fetch all of the submodules!
To generate solution you need to execute script Win-GenerateProject.bat which is located inside /scripts directory.
The plan for FarLight is two-fold: to create a powerful 2D/3D engine, but also to serve as an education tool for studing game engine design and architecture. Because of this the development inside this repository is rather slow.
- Fast 2D rendering (UI, particles, sprites, etc.)
- High-fidelity Physically-Based 3D rendering (this will be later, 2D to come first)
- Support for Mac, Linux, Android and iOS
- Native rendering API support (DirectX, Vulkan, Metal)
- Fully featured viewer and editor applications
- Fully scripted interaction and behavior
- Integrated 3rd party 2D and 3D physics engine
- Procedural terrain and world generation
- Artificial Intelligence
- Audio system
The Apache 2.0 license is a permissive free software license by the Apache Software Foundation. The 2.0 version requires preservation of the copyright notice and disclaimer. It also allows the user of the software the freedom to use the software for any purpose, modify it, and distribute the modified versions of the software, under the terms of the license, without concern for royalties.
Key points:
1. Keep the copyright notice.
2. Your software has to contain a copy of the Apache 2.0 license.
3. You are free to use, modify, distribute, and redistribute the software.
4. If you modify the code, you have to mention your modifications particularly.
5. If there is a text file called NOTICE, take time and read it. It contains further information about the specific parts of the license and the purpose of the software.
6. The NOTICE file has to be included in your software release too.More information on about the Apache 2.0 license can be found here.