Skip to content
This repository was archived by the owner on Oct 4, 2022. It is now read-only.

Commit 6b8dd98

Browse files
nechnech
nech
authored and
nech
committed
Lumberyard Release 1.10.0.0
 Binaries Uncompressed Size: 7.49GB (8041132924 bytes)
0 parents  commit 6b8dd98

File tree

25,468 files changed

+8112217
-0
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

25,468 files changed

+8112217
-0
lines changed

‎.gitignore

+136
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,136 @@
1+
# Ignore every file.
2+
*
3+
4+
# Except for all other directories & subdirectories
5+
!**/
6+
7+
# In every subdirectory, avoid ignoring files with the following extensions.
8+
!**/*.[cC][pP][pP]
9+
!**/*.[hH]
10+
!**/*.args
11+
!**/*.asp
12+
!**/*.attribute_layout
13+
!**/*.bat
14+
!**/*.c
15+
!**/*.cbc
16+
!**/*.cfg
17+
!**/*.chrparams
18+
!**/*.cmake
19+
!**/*.cmd
20+
!**/*.conf
21+
!**/*.coffee
22+
!**/*.cpp
23+
!**/*.cs
24+
!**/*.csproj
25+
!**/*.decTest
26+
!**/*.def
27+
!**/*.ent
28+
!**/*.ent_template
29+
!**/*.env
30+
!**/*.exportsettings
31+
!**/*.filters
32+
!**/*.h
33+
!**/*.hpp
34+
!**/*.html
35+
!**/*.hxx
36+
!**/*.ico
37+
!**/*.ignore
38+
!**/*.ini
39+
!**/*.inl
40+
!**/*.java
41+
!**/*.js
42+
!**/*.json
43+
!**/*.lua
44+
!**/*.lua_template
45+
!**/*.lyr
46+
!**/*.m
47+
!**/*.manifest
48+
!**/*.md
49+
!**/*.mel
50+
!**/*.mm
51+
!**/*.mk
52+
!**/*.ms
53+
!**/*.mtl
54+
!**/*.npmignore
55+
!**/*.p4ignore
56+
!**/*.plist
57+
!**/*.prefab
58+
!**/*.pro
59+
!**/*.props
60+
!**/*.py
61+
!**/*.pyproj
62+
!**/*.pys
63+
!**/*.pyw
64+
!**/*.qml
65+
!**/*.qmldir
66+
!**/*.qmltypes
67+
!**/*.qrc
68+
!**/*.qss
69+
!**/*.rc
70+
!**/*.sct
71+
!**/*.sh
72+
!**/*.slice
73+
!**/*.sln
74+
!**/*.spec
75+
!**/*.sql
76+
!**/*.targets
77+
!**/*.tcl
78+
!**/*.tip
79+
!**/*.[tT][xX][tT]
80+
!**/*.ui
81+
!**/*.uicanvas
82+
!**/*.vbs
83+
!**/*.vcproj
84+
!**/*.vcxproj
85+
!**/*.vssscc
86+
!**/*.waf_files
87+
!**/*.xbm
88+
!**/*.xml
89+
!**/ChangeLog
90+
!**/configure
91+
!**/DEVEL
92+
!**/lmbr_waf
93+
!**/[mM]akefile
94+
!**/makefile.appletv
95+
!**/wscript
96+
!**/README
97+
!**/TODO
98+
!**/waf
99+
100+
# Make an exception to ignore specific directories
101+
# Most of these directories are brought in by executing git_bootstrap.
102+
/3rdParty
103+
/dev/AssetProcessorTemp
104+
/dev/BinTemp
105+
/dev/Bin64
106+
/dev/Bin64vc120
107+
/dev/Bin64vc120.Debug
108+
/dev/Bin64vc140
109+
/dev/Bin64vc140.Debug
110+
/dev/Cache
111+
/dev/FeatureTests
112+
/dev/SamplesProject
113+
/dev/Code/SDKs
114+
/dev/Code/Sandbox/SDKs
115+
/dev/Solutions
116+
/dev/Code/Tools/SDKs
117+
/dev/MultiplayerSample
118+
/dev/MultiplayerProject
119+
/dev/Gems/GameEffectSystem
120+
/dev/Gems/Oculus
121+
/dev/Gems/OpenVR
122+
/dev/Gems/PBSreferenceMaterials
123+
/dev/Gems/Substance
124+
/dev/Tools/CrySCompileServer/x64
125+
/dev/Tools/LmbrSetup/Win.vc140.Debug
126+
/dev/Tools/LmbrSetup/Win.vc120.Debug
127+
128+
# Ignore ico files from Lumberyard folders but preserve ico files in project folders
129+
/dev/Code/**/*.ico
130+
/dev/CloudGemSamples/**/*.ico
131+
/dev/Tools/**/*.ico
132+
133+
# Misc ignore files
134+
/dev/SetupAssistantUserPreferences.ini
135+
/dev/_WAF_/environment.json
136+
/SetupAssistant.bat

