<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Alex Volkov on Medium]]></title>
        <description><![CDATA[Stories by Alex Volkov on Medium]]></description>
        <link>https://medium.com/@alex-wolf-kh?source=rss-e9d4691eaf94------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*cKG-3j7d6jdiczWSpWpuWA.png</url>
            <title>Stories by Alex Volkov on Medium</title>
            <link>https://medium.com/@alex-wolf-kh?source=rss-e9d4691eaf94------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 03:40:45 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@alex-wolf-kh/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Crafting Interactive Bridges: The Evolution of an In-Game Console — Part 1]]></title>
            <link>https://alex-wolf-kh.medium.com/crafting-interactive-bridges-the-evolution-of-an-in-game-console-part-1-4e2493fa921c?source=rss-e9d4691eaf94------2</link>
            <guid isPermaLink="false">https://medium.com/p/4e2493fa921c</guid>
            <category><![CDATA[c-sharp-programming]]></category>
            <category><![CDATA[unity]]></category>
            <category><![CDATA[game-development]]></category>
            <category><![CDATA[game-design]]></category>
            <category><![CDATA[indie-game]]></category>
            <dc:creator><![CDATA[Alex Volkov]]></dc:creator>
            <pubDate>Sat, 26 Aug 2023 10:22:52 GMT</pubDate>
            <atom:updated>2023-08-26T10:22:52.749Z</atom:updated>
            <content:encoded><![CDATA[<h3>Crafting Interactive Bridges: The Evolution of an In-Game Console — Part 1</h3><h4>From Concept to Code: Unraveling the Layers of an Advanced In-Game Console</h4><h3>Background</h3><p>My name is <a href="https://www.linkedin.com/in/alexwolf-kh/">Alex Volkov</a>, and I have a hobby: creating RPGs in my free time. If you’d like, you can call it my pet project. This project is being developed by two people, and I’m one of them. You should also know that I’m the tech guy; I handle all the development on my own. The other person works on the lore, quests, and other game design aspects that don’t involve coding.</p><h3><strong>Context</strong></h3><p>In our game, there’s an in-game console where players can view live in-game events, such as: damage calculations, NPC information, and even an online chat feature for player-to-player communication. Given this, I’ve been tasked with designing a highly extendable system. This system should allow for tabs, a scroll view, and other functionalities, enabling the multifaceted use of this in-game console.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/982/1*wUgIYYXiKageTad55dWDiw.jpeg" /></figure><p>Also, remember, we’re in the development phase of the game. This means that the game console should include a “devlog console” for logging debug information events. Additionally, there should be a capability for players to create tickets directly from the game, reporting bugs or suggesting new features.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/562/1*sFEp2SAykzNWehYRcZvSjA.gif" /><figcaption>The implemented game-in console in our RPG</figcaption></figure><h3><strong>Concept</strong></h3><p>Every feature should begin with the creation of a concept. This functionality was no exception. Having seen numerous consoles, primarily in MMO online games, I’ve gained an understanding of what our game requires and how it should function. As one of the initial steps, I drafted a list of functionalities for the first phase of the console.</p><p><strong>In-game console functionality</strong>:</p><ul><li>Tabs with icons and custom names.</li><li>Search input field and a page displaying search results.</li><li>Stick to the bottom (when enabled, the scroll will always remain at the bottom of the console log).</li><li>Styles for log events (customizable icons and colors, along with data such as timestamps, event types, primary and meta descriptions).</li><li>Actions for logs (options to copy to clipboard, delete logs, save logs as a *.txt file, and so on).</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/972/1*dDN18dePA61krE4aOn1W8w.png" /><figcaption>The sketch of the in-game console</figcaption></figure><p>This comprehensive list outlines the functionalities I aimed to incorporate in the console’s first iteration. While I haven’t drawn a detailed sketch for these features, my sketches still provide sufficient detail and encompass the core functions.</p><blockquote>Never skip steps when developing new features for a game or product. Visualization and concept creation prompts many questions, aiding you in fully understanding the feature before you delve into coding it.</blockquote><h3><strong>Initial Steps</strong></h3><p>Generally, I favor generating <a href="https://docs.unity3d.com/ScriptReference/GameObject.html">GameObject</a> via scripts whenever feasible. Within the game, I employ Dependency Injection using the <a href="https://github.com/modesttree/Zenject">Zenject</a> framework. Given this, I opted to create a master prefab for the tab and devised a simple <em>MonoBehaviour</em> class that I plan to instantiate and initialize later.</p><pre>using UnityEngine;<br>using TMPro;<br><br>public class LogItem : MonoBehaviour<br>{<br>    [SerializeField] private Image icon;<br>    [SerializeField] private TextMeshProUGUI timeStampTMP;<br>    [SerializeField] private TextMeshProUGUI eventTypeTMP;<br>    [SerializeField] private TextMeshProUGUI informationTMP;<br>    [SerializeField] private LogActions logActions;<br><br>    public Log Log { get; private set; }<br>    public LogActions LogActions =&gt; logActions;<br><br>    private IConsole console;<br><br>    [Inject]<br>    private void Constructor(IConsole console)<br>    {<br>        this.console = console;<br>    }<br><br>    public void Initialize(Log log, ILogView logView)<br>    {<br>        // Set model data<br>        Log = log;<br><br>        // Initialize log actions<br>        logActions.Initialization(log, console);<br><br>        // Set basic description <br>        icon.sprite = logView.Thumbnail;<br>        timeStampTMP.text = log.Timestamp.ToString(&quot;h:mm:ss&quot;);<br>        eventTypeTMP.text = logView.EventName;<br>        informationTMP.text = log.Description;<br><br>        // Set color <br>        icon.color = logView.Color;<br>        timeStampTMP.color = logView.Color;<br>        eventTypeTMP.color = logView.Color;<br>        informationTMP.color = logView.Color;<br>    }<br><br>    private void OnDestroy()<br>    {<br>        logActions.Dispose();<br>    }<br><br>    /// &lt;summary&gt;<br>    /// Call from Unity Editor<br>    /// &lt;/summary&gt;<br>    /// &lt;param name=&quot;isVisible&quot;&gt;&lt;/param&gt;<br>    public void SetActionVisibility(bool isVisible)<br>    {<br>        if (logActions.Enabled) <br>            logActions.SetVisibility(isVisible);<br>    }<br>}</pre><p>The subsequent phase involves crafting a factory for instantiating this component using <a href="https://github.com/modesttree/Zenject">Zenject</a>. This is a conventional approach, so I won’t delve into my personal thoughts on it too much here.</p><pre>using UnityEngine;<br><br>public class LogFactory : ILogFactory<br>{<br>    private readonly DiContainer diContainer;<br><br>    public LogFactory(DiContainer diContainer)<br>    {<br>        this.diContainer = diContainer;<br>    }<br><br>    public LogItem CreateLogItem(LogItem prefab, Transform parent)<br>    {<br>        return diContainer.InstantiatePrefabForComponent&lt;LogItem&gt;(prefab, parent);<br>    }<br>}<br><br>public interface ILogFactory<br>{<br>    LogItem CreateLogItem(LogItem prefab, Transform parent);<br>}</pre><p>Bind factory in <a href="https://github.com/modesttree/Zenject">Zenject</a> Installer</p><pre>Container.Bind&lt;ILogFactory&gt;().To&lt;LogFactory&gt;().AsSingle().NonLazy();</pre><p>You might be wondering why I’m taking such a seemingly intricate route. I have two primary reasons:</p><ul><li>The settings for the console comprise two options: the first pertains to the console’s visibility, while the second dictates row limitations within the console.</li><li>My console’s serializable class will require injections in the future, necessitating its instantiation via a factory.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*dL5-LUsrOYLhSQ3DjxGnIw.gif" /><figcaption>In-game console and console settings demonstration</figcaption></figure><p>In light of these considerations, I’ve engineered a system that enables me to dynamically create and modify tabs and the console at runtime. The result is a versatile framework permitting me to dictate the title, icon, row limit, visibility of each tab, and console itself. Furthermore, I have the flexibility to generate as many of these tabs as required.</p><p><strong>Log Implementation</strong></p><p>Each of my log items encompasses an icon, event type, primary description, and an array of meta descriptions. To ensure this entity is as versatile as possible, I crafted a separate <a href="https://docs.unity3d.com/ScriptReference/MonoBehaviour.html">MonoBehaviour</a> coupled with an interface that encapsulates all necessary behaviors. Depending on the event type, I determine the icon and log color. When required in the initialization method (using one of its overrides), I can introduce an array of strings, specified in a variable named “meta.” Why the addition of a meta array to the log? On certain occasions, logs, especially developer logs, might include stack traces or other extensive details that are cumbersome for UI display. This additional information can conveniently be housed within the meta.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/610/1*25kGQ3ifZy-6WodYu_xGhA.png" /></figure><p>Another noteworthy approach is my distinction between the <a href="https://docs.unity3d.com/ScriptReference/MonoBehaviour.html">MonoBehaviour</a> representation of the log and the data class utilized for log data storage. This stratagem proves invaluable when one anticipates serializing the call in subsequent stages or when transmitting the data class as parameters. It’s prudent to differentiate between data classes and their visual representation.</p><p><strong>Search History</strong></p><p>Each tab comes equipped with an input field, allowing users to execute searches within it. Users can comb through log descriptions and event values.</p><pre>public IEnumerable&lt;LogItem&gt; Search(string searchTerm)<br>{<br>    // Case-insensitive search<br>    return queue.Where(item =&gt;<br>        item.Log.Description.IndexOf(searchTerm, StringComparison.OrdinalIgnoreCase) &gt;= 0 ||<br>        item.Log.Event.ToString().IndexOf(searchTerm, StringComparison.OrdinalIgnoreCase) &gt;= 0);<br>}</pre><p>Given that search operations often span more than a single frame, it’s crucial to account for ongoing user input. To address this, I introduced a spinning wheel indicator during the search process.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/595/1*Ymw9RurS-9J7Zb-ovaKqVw.gif" /><figcaption>Search implementation in in-game console</figcaption></figure><p>Moreover, we’ve incorporated a concealed Log tab specifically for search operations, providing a concise summary of search results. This design is essentially a variant of our original Log Tab prefab, albeit with a few modifications. Unity Technologies truly broke ground when they rolled out <a href="https://docs.unity3d.com/Manual/PrefabVariants.html">prefab variants</a>. I wholeheartedly endorse leveraging this feature for any prefabs that might be repurposed with minor alterations. It’s these seemingly trivial efficiencies that significantly streamline intricate projects. Believe me, I speak from experience!</p><p><strong>Additional Log Actions</strong></p><p>Each log item features a section dedicated to supplementary actions, which houses three buttons:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/595/1*7bTa7j_AxlnFre2kdbxZMg.gif" /><figcaption>In-game console and additional actions</figcaption></figure><ul><li><strong>Copy to Clipboard</strong>: This function copies the log description and all metadata, formatting them neatly before placing them in the clipboard. For its implementation, I utilized Unity’s default functionality.</li></ul><pre>/// &lt;summary&gt;<br>/// Copies the value to the system clipboard.<br>/// &lt;/summary&gt;<br>private void Copy()<br>{<br>    GUIUtility.systemCopyBuffer = GetTextValue();<br>}</pre><ul><li><strong><em>Save as .txt File</em></strong>: This feature allows users to save the log item, complete with all its details, to a file on their PC. Every time I need to save a file, I employ a consistent pattern for its creation and storage. It’s worth noting that interacting with the file system synchronously can be detrimental. Hence, always opt for asynchronous operations, even if you believe an 8-bit file is too minuscule to bog down the main thread.</li></ul><pre>/// &lt;summary&gt;<br>/// Save description and meta to a *.txt file.<br>/// &lt;/summary&gt;<br>private async void Save()<br>{<br>    var path = Path.Combine(Application.persistentDataPath, DebugFilePath);<br>    <br>    if (!Directory.Exists(path))<br>        Directory.CreateDirectory(path);<br><br>    string logText = GetTextValue();<br><br>    string filePath = Path.Combine(path, $&quot;{log.Uuid}.txt&quot;);<br><br>    await using (var writer = new StreamWriter(filePath, false))<br>    {<br>        await writer.WriteAsync(logText);<br>    }<br><br>    console.CreateLog(IConsole.Event.LogInfo, $&quot;Log has been saved at: {filePath}&quot;);<br>}</pre><ul><li><strong>Delete Log</strong>: This offers users the option to remove a log from the Console Tab. While the premise is straightforward, the actual removal of an object from a Queue presents an intriguing challenge. I delve into the specifics of how I approached this functionality on my end in subsequent sections.</li></ul><pre>/// &lt;summary&gt;<br>/// Deletes a LogItem with the specified UUID.<br>/// &lt;/summary&gt;<br>/// &lt;param name=&quot;uuid&quot;&gt;The UUID of the LogItem to delete.&lt;/param&gt;<br>public void Delete(string uuid)<br>{<br>    // Convert the queue to a list for manipulation<br>    var list = queue.ToList();<br><br>    // Find the LogItem with the specified guid<br>    var itemToRemove = list.FirstOrDefault(item =&gt; item.Log.Uuid == uuid);<br><br>    if (itemToRemove != null)<br>    {<br>        // Remove the item and destroy its associated gameObject<br>        list.Remove(itemToRemove);<br>        Object.Destroy(itemToRemove.gameObject);<br><br>        // Clear the existing queue and enqueue the items from the list<br>        queue.Clear();<br>        foreach (var item in list)<br>        {<br>            queue.Enqueue(item);<br>        }<br>    }<br>}</pre><p>To toggle the visibility of the Additional Log Actions, I made use of the Canvas Group element. Employing this element proves more efficient for games compared to simply activating or deactivating objects. Additionally, within the log parameters, I’ve incorporated the ability to enable or disable the functions housed within the Additional Log Actions Panel.</p><p><strong>Log Sender</strong></p><p>The primary objective of our custom console is to merge the in-game process console, thereby enhancing the in-game user experience. To achieve this, I implemented the Facade pattern. This approach facilitates the transmission of messages to my console via a straightforward, singular line of code.</p><pre>/// &lt;summary&gt;<br>/// Controller for handling debug logs and forwarding them to a console.<br>/// &lt;/summary&gt;<br>public class DebugController<br>{<br>    private readonly IConsole console;<br><br>    public DebugController(IConsole console)<br>    {<br>        this.console = console;<br>    }<br><br>    /// &lt;summary&gt;<br>    /// Subscribes to Unity&#39;s log messages.<br>    /// &lt;/summary&gt;<br>    public void Subscribe()<br>    {<br>        Application.logMessageReceived += HandleLog;<br>    }<br><br>    /// &lt;summary&gt;<br>    /// Unsubscribes from Unity&#39;s log messages.<br>    /// &lt;/summary&gt;<br>    public void UnSubscribe()<br>    {<br>        Application.logMessageReceived -= HandleLog;<br>    }<br><br>    private void HandleLog(string logString, string stackTrace, LogType type)<br>    {<br>        // You can do whatever you want with the log messages here<br>        // For example, you might log them to a file, send them over the network, etc.<br>        // The &#39;type&#39; parameter tells you whether it&#39;s a regular log message, a warning, or an error<br><br>        switch (type)<br>        {<br>            case LogType.Error:<br>            case LogType.Assert:<br>            case LogType.Exception:<br>                console.CreateLog(IConsole.Event.LogError, logString, new[] { stackTrace });<br>                break;<br>            case LogType.Warning:<br>                console.CreateLog(IConsole.Event.LogWarning, logString, new[] { stackTrace });<br>                break;<br>            case LogType.Log:<br>                console.CreateLog(IConsole.Event.LogInfo, logString, new[] { stackTrace });<br>                break;<br>            default:<br>                throw new ArgumentOutOfRangeException(nameof(type), type, null);<br>        }<br>    }<br>}</pre><p>The method I’ve set up, which is publicly accessible, requires an event type, a message, and an array of strings as parameters. This streamlined process allows for logging events using just one line of code. To obtain a reference to this primary logger class, I employed Zenject Injection.</p><p><strong>Use Cases</strong></p><p>Within the game, I have the capability to generate a plethora of events. For instance, when a player loots a piece of equipment, this information, complete with event details, is displayed in the Info Tab. If there’s an issue with the game code, it can be observed directly during gameplay, even in the game’s built version outside of Unity.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/595/1*-3kZOWR5G1rq8cu74a40FA.gif" /><figcaption>In-game console and different events receiving</figcaption></figure><p>This console serves as a bridge, facilitating communication between users and the game through the Game Console. It enhances the in-game experience, fostering a connection between game enthusiasts and developers. Furthermore, in upcoming iterations, this console is slated to function as a feedback reporter and even as an online chat platform for users.</p><p><strong>Conclusion</strong></p><p>Throughout the development journey of our RPG game, the introduction of an advanced in-game console has emerged as a significant enhancement. Beginning as a passionate endeavor helmed by two individuals, our game has seen the integration of several features, with the console being a noteworthy addition. Crafted with precision, it offers functionalities ranging from search history and diverse log actions to straightforward logging mechanisms. This console not only serves as a medium of communication between developers and players but also anticipates an evolution into a platform for feedback and real-time chat.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dXqxQR_hLA7koXkgHbSkGg.jpeg" /></figure><p>The various use cases highlight the console’s adaptability and its potential to refine in-game interactions. Whether it’s granting players insights into their in-game activities or assisting developers with real-time troubleshooting, the console illustrates the kind of thoughtful design we aim to incorporate. Looking ahead, I plan to explore the integration of <a href="https://www.atlassian.com/software/jira/service-management/features/service-desk">Jira Service Desk</a> with our console in a subsequent article, promising further layers of functionality.</p><p>While the console is a significant feature, it’s one of many components that contribute to our ongoing mission: crafting a rich and immersive gaming experience that emphasizes both innovation and player-developer collaboration.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4e2493fa921c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[3D Modeling on iPad Pro: Challenges and Recommendations for Non-Professionals]]></title>
            <link>https://alex-wolf-kh.medium.com/3d-modeling-on-ipad-pro-challenges-and-recommendations-for-non-professionals-9ee583a30f89?source=rss-e9d4691eaf94------2</link>
            <guid isPermaLink="false">https://medium.com/p/9ee583a30f89</guid>
            <category><![CDATA[game-development]]></category>
            <category><![CDATA[3d-modeling]]></category>
            <category><![CDATA[unity3d]]></category>
            <category><![CDATA[3d-design]]></category>
            <dc:creator><![CDATA[Alex Volkov]]></dc:creator>
            <pubDate>Tue, 11 Apr 2023 11:52:10 GMT</pubDate>
            <atom:updated>2023-04-12T06:52:51.927Z</atom:updated>
            <content:encoded><![CDATA[<p>3D Modeling on iPad Pro: Challenges and Recommendations for Non-Professionals</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VCy5Ybd7p8H4JIN4w6ApCQ.png" /><figcaption>Blender Rendering</figcaption></figure><p>As a professional software developer, I was curious to explore the possibilities of using my iPad Pro for 3D modeling. After some research, I decided to use <a href="https://www.shapr3d.com/">Shapr3D</a> for 3D modeling and <a href="https://procreate.com/">Procreate</a> for 3D painting. In this article, I will share my experience and challenges encountered while using these apps, and provide some recommendations for other non-professional 3D artists who may be interested in using their iPad Pro 12.9 (6th generation) for 3D modeling.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7GV2E3VnNTA_yGhiFeULOg.png" /><figcaption>Sharp3D</figcaption></figure><p>Shapr3D is a powerful 3D modeling app that is easy to use, even for non-professionals. It offers an intuitive interface and a variety of tools that allow users to create complex 3D models with ease. I found it to be a great app for quickly creating simple 3D models, such as geometric shapes, furniture, and household items. The app also allows users to export their models in various formats, making it easy to use them in other applications.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/540/1*GjGJy9d5aycsUGdhX2PYFg.gif" /></figure><p>Procreate, on the other hand, is a popular app for digital painting and drawing. While it is not specifically designed for 3D painting, it offers some great features that can be used for this purpose. One of the advantages of Procreate is its wide range of brushes and tools that can be used to create unique textures and effects. This makes it a great app for painting 3D models and adding a personal touch to them.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*i2b8uIOmZKMPWzeuKUx5ZQ.gif" /></figure><p>However, during my experimentation with Shapr3D and Procreate, I encountered a major challenge — a bad topology of the models created in Shapr3D. Bad topology refers to the way in which the vertices and edges of a 3D model are arranged, which can affect the model’s appearance and usability. Unfortunately, I found that the topology of the models created in Shapr3D was not suitable for use in Procreate, as it made it difficult to paint the models accurately.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/360/1*7_bOFIf9PxL7kRrm6qfPVQ.gif" /></figure><p>Despite this challenge, there are still some recommendations that I would like to share for non-professional 3D artists who are interested in using their iPad Pro for 3D modeling:</p><ul><li>Consider using other 3D modeling apps: While Shapr3D is a great app for beginners, there are many other 3D modeling apps that may offer better topology for 3D painting. Some popular alternatives include <a href="https://www.blender.org/">Blender</a>, <a href="https://www.sketchup.com/">SketchUp</a>, and <a href="https://www.autodesk.com/products/fusion-360/">Autodesk Fusion 360</a>.</li><li>Use Procreate for texturing and effects: While Procreate may not be the best app for 3D painting, it is still a great tool for adding textures and effects to 3D models. Consider exporting your 3D models to Procreate after creating them in another app, such as Blender or SketchUp.</li><li>Keep experimenting: Don’t be discouraged by the challenges you may encounter while using your iPad Pro for 3D modeling. Keep experimenting with different apps and tools, and don’t be afraid to try new things. With time and practice, you will develop your skills and find the right tools for your needs.</li></ul><p>In conclusion, as a professional software developer, I have found that using an iPad Pro as an extension to my work desk for drawing, painting, and 3D modeling can be a great way to explore new creative outlets. While there are some challenges when it comes to using the iPad Pro for 3D modeling, there are still many great apps and tools available that can help you create amazing 3D models. By focusing on finding the best workflow for your needs, you can make the most out of your iPad Pro and use it as a complementary tool to your MacBook Pro. So, keep experimenting and see how the iPad Pro can enhance your creativity and productivity in new and exciting ways!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9ee583a30f89" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>