Smart UI Discrete Progress Part behavior handles progress parts UI components. If you use it as part of a hierarcy, you must add it to an object using a Smart UI Container behavior to be rendered correctly, since it will use its parent to determine the total Discrete Progress Part components available to alter.

Properties

Actions

Set Enabled

Disable/Enable the Component

Set Name

Sets the name of the component.

Set Part Sequence

Sets the parts sequence index for this component.

Set Max Parts

Sets the maximum parts for this component.

Set Group Value

Sets the value to be distributed among the parts of the same group. The group is determined by the container to which the parts belong.

Conditions

Is Enabled

Returns true if the component is enabled

Compare Value

Compares the value of the part.

Compare Name

Returns true if the radio button components name equals the parameter

On Value Change

Triggered when the part value changes.

Expressions

Value

Part current value.

MaxParts

Maximum parts for this component.

Name

Component name

(c) Pixel Perfect Studio 2024

The post Smart UI Discrete Progress first appeared on Pixel Perfect Studio.

Smart UI Progress Bar behavior handles progress bar UI components. It provides built-in animations and triggers to handle value changes. The component relies on its width. If you use it as part of a hierarcy, you must add it to an object using a Smart UI Container behavior to be rendered correctly, since it will use its parent width as the base for rendering.

Properties

Actions

Set Enabled

Disable/Enable the Button

Set Name

Sets the name of the component.

Set Value

Sets the current value of the progress bar. If the value is below 0 or above the maximum, it will be clamped.

Set Max

Sets the maximum value of the progress bar.

Set Animation

Sets the animation function of the progress bar.

Set Animation Time

Sets the time period in seconds to complete the animation of progress bar.

Conditions

Is Enabled

Returns true if the Progress Bar is enabled

Compare Value

Compares the value of the progress bar.

Compare Name

Returns true if the progress bar components name equals the parameter

On Animated Value

Triggered when the progress bar animation is running. Use it to in combination of expressions AnimatedValue and AnimatedProgress to retrieve the animation data.

On Animation Finished

Triggered when the progress bar animation completes.

Expressions

Value

Progress Bar current value.

Progress

Progress Bar progress value in percentage.

Max

Progress Bar Maximum value.

AnimatedValue

Current animated value. This value is set only when the animation is running. E.G. If you are changing the value from 0 to 10, it will contain all the step values to reach the 10, as if it was counting.

AnimatedProgress

Percentage representing the AnimatedValue from the Max value allowed to be set for the progress bar. This value is set only when the animation is running

Name

Component name

(c) Pixel Perfect Studio 2024

The post Smart UI Progress Bar Behavior first appeared on Pixel Perfect Studio.

Smart UI Radio Button behavior. Controls the object like a radio button, with values: check, and unchecked. It handles ten diferent sprite animations to match all the states of the object, and can be animated with several built-in animations and easings.

Properties

Actions

Set Enabled

Disable/Enable the radio button

Set Index

Sets the sequence index to influence the selection of components.

Set Invisible Component

Sets whether the component should be processed when it's invisible. Opacity is not taken in consideration.It doesn't affect the visibility attribute of the object, you are responsible of turning it visible or invisible when needed.

Set Focusable

Disable/Enable the radio button

Set Focus

Sets the focus on the component, removing the focus from all the components within the same container.

Set Name

Sets the name of the radio button.

Set Check

Toggles the value of the radio button.

Simulate Hover

Trigger the hover event of the plugin, simulating the interaction of the user.

Set Checked Hover Animation

Sets the animation when hovering the radio button

Set Unchecked Hover Animation

Sets the animation when hovering the radio button

Set Hover Time

Sets the animation duration when hovering the radio button

Set Hover Change Factor

Sets the animation when hovering the radio button

Set Hover Function

Sets the animation when hovering the radio button

Set Checked Press Animation

Sets the animation when pressing the radio button

Set Unchecked Press Animation

Sets the animation when pressing the radio button

Set Press Time

Sets the animation duration when pressing the radio button

Set Press Change Factor

Sets the animation when pressing the radio button

Set Press Function

Sets the animation when pressing the radio button

Set Unchecked Animation

Sets the animation when restoring the radio button to its normal unchecked state

Set Checked Animation

Sets the animation when restoring the radio button to its normal checked state

Set Restore Time

Sets the animation duration when restore the radio button to its original state

Set Restore Function

Sets the animation when restoring the radio button