‎CONTRIBUTING.md

+45
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,45 @@
1+
# Contribution Guidelines
2+
Thank you for visiting our contribution guidelines! An active and healthy development community is what makes a good game engine an exceptional game engine. As we focus on developing new features and resolving bugs with every version of Lumberyard, we want to hear from you. We are interested in seeing how you're using the engine and what improvements you're making while you work on your own game projects. This is why, in addition to our [GameDev Forums](https://gamedev.amazon.com/forums/index.html), [Tutorials](https://gamedev.amazon.com/forums/tutorials) and [Documentation](https://aws.amazon.com/documentation/lumberyard/), we provide you with the opportunity to share your features and improvements with your fellow developers. After you modify the core engine code, simply submit a pull request.
3+
4+
To make it easy for you to contribute to our game engine, the Lumberyard development team adheres to the following coding conventions. We believe that these guidelines keep the engine code consistent and easy to understand so that you can spend less time interpreting code and more time coding. We look forward to your contributions!
5+
6+
## Compiler Compatibility:
7+
- Use the C++11 standard whenever possible.
8+
- Stick to the C++11 features that are commonly supported by Microsoft Visual Studio 2013/2015 (refer to https://msdn.microsoft.com/en-us/library/hh567368.aspx).
9+
10+
## Formatting:
11+
- Lumberyard recommends using the Uncrustify code beautifier to keep C++ code consistent with the engine code. Refer to http://uncrustify.sourceforge.net/.
12+
- Apply indentation in a consistent manner:
13+
- Files should start without any indentation.
14+
- Use a single additional level of indentation for each nested block of code.
15+
- Indent all lines of a block by the same amount.
16+
- Make lines a reasonable length.
17+
- Indent preprocessor statements in a similar way to regular code.
18+
- When positioning curly braces, open braces on a new line and keep them flush with the outer block's indentation.
19+
- Always use curly braces for flow control statements.
20+
- Each line of code should only include a single statement.
21+
- Naming conventions for classes, functions, types and files should adhere to CamelCase and specify what the function does.
22+
- All header files must include the directive, "#pragma once".
23+
- Use forward declarations to minimize header file dependencies. Compile times are a concern so please put in the effort to minimize include chains.
24+
- The following syntax should be used when including header files: #include <Package/SubdirectoryChain/Header.h>
25+
This rule helps disambiguate files from different packages that have the same name. <Object.h> might appear relatively often, but <AZRender/Object.h> is far less likely to.
26+
27+
## Classes:
28+
- You should define a default constructor if your class defines member variables and has no other constructors. Unless you have a very specifically targeted optimization, you should initialize all variables to a known state even if the variable state is invalid.
29+
- Do not assume any specific properties based on the choice of struct vs class; always use <type_traits> to check the actual properties
30+
- Public declarations come before private declarations. Methods should be declared before data members.
31+
- All methods that do not modify internal state should be const. All function parameters passed by pointer or reference should be marked const unless they are output parameters.
32+
- Use the override keyword wherever possible and omit the keyword virtual when using override.
33+
- Use the final keyword where its use can be justified.
34+
35+
## Scoping:
36+
- All of your code should be in at least a namespace named after the package and conform to the naming convention specified earlier in this document.
37+
- Place a function's variable declarations in the narrowest possible scope and always initialize variables in their declaration.
38+
- Static member or global variables that are concrete class objects are completely forbidden. If you must have a global object it should be a pointer, and it must be constructed and destroyed via appropriate functions.
39+
40+
## Commenting Code:
41+
Clear and concise communication is essential in keeping the code readable for everyone. Since comments are the main method for communication, please follow these guidelines for commenting the code:
42+
- Use /// for comments.
43+
- Use /**..*/ for block comments.
44+
- Use @param, etc. for commands.
45+
- Full sentences with good grammar are preferable to abbreviated notes.

‎LICENSE.txt

+35
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,35 @@
1+
Amazon Lumberyard
2+
Copyright (c) 2017 Amazon Web Services, Inc., its affiliates or licensors. All Rights Reserved.
3+
4+
Learn more at https://aws.amazon.com/lumberyard.
5+
6+
This product includes software developed by Amazon Technologies, Inc.
7+
8+
All materials are made available on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, express or implied. Do not remove or modify any license notices.
9+
10+
11+
*************************************
12+
AMAZON LUMBERYARD
13+
14+
The Amazon Lumberyard engine, integrated development environment, and related assets and tools included in this distribution are licensed as "Lumberyard Materials" under the terms and conditions of the AWS Customer Agreement, located at https://aws.amazon.com/agreement and the Lumberyard Service Terms, located at https://aws.amazon.com/service-terms. By using or accessing these materials, you agree to such terms and conditions. The term "Lumberyard Materials" does not include software and assets distributed with the Lumberyard Materials under separate license terms (such as code licensed under an open source license).
15+
16+
17+
*************************************
18+
TWITCH API
19+
20+
By using the Twitch API you agree to the Twitch API Terms of Service posted at http://www.twitch.tv/p/api_terms_of_service and the Twitch Terms of Service posted at http://www.twitch.tv/p/terms_of_service.
21+
22+
23+
*************************************
24+
THIRD PARTY COMPONENTS
25+
26+
Amazon Lumberyard requires the use of and makes available to you software and assets that have been developed by third parties and are subject to separate license terms (such as code licensed under an open source license), including the materials provided in \3rdParty. It is your responsibility to obtain and comply with the applicable licenses, along with any platform policies that may apply to you. Information on third party materials, and the applicable license terms, are referenced in or included with the materials, such as in separate LICENSE.txt files accompanying the materials.
27+
28+
Please note that certain materials are subject to "copyleft" licenses, which require distribution of source code, including:
29+
- Qt Toolkit https://github.com/qtproject/, which is subject to the GNU Lesser General Public License version 2.1 (with certain exceptions, see \3rdParty\Qt\). A copy of the source code for Qt Toolkit may be found at https://s3-us-west-2.amazonaws.com/ly-legal/LicenseConformance/Qt/Src.zip
30+
- Qwt Widgets for Technical Applications http://qwt.sourceforge.net, which is subject to the GNU Lesser General Public License version 2.1. A copy of the source code may be found in \3rdParty\Qwt\.
31+
- Chardet https://chardet.github.io/, which is subject to the GNU Lesser General Public License version 2.1. A copy of the source code may be found in \3rdParty\AWS\AWSPythonSDK\1.2.1\botocore\vendored\requests\packages\.
32+
33+
This software contains Autodesk(R) FBX(R) code developed by Autodesk, Inc. Copyright 2013 Autodesk, Inc. All rights, reserved. Such code is provided "as is" and Autodesk, Inc. disclaims any and all warranties, whether express or implied, including without limitation the implied warranties of merchantability, fitness for a particular purpose or non-infringement of third party rights. In no event shall Autodesk, Inc. be liable for any direct, indirect, incidental, special, exemplary, or consequential damages (including, but not limited to, procurement of substitute goods or services; loss of use, data, or profits; or business interruption) however caused and on any theory of liability, whether in contract, strict liability, or tort (including negligence or otherwise) arising in any way out of such code.
34+
35+
This product includes components of the PowerVR Tools Software from Imagination Technologies Limited.

‎README.md

+59
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,59 @@
1+
![lmbr](https://s3-us-west-2.amazonaws.com/git-release/ReadmeResources/readme_header.jpg)
2+
3+
# Amazon Lumberyard
4+
Amazon Lumberyard is a free, AAA game engine that gives you the tools you need to create high quality games. Deeply integrated with AWS and Twitch, Amazon Lumberyard includes full source code, allowing you to customize your project at any level.
5+
6+
For more information, visit: https://aws.amazon.com/lumberyard/
7+
8+
## Acquiring Lumberyard source
9+
Each release of Lumberyard exists as a separate branch in GitHub. You can get Lumberyard from GitHub using the following steps:
10+
11+
### Fork the repository
12+
Forking creates a copy of the Lumberyard repository in your GitHub account. Your fork becomes the remote repository into which you can push changes.
13+
14+
### Create a branch
15+
The GitHub workflow assumes your master branch is always deployable. Create a branch for your local project or fixes.
16+
17+
For more information about branching, see the [GitHub documentation](https://guides.github.com/introduction/flow/).
18+
19+
### Clone the repository
20+
Cloning the repository copies your fork onto your computer. To clone the repository, click the "Clone or download" button on the GitHub website, and copy the resultant URL to the clipboard. In a command line window, type ```git clone [URL]```, where ```[URL]``` is the URL that you copied in the previous step.
21+
22+
For more information about cloning a reposity, see the [GitHub documentation](https://help.github.com/articles/cloning-a-repository/).
23+
24+
25+
### Downloading additive files
26+
Once the repository exists locally on your machine, manually execute ```git_bootstrap.exe``` found at the root of the repository. This application will perform a download operation for __Lumberyard binaries that are required prior to using or building the engine__. This program uses AWS services to download the binaries. Monitor the health of AWS services on the [AWS Service Health Dashboard](https://status.aws.amazon.com/).
27+
28+
### Running the Setup Assistant
29+
```git_bootstrap.exe``` will launch the Setup Assistant when it completes. Setup Assistant lets you configure your environment and launch the Lumberyard Editor.
30+
31+
## Contributing code to Lumberyard
32+
You can submit changes or fixes to Lumberyard using pull requests. When you submit a pull request, the Lumberyard support team is notified and evaluates the code you submitted. You may be contacted to provide further detail or clarification while the support team evaluates your submitted code.
33+
34+
### Best practices for submitting pull requests
35+
Before submitting a pull request to a Lumberyard branch, please merge the latest changes from that branch into your project. We only accept pull requests on the latest version of a branch.
36+
37+
For more information about working with pull requests, see the [GitHub documentation](https://help.github.com/articles/cloning-a-repository/).
38+
39+
## Purpose of Lumberyard on GitHub
40+
Lumberyard on GitHub provides a way for you to view and acquire the engine source code, and contribute by submitting pull requests. Lumberyard does not endorse any particular source control system for your personal use.
41+
42+
## Lumberyard Documentation
43+
Full Lumberyard documentation can be found here:
44+
https://aws.amazon.com/documentation/lumberyard/
45+
We also have tutorials available at https://gamedev.amazon.com/forums/tutorials
46+
47+
## License
48+
Your use of Lumberyard is governed by the AWS Customer Agreement at https://aws.amazon.com/agreement/ and Lumberyard Service Terms at https://aws.amazon.com/serviceterms/#57._Amazon_Lumberyard_Engine.
49+
50+
For complete copyright and license terms please see the LICENSE.txt file at the root of this distribution (the "License"). As a reminder, here are some key pieces to keep in mind when submitting changes/fixes and creating your own forks:
51+
- If you submit a change/fix, we can use it without restriction, and other Lumberyard users can use it under the License.
52+
- Only share forks in this GitHub repo (i.e., forks must be parented to https://github.com/aws/lumberyard).
53+
- Your forks are governed by the License, and you must include the License.txt file with your fork. Please also add a note at the top explaining your modifications.
54+
- If you use someone else’s fork from this repo, your use is subject to the License.
55+
- Your fork may not enable the use of third-party compute, storage or database services.
56+
- It's fine to connect to third-party platform services like Steamworks, Apple GameCenter, console platform services, etc.
57+
To learn more, please see our FAQs https://aws.amazon.com/lumberyard/faq/#licensing.
58+
59+

‎bootstrap_config.json

+5
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,5 @@
1+
{
2+
"Checksum": "3e36c3cf356bec79843dc58d75f81615f3f01df07e0954344b8e1fd5f53f6200e4408d7ae79c7e83fbec6e5e4e0f94f98da80da4d0ab6b4a43757b8915831d0d",
3+
"URL": "https://d3dn1rjl3s1m7l.cloudfront.net/1.10.0.0/lumberyard-1.10-448546f-pc_121117_212248-binaries.zip",
4+
"Uncompressed Size": 8041132924
5+
}

‎dev/.p4ignore

+24
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,24 @@
1+
*.ilk
2+
*.suo
3+
*.user
4+
*.o
5+
*.temp
6+
*.bootstrap.digests
7+
*.log
8+
*.exp
9+
*.vssettings
10+
*.exportlog
11+
*.mayaSwatches
12+
*.ma.swatches
13+
*.dds
14+
*.bak
15+
*.bak2
16+
Solutions
17+
BinTemp
18+
*.options
19+
*.pyc
20+
*.db
21+
Cache
22+
AssetProcessor_tmp.exe
23+
Builders_Temp
24+
Bin64vc*

0 commit comments

Comments
 (0)