DOCSLIB.ORG

Confidential. © 2009-2015 Crytek Gmbh. All Rights Reserved. Page

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Confidential. © 2009-2015 Crytek Gmbh. All Rights Reserved. Page With CRYENGINE 5.1.0, we have deprecated the support for Visual Studio 2012 and 2013. For more information, please check Visual Studio Supported Versions. This has implications on the language features that can be used in the code-base. This document outlines the most important coding standards that are applicable to CRYENGINE. Its main purpose is to achieve overall code consistency and software structural quality. It is a helper for improving code readability and easing maintenance. Programmers are expected to follow this standard while writing code for CRYENGINE. There may be few exceptions to deviate from the coding standard, since we cannot predict every scenario or situation that may occur in the future. The majority of code should follow these rules, so that we can have a clearer and maintainable code base. These rules apply to CRYENGINE, Sandbox and plug-in/extensions thereof. (All the code can be found under Code/CryEngine, Code/Sandbox and Code/CryExtensions) When you intend to deviate from the guidelines, you should mention this in the code review so that: Reviewer spends less time marking them. You can immediately state the reason for the deviation to avoid any confusion. Coding standard Disabled C++ features Uncrustify code formatting tool Common rules: Tabs and spaces Spaces in expressions Long and complex expressions Wrapping Long function parameter lists if statement for statement Infinite loops switch statement Conditional operator (ternary) Constructor initialization lists Formatting rules for composite types Naming conventions General naming rules Namespaces, using directives Class name Struct name Interface name Custom type name (typedef, using) Primitive types Enum names Template name Function name Complement names Non-member variable name Member variable name Global variable name Static variable name Thread-local storage variable name Macro name Variable naming prefixes File naming Copyright notice Implementation details in common interfaces Layout of C++ classes header files source files C++11 and newer, on the use of Modern C++ Using std::enable_if Using smart pointers Code quality Globals Macros Pointers and memory Const correctness Numeric compile-time constants Best practices Commenting Preprocessor CRT Memory allocation Standard Template Library (STL) Strings Compiler-specific features Confidential. © 2009-2015 Crytek GmbH. All Rights Reserved. Page 1 of 23 Undefined behavior Miscellaneous Express your intentions clearly Reduce code complexity Get rid of shared mutable state Disabled C++ features The CRYENGINE codebase is written in C++. The use of C language is discouraged, but may be appropriate for interactions with 3rd party C libraries, at your discretion. These features are disabled at the compiler level for all CRYENGINE modules, and cannot be used: Exceptions Run-time type information (RTTI) dynamic_cast operator Some plugins or extensions may (at their discretion) enable one or more of these features. However, it is then the responsibility of those plug-in or extension to ensure that no exceptions can propagate into the CRYENGINE modules, as this may cause undefined behavior. RTTI must be assumed to be incompatible across modules (use it only with types from the containing module). Uncrustify code formatting tool We recommend using our customized Uncrustify code formatting tool to format the code according to the rules described in this document. It can be found in <root>/Code/Tools/uncrustify, along with a config file (CryEngine_uncrustify.cfg). Note that any deviation from the guidelines introduced by the tool that cannot be formatted is acceptable. Unfortunately, no tool is 100% accurate, however if there is a systematic issue please inform the tool maintainer so that they can try to fix it. Common rules: Curly brackets should not be in the same line with other text (allowed exclusions are short single-liners in header files: constructors/destructors and get/set-like functions) Opening and closing curly brackets should be on the same column (allowed exclusions are '{}' in header files and single-liners mentioned above) When changing code in another module, mimic the style which is already present in the module Use one statement on each code line which: helps setting debugger breakpoints simplifies reading simplifies code merging allows to add an end-of-line comment easily when required A sample code block is outlined below: Confidential. © 2009-2015 Crytek GmbH. All Rights Reserved. Page 2 of 23 Example // good CMyGoodBar() : m_memberA(0) , m_memberB(0) { } // acceptable (exclusion) CMyGoodBar() : m_memberA(0) , m_memberB(0) {} // acceptable (exclusion) CMyGoodBar() : m_memberA(0), m_memberB(0) {} // bad CMyGoodBar() : m_memberA(0) , m_memberB(0) { } // bad CMyGoodBar() : m_memberA(0) , m_memberB(0) {} // bad CMyGoodBar() : m_memberA(0), m_memberB(0) {} // bad CMyGoodBar() : m_memberA(0), m_memberB(0) { } Tabs and spaces Format of every non-empty line of code should be: [<tabs>]text[<spaces>]text[<spaces>]... The following formatting options are not allowed: Space characters in the beginning of a row Tab characters in the right part of a row Recommended tab size is 2, although any setting can be used if the above rule is followed, and code should look good regardless. By setting the tab size to 2, the formatting tool will attempt to create a fixed block (spaces only) out of certain contexts, such as multi-line macro's, in an attempt to maintain right-alignment for the escape-newline sequence. However, more than 99% of the code should not be fixed-block since there is no right-alignment option that can be performed. Note: Don't use Convert tabs to spaces or similar options in your editor. Use Tab character to insert tabs in the code. If you follow this rule, then you can use any tab size without destroying existing format. Note that some old code still uses space characters instead of tabs and assumes that indentation is 2 to view such code properly, you can use Visual Studio's macros to switch between tabs size 2 and 4. Do not use space characters or multiple tabs to align expressions after wrapping lines. Preferably, let the formatting tool do this for you. Alternatively, you should use exactly one tab for indentation of wrapped lines if the tool cannot be used. Spaces in expressions Please ensure the below mentioned conditions are met: No space between function’s name and parentheses"(" No space before comma, semicolon, and parentheses Confidential. © 2009-2015 Crytek GmbH. All Rights Reserved. Page 3 of 23 Single space character before open and close brackets except while using double parentheses "))", and also after a comma Single space character before and after binary arithmetic operators (+, -, *, /, *, /, %, &, &&, |, ||, |=, ==, +=, etc.) and before unary operators (-, !, ~, etc.) Single space character before and after '?' and ':' in the conditional operator No spaces around < and > in template argument lists (see example below) Single space character between statement (if, while, for, switch, etc.) and the opening '(' Example if (a > b * c * (e - f)) { Grid<Sensor<float, double>> grid; const float r = ((a * 15.4f) / 3) + 2 + d * 4; DoSomething(&grid, a, c, e * f); ... } Long and complex expressions The below mentioned conditions should be followed while using long and complex expression in the code: Do not add multiple expressions, parameters or variables on the same line as it complicates both reading and code merging. It's always recomme nded to use a separate line for different expressions. Exceptions are possible. Do not use very complex expressions, especially as part of control statements. This may cause confusion for the user while decrypting the logic. Split complex expressions into multiple parts and use temporary const variables. It will make the code more readable and easier to debug. Use parentheses/brackets to improve readability of complex logical and arithmetical expressions. Understanding a complex braceless expression requires more time than understanding an expression with braces. Example // good int a = 3; int b = 5; // bad int a = 3, b = 5; Even though an expression is well-formed and non-ambiguous according to the C++ operator precedence rules, compilers will typically warn about omitted parentheses in certain expressions, even though they don't change the meaning of the expression. Therefore, prefer to introduce parentheses to clarify intentions when operators are "competing" inside one sub-expression: Two logical operators: a && b || c clarify to (a && b) || c Two bitwise operators: a | b & c clarify to a | (b & c) A shift and a compare: a >> b > c clarify to (a >> b) > c Any non-top-level assignment expression: if (a = b * c) clarify to if ((a = b * c)) Wrapping The formatting tool will maintain alignment for wrapped lines (By using spaces, it looks identical regardless of tab-space). This guideline can still be used for code where the code formatting tool cannot be used, but is generally obsolete since the code-base was reformatted. Use single tab indentation for wrapped lines. Do not align with ‘(‘, such alignment is hard to maintain in case of renaming functions and also sometimes it just looks like hanging in the middle of a page. If you think that the code looks bad after wrapping then use temporary variables to decrease sizes of the expressions. Confidential. © 2009-2015 Crytek GmbH. All Rights Reserved. Page 4 of 23 Example // good DoSomethingImportant( plumCount, “Alabama”, name, age, mass, validationPassed); // good DoSomethingImportant(plumCount,
Load more