Set Check Disabled Animation

Sets the animation when disabling the radio button

Set Uncheck Disabled Animation

Sets the animation when disabling the radio button

Set Checked Focus Animation

Sets the animation when focusing the radio button. Focus animation overrides the normal animation if the radio button has the focus.

Set Unchecked Focus Animation

Sets the animation when focusing the radio button. Focus animation overrides the normal animation if the radio button has the focus.

Set Focus Time

Sets the animation duration when focusing the radio button

Set Focus Change Factor

Sets the animation when focusing the radio button

Set Focus Function

Sets the animation when focusing the radio button

Conditions

Is Enabled

Returns true if the radio button is enabled

Compare Name

Returns true if the radio button components name equals the parameter

Is Checked

Returns true if the radio button is checked

Is Invisible Component

Returns true if the radio button is configured as an invisible component.

Is Focused

Returns true if the radio button has the focus

Is Hovered

Returns true if the radio button is hovering

Is Pressed

Returns true if the radio button is being pressed

On Focus

Triggered when the radio button gets the focus

On Focus Lost

Triggered when the radio button loses focus

On Selected

Triggered when the radio button is selected.

On Hover

Triggered when the radio button starts hovering

On Hover Lost

Triggered when the radio button ends hovering

On Pressed

Triggered when the radio button started pressing.

On Released

Triggered when the radio button is released.

Expressions

Name

Component name

(c) Pixel Perfect Studio 2024

The post Smart UI Radio Button Behavior first appeared on Pixel Perfect Studio.

Smart UI Dialog behavior groups UI components, provides focusing abilities and default interactions to navigate within the dialog and its children components that uses Smart UI behaviors, and handles cascading Enabling/Disabling events. It also responds to pointer interactions prioritizing by zIndex.

Properties

Actions

Set Enabled

Disable/Enable the Button

Set Name

Sets the name of the component.

Set Sequence

Sets the sequence index to influence the selection of components.

Set Focusable

Disable/Enable the Button

Set Focus

Request the focus for this dialog

Focus First Element

Request the focus for the first interactable element of the dialog.

Focus Last Element

Request the focus for the last interactable element of the dialog.

Set Invisible Component

Sets whether the component should be processed when it's invisible. Opacity is not taken in consideration.It doesn't affect the visibility attribute of the object, you are responsible of turning it visible or invisible when needed.

Close

Closes the dialog.

Restore

Restores the dialog.

Minimize

Minimizes the dialog.

Maximize

Maximize the dialog.

Conditions

Is Enabled

Returns true if the dialog is enabled

Is Invisible Component

Returns true if the Button is configured as an invisible component.

Compare Name

Returns true if the radio button components name equals the parameter

Is Focused

Returns true if the Button has the focus

Has Control

True if the dialog has the control to navigate over components.

On Open

Triggered when the dialog opens. If it's animated, it triggers when the animation finishes.

On Close

Triggered when the dialog closes. If it's animated, it triggers when the animation finishes.

On Maximize

Triggered when the dialog maximizes

On Minimize

Triggered when the dialog minimizes

On Restore

Triggered when the dialog restores back to its original state.

On Focus

Triggered when the dialog gets the focus

On Focus Lost

Triggered when the dialog loses focus

Is Open

Returns true if the dialog is Open

Is Minimized

Returns true if the dialog is Minimized

Is Maximized

Returns true if the dialog is Maximized

Expressions

Name

Component name

(c) Pixel Perfect Studio 2024

The post Smart UI Dialog Behavior first appeared on Pixel Perfect Studio.

Smart UI Button behavior covers all the basic functionality of a Push Button, handles event animations, provides built-in animations and easings, and triggers user event interactions.

Properties

Actions

Set Enabled

Disable/Enable the Button

Set Name

Sets the name of the radio button.

Set Index

Sets the sequence index to influence the selection of components.

Set Invisible Component

Sets whether the component should be processed when it's invisible. Opacity is not taken in consideration.It doesn't affect the visibility attribute of the object, you are responsible of turning it visible or invisible when needed.

Set Focusable

Sets the component to be able to receive the focus

Set Focus

Sets the focus on the component, removing the focus from all the components within the same container.

Simulate Click

Trigger the click event of the plugin, simulating the interaction of the user. Button will be locked for interactions until the animation time is completed.

Simulate Hover

Trigger the hover event of the plugin, simulating the interaction of the user.

Set Hover Animation

Sets the animation when hovering the button

