The goal of this manifesto is to provide an easy to follow and reasonable rules that realtime and video game renderers can follow.
These rules highly prioritize image clarity/stability and pleasant gameplay experience over photorealism and excess graphics fidelity.
Keep in mind that shipping a game has priority over everything else and it is allowed to break the rules of the manifesto when there are no other good options in order to ship the game.
| { | |
| "FileVersion": 3, | |
| "EngineAssociation": "5.2", | |
| "Description": "Minimum viable plugin dependencies for a usable Unreal Engine project", | |
| "DisableEnginePluginsByDefault": true, | |
| "Plugins": [ | |
| { | |
| "Name": "PluginBrowser", | |
| "Enabled": true | |
| }, |
A metatable in Lua defines various extraneous behaviors for a table when indexed, modified, interacted with, etc. They are Lua's core metaprogramming feature; most well known for being useful to emulate classes much like an OOP language.
Any table (and userdata) may be assigned a metatable. You can define a metatable for a table as such:
-- Our sample table
local tab = {}
-- Our metatable
local metatable = {
-- This table is then what holds the metamethods or metafields
Please stop using this extension and Microsoft's C++ extension for Unreal code completion.
The VSCode extension clangd has blazing fast code completion in comparison. I've made a VSCode extension for it:
https://github.com/boocs/unreal-clangd
You will use clangd for code completion(Intellisense) and use Microsoft's C++ extension for Building/Debugging
tl;dr: Wayland is not "the future", it is merely an incompatible alternative to the established standard with a different set of priorities and goals.
Wayland breaks everything! It is binary incompatible, provides no clear transition path with 1:1 replacements for everything in X11, and is even philosophically incompatible with X11. Hence, if you are interested in existing applications to "just work" without the need for adjustments, then you may be better off avoiding Wayland.
Wayland solves no issues I have but breaks almost everything I need. Even the most basic, most simple things (like xkill) - in this case with no obvious replacement. And usually it stays broken, because the Wayland folks mostly seem to care about Automotive, Gnome, maybe KDE - and alienating e
| /* | |
| * This is free and unencumbered software released into the public domain. | |
| * | |
| * For more information, please refer to <https://unlicense.org> | |
| */ | |
| //Regular text | |
| #define BLK "\e[0;30m" | |
| #define RED "\e[0;31m" | |
| #define GRN "\e[0;32m" |
What is strict aliasing? First we will describe what is aliasing and then we can learn what being strict about it means.
In C and C++ aliasing has to do with what expression types we are allowed to access stored values through. In both C and C++ the standard specifies which expression types are allowed to alias which types. The compiler and optimizer are allowed to assume we follow the aliasing rules strictly, hence the term strict aliasing rule. If we attempt to access a value using a type not allowed it is classified as undefined behavior(UB). Once we have undefined behavior all bets are off, the results of our program are no longer reliable.
Unfortunately with strict aliasing violations, we will often obtain the results we expect, leaving the possibility the a future version of a compiler with a new optimization will break code we th
| Windows command | Unix command | Notes |
|---|---|---|
| set | env | Set on Windows prints a list of all environment variables. For individual environment variables, set is the same as echo $ on Unix. |
| set Path | export $PATH | Print the value of the environment variable using set in Windows. |
| set PROJ | -- | result: PROJ=c:\project |
| echo %PROJ% | echo $PROJ | result: c:\project |
|