General: This is the home page of a channel. It is similar to someone's profile "wall" in a social network context. Posts created by the channel are displayed according to the observer's viewing permissions.
Create a Post: If you have permission to create posts on the channel page, then you will see the post editor at the top.

Wed, 22 May 2019 18:47:59 +0200 last edited: Thu, 23 May 2019 00:10:50 +0200

jMonkeyEngine 3.3.0-alpha2

A non-production release, for development and testing only, not intended to be used in any product. Largely untested, without complete/reliable documentation, and without SDK support. Vital features may be missing. The feature-set, API, and serialization format might change drastically before the next release, if there is one.

Major update for Visual Shaders in Godot 3.2

Godot Engine Official

Wed, 22 May 2019 10:48:46 +0200

Major update for Visual Shaders in Godot 3.2

With the Godot 3.1 release, the Visual Shader editor was recreated from the ashes of its Godot 2.x ancestor. While usable and packed with visual features, Visual Shaders lacked many features from their Shader (script) big brother. A new update has been prepared for Godot 3.2 to solve this problem.

My name is Chaosus, I'm the one of the core contributors of Godot, and I'm gladly presenting this update to our beloved engine. So, let's begin reviewing the new features.

Members menu

The menu which the user used for adding nodes to the shader graph was the most unwieldy part of the old visual shader graph. This menu has been rewritten to a comfortable, tree-based popup.

Image/photo

As you can see, there are many categories inside, each one with subcategories filled with nodes.

Image/photo

If you are lost in this tree or want to find a specific node, you can use the search bar above the tree.

Once you've found the required node, you can add it to the graph by using drag and drop, pressing the Create button, hitting Enter, or double-clicking on the node in the tree.

Image/photo

Also, this popup has the following properties:

If you right-click on the graph, this menu will be called at the cursor position and the created node, in that case, will also be placed under that position; otherwise, it will be created at the graph's center.
It can be resized horizontally and vertically allowing more content to be shown. Size transform and tree content position are saved between the calls, so if you suddenly closed the popup you can easily restore its previous state.
The Expand All and Collapse All options in the drop-down option menu can be used to easily list the available nodes.

New API and exposed scalar functions to Vector

There a bunch of new nodes added as the part of this update. Here are the lists of new nodes.

For Scalar and Vector:

ACosH
ASinH
ATanH
Clamp
Degrees
Distance
Exp2
Log2
SmoothStep
Step
FaceForward
Radians
Reflect
Refract
RoundEven
Trunc
InverseSqrt
Reciprocal
OneMinus

Exposed to Vector from Scalar:

Abs
ACos
ASin
ATan
Ceil
Cos
CosH
Exp
Floor
Frac
Log
Round
RoundEven
Sign
Sin
SinH
Sqrt
Tan
TanH

For Transform:

TransformFunc
Determinant
Inverse
Transpose
OuterProduct
Pre-component multiplication modes for TransformMult

For Color:

ColorFunc
Grayscale
Sepia

Other:

Expression
Fresnel
BooleanScalar
BooleanUniform
ScalarDerivativeFunc
VectorDerivativeFunc
If
Switch

Notes

Vector now has all the Scalar functions which are executed per-component, e.g. Round will round all components. These can be used to achieve various effects.

The majority of these new functions reuse standard nodes such as ScalarFunc or VectorFunc as a base. This is intended, for compactness.
All the added nodes are compatible with pre-existing visual shaders. There should be no problems (i.e. no compatibility breakage) when converting existing visual shaders from 3.1 to the new system; just open it and continue to work.

Input nodes

These nodes are helpers to link the associated input parameters in the Input node. Currently, they are subdivided in All (with input parameters which can be used in all three shader modes) and Vertex/Fragment/Light categories for comfortability.

Image/photo

Expression node

The Expression node allows you to write Godot Shading Language (GLSL-like) expressions inside your visual shaders! The node has buttons to add any amount of required input and output ports and can be resized. You can also set up the name and type of each port. The expression you've entered will apply immediately(after focus leaves out the expression text box) to the material, any parsing or compilation errors will be printed to the Output tab. The outputs are initialized to their zero value by default. The new node is located under the Special tab and can be used in all shader modes.

Image/photo

This example gif shows you how to create and use it. It's quite simple as you can see.

The possibilities of this node are almost limitless – you can write complex procedures, and use all the power of Godot (text-based) shaders, such as loops, discard keyword, extended types, etc. For example:

Image/photo

Swirl shader code by LKS: https://www.reddit.com/r/godot/comments/90de7a/swirl_shader/

Many thanks K. S. Ernest Lee (iFire) for helping me fixing the bugs, testing and giving suggestions to create this feature!

Fresnel

The Fresnel node is designed to accept normal and view vectors and produces a scalar which is the saturated dot product between them. Additionally you can setup the inversion and the power of equation. Currently it is placed under Special menu section.

Image/photo

You can read more about this nice effect on this blog postor the dedicated Wikipedia article.

Boolean node

The Boolean node was not exposed to the visual shaders until now. They can be converted to Scalar or Vector to represent 0 or 1 and (0, 0, 0) or (1, 1, 1) respectively. This property can be used to enable or disable some effect parts by one click.

Image/photo

Conditional nodes

The If node allows you to setup a vector which will be returned after performing comparison between a and b. There are three vectors which can be returned: a == b (in that case the tolerance parameter is provided as a comparison threshold – by default it is equal to the minimal value, e.g. 0.00001), a > b and a < b.

Image/photo

The Switch node returns a vector if the boolean condition is true or false. Boolean was introduced above. If you convert a vector to a true boolean, all components of the vector should be above zero.

Image/photo

Grayscale and Sepia nodes

These are useful effects which have been added to ColorFunc (a container for such effects), so there is no need to create them manually.

Image/photo

Per-component multiplication modes for TransformMult

Derivative nodes

These nodes are Fragment specific, and cannot be used in the Vertex mode context. They are put under the Special category tab and divided into ScalarDerivativeFunc and VectorDerivativeFunc.

Image/photo

Testing these changes

All the above improvements have been made in Godot's master branch (the development branch for the future Godot 3.2). As of this writing, you have to build the compile the master branch from GitHub or use one of the nightly builds provided by community members to test it.

That's all for now, in the future new types of nodes can be easily added to this new system (especially after Vulkan has been implemented), thanks to the magnificent possibilities provided by Godot's design!

Engine

WebRTC support, progress report #2

Godot Engine Official

Tue, 21 May 2019 15:30:00 +0200

WebRTC support, progress report #2