Set Hover Time

Sets the animation duration when hovering the button

Set Hover Change Factor

Sets the animation when hovering the button

Set Hover Function

Sets the animation when hovering the button

Set Press Animation

Sets the animation when pressing the button

Set Press Time

Sets the animation duration when pressing the button

Set Press Change Factor

Sets the animation when pressing the button

Set Press Function

Sets the animation when pressing the button

Set Normal Animation

Sets the animation when restoring the button to its normal state

Set Restore Time

Sets the animation duration when restore the button to its original state

Set Restore Function

Sets the animation when restoring the button

Set Disabled Animation

Sets the animation when disabling the button

Set Focus Animation

Sets the animation when focusing the button. Focus animation overrides the normal animation if the button has the focus.

Set Focus Time

Sets the animation duration when focusing the button

Set Focus Change Factor

Sets the animation when focusing the button

Set Focus Function

Sets the animation when focusing the button

Conditions

Is Enabled

Returns true if the Button is enabled

Is Invisible Component

Returns true if the Button is configured as an invisible component.

Compare Name

Returns true if the button components name equals the parameter

Is Focused

Returns true if the Button has the focus

Is Hovered

Returns true if the Button is hovering

Is Pressed

Returns true if the Button is being pressed

On Focus

Triggered when the button gets the focus

On Focus Lost

Triggered when the button loses focus

On Click

Triggered when the button is clicked

On Hover

Triggered when the button starts hovering

On Hover Lost

Triggered when the button ends hovering

On Pressed

Triggered when the button started pressing.

On Released

Triggered when the button is released.

Expressions

Name

Component name

(c) Pixel Perfect Studio 2024

The post Smart UI Button Behavior first appeared on Pixel Perfect Studio.

Smart UI is a framework and a set of addons developed with the purpose to simplify the UI design and build in the game engine Construct 3. The framework is still in development but has already reach a stage where the addons and the design components are fully usable to create functional UI's.

The framework came from the need of upgrading the existing tools and addons from Construct's SDK v1 which has evolved into the SDK v2, introducing breaking changes and forbidding backwards compatibility for the tools developed by the community. Therefore, I decided to develop my own framework, highly integrated with the current SDK and aiming to live for long to keep my game projects running for several years. Compatibility with the SDK v2 is a major challenge, considering that the current state of the SDK is still in development, but with a stable version already rolled out.

As part of this project, I've been reporting multiple bugs that Scirra, who has been resolving them swiftly, allowing me to move on and complete the milestones I've set for these addons, while helping the Construct 3 community to have a more stable SDK in the process.

Products and Milestones

This is a big project, since it has to consider multiple use cases and testing scenarios to be properly integrated with the game engine. Therefore, all the addons must support the following minimum features:

• Advanced Minification.
• Load / Save game states.
• zIndex based interactivity.
• Automatic focusing and siblings interactions.
• Managing Multiple dialog windows in the same layout and layer.
• Object containers to manage the components focus, document flow and default actions, as well as grouping components.
• Flexibility for custom design
• Simple implementation and comprehensible ACE's
• Integration with C3 through native SDK features and UI composition through the Objects Hierarchy / Scene Graph.

With above points in mind, I've come a list of the components that need a short-term replacement since they were provided by existing products that will get deprecated by 2025. All of these UI components will be provided in the form of Behaviors, allowing the game developers to utilize them in different forms to suit their needs.

All of above are being designed and developed aiming to provide out-of-the-box animations and functionalities, but also flexibility for customizing its appearance and interactions through the set of ACEs available for each addon.

At the current stage of development, these are the components available and working.

Available Addons Features

Smart UI

Icon	Dev. Stage	Type
	Alfa	Plugin

Smart UI Plugin. Automatically loads the SmartUI framework to controll all the components. It will automatically communicate with all the Smart UI addons to provide a proper response to interactions and ACEs.

Creating objects that use the SmartUI behaviors will automatically register their instances in the framework, allowing you to dinamically create more complex and custom components on the fly, using hierarchies and object templates.

Main Features:

• Enable/Disable the framework preventing interactions.
• Container and Dialog pass-control logic, to provide automatic component navigation through default keyboard inputs or plugin actions.
• Dinamically create and trigger open animations for dialogs

Push Buttons

Icon	Dev. Stage	Type
	Alfa	Behavior

Smart UI Button behavior covers all the basic functionality of a Push Button, handles event animations, provides built-in animations and easings, and triggers user event interactions.