Recommended publications
  • Unity Training Academy 2018-2019, #2 Aras Pranckevičius
    Random Things About Code Unity Training Academy 2018-2019, #2 Aras Pranckevičius 1 Generative Art – Made with Unity Caveat Emptor ● This is going to be totally random! ● Without any structure! ● ...so yeah :) 2 Random Intro 3 A long time ago in a galaxy far, far away... ● I thought these are awesome: ○ C++ ○ STL, Boost ○ Object Oriented Programming ○ Design Patterns ● Had hair! 4 Now... ● Most of these are... ”not that good” ○ C++: too complicated ○ STL/Boost: too complicated, over-engineered ○ OOP: only useful for UI widgets ○ Design Patterns: BS to sell books/courses ● No hair :( 5 Some things which I like: Futurist Programming ● “Futurist Programming” by Nick Porcino ● http://nickporcino.com/meshula-net-archive/posts/post168.html 6 Some things which I like: Futurist Programming ● No Compromise, No Waste Programming ○ The program is the BEST at what it does ○ The program is FAST ○ The footprint is SMALL ○ The code is CLEAR ○ The program is BUG-FREE ○ Abstractions must SIMPLIFY ○ The unnecessary is ELIMINATED ○ NO COMPROMISES in the name of Extensibility, Modularity, Structured Programming, Reusable Code, Top Down Design, Standards, Object Oriented Design, or Agility. 7 Some things which I like: Three Big Lies ● “Three Big Lies” by Mike Acton ● https://www.gdcvault.com/play/1012200/Three-Big-Lies-Typical-Design ● https://cellperformance.beyond3d.com/articles/2008/03/three-big-lies.html ● Fun fact: Mike is at Unity now, working on ECS and stuff! 8 Some things which I like: Three Big Lies ● Software is a platform ● Code designed around
    [Show full text]
  • BITSQUID: BEHIND T HE SCENES Building a Game Engine Design, Implementation & Challenges
    BITSQUID: BEHIND T HE SCENES Building a Game Engine Design, Implementation & Challenges Niklas Frykholm System Architect, Bitsquid DESIGN GOALS • An engine that is:! Flexible! Fast! And supports good workflows! ! • Not a click-and-play “game maker”! Aimed at professionals who want full performance and full control! • Not a repurposed first-person shooter! For all game types FLEXIBLE • Engine! Avoid bit-rot (large software systems get worse over time)! • Any game type! FPS, platformer, RPG, racing game, architectural visualization, etc! User must be in full control of game logic! • Wide range of platforms (mobile → high end PC)! Very different performance characteristics! Don’t try to hide platform differences (abstraction → inefficiency)! Users must be able to control the entire rendering pipeline (forward/deferred)! • Flexibility puts higher demands on users than click-to-play Hamilton’s Great Adventure (Fatshark: PC, PS3, Android) War of the Roses (Fatshark: PC) Krater (Fatshark: PC, OS X) The Showdown Effect (Arrowhead: PC, OS X) War of the Vikings (Fatshark) Magica Wizard Wars (Paradox North) Helldivers (Arrowhead) AVOIDING BIT-ROT • Care about code quality! Publish your source code! (We give it to our customers)! • Keep the engine small! Less code is better! Aggressively remove what you don’t use!! Don’t do everything that our customers want! (They can do it themselves in the source.)! • Refactor! When you find a better way to do things → rewrite! • Decouple! As few dependencies between systems as possible! Individual systems can be replaced
    [Show full text]
  • Flexible Rendering for Multiple Platforms
    Flexible Rendering for Multiple Platforms [email protected] Nikolaj Kledzik / Frans Enmark Polygon – Verktygslåda 8 Art Direction & Design Inspiration Logotyp 2011 © Nikolaj Kledzik / Frans Enmark Breakdown –Introduction –Bitsquid Rendering Architecture –Tools Bitsquid –High-end game engine for licensing –Multi-platform: PC, MAC, PS3, X360, High-end mobile –Currently powering 10 titles in production – Production team sizes 15-40 developers Bitsquid –Key design principles – Simple & lightweight code base (~200KLOC) –Including tools – Heavily data-driven – Quick iteration times – Data-oriented design –Highly flexible... Screenshot : WOTR “War of the Roses” Courtesy of Fatshark and Paradox Interactive Screenshot : WOTR “War of the Roses” Courtesy of Fatshark and Paradox Interactive Content Slide – Text Here – Or here “Krater” Courtesy of Fatshark Krater “Krater” Courtesy of Fatshark Screenshot: Shoot “The Showdown Effect” Courtesy of Arrowhead Game Studios & Paradox Interactive Screenshot Hamilton “Hamilton’s Great Adventure” Courtesy of Fatshark “Stone Giant” DX11 tech demo Flexible rendering –Bitsquid powers a broad variety of game types – Third-person, top-down, 2.5D side-scrollers and more –Different types of games can have very different needs w.r.t rendering – 30Hz vs 60Hz – Shading & Shadows – Post effects, etc.. –Game context aware rendering – Stop rendering sun shadows indoors, simplified rendering in split-screen Flexible rendering –Also need to run on lots of different HW-architectures –Cannot abstract away platform differences, we need stuff like: – Detailed control over EDRAM traffic (X360) – SPU offloading (PS3) – Scalable shading architecture (forward vs deferred, baked vs real-time) –What can we do? – Push the decisions to the developer! –But, make it as easy as possible for them..
    [Show full text]
  • Practical Particle Lighting
    Practical Particle Lighting [email protected] Nikolaj Kledzik / Frans Enmark Polygon – Verktygslåda 8 Art Direction & Design Inspiration Logotyp 2011 © Nikolaj Kledzik / Frans Enmark Overview –Introduction –Basic Particle Lighting –Improvements –Conclusions Introduction: Bitsquid –High-end game engine for licensing –Currently powering 10 titles in production – Team sizes between 15 and 40 developers –Techniques presented used in one announced title so far – “War of the Roses”, Fatshark / Paradox Interactive TODO: WOTR screenshot –Showing lit smoke pillars – “War of the Roses” Courtesy of Fatshark and Paradox Interactive Introduction: Particle Lighting –a.k.a. Billboard lighting –Focus on making billboards fit in with the environment – Must support dynamic local lights as well as global lighting environment –Cheap enough to be used on all non-emissive particles – Keep PS work to a minimum, push bulk cost to earlier stage (VS or DS or even off GPU on some arch.) Unlit Particles Motivation screenshot –Unlit particles Lit Particles Motivation screenshot –Lit particles Vertex Lighting –Super cheap – Calc incoming light per-vertex in VS (or on CPU) – Modulate with particle color in PS –Solves problem with fitting into rest of the scene –Better than nothing but looks very flat – No sense of incoming light direction biggest problem –Can we do better? Resurrecting an old friend: HL2-basis –Project lighting environment to HL2-basis[1] –Align HL2-basis vectors with billboard (i.e view space) Z+ Y+ X+ Lighting using HL2-basis –In VS: For
    [Show full text]
  • Theindiegamedeveloperhandbook.Pdf
    THE INDIE GAME DEVELOPER HANDBOOK This page intentionally left blank THE INDIE GAME DEVELOPER HANDBOOK Richard Hill-Whittall First published 2015 by Focal Press 70 Blanchard Road, Suite 402, Burlington, MA 01803 and by Focal Press 2 Park Square, Milton Park, Abingdon, Oxon OX14 4RN Focal Press is an imprint of the Taylor & Francis Group, an informa business © 2015 Taylor & Francis The right of Richard Hill-Whittall to be identified as the author of this work has been asserted by him in accordance with sections 77 and 78 of the Copyright, Designs and Patents Act 1988. All rights reserved. No part of this book may be reprinted or reproduced or utilised in any form or by any electronic, mechanical, or other means, now known or hereafter invented, including photocopying and recording, or in any information storage or retrieval system, without permission in writing from the publishers. Notices Knowledge and best practice in this field are constantly changing. As new research and experience broaden our understanding, changes in research methods, professional practices, or medical treatment may become necessary. Practitioners and researchers must always rely on their own experience and knowledge in evaluating and using any information, methods, compounds, or experiments described herein. In using such information or methods they should be mindful of their own safety and the safety of others, including parties for whom they have a professional responsibility. Product or corporate names may be trademarks or registered trademarks, and are used only for identification and explanation without intent to infringe. Library of Congress Cataloging-in-Publication Data Hill-Whittall, Richard.
    [Show full text]
  • Karelia-Ammattikorkeakoulu Viiden 3D
    KARELIA•AMMATTIKORKEAKOULU Tietojenkäsittelyn koulutusohjelma Janne Mononen VIIDEN 3D-PELIMOOTTORIN VERTAILU UUDEN KEHITTÄJÄN NÄKÖKUL- MASTA Opinnäytetyö Marraskuu 2016 OPINNÄYTETYÖ Marraskuu 2016 Tietojenkäsittelyn koulutusohjelma Tikkarinne 9 80220 JOENSUU 013 260 600 Tekijä(t) Janne Mononen Nimeke Viiden 3D-pelimoottorin vertailu uuden kehittäjän näkökulmasta Toimeksiantaja Joensuu Games Tiivistelmä Tässä opinnäytetyössä vertaillaan viittä helposti saatavilla olevaa 3D-pelimoottoria uuden tai kokemattoman kehittäjän näkökulmasta. Opinnäytetyön tavoitteena on vertailla peli- moottoreiden ominaisuuksia ja selventää lukijalle minkälaiselle kehittäjälle tai kehittäjäryh- mälle opinnäytetyöhön valitut pelimoottorit sopivat. Opinnäytetyö on tutkimuksellinen. Opinnäytetyöhön valittuja pelimoottoreita vertailtiin sellaisten ominaisuuksien osalta, jotka ovat tärkeitä kaikissa 3D-peliprojekteissa. Ominaisuuksia vertailtiin niiden monipuolisuu- den, helppokäyttöisyyden ja dokumentaation kattavuuden osalta. Opinnäytetyössä luotiin myös katsaus pelimoottoreiden käyttökustannuksiin ja rojaltimaksuihin. Opinnäytetyön tuloksena arvioidaan minkälaiselle kehittäjälle tai kehittäjäryhmälle vertai- lun pelimoottorit soveltuvat. Opinnäytetyön lopputuloksena kehittyi myös paljon vertailutie- toa ja huomioita pelimoottoreiden ominaisuuksista. Opinnäytetyön tuloksien on tarkoitus helpottaa uuden kehittäjän pelimoottorivalintaa. Kieli Sivuja 95 Suomi Liitteet Asiasanat pelimoottori, vertailu, Unity, Unreal Engine, Cryengine, Autodesk, Amazon, Stingray, Lumberyard
    [Show full text]
  • Maxime Capuano
    Maxime Capuano 164 rue Adhemar Fabri, La Roche-sur-Foron, France 07 78 39 57 69 – [email protected] malkaviel.github.io/particle/ Education Professional bachelor degree 2018 - 2019 • Puy-en-Velay IUT, France. • Academic interests: Medical imaging, 3D mathematics, algorithms and programming. • Developed a MRI visualization software with the Unity Game Engine and the Microsoft Hololens, to display and manipulate MRI images on top of patients in real-time. DUT 2015 - 2017 • Puy-en-Velay IUT, France. • Academic interests: General computer science knowledge, C++ and C# programming, 3D mathematics and algorithms, game development. • Developed a complete 2D game with the Unity Game Engine with a group of 14 students. • Reworked the Puy-en-Velay IUT’s website. Capuano Resume – Page 1 of 3 Professional Experience OpenStudio 2018 – 2019 Back-end Web Developer (Apprenticeship) • Puy-en-Velay, France. • Helped at the development of new functionalities, correction of bugs, and refactoring of the back-end framework and plugins used by OpenStudio. • Worked on the introduction of automating tools and debugging tools in the development process, in order to automatically test the websites functionalities, make their deployment easier and make the development and debugging of projects easier and faster. FB Digital 2017 Back-end Web Developer (Internship) • Brioude, France. • At first, assisted the lead developer with small tasks, in order to gain experience with the tools used by FB Digital (PHP, Symfony web framework, Thelia e-commerce framework). • Later, worked as the lead developer on an e-commerce project, implementing most back-end functionalities. Capuano Resume – Page 2 of 3 Personal Projects The Forgotten Ark 2017 • A first person shooter arena in a sci-fi universe, where the player can select its archetype to fit its play-style.
    [Show full text]
  • Swedish Game Developer Index 2016 Game Developer Index
    Swedish game developer index 2016 game developer index First Edition Published by Swedish Games Industry Research: Hanna Metsis, Jacob Kroon Text & Design: Jacob Kroon Swedish Games Industry is a partnership between ANGI and Spelplan-ASGD. Dataspelsbranschen Swedish Games Industry Klara norra kyrkogata 31, Box 22307 SE-104 22 Stockholm www.dataspelsbranschen.se Contact: [email protected] 2016 2 Table of contents summary 4 preface 5 revenue & profit 6-7 employment 8 number of companies 8 gender distribution 9 turnover per company 10 employees per company 10 largest companies 11 company map 12-13 future 15 actual revenues 16 domestic market 17 worldwide 18-20 intellectual property infringement 20 threats & challenges 23 listed game companies 24-26 conclusion 28 methodology 31 timeline - a selection 33 glossary 34 3 summary ame Developer Index analyzes the growth of Swedis video game companies and international trends by compiling the annual accounts of the companies. Swedish game development is an export industry operating on a highly globalized market. The domestic Gindustry has grown from a hobby of enthusiasts to a world-wide industry with cultural and economic significance under just a few decades. The Game Developer Index 2016 summarizes the growth of the latest fiscal year. The sumary in brief: Revenue increased by 41 per cent to almost EUR1,3 billion in 2015. A 200 per cent increase in two years. A majority of companies are profitable and the industry has reported a total profit for seven years running. Employment increased by 19 per cent, more than 550 full-time positions, to a total of 3709 employees.
    [Show full text]
  • Swedish Technology Report 2 0 1 7
    Swedish Technology Report 2 0 1 7 Table of contents EXECUTIVE SUMMARY...............................................................2 TECHNOLOGY MARKET DRIVERS................................................4 SWEDISH TECH IPOs 2016: A REVIEW.......................................9 MARKET EXPECTATIONS...........................................................12 REDEYE SCREENING................................................................18 TOP PICKS-PORTFOLIO............................................................24 APPENDIX: REDEYE RESEARCH & RATING................................31 APPENDIX COMPANIES: Addnode, Allgon, AllTele, Anoto, Arise, Avega..................................36 Avtech, aXichem, Bredband2, Cherry, Cinnober..............................48 Crowdsoft, DGC, Doro, Enea, Ericsson.............................................58 Fingerprint Cards, Formpipe, Heliospectra.................................... 68 Hexatronic, Invisio, Lagercrantz, Mr Green.....................................74 Mycronic, myTaste, NC Lahega, Neonode, Nokia.............................82 Opus, Paynova, Photocat, Polygiene, Powercell.............................92 Prevas, Sensys Traffic, Stillfront, Systemair...................................102 Waystream, Verisec, West International........................................110 APPENDIX: REDEYE TECHNOLOGY TEAM.................................116 APPENDIX: DISCLAIMER.........................................................119 Executive Summary Redeye’s technology team consists of 7 analysts, which
    [Show full text]
  • Realtidsrendering Av Hud Daniel Holst
    LiU-ITN-TEK-A--17/019--SE Realtidsrendering av hud Daniel Holst 2017-06-09 Department of Science and Technology Institutionen för teknik och naturvetenskap Linköping University Linköpings universitet nedewS ,gnipökrroN 47 106-ES 47 ,gnipökrroN nedewS 106 47 gnipökrroN LiU-ITN-TEK-A--17/019--SE Realtidsrendering av hud Examensarbete utfört i Medieteknik vid Tekniska högskolan vid Linköpings universitet Daniel Holst Handledare Apostolia Tsirikoglou Examinator Jonas Unger Norrköping 2017-06-09 Upphovsrätt Detta dokument hålls tillgängligt på Internet – eller dess framtida ersättare – under en längre tid från publiceringsdatum under förutsättning att inga extra- ordinära omständigheter uppstår. Tillgång till dokumentet innebär tillstånd för var och en att läsa, ladda ner, skriva ut enstaka kopior för enskilt bruk och att använda det oförändrat för ickekommersiell forskning och för undervisning. Överföring av upphovsrätten vid en senare tidpunkt kan inte upphäva detta tillstånd. All annan användning av dokumentet kräver upphovsmannens medgivande. För att garantera äktheten, säkerheten och tillgängligheten finns det lösningar av teknisk och administrativ art. Upphovsmannens ideella rätt innefattar rätt att bli nämnd som upphovsman i den omfattning som god sed kräver vid användning av dokumentet på ovan beskrivna sätt samt skydd mot att dokumentet ändras eller presenteras i sådan form eller i sådant sammanhang som är kränkande för upphovsmannens litterära eller konstnärliga anseende eller egenart. För ytterligare information om Linköping University Electronic Press se förlagets hemsida http://www.ep.liu.se/ Copyright The publishers will keep this document online on the Internet - or its possible replacement - for a considerable time from the date of publication barring exceptional circumstances. The online availability of the document implies a permanent permission for anyone to read, to download, to print out single copies for your own use and to use it unchanged for any non-commercial research and educational purpose.
    [Show full text]
  • Data Driven Visualization Tool for Game Telemetry Martin Engelbrektsson Marcus Lilja
    LiU-ITN-TEK-A--17/055--SE Data Driven Visualization Tool for Game Telemetry Martin Engelbrektsson Marcus Lilja 2017-10-20 Department of Science and Technology Institutionen för teknik och naturvetenskap Linköping University Linköpings universitet nedewS ,gnipökrroN 47 106-ES 47 ,gnipökrroN nedewS 106 47 gnipökrroN LiU-ITN-TEK-A--17/055--SE Data Driven Visualization Tool for Game Telemetry Examensarbete utfört i Medieteknik vid Tekniska högskolan vid Linköpings universitet Martin Engelbrektsson Marcus Lilja Handledare Henry Fröcklin Examinator Stefan Gustavson Norrköping 2017-10-20 Upphovsrätt Detta dokument hålls tillgängligt på Internet – eller dess framtida ersättare – under en längre tid från publiceringsdatum under förutsättning att inga extra- ordinära omständigheter uppstår. Tillgång till dokumentet innebär tillstånd för var och en att läsa, ladda ner, skriva ut enstaka kopior för enskilt bruk och att använda det oförändrat för ickekommersiell forskning och för undervisning. Överföring av upphovsrätten vid en senare tidpunkt kan inte upphäva detta tillstånd. All annan användning av dokumentet kräver upphovsmannens medgivande. För att garantera äktheten, säkerheten och tillgängligheten finns det lösningar av teknisk och administrativ art. Upphovsmannens ideella rätt innefattar rätt att bli nämnd som upphovsman i den omfattning som god sed kräver vid användning av dokumentet på ovan beskrivna sätt samt skydd mot att dokumentet ändras eller presenteras i sådan form eller i sådant sammanhang som är kränkande för upphovsmannens litterära eller konstnärliga anseende eller egenart. För ytterligare information om Linköping University Electronic Press se förlagets hemsida http://www.ep.liu.se/ Copyright The publishers will keep this document online on the Internet - or its possible replacement - for a considerable time from the date of publication barring exceptional circumstances.
    [Show full text]
  • GAME DEVELOPER INDEX 2015 Based on 2014 Swedish Annual Reports Table of Contents
    GAME DEVELOPER INDEX 2015 Based on 2014 Swedish Annual Reports Table of Contents SUMMARY 2 PREFACE 4 TURNOVER AND PROFIT 5-6 NEW EMPLOYMENT 8 NUMBER OF COMPANIES 8 GENDER DISTRIBUTION 9 TURNOVER PER COMPANY 9 EMPOYEES PER COMPANY 9 BIGGEST PLAYERS 12 DISTRIBUTION PLATFORMS 12 REVIEWS 13 GAME DEVELOPER MAP 15-16 FUTURE 17-20 ACTUAL REVENUES 22 PIRACY 22 GLOBALLY 23 THREATS 25 CONCLUSION AND METHODOLOGY 26 TIMELINE - A SELECTION 27 GLOSSARY 28 On the cover: Unravel, Coldwood Interactive 1 Summary The Game Developer Index analyzes the activities of Swedish game developers, as well as international trends, throughout the year by compiling the annual accounts of the companies. Swedish game development is an export industry operating in a highly globalized market. The gaming business has grown from a hobby of enthusiasts to a world-wide industry with cultural and economic significance. The Game Developer Index 2015 summarizes the reports of the latest financial year. The summary in brief: • Turnover of Swedish game developers increased by 35 percent to EUR 930 million in 2014. • The majority of the companies are profitable and the industry has reported a total profit for six years running. • Employment increased by 23 percent, or 583 full-time positions, to a total of 3,117 employees. • The proportion of women increased by 39 percent, compared with 17 percent for men. • The compound annual growth rate (CAGR) in the period 2006-2014 is 39 percent. • Forty-three new companies have been added, which amounts to 213 active companies - an increase of 25 percent. • The total value, including acquisitions, of Swedish game developers was over EUR 2.75 billion in 2014.
    [Show full text]