In the last report we introduced WebRTC and the reasons why it's being added to the list of web standards (and thus to Godot). As mentioned there, the WebRTC protocol supports a wide variety of applications: from VoIP, to video streaming, to custom data transfers. The interface that allows you to send custom data is called a data channel and is now exposed in Godot via a new WebRTCDataChannel interface (more on that later).

Data Channels

WebRTC data channels can be configured to either be reliable or unreliable (and optionally non-ordered).

The reliable data channels can be seen as a TCP connection (like WebSocket) so all your data is guaranteed to arrive at the destination in order. If you send too much data here, latency will grow, and the connection might be closed.

The unreliable data channels can be seen more as a form of "UDP connection" (it's actually SCTP beneath), meaning that not all the packets you send might arrive at the other destination, and they will only be retransmitted according to certain limits. By default, these channels are configured to be ordered, so packets are either received in order, or the are not received at all. The "ordered" feature can be optionally disabled, but a retransmission policy must be indicated in any case, specifying either the maximum number of retransmissions or a maximum packet lifetime (i.e. max time in milliseconds the channel will attempt a retransmission if not acknowledged).

Godot implementation

During last month, I worked on introducing full data channels support to our WebRTC interface. This required, as mentioned, some API changes:

WebRTCPeer was renamed to WebRTCPeerConnection and no longer is a PacketPeer, it only handles the connection.
A new WebRTCDataChannel interface was added which inherits from PacketPeer to handle data transfer (so now each connection can have multiple channels).
A new WebRTCPeerConnection.create_data_channel method was added to create a new WebRTCDataChannel for the given connection. The connection must be in STATE_NEW as specified by the standard, the data channel must have a label, and can be optionally configured (see MDN docs for options).
You now need to call create_data_channel at least once before calling create_offer (or the connection will have nothing to setup at all).
offer_created was renamed to session_description_created and new_ice_candidate to ice_candidate_created to better fit Godot's signal naming.
A new data_channel_received signal was added to receive in-band (not pre-negotiated) channels (if you don't store it, the channel will be closed).

Other featuers that were added includes:

A new WebRTCPeerConnection.initialize method to create a new connection with the desired configuration provided as dictionary (see MDN docs). This allows STUN/TURN configuration.
The WebRTC GDNative plugin (for desktop plaforms) is now a singleton, and will be loaded automatically if dropped inside the project.

Reference work

The PR this report is about. Merged! Fresh master builds will have all these new features.

The updated GDNative plugin that works as a drop-in plugin (need a recent build from master branch).

The updated GDScript demo that uses the new functionalities.

We want goodies, where's the multiplayer?

I've spent some time to get the Multiplayer API running, but I feel that it still needs a finishing touch and it's not ready to be released yet. Additionally, this report was already overdue and I'm sorry about that.

For now I can tease you with the following image and this small video (forgive the screencast quality), while you wait a few weeks for another update.

Image/photo

Engine

Community Code of Conduct

Forums | Torque 3D

Tue, 21 May 2019 07:50:20 +0200

Community Code of Conduct

Hey everyone!

As we've marched onwards to the ever-looming release of 4.0, we've had a pretty constant trickle of new people, as well as old Torque hands returning to the fold, let alone the guys that have been trucking on this whole time.

With the continuing growth of the community, and some concerns of conflicting viewpoints, behaviors, and stances, I figured it was a good opportunity to set some ground expectations via a Code of Conduct.

We like to keep things pretty easy-breezy here as you all no doubt have come to appreciate, keeping the forums a open place for people to show off, post what they're working on, ideas and feedback as well as just discussions about whatever gamedev stuff. But the internet being what it is, sometimes opinions can clash, viewpoints can differ and tensions can raise to the point where things can get ugly.

Which means that while we'll strive to avoid needing to lean on it, the Code of Conduct will be kept here as a framework everyone can understand the expectations of interacting with the rest of the community and - in the hopefully unlikely event is not adhered to, moderation will be applied in accordance to these expectations.

We, as a community, are committed to providing a friendly, safe and welcoming environment for all, regardless of experience, background, history or characteristic.
Please avoid using any overly sexual, offensive, or insulting alias or nicknames for yourself or others that would otherwise detract from a friendly, safe and welcoming environment.
Please be kind and courteous. There's no need to be rude.
Respect that people have differences of opinion, and that every design, implementation, or choice carries considerations, trade-offs, and costs. There is rarely ever a perfect answer.
Please keep critiques constructive. If you are going to critique someone's work, ideas, or decisions, do it with topical and specific feedback so that they can improve. Unconstructive critiques don't help anyone better their work.
Insulting, demeaning or harassing anyone is not welcome behavior, whether in public or private conversations. If you feel you have been subjected to any of this behavior, please contact any moderator or admin immediately. Whether you're a regular or a newcomer, we care about making this community a safe place for you. If you have any lack of clarity about what might fall under those concepts, feel free to ask for clarification from the moderation team.
Likewise, any spamming, trolling, flaming, baiting or other attention-stealing/seeking behavior is not welcome.

In the hopefully unlikely event someone is found to have violated an aspect of the CoC, they will be provided a direct, specific warning, explaining what they have broken in terms of the CoC that the moderation has felt needed to be corrected.
If the user then goes on to violate the CoC again in a similar manner, not having shown any acknowledgement to their behavior or what they have done wrong, they weill be suspended temporarily(3 days).
If they, after returning from suspension go to violate the CoC yet again, then they will face a ban.

Anyone facing a suspension or ban is free to appeal this by messaging anyone on the admin or moderation team and their case will be reviewed. If it is found to not have been in violation, then the user can disregard the original moderation verdict. Otherwise, if found to have been a correct moderation action, then it is considered to be upheld and the user appealing will be informed of the decision so they may - if required - adjust their behavior accordingly.

If there is any element of this Code of Conduct that is unclear, feel free to ask for clarification. As mentioned above, if you feel any of these have been violated by a member of the community, contact the mods or admins so that we can take care of the situtation.

As said, I hope that everyone takes the intent to heart to create a welcoming environment for anyone that wants to make games(or heck, just people that find making games super cool - because it is!) so that we never need to lay down corrective or moderative behavior.

With that, I look forward to this community growing and becoming even more awesome!

-JeffR
Statistics: Posted by JeffR — Tue May 21, 2019 7:50 am — Replies 0 — Views 19

Announcements Engine

Community Code of Conduct

Forums | Torque 3D

Tue, 21 May 2019 07:50:20 +0200

We, as a community, are committed to providing a friendly, safe and welcoming environment for all, regardless of experience, background, history or characteristic.
Please avoid using any overly sexual, offensive, or insulting alias or nicknames for yourself or others that would otherwise detract from a friendly, safe and welcoming environment.
Please be kind and courteous. There's no need to be rude.
Respect that people have differences of opinion, and that every design, implementation, or choice carries considerations, trade-offs, and costs. There is rarely ever a perfect answer.
Please keep critiques constructive. If you are going to critique someone's work, ideas, or decisions, do it with topical and specific feedback so that they can improve. Unconstructive critiques don't help anyone better their work.
Insulting, demeaning or harassing anyone is not welcome behavior, whether in public or private conversations. If you feel you have been subjected to any of this behavior, please contact any moderator or admin immediately. Whether you're a regular or a newcomer, we care about making this community a safe place for you. If you have any lack of clarity about what might fall under those concepts, feel free to ask for clarification from the moderation team.
Likewise, any spamming, trolling, flaming, baiting or other attention-stealing/seeking behavior is not welcome.

Announcements Engine

Server Maintenance - affects Logins 3 hours

Announcements - Cocos2d-x Forums

Thu, 16 May 2019 18:30:13 +0200

Server Maintenance - affects Logins 3 hours

@slackmoehrle wrote:

Hello everyone:

Due to server migration & upgrade, the server where the auth.cocos.com account system is located is scheduled to undergo one-time downtime maintenance at 22:00 on May 16, 2019. The short-term inconvenience is to provide you with faster and more stable access services.

The system that relies on the auth.cocos.com unified account login will be temporarily unable to log in, including: Creator login, developer background, Chinese forum, English forum, CocoaChina.

Maintenance start time: May 16, 2019 22:00
Estimated recovery time: May 17, 2019, 01:00

The entire maintenance process takes about 1-3 hours.

Friendly reminder:
1, Creator can skip login, does not affect the use;
2. If there is any access issues before and after the migration, please leave a message in this post, we will follow up in time.

Posts: 2

Participants: 1

Read full topic

Announcements Engine

Week recap — 15 May 2019

Libre Graphics World. Blog

Wed, 15 May 2019 17:54:49 +0200

Week recap — 15 May 2019

Recent highlights: new version of AzPainter and RawTherapee, GIMP and Krita preparing for respective releases, Blender keeps getting tons of improvements, GSoC 2019 students and project announced.

Since I had to skip quite a few weeks, below goes the list of things that I personally consider most important over the time span since the last recap (you don’t have to agree with my priorities!).

Google Summer of Code 2019

Projects like Blender, appleseed, Krita, Synfig, Apertus, Godot, and others now have GSoC students to work this summer. This probably deserves a separate post, but you can have a look at the complete list of organizations, assigned students, and projects.

Graphics

    GIMP developers are likely to release version 2.10.12 in May, before the beginning of Libre Graphics Meeting 2019 in Saarbrücken. This is partly because of various fixes (e.g. the new smart bucket fill option is giving people crashes), and partly because there are new features worth shipping to end users. Here are some of them:

    Tobias Ellinghaus added layers exporting to the TIFF plug-in. This is an option in the exporting settings dialog.

    Ell added incremental mode to the Dodge/Burn tool. The new option works pretty much like the one in the Paintbrush tool and applies the effect incrementally as the pointer moves.

    He also introduced several changes to the Curves dialog, which are discussed in a video I shot last week (subtitles available):



    Finally, the new version will be shipping with a fix for the Free Select tool. As you may have noticed, since version 2.10.0, GIMP has been allowing the editing of polygonal selection but demanding to either press the Enter key or double-click inside the selection to confirm it. If you didn’t do it, GIMP would copy and paste the whole layer rather than selection.

    The design was consistent with other tools, but for those who tried to do just the free selection, this extra step was way too annoying. So Ell made the tool create a preliminary selection. Now you can quickly draw a free selection and then copy-paste it without confirmation.

    Krita developers released the first alpha of version 4.2.0 and expect to have the final release by the end of May 2019, around the time Libre Graphics Meeting kicks off in Saarbrücken, Germany.

    The team is valiantly fighting off bugs to make the final release as bug-free as humanly possible. Until the release, don’t expect any fancy new features (source code has been in hard freeze mode for the past couple of weeks, by the look of it, which means only bugfixes are allowed).

    For more info on the 4.2.0 alpha (and downloads) see the announcement.

    Azel released AzPainter 2.1.4 with several improvements: new "Luminance (addition)" and "Luminance (dodge)" blending modes, sharper display of an image when zoomed out, the maximum display magnification bumped from 1000% to 2000%, and drag’n’drop support in the Brushes panel (to be fair, I couldn’t get this last one to work). Source code is available, there might be an appimage soon.

    AzPainter 2.1.4, featuring a PSD project by Djamila Knopf

    Brien Dieterle has been toying with the Oren-Nayar reflectance model in MyPaint, which essentially predicts how various natural surfaces reflect light. This work is being done in the bumpmap branch.



    The Inkscape team has been busy lately, just a few notable recent changes to mention.

    Tavmjong Bah added basic ‘SVG in OpenType’ support. This is kinda exciting given what you can do with that. Jabier Arraiza introduced some improvements to the new LPE Add dialog. Patrick Storz improved keyboard shortcuts configurator which, in case of a conflict, now suggests an option to reassign already used shortcuts. Nathan Lee made all of the toolbars (and at least some dockable dialogs) respect the unit set in the Document Properties dialog:



    Nathan also slightly restyled the Guide properties dialog:

Photography

The RawTherapee team released version 5.6 featuring an optional Pseudo-HiDPI mode, ability to move tools to a new Favorites tab for fast access, lots of speed optimizations, and more changes. For details, please see the release announcement.

3D

There has been a ton of changes in Blender for the past month. Here are some of them in no particular order:

Color-managed image buffers in Cycles via OpenColorIO
More unification of material and lights settings between Cycles and Eevee
Eevee now supports viewport preview of background alpha
Collections can be easily enabled and disabled in the Outliner using checkboxes now
In animation editors, the scrubbing area is now at the top and is part of the ruler
The Scene strip in VSE got various performance improvements

    Some of these changes have been covered in Pablo’s recent stream:



    And let’s not forget about textured brushes in Grease Pencil:



    Also, check out the report from Blender 2.80 Homestretch:



    The final release of 2.80 is currently scheduled for July 2019, not too far off!

CAD

Yorik van Havre posted his monthly report on FreeCAD that, as usual, focuses on his contribution to the architecture design feature set.

Notable new features:

IFC exporter now supports transparency, multicolor objects, and compounds
Shape2DViews can now fuse walls and structures, to be added to TechDraw Arch views as well later on
Cloning entire levels of a building is now possible
All Draft objects now have an Area property, for easy calculation of areas

    KiCon 2019, the annual KiCad EDA conference, took place in Chicago in late April. Videos have been published by Contextual Electronics on YouTube.



    Oh, and Dave Jones from EEVblog has considerably changed his opinion of KiCad since his first encounter with the project.

Music-making

VCV Rack got a new record module:

Also, Alright Devices released T-Wrex and Chronoblob 2 modules for VCV Rack.

Andrew Belt is also considering relicensing VCV Rack to GPLv3 with freeware/commercial exceptions to, as he put, “prevent commercial modules from being sold without supporting the VCV project, and prevent unlicensed commercial clones of VCV Rack itself that do not support the VCV project”. See this post for more details.

Video

    Matt KC released Olive 0.1.0, then merged all his new pipeline code. For now, it contains OpenColorIO-based color management and early implementation of built-in node compositing. Future plans include a cached playback engine and masking. See his roadmap post on Patreon for more details.



    Shotcut got a lot of fixes and several new filters: Audio Dance Visualization, Audio Light Visualization, RGB Shift (frei0r.rgbsplit0r), Glitch (frei0r.glitch0r), Distort (frei0r.distort0r). All of that is already available in version 19.04.30.

    Cinelerra-GG recently got hardware decoding and encoding via VDPAU/VAAPI. The decoding part is available in the latest release, the encoding part will be present in the next build (we don’t of any scheduled release dates to share). The video editor also got a plug-in called Tracer for creating a quick outline around an object, a kind of an mask. See here for more changes.

    As for Flowblade, Janne Liljeblad spent most of the time working on keyframing and Rotomask features and UI, as well as bug fixing.

    Pitivi has been accepted to Google’s Season of Docs program. If you are good with words and interested in writing a developer guide for the GStreamer Editing Services library, consider applying.

    Caching system in Blender’s VSE was rewritten and allows more user control. All settings are now in the Proxy & Cache panel in the sidebar.

Tutorials

    A new tutorial by Nick Saporito explains how to draw retro style numbers.



    Another one is about creating glowing neon text with GIMP.



    As usual, grafikwork puts out a new solid Krita timelapse.



    In a new Blender tutorial, Wayward Art Company talks about creating and resuing custom node groups in procedural tetxures.



    GDquest published an introduction to VisualScript in Godot 3.1.

Art and showcases

Sven Ebert pisted a new artwork made with Inkscape, Bravest Warrior.

New painting by Jarry H., made with Krita.

New Cycles render by debopam_das looks yummy.

Assets

IBM released the Plex Sans Variable v1.0 typeface featuring Weight (100-700) and width (85-100) axes, presets for 32 styles, variable TrueType hinting. All is available under the terms of the OFL 1.1 license.

News Editorial art

Week recap — 15 May 2019

Libre Graphics World. Blog

Wed, 15 May 2019 17:53:59 +0200

Week recap — 15 May 2019

Recent highlights: new version of AzPainter and RawTherapee, GIMP and Krita preparing for respective releases, Blender keeps getting tons of improvements, GSoC 2019 students and projects announced.

Since I had to skip quite a few weeks, below goes the list of things that I personally consider most important over the time span since the last recap (you don’t have to agree with my priorities!).

Google Summer of Code 2019

Graphics

Photography

3D

There has been a ton of changes in Blender for the past month. Here are some of them in no particular order:

Color-managed image buffers in Cycles via OpenColorIO
More unification of material and lights settings between Cycles and Eevee
Eevee now supports viewport preview of background alpha
Collections can be easily enabled and disabled in the Outliner using checkboxes now
In animation editors, the scrubbing area is now at the top and is part of the ruler
The Scene strip in VSE got various performance improvements

CAD

Yorik van Havre posted his monthly report on FreeCAD that, as usual, focuses on his contribution to the architecture design feature set.

Notable new features:

IFC exporter now supports transparency, multicolor objects, and compounds
Shape2DViews can now fuse walls and structures, to be added to TechDraw Arch views as well later on
Cloning entire levels of a building is now possible
All Draft objects now have an Area property, for easy calculation of areas

Music-making

VCV Rack got a new record module:

Also, Alright Devices released T-Wrex and Chronoblob 2 modules for VCV Rack.

Video

    Matt KC released Olive 0.1.0, then merged all his new pipeline code. For now, it contains OpenColorIO-based color management and early implementation of built-in node compositing. Future plans include a cached playback engine and masking. See his roadmap post on Patreon for more details.



    Shotcut got a lot of fixes and several new filters: Audio Dance Visualization, Audio Light Visualization, RGB Shift (frei0r.rgbsplit0r), Glitch (frei0r.glitch0r), Distort (frei0r.distort0r). All of that is already available in version 19.04.30.

    The Kdenlive team completed much anticipated refactoring and released version 19.04. Highlights: autosplitting of audio tracks from video clips upon dropping onto the timeline, resizeble track height, improved keyframe handling, voiceover recording (with video playback). See release notes for more info. A bugfix update is already available.

    Cinelerra-GG recently got hardware decoding and encoding via VDPAU/VAAPI. The decoding part is available in the latest release, the encoding part will be present in the next build (we don’t of any scheduled release dates to share). The video editor also got a plug-in called Tracer for creating a quick outline around an object, a kind of an mask. See here for more changes.

    As for Flowblade, Janne Liljeblad spent most of the time working on keyframing and Rotomask features and UI, as well as bug fixing.

    Pitivi has been accepted to Google’s Season of Docs program. If you are good with words and interested in writing a developer guide for the GStreamer Editing Services library, consider applying.

    Caching system in Blender’s VSE was rewritten and allows more user control. All settings are now in the Proxy & Cache panel in the sidebar.

Tutorials

Art and showcases

Sven Ebert pisted a new artwork made with Inkscape, Bravest Warrior.

New painting by Jarry H., made with Krita.

New Cycles render by debopam_das looks yummy.

Assets

News Editorial art

Ogre 1.12 released

OGRE – Open Source 3D Graphics Engine

Wed, 01 May 2019 17:12:32 +0200 last edited: Tue, 21 May 2019 21:29:53 +0200

View article

Ogre 1.12 released

We just tagged the Ogre 1.12 release, making it the new current and recommended version. We would advise you to update wherever possible, to benefit from all the fixes and improvements that made their way into the new release.
This release represents 1 year of work from various contributors when compared to the previous 1.11 release. Compared to the last Ogre 1.11 release (1.11.5), however we are only talking about 4 months. Here you will mainly find bugfixes and the architectural changes that justify the version number bump.

For source code and precompiled SDKs, see the download page. Currently the Android is still missing. We will update the download page as it becomes available.

Changes

The 1.12 release focuses on preparing the codebase for future development instead of on new features. Some obsolete parts were removed and certain APIs adapted to be more generic. This is also reflected by the diff between v1.11.5..v1.12.0 as: 10994 insertions(+), 27142 deletions(-)

For an detailed overview of the changes see the New And Noteworthy Document. Among the highlights are:

#include directive supported for GLSL shaders
PF_DEPTH support for shadows with the RTSS and the Terrain component
RTSS 3.0: vastly improved internal API and refactored shader library
Per pixel-shading on D3D11/ GL3+/ GLES2 by default (via RTSS)
The GL3+ RenderSystem is now used for rendering the reference Test images
More precise timings for built-in profiler and support for external profiling via Remotery
unified API for fixed-function pipeline and shaders
NEON intrinsics for OptimizedMath on ARM (Android)
Stable Material library (Media/) that you can reference in your projects
the MSVC SDK now also includes the Python and Java components
support for loading 1.7 style terrains (aka “terrain.cfg”)

For an overview of the bugfixes, see the v1.11.6 changelog.

We continued removing the deprecated API with this release and together with the architectural improvements it means that your code might not compile any more. However we tried to keep API changes as non-invasive as possible.

We are keeping the time based release model for the 1.x branch. This means that you can expect OGRE 1.13 in April 2020.

Contributors

We would like to thank everyone who helped us make this release possible. The following list shows a list of contributors for 1.12 based on the git logs:

Pavel Rojtberg, Eugene Golushkov, Alex Choi, Dmytro Yunchyk, George Evmenov, SNiLD, Apivan, Rémi Verschelde, cread mefford, 1k0, Alex, Alexey Pavlov, Alon Faraj, Arthur Brainville, Bastien Bourineau, Edgar, Felipe Martínez, Felix Tschirschwitz, Gabriel Cuvillier, Gaudet Kevin, Grzegorz Szadkowski, Kevin Gaudet, LuChu, Mitja, Petr Ohlidal, Robin Norrman, Sonu Lohani, Stefan Roellin, Stoyanov Vlad, Tobias Schmidt, Xu Zhongxing, ulteq, wxyu247

Additionally you might have noticed that OGRE got a modern Logo. It has been contributed by Pierre Fontaine

Ogre 1.11.6

If you are currently deep in the development cycle using 1.11.5 and do not want any disruptions, I have good news for you: relevant bug-fix only commits were cherry-picked from master (1.12) to 1.11 and accumulated in the 1.11.6 release, which you can find here.

News ogre1

Cocos2d-x 3.17.1 -> Make sure to update deps!

Announcements - Cocos2d-x Forums

Tue, 30 Apr 2019 15:01:05 +0200

Cocos2d-x 3.17.1 -> Make sure to update deps!

@slackmoehrle wrote:

If you are using Cocos2d-x 3.17.1, update the cocos2d-x 3rd party libraries. Use v3-deps-156.

From your cocos2d-x root:
./download-deps.py

Posts: 2

Participants: 1

Read full topic

Announcements Engine

New sound features: alternative backends, new demo, aliases

Castle Game Engine

Mon, 29 Apr 2019 22:06:28 +0200

Our sound engine was refactored to support various backends. There are 3 backends available now: OpenAL (full-featured, with spatial (3D) sound support), SOX (only useful for testing — executes command-line sox to play files), and Nintendo Switch sound backend (not open-source, only available for developers who signed an agreement with Nintendo). A new sound demo …

Continue reading ➤

View article

Uncategorized Engine

Castle Game Engine 6.5 “Beta” available for download, many editor and release improvements

Castle Game Engine

Sun, 28 Apr 2019 18:22:21 +0200

View article

Castle Game Engine 6.5 “Beta” available for download, many editor and release improvements

First of all, notice that big shiny button on the main page to download CGE version 6.5. Try it out!

While we work on making next stable 6.6 (or maybe 7.0?) release perfect, you should enjoy using the latest 6.5 snapshot. It’s in practice very stable (at Cat-astrophe Games company we even use it in production). It also contains a ton of new features compared to the last stable release (6.4, more than a year ago), and you should enjoy them:)

Probably the biggest new feature is the Castle Game Engine Editor. It is documented in the manual, and our “Getting Started” page was also updated to clearly advise using it. The 6.5 engine snapshots contain the editor (as well as other tools) in a ready, compiled version. Just execute bin/castle-editor.

Editor and packaging improvements from April:

Selecting file in the file browser (bottom of the editor) opens a small asset preview (useful for scenes, images, and quickly playing sound files).
Double-clicking in the file browser opens a suitable viewer, like view3dscene or castle-view-image.
The editor, build tool and some other tools are now also provided in compiled form, and more integrated. E.g. you no longer need to define CASTLE_ENGINE_PATH environment variable if you just run the editor (or build tool) from the bin subdirectory of the engine. They will find the CGE code (and other tools) in any case.
view3dscene and castle-view-image (formerly called glViewImage) are also distributed along with the engine. No need to download them separately.
When using snapshots, the CGE version number contains the GIT commit hash.
Compiling with the build tool now automatically places relevant DLLs alongside the EXE file on Windows.
CGE applications automatically use Libpng if available, and only fallback on FPImage. You do longer have to compile with any symbol to use Libpng.
Editor “File Browser” automatically hides some files/dirs, like castle-engine-output.

Uncategorized Engine

Maintenance release: Godot 3.1.1

Godot Engine Official

Sat, 27 Apr 2019 02:00:00 +0200

Maintenance release: Godot 3.1.1

It's been about a month and a half since the release of 3.1-stable, and our contributors have worked hard to get you, most valued users, bugfixes, new features, and documentation updates. So on this nice and sunny Dutch King's Day we're happy to announce the availability of the first maintenance release in the 3.1 series Godot 3.1.1-Stable. Hail to the king, baby!

With the -stable releases we offer you the backwards compatible changes and bugfixes. However in this release we had to break some compatibility with networking due to a security issue. See the Known incompatibilities section of this blog post. If we inadvertendly changed behavior for your project started with Godot 3.1-stable please report a bug.

I'd like to use this space to say "Thank you" to our amazing contributors, none of whom would ever give you up, let you down, and/or desert you. If you too would like to to be counted amongst their ranks join us and fix bugs, write documentation, or file bugreports.

If you enjoy our work please consider becoming our Patron and help Godot main developers work full time on the project!

Changelog

A security issue was reported and fixed. This change does add some API to Godot in case you need to be able to deserialize Object data. Please see This PR for details. If you do not use networking in your project you should not be affected. However GDNative ABI was changed so any native plugins need to be rebuilt for 3.1.1.
GLES 3 support for depth textures was fixed. This was a regression in 3.1 from 3.0.x.
GLES 2 crash on older iOS devices was resolved.
OS.get_unique_id() was fixed on Android.
A HeightMapShape was added to the Bullet physics engine implementation.
FPS snapping in the Animation player was added to the engine, along with other quality of life improvements.
New audio features for 3.2 were backported.
New menu options for the Sprite editor were added: "Convert to Mesh2D", "Convert to Polygon2D", "Create CollisionPolygon2D Sibling" and "Create LightOccluder2D Sibling".
AnimatedSprite can now play backwards.
Emission Mask was added to CPUParticles2D.
GLTF2 importer fixes.
C#: Support for MSBuild from VS2019 was added.
C#: Improvements were made to the generated C# documentation comments. The BBCode is now translated to XML doc comments.
C#: _GetPropertyList never being called was fixed.
C#: Unhandled exceptions no longer hard-crash the application.
C#: Exports information now only gets updated in the editor, this fixes temporary instances being created in-game.
C#: Fixed parsing of generic type declarations in C# source files.

And many more small quality of life improvements and bugfixes. See the full changelog below for details.

See the changes between 3.1-stable and 3.1.1-stable on Github, or the full changelog in text format. This release is built from commit 66baa3b.

Downloads

As always, you will find the binaries for your platform on our mirrors:

Classical version: [HTTPS mirror]
Mono version: [HTTPS mirror]

Known incompatibilities

Below we describe the known incompatibilities with previous releases in this cycle.

Known incompatibilities with Godot 3.1

Due to a security fix the GDNative ABI has changed. If you use GDNative modules in your project they will need to be rebuilt from source.
Godot no longer automatically decodes Objects when using high level multiplayer. If you do want your client or server to do this it is now necessary to explicitly allow it. See this PR for details.
Previously on Android OS.get_unique_id() would return the static value for Secure.ANDROID_ID. This was a bug and now an actually unique ID is returned. If you were using the unique ID for encryption purposes you must now also check the original static value or your users may lose access to any encrypted (save) data.

Known bugs in Godot 3.1.1

None

The illustration picture is a screenshot of GRIEF. A game in devlopment by Manuel 'TheDuriel' Fischer and IAmActuallyCthulhu.

Engine

Godot 3.2 will get a new Android plugin system

Godot Engine Official

Wed, 24 Apr 2019 02:00:00 +0200

Godot 3.2 will get a new Android plugin system

Godot has the simplest and most efficient Android deploy system you can find in any game engine. With a single click, your project is runing on the phone. With a single option (network fs deploy) your gigabyte-sized project is running on your device in mere seconds. You can use the editor to debug your running game while it runs on your device and you can make changes in the scenes or scripts and they will reflect in real-time in your phone or tablet. The big drawback, however, was that adding plugins was a pain in the butt.

Beginnig Godot 3.2, the Android plugins system has been overhauled. It is no longer required to recompile the whole engine just add a new Plugin.

New custom build system

Godot export templates for Android projects are just two .apk files, one for debug and one for release. On Export, Godot fills them with the project files and tweaks some internal variables of the format. This works well in general, but many times the Android project needs to be actually modified and the current approach is not flexible enough.

Instead of going the way of other engines, which just export an Android project, it was decided to keep the current approach (which is so far, unmatched in ease of use), but just make it easier to generate the base templates from source.

To do this, there is a very simple option in the Project menu to install the build template:

Image/photo

When used, the Godot android project that is used to build Godot for Android is installed in "res://android/build", including full Java source code (a proper .gdignore file is added in res://android to avoid Godot filesystem dock from entering this folder).

When the build template is installed, the following option can be turned on in the Android export presets:

Image/photo

And from now on, every time the project is exported, gradle will be executed to produce fresh export templates from the Android source. The output (as well as potential errors) are displayed in the editor UI:

Image/photo

The generated templates are used automatically without any user intervention.

Setting this system up still requires installing the Java and Android SDK in order for Godot to build, but detailed instructions can be found in this new tutorial.

New plugin system

Having the Godot Android project source built automatically allows doing modifications to it, in a way more similar to how it works in other engines. This way you can keep modifying your Android project and bypass the rigidity of the export system as desired.

Still, however, the problem persists where, if a new Godot version is released, the Android build template will need to be erased and updated, discarding any changes you may have done to it.

To avoid this situation, a new plugin system was also added. This allows adding plugins inside the "res://android" directory (with any name other than "build", of course). When Godot exports using the custom build option, the plugins are be compiled-in automatically.

Plugins allow extending the existing base build template by adding extra files and resources to it in outside directories. They also support blitting chunks of text into AndroidManifest.xml and build.gradle, so these files can be modified without risking to lose these changes as soon as the build template is updated.

The code part (Java) for creating plugins remains unmodified so existing plugins should be very easy to port to the new system. For more detail on how to create them, this new tutorial was added too.

As plugins are just extra files that are added to the project, it's now also very easy to distribute them via our asset library. This was not possible before.

Future

With upcoming Godot 3.2, it will be very easy for both our community or third party vendors to create and distribute Android add-ons (such as Ad-Mob, Firebase, Facebook, etc) for others to use. Let's hope a wonderful ecosystem for this flourishes!

And as always, remember that this is done with love from us. This was a very requested feature that we're glad to finally be able to provide. If you are not, please consider becoming our Patron and help Godot main developers work full time on the project, so the world can have a a free and open source tool that let's you create games without any restriction. Even a small donation is a huge help

Engine

Release candidate: Godot 3.1.1 RC 1

Godot Engine Official

Tue, 23 Apr 2019 02:00:00 +0200

Release candidate: Godot 3.1.1 RC 1

Welcome to the first release candidate of what will shortly become Godot 3.1.1-stable. After the release of 3.1-stable about a month and a half ago we didn't sit on our laurels. No sirre, not at all! Many bugs were fixed, improvements made, and documentation was written.

With the -stable releases we offer you the backwards compatible changes and bugfixes. However in this release we had to break some compatibility with networking due to a security issue. See below for details.

Please test this release with your existing projects and as usual: Any breakage of existing projects after upgrading is a bug, unless noted in the Known incompatibilities section of this blog post. If we somehow missed something please report a bug.

I invite you, dear reader, to take a moment to close your eyes and silently thank all of the awesome people who helped make this release a reality. If you too would like to be thanked by a multitude of Internet people join us in fixing bugs, writing documentation, and/or reporting bugs!

Changelog

A security issue was reported and fixed. This change does add some API to Godot in case you need to be able to deserialize Object data. Please see This PR for details. If you do not use networking in your project you should not be affected. However GDNative ABI was changed so any native plugins need to be rebuilt for 3.1.1.
GLES 3 support for depth textures was fixed. This was a regression in 3.1 from 3.0.x.
GLES 2 crash on older iOS devices was resolved.
OS.get_unique_id() was fixed on Android.
A HeightMapShape was added to the Bullet physics engine implementation.
FPS snapping in the Animation player was added to the engine, along with other quality of life improvements.
New audio features for 3.2 were backported.
New menu options for the Sprite editor: "Convert to Mesh2D", "Convert to Polygon2D", "Create CollisionPolygon2D Sibling" and "Create LightOccluder2D Sibling".
AnimatedSprite can now play backwards.
Emission Mask added to CPUParticles2D.
GLTF2 importer fixes.

And many more small quality of life improvements and bugfixes. See the full changelog below for details. The 3.1-stable release blog post will also have some more details about changes made.

See the changes between 3.1-stable and 3.1.1-rc1. This RC is built from commit 39f1a11.

Downloads

As always, you will find the binaries for your platform on our mirrors:

Classical version: [HTTPS mirror]
Mono version: [HTTPS mirror]

Known incompatibilities

Below we describe the known incompatibilities with previous releases in this cycle.

Known incompatibilities with Godot 3.1

Due to a security fix the GDNative ABI has changed. If you use GDNative modules in your project they will need to be rebuilt from source.
Godot no longer automatically decodes Objects when using high level multiplayer. If you do want your client or server to do this it is now necessary to explicitly allow it. See this PR for details.
Previously on Android OS.get_unique_id() would return the static value for Secure.ANDROID_ID. This was a bug and now an actually unique ID is returned. If you were using the unique ID for encryption purposes you must now also check the original static value or your users may lose access to any encrypted (save) data.

Known bugs in Godot 3.1.1 RC 1

Documentation hyperlinks not working properly [GH-27983]
Button layout changed compared to 3.1.0-stable [GH-28335]

Engine

WebRTC support, progress report #1

Godot Engine Official

Fri, 19 Apr 2019 16:53:33 +0200

WebRTC support, progress report #1

Presentations

Hello Godotters, my name is Fabio Alessandrelli, you may know me by my handle fales (faless on GitHub). Here are a few words about my Godot journey.

I first discovered Godot in 2015 while looking for a good game engine (that would also work on GNU/Linux) to develop a small game for a university project with a friend.

It was the early era of Godot 1.0, which was open sourced just few months before.

It was love at first sight, and since then, I slowly started contributing to its development, proposing small PRs whenever I found something that was missing or not working and I had the time to fix, learning a lot in the process.

Finally, I started specializing in the networking subsystem (again, because I needed it for my projects). I slowly became the “network guy”, so if your networking PR or issue is stalling, yes, it's my fault, I'll try to review them soon™.

On HTML5, WebSockets, WebRTC

One of the thing that struck me after some time playing with Godot, was how easily it enables developers to export for different platforms, and among those, HTML5/WebAssembly (thanks to the great effort of many developers, especially eska, the current HTML5 platform maintainer). Enabling developers to share their beautiful games running in browsers is a great feature for an engine!

Networking trough browsers used to be very limited and originally only HTTP requests were possible.

Websocket

Then, in December 2011, the WebSocket protocol was standardized, allowing browsers to create bidirectional channels to a WebSocket server. The protocol is pretty simple, it begins with an HTTP request from the browser with some protocol specific headers. From there, if the server accepts the connection (replying with similar headers), the connection is kept open, and data begins to flow bidirectionally using the quite simple protocol message format.

That though, wasn't enough. WebSockets still uses a TCP connection, which is good for reliability but not for latency, rendering it useless for real-time applications (e.g. VoIP, fast-paced real-time games).

WebRTC

For this reason, since 2010, Google started working on a new technology called WebRTC, which later on, in 2017, became a W3C candidate recommendation (i.e. it's considered quite stable but it's still being worked on). WebRTC is a much more complex set of specifications and API, and uses a lot of other technology underneath (ICE, DTLS, SDP), to provide fast, real-time, and secure communication between two peers.

The idea, is to find the fastest route between the two peers and establish whenever possible a direct communication (as in try to avoid a relaying server).

This comes at a price though, and the price is that some media information must be exchanged between the two peers before the communication can start (in the form of Session Description Protocol – SDP strings). This usually takes the form of a so-called WebRTC Signaling Server.

Image/photo

A signaling server (for example a WebSocket server) to which peers connects and send their media information. The server then relays those information to other peers, allowing them to establish the desired direct communication. Once this step is done, peers can disconnect from the signaling server and keep the direct P2P connection open.

Current work on supporting WebRTC in Godot

During the last month, I've spent most of my time (paid by the Software Freedom Conservancy thanks to a grant by Mozilla Foundation) working on a WebRTC implementation for Godot Engine. Part of the work, was already done by Brandon Makin during GSoC 2018.

I focused on getting the Javascript version ready, and porting the work of Brandon Makin to GDNative (to support WebRTC in native exports, without having to bundle the huge WebRTC Native Code reference library into Godot sources). So, while the WebAssembly export will have WebRTC support out of the box, native exports (e.g. GNU/Linux, Windows, macOS, Android, etc.) will need a GDNative library to work.

This is done by having a WebRTCGDNative class, which we then implement via GDNative, and will be released in a separate repository.

But how does this work?

Here are the Godot-exposed functions for the current state in my branch (yes, yes, I will document them, when the work is ready :) ):

Image/photo

NOTE: The API will slightly change to allow creating multiple data channels.

And here is a simple schema on how to use it:

Image/photo

Wait, that doesn't look simple! Well, that's true, WebRTC has a fairly complex setup phase, but it can be boiled down to 4 steps:

The peer that wants to establish a new connection calls create_offer().
- A new offer_created signal is emitted by that same WebRTC peer.
- The signal values need to be passed to set_local_description.
- The signal values need to also be passed to the remote peer, using any means desired (usually, the Signaling Server).
The remote peer will need to pass the received parameters (type and sdp) to its WebRTCPeer set_remote_description.
- This will generate an offer_created signal on that peer.
- The signal values need to be passed to set_local_description.
- The signal values need to also be passed to the peer that generated the offer in the first place.
The peer that originally generated the offer will pass the received parameters (i.e. the answer from the remote peer) to its own WebRTCPeer set_remote_description.
After calling set_remote_description on each peer, multiple new_ice_candidate events will be emitted.
- The values from those events needs to be sent to the other peer (again, via the signaling server).
- Each peer will then pass the candidates received from the signaling server to the add_ice_candidate function (i.e. each peer must pass to the function the candidate generated by the other peer).

After that, the connection will be established!

Reference work

You will need a recent build of Godot's master branch:https://github.com/godotengine/godot/tree/master

A compiled version of the WebRTC GDNative library is available at:

https://github.com/godotengine/webrtc-native/releases/tag/0.2

A small demo to test it can be found at:

https://github.com/Faless/webrtc-native-demo/releases/tag/0.2

The work on the reference WebRTC signaling server based on WebSocket is available at:

https://github.com/Faless/gd-webrtc-signalling

Additional resources

Websocket

RFC: https://tools.ietf.org/html/rfc6455

JS API: https://developer.mozilla.org/en-US/docs/Web/API/WebSockets_API

WebRTC

W3C Recommendation: https://www.w3.org/TR/webrtc/

JS API: https://developer.mozilla.org/en-US/docs/Web/API/WebRTC_API

Engine

Atlas support returns to Godot 3.2

Godot Engine Official

Fri, 19 Apr 2019 02:00:00 +0200

Atlas support returns to Godot 3.2

With the import system rewrite in Godot 3.0, the ability to import atlases was lost. Using atlases is not as common nowadays, given the processing power of desktop and devices has increased a lot, but there are many use cases where this may be worth it. Godot 3.2 will bring back support for it.

What is an Atlas?

Importing images into an atlas is a process that will take all of the images, and pack them into a single larger image (called an "Atlas"). Then, when the original image needs to be drawn, it actually draws the piece of the larger atlas.

Image/photo

Character is (c) Square Enix.

This is also only useful for 2D (Godot does not support 3D atlases).

So, why would one use an atlas instead of individual images? In most cases, it doesn't make sense, but for some situations it may provide some improvement in memory usage or performance. Here are such cases:

Batching

In cases where a lot of objects need to be drawn, having them all share the same texture (or material) may reduce draw calls or state changes. When working on tile-sets, it's normal to have everything already drawn to a single texture but if the level uses a lot of separate images, then using an atlas may make sense to improve performance.

Optimizing Memory

When doing character animations, specially characters with hundreds of thousands of animation frames (like Cuphead), using an atlas will not give any increase in performance (as only one frame is drawn at the same time).

However, to ensure animation remains fluid and easy to integrate, animators will use a relatively large image size that remains constant, then animate a smaller character inside. This produces a lot of wasted memory, as these empty places in the animation frames take up a lot of video memory and make loading slow.

Image/photo

Using atlases ensures that, before placing all the animation frames in a single image, the frames are cropped (and the offset to the crop remembered). The packer will then, ensure everything is fit in the atlas image as compactly as possible. This makes it easy to optimize for memory, as only the places in the images that contain information are saved.

How to use atlases in Godot

Using atlases in Godot is extremely easy. Just select all the files that you want to pack together in the Filesystem Dock, then change the import type to "Texture Atlas".

When the new file type is selected, change the "atlas file" setting to the image you will want to create, then push the "Re-Import" button. All your assets will be re-imported and added to an atlas. (The editor will restart afterwards, as the images may be in use, to ensure everything is re-opened in a clean state).

Here is a visual explanation:

Image/photo

Packing is also deterministic, which means that the same image should always be generated (this ensures it works for generating normal map atlases separatedly, as an example).

Import modes

As you may have noticed, atlas files have an Import Mode, settings. There are two possible ones:

Region

This packs the used part of the image in a square region in the atlas, then this is referenced in an AtlasTexture.Region takes up more space, but allows drawing only parts of the image, clipping it, etc. It also means that it can be batches. This mode is ideal for optimizing performance, as mentioned above.

Mesh2D

This cuts a polygon around the used part and packs it, resulting in considerably more efficient packing. The downside is that drawing it is less flexible (some operations such as showing a region of it are not possible). It is not possible to batch meshes either. This mode is ideal for optimizing memory in the mode mentioned before.

Future

I hope this is the last feature I will personally add to Godot 3.2, so I can soon move to work on Vulkan. As always, if you are not yet, please consider becoming our patron, help us hire an extra developer and ensure that Godot development remains free.

Engine

The new Cocos Website is here!

Announcements - Cocos2d-x Forums

Thu, 18 Apr 2019 12:40:17 +0200

The new Cocos Website is here!

@slackmoehrle wrote:

It has taken the team a lot of hard work and dedication, but the new Cocos Website is finally here. Please join me in thanking the entire team for bringing the Cocos brand into it’s next stage of life.

Just a few housekeeping items:
Cocos2d-x.org will start redirecting to the new Cocos Website
these forums will remain here and__NOT__ be changed.
We will be experimenting with some fonts to make our websites easier to read. Let us know what you think as we experiment.

Posts: 2

Participants: 1

Read full topic

Announcements Engine

What should Cocos2d-x v4 be?

Announcements - Cocos2d-x Forums

Wed, 17 Apr 2019 18:02:31 +0200

What should Cocos2d-x v4 be?

@slackmoehrle wrote:

@walzer if working on deciding what v4.0 will be. Let’s help him!

So far:
For sure metal support
Solid 3D renderer, new 3D features and a new 3D editor
What are your thoughts on these item?

Should we merge GitHub.com/cocos-creator/cocos2d-x-lite to cocos2d-x v4, and publish with the Cocos Creator editor support?

Could we focus JavaScript & TypeScript only, and abandon C++ & Lua API?

Should we promote the totally rewritten 3D framework in v4?

Posts: 2

Participants: 1

Read full topic

Announcements Engine

Announcing the Godot 2019 showreel

Godot Engine Official

Tue, 16 Apr 2019 02:00:00 +0200

Announcing the Godot 2019 showreel

Another year, another showreel. As every year, the amount of quality games being created by Godot has increased significantly (as did the amount of submissions).

Submissions

The idea of the reel is to include games both published and in development.

We got well over a hundred submissions this year, 3 or 4 more times than last year. Most of them are fantastic, but it became impossible to put all of them in the official reel, not even in the extended one.

After discussing, we decided to split into two, one for Mobile and one for Desktop/Console games, so have a seat, grab a drink and enjoy the 2019 showreels!

Desktop / Console showreel

Mobile showreel

Future

In some days we will also put up the extended showreel, including significantly more games.

As always, big thanks to Hubert Lamontagne for supplying music to the reel and to Hugo Locurcio for the editing.

Remember that, as always, Godot is open souce and community developed. The core contributors have decided to dedicate their lives to this project, rejecting very juicy offers by the biggest companies in the world. But this can only happen thanks to donations so, if you are not yet, please consider becoming our patron, and help Godot development remain free and open. Even a small donation is enormously helpful.

Engine