The behaviors allows you to set Enable/Disabled, Hover, Press, Focus and Restore animations for Sprite plugins, and provides a list of built-in easings to instantly give a highly polished finishing.

Main Features:

• Focusable Component with priorization index using document flow.
• zIndex priorization reaction
• Built-in easings for animations
• Multiple Sprite animations for each button state
• Automatic context detection based on objects hierarchy tree.

Radio Buttons

Icon	Dev. Stage	Type
	Alfa	Behavior

Smart UI Radio Button behavior. Controls the object like a radio button, with values: check, and unchecked. It handles ten diferent sprite animations to match all the states of the object, and can be animated with several built-in animations and easings. Reacts accordingly to the context where it is placed.

Main Features:

• Focusable Component with priorization index using document flow.
• Automatic detection of context. Radio-buttons will interact with other radio buttons grouped in the same container/dialog window.
• zIndex priorization reaction
• Built-in easings for animations
• Multiple Sprite animations for each button state
• Automatic context detection based on objects hierarchy tree.

Check Boxes

Icon	Dev. Stage	Type
	Alfa	Behavior

Smart UI Checkbox behavior. Controls the object like a checkbox, with values: check, and unchecked. It handles ten different sprite animations to match all the states of the object, and can be animated with several built-in animations and easings.

Main Features:

• Focusable Component with priorization index using document flow.
• zIndex priorization reaction
• Built-in easings for animations
• Multiple Sprite animations for each button state
• Automatic context detection based on objects hierarchy tree.

Progress Bar

Icon	Dev. Stage	Type
	Alfa	Behavior

Smart UI Progress Bar behavior handles progress bar UI components. It provides built-in animations and triggers to handle value changes. The component relies on its width. If you use it as part of a hierarcy, you must add it to an object using a Smart UI Container behavior to be rendered correctly, since it will use its parent width as the base for rendering.

Main Features:

• Built-in easings for animations
• Rendering based on component's width or context width (containers and dialogs).
• ACEs to get animated values and actual values to render progress.
• Automatic context detection based on objects hierarchy tree.

Discrete Progress Part

Icon	Dev. Stage	Type
	Alfa	Behavior

Smart UI Discrete Progress Part behavior handles progress parts UI components to represent an integer value with multiple heterogeneous sprites and animations. If you use it as part of a hierarcy, you must add it to an object using a Smart UI Container behavior to be rendered correctly, since it will use its parent to determine the total Discrete Progress Part components available to alter.

Just like radio buttons, Discrete Progress Parts will automatically communicate with their siblings in the same context regardless of their object type, it can manage multiple animations and multiple different parts for all the sprites in the same context. For instance, you can use a hearth with 2 parts plus a 6-slices pie in the same group and render up to 8 different animations to represent a value.

Main Features:

• Rendering based on context (containers and dialogs).
• Multiple sprites and animations support to render a single value with several different parts.
• Automatic context detection based on objects hierarchy tree.

Scroll Bars

Icon	Dev. Stage	Type
	In Development	Behavior

Smart UI Scroll Bars provide a discrete and step value capabilities, allowing you to handle float or integer numbers. It's composed by a progress bar and a push button to work like a slider.

Main Features:

• Focusable Component with priorization index using document flow.
• zIndex priorization reaction
• Automatic context detection based on objects hierarchy tree.
• Composition by component's name

Containers

Icon	Dev. Stage	Type
	Alfa	Behavior

Smart UI Container behavior groups UI components setting a context, provides focusing abilities, and default interactions to navigate within the container and its children components that uses Smart UI behaviors.Handles cascading Enabling/Disabling events. It also responds to pointer interactions prioritizing by zIndex.

Main Features:

• Focusable Component with priorization index using document flow.
• Automatic context detection based on objects hierarchy tree.
• Component grouper.

Dialogs

Icon	Dev. Stage	Type
	Alfa	Behavior

Similarly to a container, Smart UI Duakigs behavior groups UI components setting a context, provides focusing abilities, and default interactions to navigate within the container and its children components that uses Smart UI behaviors. Handles cascading Enabling/Disabling events. It also responds to pointer interactions prioritizing by zIndex.

It provides also built-in animations and easings, maximize, minimize, restore and close capabilities. Can be instantiated dinamically through create object, or it can be opened using the SmartUI Plugin OpenDialog action to trigger animations. Multiple dialogs can be rendered in the same layer and in the same layout.

