To launch a game on Steam, it is necessary to integrate the SteamSDK. This article briefly introduces the method of integrating SteamSDK in UE4, with future content related to integrating Steam platform services also included in this article.
The integration of SteamSDK allows the game to connect with the Steam community, which has a robust community ecosystem that Epic’s newly launched Epic Games Store cannot currently compete with~(of course, I support market competition).
The UE4 provides a mature configuration mechanism for INI files, and the engine uses ini as configuration files for both the engine and projects. This article will briefly analyze the loading of GConfig in the engine.
In daily development and learning, I have encountered and resolved some issues and collected some materials, which I have casually written down in notes. I have accumulated a fair amount related to UE, while other topics are mixed together and relatively chaotic. I have organized them into this article. Unlike the UE4 and VR Development Technical Notes, the content here is more focused on actual problem records and material collection within projects.
HTC released the Vive accessory Vive Tracker to expand devices connected to SteamVR. It also features Pogo pins, allowing users to DIY special function accessories. Recently, I’ve seen some amazing creative uses of the Vive Tracker. Relevant materials and technical details are organized in this article.
Although UE is a game engine, it is not limited to writing games—you can even use it to write Win32 GUI applications 😏. Typically, we create a UE game project using the Editor and build our own classes based on it for use in the game. However, if you don’t want to create a game project, UE also supports Standalone Applications that can construct their own programs autonomously from the main function, fully controlling which Modules to enable without relying on the engine’s own logical architecture. This can also serve as a lightweight method for learning and testing UE modules.
Note: UE does not provide a direct method to create a Standalone Application, so I wrote a tool to create a
Programproject: hxhb/ue4program, and implemented a demo for a standalone tool: hxhb/UE4Launcher.
Recently, while reading The Dragon Book DX12, I’ve been using LaTeX to document some formulas. To facilitate searching, I’ve compiled a table of commonly used LaTeX mathematical symbols syntax. More symbols can be found at LaTeX:Symbols.
UE is a modular architecture, where Engine/Game Project/StandaloneApplication/Plugins are all Modules (Unreal Engine API Reference lists the Modules provided by the Engine). This article analyzes how UE’s Modules are loaded and started via FModuleManager::LoadModule using the code from FModuleManager.
UE builds projects through UBT (whether using Build in VS or Compile in the Editor, it eventually calls UBT). UBT and UHT are the cornerstones of the UE toolchain, and due to the vast amount of content, it is impossible to analyze everything at once. Let’s outline the main points now and supplement them later as time allows.
C++ is a language that supports object-oriented programming (object-oriented Programming), with inheritance and polymorphism (Polymorphic) being its most important features. There has been considerable discussion in previous articles about various aspects of C++ inheritance and class member content. This article primarily investigates one implementation method of C++ polymorphism by the compiler: virtual function tables.
The C++ standard ([IOS/IEC 14882:2014]) states:
Virtual functions support dynamic binding and object-oriented programming. A class that declares or inherits a virtual function is called a polymorphic class.
Note: The C++ standard does not specify how polymorphism is implemented, so the implementation of polymorphism by the compiler is Implementation-defined Behavior, meaning different compilers may implement polymorphism differently, and different platforms may yield different experimental results.
Recently, I encountered a very strange error during the project packaging:
1 | // package log |
I debugged the UE4 code and analyzed the cause and solution process.