Показаны сообщения с ярлыком Godot. Показать все сообщения
Показаны сообщения с ярлыком Godot. Показать все сообщения

16 февраля 2018

Tetris-Karro 2.0.0 / Godot Engine 2.1.4



Path 1.9.10 - 2.0.0

- Правка tetris_doc.txt
- Правка строки Credits.
- Новые звуки, старт, пауза.
- Доработки текстуры блока.
- Доработки текстуры фона, кубы.
- Доработки эффекта фона, кубы.
- Доработки эффекта фона, смаил.
- Удален эффект линии (огненная сфера).
- Обновление игрового движка Godot Engine 2.1.4.
- Правка логики, расположения интерфейса пользователя.
- Удален звук мелодии при повторном рестарте сессии игры.
- Дополнительные кнопки управления (клавиши), пауза, звук, сброс и тд.
- Две новые фигуры, точка (один блок) и двоеточие (два блока).
- Импорт нового шрифта с продержкой Юникода (NotoSans).
- Оптимизация интерфейса пользователя для нового шрифта (NotoSans).
- Доработки эффекта фона, молния (анимация, расположение).
- Проверка поддержки контролеров (геймпадов) серии X-box 360.
- Замена названия кнопки, (R)estart - Очистить на дне стакана все блоки, увеличить счетчик сессии.
- Оптимизация размещения ресурсов проекта (отдельные папки ресурсов, sound, scripts и тд).
- Добавлена стартовая сцена с логотипом, только при первом запуске проекта.
- Добавлен общий внутреигровой таймер (время игры/работы приложения).
- Добавлена начальная локализация проекта, русский и английский язык.
- Правка базовой версии сайта (http://crimea-karro.ru/dev_karro/tetris/).
- Добавлена начальная логика переключения локализации проекта, при старте (GUI).
- Удаление анимации интерфейса пользователя (левый блок цифр).
- Корректировка архивов игрового проекта для разных типов ОС (загрузка / сайт).

* Патчноут отражает ключевые изменения в игре и не содержит список всех исправлений.

https://crimea-karro.ru/dev_karro/tetris/

30 января 2018

Godot 3.0

Студия OKAM после 18 месяцев разработки подготовила выпуск свободного игрового движка Godot 3.0, предоставляющего средства для создания 2D- и 3D-игр. Движок поддерживает простой для изучения язык задания игровой логики, удобную графическую среду для проектирования игр, систему развёртывания игр в один клик, широкие возможности анимации и симуляции физических процессов, мощный встроенный отладчик и систему выявления узких мест в производительности.
Код игрового движка, среды проектирования игр и сопутствующих средств разработки (физический движок, звуковой сервер, бэкенды 2D/3D рендеринга и т.п.) распространяются под лицензией MIT.

Исходные тексты движка были открыты в 2014 году, после десяти лет развития проприетарного продукта профессионального уровня, который использовался для создания и публикации многих игр для PC, игровых консолей и мобильных устройств. Движком поддерживаются все популярные стационарные и мобильные платформы (Linux, Windows, macOS, Wii, Nintendo 3DS, PlayStation 3, PS Vita, Android, iOS, BBX), а также разработка игр для Web. Готовые для запуска бинарные сборки сформированы для Linux, Windows и macOS.   

25 января 2018

Godot / GLES2 and GDNative, progress report #1

Introduction

Thanks to our very supporting patrons I have the opportunity to work part-time on Godot! My work will be mostly about implementing an OpenGL ES 2.0 compatible rendering backend for Godot 3.1, as well as maintaining the GDNative system and bindings.
The first month I spent on getting started and familiar with the rendering in Godot.
Since I want to be able to help out with more rendering related tasks in the future, in places where existing code could be re-used, I am rewriting those parts myself to get a better understanding of the code.

Roadmap


Because I am still new to the rendering system in Godot, I might not be experienced enough to make good estimates of what can be achieved, but the rough roadmap looks like this.

https://godotengine.org/article/gles2-and-gdnative-progress-report-1

09 января 2018

Godot / A look at the GDNative architecture

The GDNative architecture changed a lot since the very first version of the then-called "DLScript". With the release of Godot 3.0 approaching and the API getting more and more stable it is a good time to give an overview of what GDNative actually looks like now.

GDNativeLibrary

A GDNativeLibrary is a resource type that abstracts over the actual binary files needed for each platform. It contains a few properties (how Godot should deal with repeated loads of the library, name prefixing, ...), a list of "entry" library paths and a list for libraries that an "entry" library depends on.

Those lists are a simple mapping from a set of feature tags to either a file path or an array of file paths in case of the dependencies.

Feature tags

Godot has a feature tag system. A feature tag hints that a certain attribute or feature is available. Example tags are Windows, X11, 32, 64, mobile and many more. When exporting a game it is also possible to define tags yourself which then might change how the game will work.

For more information on feature tags see this docs page.
An entry in either of those lists inside the GDNativeLibrary resource consists of a key and a value. The key is a .-separated list of feature tags that need to be present.
So for example the library that's supposed to be used on a 64 bit Linux machine could have the key X11.64, while the same Windows machine could have the key Windows.64.
In the Godot editor there is a graphical user interface to make the editing of such a resource more user friendly.



All the entries will be checked from top to bottom and entries with a non-existing feature tag will be skipped. The first entry where all the tags are available will be used, so order is significant.

https://godotengine.org/article/look-gdnative-architecture


18 декабря 2017

Godot / Introducing the new "last minute" Lightmapper

Wait, are we not in Beta?

A considerable number of users requested a more efficient way to have GI (Global Illumination) in their projects. Godot 3.0 currenty offers the GIProbe node, which provides a real-time approximation to GI. This generally works and looks pretty, but it's quite shader intensive, which makes it not work on mobile or low end GPUs. The newly added VR support also suffers with GIProbe, as it has to render in very high resolutions.
The solution to these problems is to add support for a more traditional lightmapper (pre-baked light texture). Light is precomputed offline and rendered to a texture, which is then used by the geometry.

I thought it may not be too difficult to add one, so I started work on Sunday and completed it on Wednesday.


The biggest challenge of this workflow is not the lightmap itself, but the fact that it should be easy to use (which is Godot's #1 design priority).

https://godotengine.org/article/introducing-new-last-minute-lightmapper

05 декабря 2017

Shedding light on Godot's development process

Godot keeps growing steadily in both users and contributors, and 3.0 will be our best release yet. As our community keeps expanding, the development process also reshapes to accommodate new contributions.

While our process is completely transparent, it is not obvious for a large part of the community how new features, fixes and improvements are added. This short article will attempt to shed some light on it.

https://godotengine.org/article/shedding-light-on-godot-development-process

29 ноября 2017

Introducing onion skinning for the Godot game engine

Right on time before Beta Freeze, our superstar contributor Pedro Estebanez completed Onion Skinning support! This implementation is really good, and allows visualizing future and past frames. This helps animators have a much greater deal of control on repositioning objects on every frame.

More can be read about this work in Pedro's Blog.

08 ноября 2017

Godot / Help fix the remaining issues for 3.0

Godot 3.0 is in its final march towards a stable release, hopefully before year's end. The first beta will be released shortly and then release candidates and stable.
There are, however, many issues open in the tracker and the idea is to fix as many as possible before 3.0 is out. We are working hard to get everything fixed, but extra hands are always very welcome.


This is a great chance to be a hero and help close issues! Also, if you are not familiar with Godot's internals, this is a great starting point to start contributing.

https://godotengine.org/article/hero-wanted-help-fix-remaining-issues-30

06 ноября 2017

Godot 3.0 switches to Bullet 3 for physics

Godot Physics Engine

Back at the first versions of Godot (a decade ago), not many physics engines existed or were available. Even if a few were, Godot always had quite demanding API requirements for them (such as Area nodes, KinematicBody, RayCast shapes, etc), so they were not usable without a lot of modification. This led me to do some research and write my own.
Over time this became quite a hassle, because maintaining a physics engine and keeping it up to date with the new techniques and algorithms is time consuming.

Introducing Bullet 3

Godot always supported an abstract physics interface, so Andrea Catania (Odino) volunteered to add Bullet 3 support as a back-end. I initially though it would not be possible to replicate Godot API in Bullet faithfully, but Andrea proved me wrong and did a fantastic job. He also finished before Beta deadline, so his work was just merged and will be present in Godot 3.0.
Physics should work just like before, and no code should change, except Bullet is being used internally. Godot old physics engine is provided for compatibility and can be selected in the project settings, but will likely be removed by the time 3.1 is out.

New Possibilities


With Bullet as physics back-end, new possibilities emerge, such as soft body and cloth support and GPU (OpenCL) physics. This will be added after 3.0 is out, likely for 3.1.

https://godotengine.org/article/godot-30-switches-bullet-3-physics

28 сентября 2017

Godot 3's renderer design explained

Godot uses a considerably different approach to rendering (and rendering abstraction) than other, popular, game engines. The motivation behind it was not to achieve the maximum performance in extreme use cases, but accomodate better to most user's needs.

This document was written in hopes to find more developers that would like to help us write rendering code, as it explains the overall design. Without it it's quite difficult to get into the internals. Rendering engineers are rare to find, so this can be a starting point. If you are not an existing or aspiring rendering engineer and you still want to help, please donate to our Patreon :) so we can eventually hire intern work for this.


Please also ask for anything that might still be unclear to be explained further if needed. As always, feedback is very welcome as this is an open project.

https://godotengine.org/article/godot-3-renderer-design-explained

25 августа 2017

Godot / A small defense of glTF 2.0 on its comparison against OpenGEX

A few weeks ago, I wrote an article about why I believe glTF 2.0 to be a great format and that we should encourage its widespread adoption. I also compared it to other formats, including Eric Lengyel's OpenGEX.

As I mentioned on the original article, I think OpenGEX is a very good format. My main criticism to the format was that development is not lead in what today would be considered an open fashion. Eric alone maintains control of it. In contrast, glTF is a true standard developed by a non profit and an open development process.
Today, Eric has published what I assume is a defense of OpenGEX vs glTF (and the ancient Collada). Eric has claimed that glTF is a format with design flaws (and that it is not fit to be a pipeline format).


While I agree on many points, and I won't argue that OpenGEX is a great format, I just wanted to clarify a few things from my point of view for those interested in the technical aspects, explaining why many of glTF "shortcomings" are, in my opinion, actually brilliant design decisions. All this, of course, always for the sake of helping glTF 2.0 gain more adoption.

https://godotengine.org/article/small-defense-gltf

04 августа 2017

Support glTF 2.0 / Godot Engine

glTF 2.0 was introduced two months ago by Khronos, the body behind Vulkan and OpenGL.

Today, this format was added to Godot, which now supports the full specification. The reasoning behind this late feature addition is that, now that we released 3.0 alpha1, users need more content to test with the new 3D engine.


Sites like Sketchfab provide plenty of PBR-ready assets for downloading, and plugins that export scenes from other popular game engines to this format.

The surprise, though, is how good this format is for video game asset exchange. Nothing as good existed before, and it solves a problem that we, as an industry, have been struggling with for a long time.

Khronos, with glTF 2.0, has given us a fantastic chance to standardize a smooth workflow between 3D modelling software and game engines. To better understand why, a list of previous attempts will be explained and why they failed.

https://godotengine.org/article/we-should-all-use-gltf-20-export-3d-assets-game-engines

12 июля 2017

GODOT / Beta release for Python support

This is a guest post by Emmanuel Leblond (touilleMan), a Godot contributor and Python lover who develops a GDNative interface to use Python 3 as alternative scripting language in Godot. To answer the obligatory question: yes, the plan is still to ship Godot 3.0 with GDScript, VisualScript and C# support. Python support should also be ready by then and usable plug 'n play thanks to GDNative; its main advantage compared to the Python-like GDScript will be the access to the whole Python ecosystem.

Who said Godot's only about waiting? Today we are releasing the first beta version of Python for Godot, the GDNative interface that enables you to use the full-blown Python 3 as a scripting language for Godot games. Now we need you to try it and give your feedback, so that it can be made as good as possible for the upcoming 3.0 release!
All core features of Godot are expected to work fine:
  • Builtins (e.g. Vector2)
  • Object classes (e.g. Node)
  • Signals
  • Variable export
  • RPC synchronization

On top of that, mixing GDScript and Python code inside a project should work fine, have a look at the Pong example to see how you can convert one by one your existing GDScript code to Python fairly easily.

https://godotengine.org/article/beta-release-python-support

01 июля 2017

Tests needed for Godot 2.1.4-beta

Already more than 2 months since the last maintenance release in the 2.1 branch, and many bug fixes as well as new developments have made it to that branch.

Some of those new developments being slightly more experimental than we use to merge in the stable branch, the upcoming 2.1.4 release will need some heavy testing from the community to make sure it does not bring regressions.

So now's your time to shine:
What are regressions? They are bugs that did not occur in the previous stable release (2.1.3) but which can now be experienced in the beta build. You can also report bugs in the new features of 2.1.4, which, even if not strictly speaking regressions, should be worth looking into before the release.

Note: In this build the 32-bit Linux binaries are missing (both for the editor and the export templates) due to a buildsystem issue; this will be fixed before the stable release.

Happy testing, and thanks for your help!

15 июня 2017

Godot Progress report April/May 2017

It's been a while since the last progress report, and there have been lots of changes in the development branch that you might not have heard of yet. Usually we let our lead developer Juan (reduz) do progress reports on his impressive work on rendering features, but since he was in holidays for more than a month, we'll showcase the work of some key contributors this time.

This report covers important changes made by all contributors from April to today, excluding Juan's recent work which will be covered in his next progress report (but check his Twitter account for some more 3.0 teasers). There were over 300 commits by more than 30 different contributors, so this was a busy time even while our lead dev was away.


Before going over some hand-picked changes, we'd like to welcome new contributors who got involved in the engine development during the last few months: magyar123, mcanders, Noshyaar, RameshRavone, toger5 and touilleMan. Thanks for your contributions, and we hope to see you stick around and become core developers!

https://godotengine.org/article/progress-report-april-may-2017

16 мая 2017

Godot: GDNative is here / Godot 3.0 progress report #6

A short introduction to the new GDNative module (formerly DLScript) and how to use it in a project. This is a very early version, but the overall process will stay the same.

https://godotengine.org/article/dlscript-here

***

Godot 3.0

Another month of work, another progress report. This month work was divided into completing the exporters, GDNative (formerly DLScript) and the new particle system.

 https://godotengine.org/article/godot-30-progress-report-6


15 мая 2017

Godot course on Kickstarter next Monday!

GDquest, content creator and gamedev teacher of Krita and Godot fame, will soon start a Kickstarter campaign for a professional quality game creation course targeting the upcoming Godot 3!

Among Godot developers, we are all thrilled about the project and want it to be a huge success, so mark the date and be sure to support the campaign!

https://godotengine.org/article/godot-course-kickstarter-next-monday

01 мая 2017

Dreams of Elendin 2 v1.6.2


Системные требования:

Processor: Intel® Pentium® Processor P6200 and newer.
Memory: 2 GB RAM.
Graphics: OpenGL 2.1+ / Nvidia GeForce 200 series and newer, AMD Radeon HD 5000 Series and newer, Intel HD Graphics in Intel P6200 (GMA 4500) processors and newer.
Hard Drive: 250+ MB HD space.
Display resolution: 1280 x 720.
HTML5: Chrome Web Browser (base).

----------------------------------------------------------------------------

Тестируемая Конфигурация:

- Intel® Core™ i5- 4690K @4.2 GHz.
- DDR3 (1600) - 24GB (Dual).
- Ubuntu 16.04.1 /  Linux Mint 18 / x-86_64.
- DE / Mate 1.16 (Compiz off).
- Kernel 4.8
- Multi-monitor 3280x1080
- Intel® HD Graphics 4600
- Nvidia GTX-1050 TI Windforce ddr5 4GB / 128 bit.
- Nvidia GTX-650 ddr5 1024 mb / 128 bit.
- Drivers 378.13
- WineHQ 2.x x-86_64 (Windows).


----------------------------------------------------------------------------

Path 1.6.1 - 1.6.2

- Правка DoE2_doc.txt
- Дополнен DoE2_doc.txt
- Обновление игрового движка Godot Engine 2.1.3


* Патчноут отражает ключевые изменения в игре и не содержит список всех исправлений.

----------------------------------------------------------------------------

https://crimea-karro.ru/dev_karro/start.html
http://crimea-karro.ru/dev_karro/doe/


14 апреля 2017

Godot 2.1.3

Short of three months after the release of Godot 2.1.2, the community is proud to announce this new maintenance update in the stable branch, Godot 2.1.3!

Due to the long development process of the upcoming Godot 3.0 (see our Devblog for technical posts about its impressive progress), many contributors took a renewed interest in the 2.1 branch. This release therefore brings various new features to GDScript, the editor, some nodes' API – but we tried to ensure that compatibility with earlier 2.1.x releases would be fully preserved.

Download it now, and read on for details on the update!

A big thankyou to all the contributors who worked on this release by implementing bug fixes or features, or testing the changes to spot potential regressions and help debug issues.

https://godotengine.org/article/maintenance-release-godot-2-1-3

11 апреля 2017

Godot 3.0 progress report #6

Another month of work, another progress report. This month work was divided into completing the exporters, DLScript and the new particle system.

Web Export

Godot has now an experimental exporter to WebAssembly+WebGL2, Thanks to Eska014's work. You need latest Chrome or Firefox to test it, but it works really well. It even runs games flawlessly on mobile web!
Here's a small demo you can try! (again, remember, latest versions of Chrome or Firefox only!).

DLScript

We wrote our own article about DLScript (Name is not final!). Let me tell you that this amazing new feature by Thomas Herzog (Karrofel) is the real deal. It allows way too many amazing things:
  1. Add Godot objects made in C++, without recompiling Godot or the editor. Before this, a module had to be created, which including recompiling everything.
  2. Optimize any part of your game by rewriting it transparently in C++, wihout recompiling the engine or templates.
  3. Bind to any external libraries (ie, SQLite, Steam, etc) without any recompiling. Even downloading the bindings from our asset sharing is possible.
  4. Add import/export formats using official libraries from outside Godot. Ie, you could download an FBX import module from the asset sharing. Same as direct support for stuff such as Spine using their own lib.
  5. Add external scripting languages, such as Lua, Python etc. Of course, without integration as nice as GDScript, and you'll have to be aware of the limitations.
This will be one of the new amazing additions of Godot 3.0

New Particle System

Godot 3.0 will come with a new particle system. As times change, the main difference is that this one processes particles entirely in GPU. What does this mean?
Speed!

you can have hundreds of thousands of particles on legacy CPUs or mobile.. or several million particles on modern desktop GPUs.

https://godotengine.org/article/godot-30-progress-report-6

Сектора Лирики