Dialogs are components that require other objects to be fully created. You can add their interaction buttons like close and minimize through component's name as long as a dialog is the top-most object in a hierarchy.

Main Features:

• Focusable Component with priorization index using document flow.
• Automatic context detection based on objects hierarchy tree.
• Component grouper.
• Modal dialog capabilities.
• Minimization, Maximization, Restore, and Close actions.
• Composition by component's name

Pricing and Licensing

I know the community is eager to have open-source and license-free addons, nevertheless it will be impossible to keep these projects running without funding. Therefore, SmartUI will be out for sale at a reasonable price for indie developers. The final prices is still to be calculated.

The framework won't be provided as an open-source tool, since their main purpose was to serve also for my game-dev projects, properly protected by copyright laws.

What's the difference between a large pizza and a game-developer? A. A pizza can feed a family of four!

Plugin Functionality Demonstrations

Since this project is still in development phase, the definitive demos and videos will be worked later as I reach stable version of the addons, closer to the launch date, which is still to be defined nevertheless I'm aiming for 2024.

If you'd like to know more about the project, follow my social media and feel free to provide feedback and suggestions to create a more robust set of addons.

Thank you for reading through!

View this post on Instagram

A post shared by Pixel Perfect Studio | Indie Gamedev (@ppstudiomonterrey)

View this post on Instagram

A post shared by Pixel Perfect Studio | Indie Gamedev (@ppstudiomonterrey)

The post Smart UI is a framework and a set of addons developed with the purpose to simplify the UI design and build in the game engine Construct 3. first appeared on Pixel Perfect Studio.

Video

Game ETA

15-25 min

Learning Objective Standards (US)

Instructions

The game provides a simplified user interface and clear instructions to guide your kids through each of the mini-games. You'll have access to instructional animations to have a better understanding of each topic. The minigames offers: break-the-crust game, accuracy games, puzzle solving games, and action scenes to keep your students engaged. Purchase as many items as you can to beautify your movie set, and unlock all the achievements.

Screenshots

Play Now

The post Fury the Capibara – Plate Tectonics first appeared on Pixel Perfect Studio.

Ashley's Quote

Just a few days ago, Ashley Gullen, founder of Scirra, the owners of the popular game engine Construct 3, posted an alarming entry on their website for all those who develop and use 3rd party addons. This may cause all your live projects to break and become inaccessible for further updates.

Construct 3 was officially announced in 2015 with a promising future, ensuring backward compatibility for its predecessor, Construct 2. Since its official release on December 4, 2017, its architecture came with an SDK that allowed advanced users to develop more complex features, enriching the engine over time and, as a consequence, helping Scirra to leverage the engine's popularity. For the last 6 years, a very active and strong community has formed around Construct 3, collaborating with all its members, who have managed to create multiple plugins that expand Construct 3's capabilities beyond what it natively provides. Popular plugins like Funky Quad, which projects 2D textures in 3D coordinates, Colyseus Multiplayer SDK, Google Analytics for Universal Analytics, ProUI, and many more were created by community members.

All of these addons were based on SDK V1 and are widely used by Construct 3 developers. They even pushed the company to support features like 3D and Scene Graphs, the latter of which was surprisingly never considered by Construct originally. I've just mentioned a couple, but there are dozens of addons that provide extended capabilities based on SDK V1 that will soon be killed by Scirra's founder, Ashley Gullen. In an attempt to "secure" its engine core, Ashley has decided to retire all support for SDK V1 permanently, to be replaced by the new SDK V2. Scirra clearly has no idea of the impact of their decision. The quantity of projects that will become unusable and even inaccessible is still to be counted, but I can guarantee the crashes will come by the hundreds.

I've been a developer for 20 years and have been using Construct professionally for the last 6 years. It became an important part of my finances, and to make games leaner and faster, I've created multiple private addons that provide functionalities that Construct 3 doesn't have, and that Scirra won't be willing to support natively. I've also purchased addons from other developers that greatly improve the engine. Like many, I use two very popular sets of addons: Aekiro's ProUI (recently open-sourced) and Chadori's Construct Master Collection. The first provides UI capabilities, which Construct really lacks, and the latter is a set with multiple functionalities that integrate PlayFab, Firebase, and Android and iOS native functionalities that are also nonexistent in Construct. If by any means your projects used one of these, you are at high risk that Construct 3 Breaks your Games Permanently.

6 years of work on plugins that use SDK V1 is a lot of work. I've invested countless hours designing, developing, and testing them to improve my delivery timeline, and thus increase my income from making games and selling addons. All of that is at risk now.

Engines like Unreal, Godot, and Phaser are either open source or provide access to their internals to allow developers to create incredible products and experiences. In contrast, Scirra has decided to fully close its engine.

Scirra's Response.

Many of the available popular addons use the engine's internal features, which won't be available in SDK V2. As a result, projects using any of those addons will be unusable and won't even open in Construct because of this restriction. Even addons that are not using any of the engine's internals will be affected just by the new design of V2, creating the need for developers to invest countless hours migrating and testing them. In some cases, developers migrated to more robust engines, leaving those addons without updates (e.g., Game Analytics, Spriter, and more). As you can imagine, the amount of work to fix/migrate them, and number projects impacted is huge. Addons for Spine and Spriter are totally based on SDK V1, and they will be completely trashed after this update.

Scirra's founder, Ashley, argues that this change will benefit the customers, but there are no benefits at all for users. On the contrary, their older projects will never open again just because SDK V2 won't provide any sort of backward compatibility, and Scirra's capability to support multiple versions of Construct is in question. No performance improvements, no additional functionalities, no backward compatibility are benefits from this change. On the contrary, you'll lose what you have now. Engines like Unreal and Unity, the market leaders, provide their older versions in a way where you won't lose access to those projects with tools like Unity Hub. In contrast, this change in Construct will restrict you from ever updating an old project because their core, which is always provided as a service from a server, will change forever.

Community's reaction - Construct 3 Breaks your Games Permanently

As a result, the developer community is in great discomfort because Construct 3 Breaks your Games Permanently, and although they have been actively trying to convince Scirra to provide permanent support for SDK V1, Scirra is completely reluctant to hear them out. In a desperate attempt to keep projects alive, the community is trying to organize to fix as many of the plugins as they can, cleaning up Scirra's mess and reinforcing the fact that Scirra's long-term decisions are questionable and, in my opinion, don't reflect a reliable company that hears and supports its community. We've seen what happened to Unity with their pricing model; they were reluctant to hear their community out until it was too late and their financials were impacted. Eventually, things changed, and I'm afraid Scirra could follow the same path. If the impact is not financial, for sure the reliability and confidence in the company will be jeopardized, and many talented developers will likely migrate to a more serious engine.

It's important that you, a reader and probably a Construct 3 user, are aware of what's happening and what these changes imply. Personally, I'll be greatly affected in terms of work and income, and I have to make a big pause to migrate my plugins because I have revenue committed to my existing games, which will put me in a difficult situation if I just leave. So, I have no options. But I'm sure that if the community organizes and tries to push this decision back, we may have Scirra develop permanent support for SDK V1 and thus keep our projects alive permanently.

Thanks for reading through my whole post. I hope I've explained the situation clearly to you, and if you can manifest against this decision, I hope we can push this decision back.

Pixel Perfect Studio

The post Construct 3 Breaks your Games Permanently first appeared on Pixel Perfect Studio.

Game ETA

15-20 min

Learning Objective Standards (US)

The game covers the following topics, aligned with the US educational standards.

Instructions

The game offers two modes:

1. Story mode will walk you through the main concepts of rounding off by using a fun pump mechanic where you'll visualize how a value is carried up or down between pumps representing the rounding process.
2. Rounding Game is meant to practice the rounding process, after you learned how to use the pumps in the story mode. Practicing is a great way to reinforce the topic within your students before they present test, or simply to refresh their knowledge.

Screenshots

Play Now

The post The Rounding Balloon Shop first appeared on Pixel Perfect Studio.

In this instructional game you will learn the concepts of points, lines, rays, line segments, and angles. A Mouse and headphones are recommended for an improved gaming experience.

Video

Game ETA

15-20 min

Learning Objective Standards (US)

The game covers the following topics, aligned with the US educational standards.

Instructions

The game will guide you on each step, assisting you on each stage. There is a hidden star cluster in the space! Use the cartesian plane and points to find it. Explore the concept of the line while speeding up through space and confirm that it is infinite. Use the pulsar portal to transport yourself a step closer to home. Finally, construct random irregular shapes using points and line segments, classify their angle types and recharge the star to continue his journey.

Screenshots

Play Now

The post Galactic Geometry first appeared on Pixel Perfect Studio.