<?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 Ece Sefercioğlu on Medium]]></title>
        <description><![CDATA[Stories by Ece Sefercioğlu on Medium]]></description>
        <link>https://medium.com/@Scriptie?source=rss-f0551a5329cd------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/2*rqhbxn2IjeyoRMkEFLT9lQ.jpeg</url>
            <title>Stories by Ece Sefercioğlu on Medium</title>
            <link>https://medium.com/@Scriptie?source=rss-f0551a5329cd------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 21:34:18 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@Scriptie/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[7 Tools in 7 Days — Day 3: Brick Wall Generator]]></title>
            <link>https://medium.com/@Scriptie/7-tools-in-7-days-day-3-brick-wall-generator-1499adde63ba?source=rss-f0551a5329cd------2</link>
            <guid isPermaLink="false">https://medium.com/p/1499adde63ba</guid>
            <category><![CDATA[xcode]]></category>
            <category><![CDATA[game-development]]></category>
            <category><![CDATA[unity3d]]></category>
            <category><![CDATA[unity-tool]]></category>
            <dc:creator><![CDATA[Ece Sefercioğlu]]></dc:creator>
            <pubDate>Sat, 03 Oct 2026 17:46:24 GMT</pubDate>
            <atom:updated>2026-10-20T10:21:01.592Z</atom:updated>
            <content:encoded><![CDATA[<h4>Building a wall brick by brick sounds fun until you have to do it again. A little procedural generation makes smashing things much easier.</h4><p>Fitness Crossing has a bunch of different exercise mechanics, and at some point I wanted to add a new one: <strong>Smash</strong>.</p><p>The idea was pretty simple. The player gets a <strong>SMASH</strong> prompt, imitates a punching motion, and on screen it looks like they just punched through a brick wall. The bricks get a force applied to them and go flying.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Cty1WxcnNsDWcTJQ7b9HWA.gif" /></figure><p>Which meant I first needed… a brick wall.</p><p>More specifically, I needed a wall made out of individual objects. If the bricks were going to react to physics and fly around separately, they actually had to <em>be</em> separate.</p><p>I could create a bunch of cubes, scale them, position them one by one, and build the wall manually.</p><p>Or I could have a tool do the math for me.</p><p>So I asked Codex for a Brick Wall Generator.</p><h3>Apparently, I Have a Tendency</h3><p>About six years ago, I had a question: could I take a single cube and divide it into smaller cubes using its transform?</p><p>So I sat down, worked out the math, and implemented the algorithm in C#. Later, I turned it into a tutorial for Devsplorer, my Unity tutorial channel at the time, and shared it on Reddit.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/739/1*zz1UvrzOOspoXENu_Udv9g.gif" /></figure><p>The Reddit post got a bigger reception than I expected, which honestly made me pretty excited at the time. Looking at it now, I think it’s kind of cute. 😄</p><p>And apparently, there is another tendency here too. I make something because I am curious or because I need it, and then at some point I want to send it out into the world. Partly to show what I am working on, but also because maybe it can inform someone, inspire an idea, or just show another possibility of what they can do with the software they are already using.</p><p>I didn’t go back to that old code when I needed the Brick Wall Generator, and the implementations aren’t the same either. But I already knew I enjoyed this kind of problem: take a larger space, figure out how to divide it into smaller pieces, and let the math handle the placement.</p><p>I think part of why I enjoy it is my computer engineering side showing up in game development. There is a visual result at the end, but there is also an algorithm I can sit down, deconstruct, calculate, and implement.</p><h3>This Time, I Didn’t Need the Old Code</h3><p>I asked Codex for a Brick Wall Generator, made a few tweaks along the way — things like gaps between the bricks and shifting alternate rows — and that was pretty much enough for what I needed.</p><p>The tool generated the wall in the Unity Editor, giving me the individual bricks I needed for the Smash mechanic. From there, I could move on to the next problem: making those bricks actually fly when the player punched the wall.</p><h3>The Tool</h3><p>The Brick Wall Generator is still a pretty simple tool at its core.</p><p>You give it a Bounds Object to define the space you want to fill, choose your rows and columns, adjust the gaps and row shifting, and generate the wall.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WdFQHwROQrJfdMtS90Po9w.gif" /></figure><p>The result is a wall made out of individual cube GameObjects rather than one combined mesh. You can add colliders, use a material override, change how much alternate rows are shifted, or turn the shifting off completely.</p><p>And while the tool generates cubes, you don’t necessarily have to keep them as cubes. You can swap the generated meshes for spheres, capsules, or your own meshes, or even use the generated transforms as spawn points for something else.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZoejNNe8Q6ggQ_tb1JLuPQ.gif" /></figure><p>Because the output is just regular GameObjects under a generated parent, you can take it from there and do whatever your project needs with it.</p><p>You can find the tool here: <a href="https://github.com/seferciogluecce/brick-wall-generator">Brick Wall Generator on GitHub</a></p><h3>I Only Wanted to Open-Source a Small Tool</h3><p>When I came back to this tool for 7 Tools in 7 Days, the local version was already doing its job. I wasn’t expecting to redesign the whole thing. I mostly wanted to clean it up, make it understandable for someone other than me, and put it on GitHub.</p><p>Then we started making product decisions.</p><p>Should the Bounds Object be assigned explicitly? Should colliders be optional? What should happen after generation? What should the defaults be? How should invalid gaps behave? What about scaled parents? Negative scale? Prefab Mode? Undo?</p><p>And the questions just… kept coming.</p><p>By the end, the breakdown looked like this:</p><ul><li><strong>10 product decisions</strong> <em>(initial concerns from the Codex audit)</em></li><li><strong>14 naming and UI decisions</strong></li><li><strong>75 defaults and validation decisions</strong></li></ul><p><strong>99 decisions.</strong></p><p>I genuinely still laugh when I look at that number, especially because this is a tool that takes a volume and fills it with cubes. 😭</p><h3>The Questions Weren’t Useless. They Just Didn’t Stop.</h3><p>To be fair, I was okay with those questions.</p><p>A lot of them were things I simply wouldn’t think much about for a tool only I was using. I know how I use my own tools. I am probably not going to enter a gap so large that there is no space left to generate a brick, and if I do break something, I usually have a pretty good idea of what I just did.</p><p>Someone else doesn’t have that context.</p><p>For example, we capped the tool at 64 rows and 64 columns. My first reaction was basically, why limit it? Then you realize that 64 × 64 is already <strong>4,096 individual GameObjects</strong>. For a brick wall generator, that is probably enough of a guardrail for now. If I ever genuinely need more, I can change it.</p><p>The gap validation was another one. If the gaps become too large for the selected bounds, the tool now tells you why it can’t generate the wall instead of just failing or producing something strange. It makes sense to warn someone in case they accidentally set the values to something that can’t actually produce a wall.</p><p>That is one thing I really like about using AI this way. It can surface edge cases I missed, but also things I might have noticed and simply wouldn’t have cared about in a local tool.</p><p>The strange part was realizing that there wasn’t a natural stopping point. Every question led to another perfectly reasonable question.</p><p>Eventually, I asked how many decisions we had left, mostly because I wanted to see the end of the road.</p><p>It stopped shortly after. I think it may have interpreted that as me getting frustrated, which wasn’t actually why I asked. It wasn’t entirely wrong, though.</p><p>And somehow, the final count was <strong>99</strong>. I definitely wasn’t expecting that when we started.</p><h3>And Somehow, It Is Still Basically My Brick Wall Tool</h3><p>The funny thing is, after all those decisions, the way I actually use the tool hasn’t changed that much.</p><p>I still give it a volume, decide how I want the bricks arranged, and generate a wall.</p><p>The public version is definitely cleaner. The UI is easier to understand, there is better feedback when something is wrong, and we actually defined and tested a lot of behavior that I never needed to think about when I was the only person using it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1002/1*rVTkRwHsx1x6T8-wLrQ2PA.png" /></figure><p>I am not going to pretend the UI of these little tools is suddenly top-notch. It isn’t. But compared to the version I made just for myself, I think it is much easier to pick up and understand.</p><p>And I think that is enough.</p><p>The goal wasn’t to turn a small editor utility into a huge polished product. It was to take something that worked for me and get it into a state where I felt comfortable letting other people use it too.</p><h3>Maybe Bricks. Maybe Hexagons Someday.</h3><p>The most obvious use for this tool is, well, a brick wall.</p><p>Maybe you need individual bricks because the wall has to break apart, like I did. Maybe you need them for a different effect, or you simply need to fill a certain space with repeated objects.</p><p>But I also like sharing tools like this because the implementation itself can be an idea.</p><p>I divided a volume into cubes. Someone else might look at it and think, <em>could I do the same thing with hexagons? </em>That someone might also be me at some point. I just haven’t needed the hexagons yet.</p><p>Or someone could just replace the cubes with something completely different and take it somewhere I never intended to.</p><p>Sometimes that is enough reason for me to put something out there: you can use my implementation if it solves your problem, or maybe it just shows you another thing you can do with the tools you already have.</p><h3>What’s next</h3><p>Brick Wall Generator is Day 3 of <strong>7 Tools in 7 Days</strong>.</p><p>Over the next four days, I’ll be open-sourcing:</p><p><strong>Day 1 — Parent From Bounds</strong><br><strong>Day 2 — Separate Mesh Bodies</strong><br><strong>Day 3 — Brick Wall Generator</strong><br><strong>Day 4 — Particle System Context Previewer</strong><br><strong>Day 5 — Object Layout Tool</strong><br><strong>Day 6 — DOTween Selection Animation Previewer</strong><br><strong>Day 7 — Wave Object Distributor</strong></p><p>Some came from mechanics I needed to implement. Others were simply small workflow problems I wanted to solve.</p><p>I’ll be sharing one each day, along with the real problem that made me build it and what happened when I turned it from a local utility into something other people could use.</p><p><strong>Four more tools to go. If you’d like to follow along, the next one is coming soon.</strong></p><p><em>Originally published at </em><a href="https://ecesefercioglu.substack.com/p/7-tools-in-7-days-day-3-brick-wall"><em>https://ecesefercioglu.substack.com</em></a><em> on October 3, 2026.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1499adde63ba" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[7 Tools in 7 Days — Day 2: Separate Mesh Bodies]]></title>
            <link>https://medium.com/@Scriptie/7-tools-in-7-days-day-2-separate-mesh-bodies-78145ee6ddb6?source=rss-f0551a5329cd------2</link>
            <guid isPermaLink="false">https://medium.com/p/78145ee6ddb6</guid>
            <category><![CDATA[game-development]]></category>
            <category><![CDATA[unity]]></category>
            <category><![CDATA[unity-tool]]></category>
            <category><![CDATA[meshy-ai]]></category>
            <category><![CDATA[xcode]]></category>
            <dc:creator><![CDATA[Ece Sefercioğlu]]></dc:creator>
            <pubDate>Fri, 02 Oct 2026 14:09:15 GMT</pubDate>
            <atom:updated>2026-10-18T20:53:49.493Z</atom:updated>
            <content:encoded><![CDATA[<h4>Generating multiple objects together is convenient. Working with them as one mesh? Not so much. As it happens, they work better apart.</h4><p>While working on Fitness Crossing, I was using AI-generated 3D models for many of the objects and obstacles I needed. I wanted variation, but I also wanted the workflow to be practical. Generating every small variation separately meant more generations, more credits, more downloading and importing, and more back and forth than I really wanted.</p><p>Generating the variations as images was much easier. Instead of asking for them one by one, I could ask the image model to generate several variations together as a sprite sheet.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*47krk-lievnRqhri4FxfXg.png" /></figure><p>That made me wonder if I could do the same thing one step later.</p><p>Instead of generating and sending each variation as a separate image, what if I asked the image model to generate all of them together as a sprite sheet and gave that single image to Meshy? If I could get one 3D model containing several separate objects, maybe I could separate them again afterward in Unity.</p><p>I wasn’t completely sure how well it would work, but I was pretty sure the separation itself should be possible.</p><p>So I tried it.</p><h3>A 3D Model Is Also Data</h3><p>I am a game developer, not a graphics programmer or a 3D artist, but I had taken courses in both 3D modeling and computer graphics. So I was familiar enough with the basics of how a mesh is represented: vertices, faces, edges, and the connections between them.</p><p>That was why I thought separating the objects should be possible in the first place. Even if Unity imported the result as one mesh, the separate objects inside it were still made of geometry that could be inspected and processed programmatically.</p><p>If the objects were not actually connected to each other, there should be a way to figure out which parts belonged together and split them back into separate meshes.</p><p>I knew it should be possible. I also knew I was definitely not going to stop and write the mesh-processing code myself. I am not a graphics programmer, and for what was basically an experiment in my asset workflow, that was a little more implementation than I wanted to take on myself.</p><p>So I asked Codex.</p><h3>The Sprite Sheet Hack</h3><p>The experiment was pretty simple. I asked the image model to generate several variations together as a sprite sheet, then used that single image for one Meshy Image-to-3D generation.</p><p>And it worked. I got one 3D model containing multiple visually separate objects.</p><p>Of course, that was only useful if I could separate those objects again. That was where Separate Mesh Bodies came in. The tool could look at the geometry, find the disconnected bodies, and turn them into separate mesh assets and GameObjects in Unity.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JmkWMz6tX9sLtWPLOrE_3g.gif" /></figure><p>So instead of:</p><p><strong>5 separate images → 5 Image-to-3D generations → 5 models</strong></p><p>I could, when the objects were suitable for this workflow, do something closer to:</p><p><strong>1 sprite sheet → 1 Image-to-3D generation → 1 combined model → 5 separated objects in Unity</strong></p><p>In a five-object example, that means one generation task instead of five. That meant I was saving credits and time, while also getting more usable objects out of a single successful generation.</p><p>Meshy also has Batch Images to 3D, which is useful when you want to process multiple images together as a batch. But each image still produces its own 3D model and costs credits separately. What I was trying here was slightly different: put several simple objects into the same input image, let them arrive together in one model, and separate them myself afterward.</p><p>A little bit like hacking my Meshy workflow, I guess.</p><p>Not every object is going to be a good fit for this, and I wouldn’t present it as the correct way to use Image-to-3D. It was simply useful for the kinds of variations and simple asset sets I was making.</p><p>And since I have mentioned Meshy this many times already, here is <a href="https://www.meshy.ai/?utm_source=meshy&amp;utm_medium=referral-program&amp;utm_content=6A4JHX&amp;share_type=invite-friends">my referral link</a> if you want to try it yourself. This is not sponsored. I just apparently have a referral link now.</p><h3>Variations and Sets</h3><p>I mainly used this workflow in two ways: variations and sets.</p><p>For variations, I could generate several versions of the same type of object together. The spikes are a good example. I wanted different versions that I could place around the scene instead of generating each one separately. I could get them together in one model, separate them in Unity, and then use each result independently.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/854/1*KzmPxMrHokt0J2e3zDN1YQ.gif" /></figure><p>But sometimes the objects did not need to be variations of the same thing.</p><p>The door set is a good example of that. Some objects make sense to design and generate together because they belong to the same visual set, but that does not mean I want them to stay together once they are inside Unity. I might want to move them separately, reuse only one piece, or simply have them as individual GameObjects.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2z7nQaKvf_yb-mV0wBv8iQ.gif" /></figure><p>So the workflow ended up being useful for both cases: generating more variations and generating related objects together.</p><p>That was really what I needed from the tool. I could group things together when that made the generation workflow more practical, without being stuck with that grouping afterward.</p><h3>Building the First Version with Codex</h3><p>I went back to my original development conversation while preparing this article, and my first request was actually quite specific.</p><p>I asked for a Unity Editor tool that could:</p><ul><li>decompose meshes containing separate bodies,</li><li>create new mesh assets for those bodies,</li><li>create corresponding scene objects,</li><li>save them under a separated-mesh output folder,</li><li>center each new pivot on its body’s bounding box,</li><li>preserve the object’s visible scene sizing,</li><li>optionally use a custom base name,</li><li>and number the resulting objects automatically.</li></ul><p>Then I added one clarification:</p><p><strong>The pivot needed to be in the middle of the object’s bounding box.</strong></p><p>Codex gave me a working first version within minutes.</p><p>During that first implementation, it chose a connected-triangle approach, handled transformed geometry, preserved submesh and material assignments where possible, added warnings for unreadable meshes, and handled the naming and generated scene hierarchy.</p><p>The important part for me was that AI did not come up with the workflow or the idea for the tool. I knew what I wanted to test, and I already thought the separation should be possible. I just did not want to stop what I was working on and implement the mesh-processing side myself.</p><p>A few days later, I came back with another adjustment for the pivots. Other than that, from the development history, it looks like I just started using the tool.</p><p>Which makes sense. I was not trying to build a general mesh-processing product at the time. I had a workflow problem, I had an idea for solving it, and now I had a tool that let me use that idea.</p><h3>From a Local Utility to a Public Tool</h3><p>When I came back to Separate Mesh Bodies for 7 Tools in 7 Days, the tool was already useful to me. But using something locally and putting it on GitHub for other people are two different things.</p><p>When I am the only person using a tool, I know its assumptions. If something needs Read/Write enabled, I can go enable it. If a warning appears in the Console, I know where to look. Some rough edges can stay rough because I already know how to work around them.</p><p>Once I decided to open-source it, I wanted to give those details a bit more attention.</p><p>Read/Write was a good example. The original tool warned when Unity could not access the mesh data. That technically did the job, but it still left the user to notice the warning, find the import setting, enable it, and come back.</p><p>In the public version, the tool detects that state before separation and shows an <strong>Enable Read/Write</strong> button when it can handle the importer directly. It is not a huge feature, but I am quite happy we added it. If the tool already knows what is preventing the next step, giving the user the action right there feels much more practical.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uLCnPLVkGpwABKAJCr31FA.png" /></figure><p>I also ended up catching one more thing almost at the end of the release process.</p><p>The generated mesh parts were correct, but their parent GameObject was sitting at the world origin. Again, technically usable, but not particularly convenient. I would rather have the parent somewhere meaningful if I want to move or manipulate the separated set afterward.</p><p>So I changed it to position the parent at the min/max center of the generated part transforms while preserving the children’s world-space positions.</p><p>There were other decisions around validation, Undo, output organization, naming, position tolerance, and what the public scope of the tool should actually be. None of them changed the original reason I built Separate Mesh Bodies. They were mostly about making the tool easier to understand and safer to hand to someone who did not build it with me.</p><p>I still would not call this the “finished forever” version. I could probably keep finding things to add or improve indefinitely.</p><p>At some point, though, I think a useful tool needs to be in a good enough condition to share. That was the goal here.</p><h3>AI-Assisted Development: Local vs. Shipping</h3><p>Working on the open-source version also made me think about the difference between using AI for something local and using it for something I am going to share.</p><p>For a quick experiment or a tool that only affects my own workflow, I think it is fine to be a little hacky. The affected pool is small. I know what I asked for, I can test whether it works for my case, and sometimes that is genuinely enough.</p><p>Shipping something for other people is different.</p><p>For this release, I found it much more useful to ask AI to analyze the implementation, surface edge cases, and report things I might have missed. Then I could look at those findings, make the product decisions myself, and test the result in Unity.</p><p>That distinction is important to me. I do not really want the workflow to be:</p><p><strong>“You decide everything. Let me know when it is ready to ship.”</strong></p><p>I would rather have something closer to:</p><p><strong>“Show me what I might be missing, then let’s decide together.”</strong></p><p>AI is very useful for finding cases I may not immediately think about, tracing what the code actually does, implementing changes, and helping with automated validation. But I still want to use the tool myself and decide whether the behavior actually makes sense.</p><p>Separate Mesh Bodies was a nice example of both sides of that workflow. The first local version came together very quickly and was useful without a huge product process around it. The public version needed more analysis, decisions, validation, and manual testing before I was comfortable sharing it.</p><p>I think both approaches are valid. They just solve different problems.</p><h3>Why I Open-Sourced It</h3><p>I think this tool also came from the particular mix of things I happen to know.</p><p>I am a game developer, but I had enough exposure to 3D modeling and computer graphics to look at a generated model and think about the geometry behind it. At the same time, I approached the problem as an engineer. If the objects were separate in the geometry, I should be able to identify that separation and split them programmatically too.</p><p>There are definitely people who know much more about 3D modeling and computer graphics than I do, and they may look at the same workflow and see completely different possibilities. That is part of why I wanted to share this one.</p><p>I am also not sure how common this exact use case is. <a href="https://ecesefercioglu.substack.com/p/7-tools-in-7-days-day-1-parent-from">Parent From Bounds</a>, the first tool in this series, solves a pretty straightforward Unity workflow problem. This one feels a little more unusual, especially because workflows around image-to-3D generation are still relatively new.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/854/1*w8n9oyqQHeLPz_tnIuJPpg.gif" /></figure><p>Maybe someone wants to generate several placeholder variations before deciding which one belongs in the final game. Maybe they are generating a small set of related props. Maybe they are trying to make better use of the credits in whatever AI modeling tool they use. Or maybe they simply imported a mesh with disconnected bodies and want them as separate assets.</p><p>They can use the tool as it is, change it for their own workflow, or just take the idea that generated 3D assets do not have to be the end of the pipeline. They are still data, and we can process them afterward.</p><p>That is really what I want from sharing these tools. I want to make the work I am doing and the way I approach problems more visible, but I also hope something I built for myself can be useful to someone else, even if they end up using it in a completely different way.</p><h3>Separate Mesh Bodies</h3><p>The final open-source version of <strong>Separate Mesh Bodies</strong> takes a selected GameObject with a MeshFilter, finds the disconnected geometry inside the mesh, and creates separate mesh assets and scene objects from those bodies.</p><p>Each generated body gets its own bounds-centered pivot, and the tool includes options for pivot orientation, position tolerance, output organization, scene parenting, and optional MeshColliders. It also preserves the source material assignments on the generated scene objects.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cJm1XCCZn-FcekeQiQZ3AQ.gif" /></figure><p>This is still the same tool I originally needed for my asset-generation workflow, just in a state I am much more comfortable sharing with someone else.</p><p>If you have a similar workflow, an imported model with disconnected bodies, or simply want to take it apart and adapt it for something else, the source is available here:</p><p><a href="https://github.com/seferciogluecce/separate-mesh-bodies"><strong>Separate Mesh Bodies on GitHub</strong></a></p><p>It is open source under the MIT License.</p><h3>What’s next</h3><p>Separate Mesh Bodies is Day 2 of <strong>7 Tools in 7 Days</strong>.</p><p>Over the next five days, I’ll be open-sourcing:</p><p><strong>Day 1 — Parent From Bounds</strong><br><strong>Day 2 — Separate Mesh Bodies</strong><br><strong>Day 3 — Brick Wall Generator</strong><br><strong>Day 4 — Particle System Context Previewer</strong><br><strong>Day 5 — Object Layout Tool</strong><br><strong>Day 6 — DOTween Selection Animation Previewer</strong><br><strong>Day 7 — Wave Object Distributor</strong></p><p>Some are tiny workflow fixes. Some became considerably more involved.</p><p>I’ll be sharing one each day, along with the real problem that made me build it and what happened when I turned it from a local utility into something other people could use.</p><p><strong>Five more tools to go. If you’d like to follow along, the next one is coming soon.</strong></p><p><em>Originally published at </em><a href="https://ecesefercioglu.substack.com/p/7-tools-in-7-days-day-2-separate"><em>https://ecesefercioglu.substack.com</em></a><em> on October 2, 2026.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=78145ee6ddb6" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[7 Tools in 7 Days — Day 1: Parent From Bounds]]></title>
            <link>https://medium.com/@Scriptie/7-tools-in-7-days-day-1-parent-from-bounds-861b8ef19b62?source=rss-f0551a5329cd------2</link>
            <guid isPermaLink="false">https://medium.com/p/861b8ef19b62</guid>
            <category><![CDATA[devlog]]></category>
            <category><![CDATA[unity-game-development]]></category>
            <category><![CDATA[game-development]]></category>
            <category><![CDATA[unity3d]]></category>
            <dc:creator><![CDATA[Ece Sefercioğlu]]></dc:creator>
            <pubDate>Thu, 01 Oct 2026 17:52:07 GMT</pubDate>
            <atom:updated>2026-10-18T20:56:53.528Z</atom:updated>
            <content:encoded><![CDATA[<h4>Sometimes, the tools that save us the most time aren’t complicated. They just remove a small annoyance that keeps showing up.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/568/0*2MXPMM7nf6JHch7t.gif" /></figure><p>Over the past few months, I have been developing <strong>Fitness Crossing</strong>, my solo Unity project. Along the way, I started accumulating small editor utilities that solved problems in my day-to-day workflow.</p><p>Most of them were never meant to become products.</p><p>I had a problem. I described what I needed to a coding agent. I got a small utility that solved it. Then I went back to developing the game.</p><p><strong>Parent From Bounds</strong> started exactly like that.</p><h3>The problem: I needed better control over my transforms</h3><p>I work with models from different sources. Some are models I generate, some come from external assets, and I don’t always have control over how their transforms are set up.</p><p>Pivot placement is one recurring problem.</p><p>Sometimes I expect a pivot at the bottom of an object and find it somewhere around the center. Sometimes the location is simply not useful for what I am trying to do. Even objects that belong together can come with pivot placements that aren’t consistent with the way I want to place them.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WV0Z-nHkuXRr6Ehb_y22og.gif" /></figure><p>Before making a tool for this, I had a workaround when a pivot bothered me enough. Effective? Yes. Recommended? Not really.</p><p>I would create an empty child, move it out of the object, make the original object a child of that empty GameObject, rename things, reposition things…</p><p>Basically, I was hacking together the hierarchy I wanted.</p><p>And if the pivot wasn’t annoying enough to justify doing all of that?</p><p>I accepted my fate and worked with the pivot I had.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*1-srzQMny4eVbNQxptc-8A.gif" /></figure><p>But pivot placement wasn’t the only reason I found a parent useful.</p><p>Models can also arrive with scale and rotation values that make perfect sense for the model itself but aren’t necessarily the values I want to work with later.</p><p>Adding a parent gives me another transform layer to work from. The model can keep its existing transform while I get a parent starting from a clean scale of (1, 1, 1).</p><p>That becomes much more convenient when I want to scale or rotate the whole object later, or when I’m working with animations and tweens. Instead of constantly reasoning around whatever scale the original model happens to have, I can manipulate the parent from a clean baseline.</p><p>So I really wanted two things:</p><p>A <strong>meaningful position</strong> for the parent, independent of whether the original pivot happened to be useful.</p><p>And a <strong>clean transform layer</strong> I could use for later manipulation.</p><p>This became especially useful while working on Fitness Crossing. I place obstacles across three lanes, and having a meaningful bottom reference makes placement and checking transform values much easier.</p><p>I didn’t want to keep fixing incoming models or rebuilding hierarchies manually just to get there.</p><h3>So I asked a coding agent for one</h3><p>The first version was not a grand engineering project.</p><p>I explained what I wanted, and a coding agent generated a small Unity Editor utility for me.</p><p>That was basically it.</p><p>It wasn’t always correct on the first try. At one point I wanted the operation available from the hierarchy context and got something closer to a toolbar/dropdown workflow instead. There was still the usual back and forth of: <em>No, not there. I want it here.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/568/1*28-f3-N_cdSFfl1FG9Tdiw.gif" /></figure><p>As far as I remember, I first asked for the parent to be created at the center.</p><p>Then, while actually using it, I realized that for placement workflows I often wanted the parent at the bottom instead.</p><p>So I asked for that too.</p><p>And that was how I ended up with two little utilities inside Fitness Crossing: one for creating a parent at the center, and another for creating one at the bottom.</p><p>Nothing fancy.</p><p>But I kept using them.</p><h3>From local utilities to a one-week challenge</h3><p>Parent From Bounds wasn’t the only small tool that accumulated while I was building Fitness Crossing.</p><p>The project has also been a place for me to explore <strong>AI-assisted game development</strong> in practice. <a href="https://www.linkedin.com/posts/ece-naz-sefercio%C4%9Flu_we-wrapped-up-our-submission-for-the-tokyo-activity-7505723043277897730-u0R0?utm_source=share&amp;utm_medium=member_desktop&amp;rcm=ACoAABY0hYwBlqYde6RvyZ9ga4DD-_lPJsVVUfg">My experience</a> at the Tokyo AI (TAI) | OpenAI 100-Hour Game Builder Challenge reinforced something I was already starting to notice:</p><p><strong>AI doesn’t always have to be inside the product. It can also improve the workflow around building it.</strong></p><p>There are plenty of things I <em>can</em> code myself but probably wouldn’t stop working on the actual game to build.</p><p>A repetitive editor operation is a good example.</p><p>And writing it myself wasn’t the only alternative.</p><p>For a small workflow problem like this, I could search for an existing script or Asset Store tool, figure out whether it actually behaved the way I needed, decide whether it was something I wanted to bring into my project, and spend time understanding or adapting it.</p><p>Sometimes that absolutely makes sense.</p><p>But for something this small and specific, asking a coding agent to build the behavior I wanted gave me another option.</p><p>If something wasn’t quite right, I could iterate on the implementation around my own workflow instead of adapting my workflow around someone else’s tool.</p><p>The cost of solving some of these small problems became low enough that I could build the utility, use it, and move on.</p><p>After a few months, I realized I had accumulated several tools this way.</p><p>I also wanted to start sharing my game-development work again rather than letting everything I was building live only on my computer. I’ve created educational content before, and I wanted to make sharing part of my work again-both to show what I’m building and, hopefully, to make some of it useful to other developers.</p><p>So I picked seven tools I genuinely use and gave myself a challenge:</p><p><strong>Clean up and open-source one tool every day for seven days.</strong></p><p>Welcome to Day 1.</p><h3>A local script is easy. Sharing it adds friction.</h3><p>Fitness Crossing didn’t need a polished tool called Parent From Bounds.</p><p>I had two scripts. I knew what they did. They worked for me.</p><p>That was enough.</p><p>But if I was going to put them in someone else’s Unity project, even this tiny utility needed a little more thought.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*W-ZHw_We-UhSNyeaFZ0jyw.png" /></figure><p>The two operations needed to become one coherent tool. The local naming needed to make sense to someone who hadn’t been living with it. And behaviors I had never needed to explicitly define-multiple selections, different parents, inactive objects, selections across scenes-suddenly mattered.</p><p>Some of these were things I was intuitively aware of while working on the game. I just hadn’t stopped to think of them as explicit cases.</p><p>Nothing here turned Parent From Bounds into a huge engineering project.</p><p>But even with a tool this small, there was still a gap between:</p><blockquote><strong><em>Works for me.</em></strong></blockquote><p>and</p><blockquote><strong><em>I’m comfortable giving this to someone else.</em></strong></blockquote><p>We cleaned up that gap, tested the result, and the two local scripts became <strong>Parent From Bounds</strong>.</p><h3>What Parent From Bounds does</h3><p>The final tool keeps the original idea intentionally small.</p><p><strong>Create Parent at Center</strong> creates a parent at the center of the selected objects’ combined bounds.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/426/1*uZ5EitDxusoV2rSqejpL1g.gif" /></figure><p><strong>Create Parent at Bottom</strong> creates one at the bottom-center of those bounds.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/568/1*Ce3vF5tiZeOK2LOaTJQu2g.gif" /></figure><p>The selected objects keep their world-space placement.</p><p>For me, that means I can get the reference point I want without changing the model itself, while also gaining a clean parent transform for further placement, scaling, rotation, or animation.</p><p>That’s it.</p><p>It’s a tiny tool because the problem was tiny.</p><p>But I’ve genuinely been using versions of it while building Fitness Crossing, and that’s enough reason for me to share it.</p><p>You can find the source, installation instructions, exact behavior, and limitations here:</p><p><a href="https://github.com/seferciogluecce/parent-from-bounds"><strong>Parent From Bounds — GitHub</strong></a></p><h3>Highlights from Day 1</h3><p>The interesting part for me wasn’t discovering some revolutionary way to parent GameObjects.</p><p>This is absolutely something I could have coded myself. It is also exactly the kind of thing I could have kept postponing because there was always something more important to do in the actual game.</p><p>A coding agent made solving that small problem cheap enough that I actually solved it.</p><p>Then I used the result.</p><p>And eventually, I realized that something doesn’t have to be a huge or particularly novel tool to be worth sharing. If it removes a little friction from my workflow, there is a chance it can remove that friction from someone else’s too.</p><p>And if someone sees Parent From Bounds and thinks, <em>I need that</em>, great.</p><p>If they see it and instead think, <em>Wait, I could ask my coding agent to make something like this specifically for my workflow</em>, that’s great too.</p><h3>What’s next</h3><p>Parent From Bounds is Day 1 of <strong>7 Tools in 7 Days</strong>.</p><p>Over the next six days, I’ll be open-sourcing:</p><p><strong>Day 1 — Parent From Bounds</strong><br><strong>Day 2 — Separate Mesh Bodies</strong><br><strong>Day 3 — Brick Wall Generator</strong><br><strong>Day 4 — Particle System Context Previewer</strong><br><strong>Day 5 — Object Layout Tool</strong><br><strong>Day 6 — DOTween Selection Animation Previewer</strong><br><strong>Day 7 — Wave Object Distributor</strong></p><p>Some are tiny workflow fixes. Some became considerably more involved.</p><p>I’ll be sharing one each day, along with the real problem that made me build it and what happened when I turned it from a local utility into something other people could use.</p><p><strong>Six more tools to go. If you’d like to follow along, the next one is coming soon.</strong></p><p><em>Originally published at </em><a href="https://ecesefercioglu.substack.com/p/7-tools-in-7-days-day-1-parent-from"><em>https://ecesefercioglu.substack.com</em></a><em> on October 1, 2026.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=861b8ef19b62" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How To Draw 3D Trajectory in Unity For Physics Shooting Using Velocity or Force Vector]]></title>
            <link>https://medium.com/@Scriptie/how-to-draw-3d-trajectory-in-unity-for-physics-shooting-using-velocity-or-force-vector-2e7c28e75e96?source=rss-f0551a5329cd------2</link>
            <guid isPermaLink="false">https://medium.com/p/2e7c28e75e96</guid>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[unity]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[game-development]]></category>
            <category><![CDATA[physics]]></category>
            <dc:creator><![CDATA[Ece Sefercioğlu]]></dc:creator>
            <pubDate>Sat, 13 Mar 2021 20:07:10 GMT</pubDate>
            <atom:updated>2021-03-13T20:11:23.716Z</atom:updated>
            <content:encoded><![CDATA[<p>If you are shooting a 3d game object using velocity or force vectors you can use motion equations to predict the trajectory of the object by your choice of the variable. I had chosen time intervals and calculated the positions of the thrown object by those using the equations on <a href="http://hyperphysics.phy-astr.gsu.edu/hbase/traj.html#tra2">hyperphysics</a>. To draw the trajectory a line renderer used containing the points on the movement path.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/620/1*3R1o5Je0kVvMJFDmFFPaNQ.png" /></figure><p>For Drag &amp; Shoot tutorial series I was using force shooting, to predict the trajectory from the force I had used the following steps:</p><ul><li>Transform force to the velocity vector</li><li>Calculate flight duration</li><li>Divide flight duration to step times</li><li>For each step, time passed calculate the position of the object</li><li>Compose the line renderer using the positions</li></ul><p>Details and the script used are explained in the following <a href="https://youtu.be/13KrnisMf14">video </a>on <a href="http://youtube.com/c/Devsplorer">Devsplorer </a>channel</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2F13KrnisMf14%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3D13KrnisMf14&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2F13KrnisMf14%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/ead7b3a67e10b4fc9eae271d09589035/href">https://medium.com/media/ead7b3a67e10b4fc9eae271d09589035/href</a></iframe><p>Using this method of trajectory prediction gave a whole path of the movement with no collision to obstacles. In the <a href="https://youtu.be/9iwdAMXydgo">second part</a> of the trajectory drawing tutorial series, it is explained how to cut the trajectory with collision or percentage.</p><p>Hopefully, this will be helpful for your games! <br>If there was a point not clear please let me know.<br>See you in the next explorations 🙋</p><p><em>Originally published at </em><a href="https://devsplorer.wordpress.com/2021/03/13/how-to-draw-3d-trajectory-in-unity-for-physics-shooting-using-velocity-or-force-vector/"><em>http://devsplorer.wordpress.com</em></a><em> on March 13, 2021.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2e7c28e75e96" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Angular Velocity Of RigidBody In The Direction Of Movement | A Unity Tutorial]]></title>
            <link>https://medium.com/@Scriptie/angular-velocity-of-rigidbody-in-the-direction-of-movement-a-unity-tutorial-4df291a94e0b?source=rss-f0551a5329cd------2</link>
            <guid isPermaLink="false">https://medium.com/p/4df291a94e0b</guid>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[physics]]></category>
            <category><![CDATA[game-development]]></category>
            <category><![CDATA[unity]]></category>
            <dc:creator><![CDATA[Ece Sefercioğlu]]></dc:creator>
            <pubDate>Sat, 09 Jan 2021 10:47:12 GMT</pubDate>
            <atom:updated>2021-01-09T10:52:38.862Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/496/0*5shkpstFLSWhLUWy" /></figure><p>We can shoot game objects in Unity, but if we don’t give them spin the movement does not look very realistic. To make it look realistic, if the object has rigidbody, we can give it an angular velocity in the direction of the movement and watch it rotating towards its course.</p><p>I have created a <a href="https://youtu.be/m5oi5eNZ4Wc">video tutorial</a> on this on <a href="https://youtube.com/c/Devsplorer">Devsplorer </a>YouTube channel</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2Fm5oi5eNZ4Wc%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3Dm5oi5eNZ4Wc&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2Fm5oi5eNZ4Wc%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/15154abcb65fb4ebd5f45353779b2ca2/href">https://medium.com/media/15154abcb65fb4ebd5f45353779b2ca2/href</a></iframe><p>While calculating the angular velocity takes one line of code, as always with development understanding why we are doing what we are could take more time.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/872/0*bmKsg_4UmUW0If4B" /></figure><p>Angular velocity vector is not parallel to the direction vector but perpendicular to it. <br>Here in the above image, the direction of the white cylinders for the balls points at the position of the game object that is on the target. But their angular velocity vector that we should use so that they will rotate towards the movement direction, the target is represented with the black cylinders.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/720/0*nuuhDewm1c60DCUp" /><figcaption>Objects rotating with world space unit vectors as angular velocity vector</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/871/0*T3LTchvBqlPHmQhE" /></figure><p>To calculate the direction of the angular velocity vector so that the object rotates towards the movement direction, in the case of the above image towards the target position, we apply cross product to two vectors that connect the selected game object.</p><p>The cylinder connected to the sphere on the ground represents the object’s positional vector. The sphere actually is at 0,0,0 position. The other cylinder connected to the selected object is the direction vector that the object will pass through when it starts moving.</p><p>When we use these vectors for cross product, we find the direction representing angular velocity and can apply it to our game object.</p><p>For details, you can check out the <a href="https://youtu.be/m5oi5eNZ4Wc">video </a>above 👆</p><p>Hopefully, this will be helpful for your projects. <br>If there was a point not clear please let me know.<br>See you in the next explorations 🙋</p><p><strong>🌟 Sources That Contributed To This Implementation</strong></p><p>⭐ HyperPhysics — Rotation Vectors <br>http://hyperphysics.phy-astr.gsu.edu/hbase/rotv.html#rvec1 <br>⭐ Unity Docs — Cross Product https://docs.unity3d.com/ScriptReference/Vector3.Cross.html <br>⭐ Wikipedia — Angular Velocity <br>https://en.wikipedia.org/wiki/Angular_velocity</p><p>👉 Wonderful Assets from KayKit — Mini-Game Variety Pack: <br>https://kaylousberg.itch.io/kay-kit-mini-game-variety-pack <br>👉 Changing Cursor Texture With Mouse Press: <br>https://youtu.be/jis0Lq1FLD8 <br>👉 Similar Shooting Series: <br>https://youtube.com/playlist?list=PLGXzgnKhu_mCTmg_AS66j8U7duSzcsub7 <br>👉 Cylinder Scaling Tutorial <br>https://youtu.be/s6qhqm3ec28 <br>👉 Previous Video On Target Shooting <br>https://youtu.be/qA7WbcJmhUM</p><p><em>Originally published at </em><a href="https://devsplorer.wordpress.com/2021/01/09/angular-velocity-of-rigidbody-in-the-direction-of-movement-a-unity-tutorial/"><em>http://devsplorer.wordpress.com</em></a><em> on January 9, 2021.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4df291a94e0b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A Fix For Unity 2020 Crashes With SteamVR Entering Play Mode]]></title>
            <link>https://medium.com/@Scriptie/a-fix-for-unity-2020-crashes-with-steamvr-entering-play-mode-3b67dcf1f968?source=rss-f0551a5329cd------2</link>
            <guid isPermaLink="false">https://medium.com/p/3b67dcf1f968</guid>
            <category><![CDATA[game-development]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[vr]]></category>
            <category><![CDATA[steamvr]]></category>
            <category><![CDATA[programming]]></category>
            <dc:creator><![CDATA[Ece Sefercioğlu]]></dc:creator>
            <pubDate>Mon, 14 Dec 2020 04:32:45 GMT</pubDate>
            <atom:updated>2020-12-14T17:31:21.194Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/545/0*UKmIgFF-qOw7pT5B" /></figure><p>If you are also experiencing Unity 2020 crash/close when trying to make it work with SteamVR like me, the solutions could be here.</p><h4><strong>First Short Solution:</strong></h4><p>Upgrade your Unity version to Unity 2020.1.17 or the latest release, you are prompted to create actions file and everything works very well 🙂</p><h4><strong>Longer Path, Try to solve it with current version:</strong></h4><p>I was trying to make SteamVR work with <strong>Unity 2020.1.6</strong>. With no error, when I press play, the editor closes down with no error message. This wasn’t helpful to solve the case so cue Google search, “unity closes when I hiit play”, (yes with the typo).</p><p>This <a href="https://stackoverflow.com/a/27228334">answer </a>on StackOverflow lead me to <a href="https://docs.unity3d.com/Manual/LogFiles.html">LogFiles </a>page on Unity Docs. As it was stated in the answer I went and looked at Editor logs from <em>“C:\Users\username\AppData\Local\Unity\Editor\Editor.log”</em> path and there at the last line I saw the error;</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*LMAxayFvZX82l1pm" /></figure><p><em>[XR] [OpenVR] [Error] Action manifest file does not exist at path (J:\Work Station\Unity__Fall2020\SteamVR — 2020\Assets\StreamingAssets\SteamVR\actions.json)</em></p><p>In <strong>2019 </strong>version of the editor when we enter play mode with no actions for SteamVR Input, we are prompted and create one and if we opt out in creating one we see an error in the console</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/869/0*rhTqS7PX84QjX6Bu" /><figcaption>In 2019 version of the Unity editor we are prompted to create actions if the file does not exist</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/862/0*uyoqJ-Y6oxEYsdCF" /><figcaption>If we are stubborn to not create one we see this error log in console</figcaption></figure><p>To solve this in <strong>2020.1.6 </strong>we need to follow <em>Window -&gt; SteamVR Input -&gt; Save and generate</em> (Only the screenshot taken in 2020.1.17, for details have a look at first shorter solution)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*KvvRdPaOeGC1TYP5" /><figcaption>Actions to create actions 😀</figcaption></figure><p>Then our project will be good to go 🙂</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/545/0*8YLwTmm2DdG6VtMh" /><figcaption>It works with no closing on us now</figcaption></figure><p>Hopefully, this will be helpful for your problem too. If there was a point not clear please let me know.<br>See you in the next explorations.</p><p>To how to setup SteamVR in Unity 2019 you can have a look at this <a href="https://devsplorer.wordpress.com/2020/07/03/unity-steamvr-setup-2020/">blog post</a> or the <a href="https://youtu.be/7WL19SiZ98g">video </a>that I have created.</p><p><em>Originally published at </em><a href="https://devsplorer.wordpress.com/2020/12/14/a-fix-for-unity-2020-crashes-with-steamvr-entering-play-mode/"><em>http://devsplorer.wordpress.com</em></a><em> on December 14, 2020.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3b67dcf1f968" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How To Create A Custom Command To Group Selection In Unity Editor | Unity Tutorial]]></title>
            <link>https://medium.com/@Scriptie/how-to-create-a-custom-command-to-group-selection-in-unity-editor-unity-tutorial-dc727292a123?source=rss-f0551a5329cd------2</link>
            <guid isPermaLink="false">https://medium.com/p/dc727292a123</guid>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[unity-game-development]]></category>
            <category><![CDATA[game-development]]></category>
            <category><![CDATA[unity]]></category>
            <category><![CDATA[programming]]></category>
            <dc:creator><![CDATA[Ece Sefercioğlu]]></dc:creator>
            <pubDate>Sat, 12 Dec 2020 07:58:41 GMT</pubDate>
            <atom:updated>2020-12-12T08:30:15.692Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/656/0*HiKX6yEbLRaoaySs" /></figure><p>When we are creating lots of independent game objects in unity editor at one point we could think, “They would be better grouped!”. I thought this when I was modelling a ghost in ProBuilder part by part. Then I set out to find a way to create a command that groups selected game objects in Unity.</p><h3></h3><p>A Tutorial on &quot;How To Create A Custom Command To Group Selection In Unity Editor&quot; A quick way to group selected game objects in Unity editor under the same parent which is centered between them.https://t.co/kKkxqXVzMp#madewithunity #gamedev #gamedevelopment pic.twitter.com/td6baJwjuk</p><p>After creating the script, now I think I use it more than 2–3 projects. I really believe it is an helpful add on for the projects. In the below video I explain my approach to create this group selection command in Unity.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FrLd1ohNkUJ0%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DrLd1ohNkUJ0&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FrLd1ohNkUJ0%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/e0a0562f66d5f34c8e3a546c834fb868/href">https://medium.com/media/e0a0562f66d5f34c8e3a546c834fb868/href</a></iframe><p>Hopefully, this will be helpful. If there was a point not clear please let me know.</p><p>See you in next explorations.</p><p><em>Originally published at </em><a href="https://devsplorer.wordpress.com/2020/12/12/how-to-create-a-custom-command-to-group-selection-in-unity-editor-unity-tutorial/"><em>http://devsplorer.wordpress.com</em></a><em> on December 12, 2020.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=dc727292a123" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Unity SteamVR Setup For Unity 2019]]></title>
            <link>https://medium.com/@Scriptie/unity-steamvr-setup-for-unity-2019-9fab77a79ca2?source=rss-f0551a5329cd------2</link>
            <guid isPermaLink="false">https://medium.com/p/9fab77a79ca2</guid>
            <category><![CDATA[virtual-reality]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[steamvr]]></category>
            <category><![CDATA[game-development]]></category>
            <category><![CDATA[programming]]></category>
            <dc:creator><![CDATA[Ece Sefercioğlu]]></dc:creator>
            <pubDate>Fri, 03 Jul 2020 05:22:05 GMT</pubDate>
            <atom:updated>2020-11-07T10:49:50.032Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*5YMz51gouKWbWd74.png" /><figcaption><a href="https://mk0uploadvrcom4bcwhj.kinstacdn.com/wp-content/uploads/2020/02/SteamVR.png">[Source]</a></figcaption></figure><p>In the lights of starting to create YouTube tutorials, I dived into creating SteamVR tutorials as well. At the start of each video, telling the steps of importing the SteamVR into Unity seemed to throw off the real focus of the video. To prevent this now we have the following video on importing SteamVr into Unity 2019. Additionally, this video serves as a stand-alone to guide importing SteamVR to Unity and prepare a scene to be the starting point of development/experimentation.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2F7WL19SiZ98g%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3D7WL19SiZ98g&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2F7WL19SiZ98g%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/0ef79d3f0ab3623017468f23133f984e/href">https://medium.com/media/0ef79d3f0ab3623017468f23133f984e/href</a></iframe><p>Here is a recap of the steps:</p><ul><li>Create the project with the 3D template</li><li>Import SteamVR</li><li>Configure SteamVR input actions</li><li>Add Player prefab to the scene</li><li>Delete if other Audio Listeners on the scene</li><li>Add a plane to the scene for the player to walk around</li><li>Add a column to the scene if you plan to interact with objects</li></ul><p>Hopefully, you find this SetamVR setup to go through helpful. Feedbacks are appreciated.<br> See you in next explorations!</p><p><em>Originally published at </em><a href="https://devsplorer.wordpress.com/2020/07/03/unity-steamvr-setup-2020/"><em>http://devsplorer.wordpress.com</em></a><em> on July 3, 2020.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9fab77a79ca2" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[#UnityTips: Automate Setting Test Mode For Advertisement API]]></title>
            <link>https://medium.com/@Scriptie/unitytips-automate-setting-test-mode-for-advertisement-api-fb262400e468?source=rss-f0551a5329cd------2</link>
            <guid isPermaLink="false">https://medium.com/p/fb262400e468</guid>
            <category><![CDATA[marketing]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[unity]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[unity-game-development]]></category>
            <dc:creator><![CDATA[Ece Sefercioğlu]]></dc:creator>
            <pubDate>Mon, 01 Jun 2020 19:17:41 GMT</pubDate>
            <atom:updated>2020-06-01T19:33:38.316Z</atom:updated>
            <content:encoded><![CDATA[<p>If you suffer from sending your apps to mobile stores on their ad configuration set to test mode or tired of changing it just before build, this short snippet may save you from these chores.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/330/0*C4gtwDhUsv88ra2O" /><figcaption>You update your game and the ad you see on your phone is a mock-up.</figcaption></figure><p>I had my fair share of sending <em>Advertisement API</em> in test mode to release. I simply forget to change <em>testMode</em> to <em>false</em> and see Unity placeholder advertisement on my updated games. I’ll not be bothered about this anymore, the below code piece is tested for the last build of <a href="https://play.google.com/store/apps/details?id=com.RegaliaGames.VirusBump">Virus Bump</a> and it works.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/34f9bffa96e5a74dce18781180b1fdba/href">https://medium.com/media/34f9bffa96e5a74dce18781180b1fdba/href</a></iframe><p>First, we have <em>testMode</em> boolean set to <em>false</em>. This variable is used to set the mode of <em>Advertisement API</em>. If it is <em>true</em>, ads will be mockups provided by the API, otherwise, the ads shown be from Unity Ads network.</p><p>For ethical and legal reasons I prefer not to use Unity Ads but use mockups for testing(they are easier to skip too). So I need to set <em>testMode</em> boolean to true for development testing.</p><p>The if condition just does that. <a href="https://docs.unity3d.com/ScriptReference/Application-isEditor.html"><em>Application.isEditor</em></a> returns true if the editor is the test environment. So the code that sets <em>testMode</em> to <em>true</em> runs and there will be no ads from Unity Ads network but only ad mockups.</p><p>If the game runs in an environment other than the editor, the condition will not be met and <em>testMode</em> stays <em>false</em> initializing the advertisement module with <em>testMode</em> <em>false</em>. Now, the ads shown will be requested from Unity Ads network.</p><p>I hope this will be helpful in eliminating this chore from your game development process. If you use another approach or have reservations on using this approach, let me know in comments. And also please tell me I am not alone on sending builds in test mode. Lastly, to see more posts like this you can follow this blog.</p><p><em>Originally published at </em><a href="https://devsplorer.wordpress.com/2020/06/01/unitytips-unity-advertisement-test-mode/"><em>http://devsplorer.wordpress.com</em></a><em> on June 1, 2020.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fb262400e468" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Color Prototyping In Unity]]></title>
            <link>https://medium.com/@Scriptie/color-prototyping-in-unity-252e67d8e64e?source=rss-f0551a5329cd------2</link>
            <guid isPermaLink="false">https://medium.com/p/252e67d8e64e</guid>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[unity]]></category>
            <category><![CDATA[game-development]]></category>
            <category><![CDATA[creativity]]></category>
            <dc:creator><![CDATA[Ece Sefercioğlu]]></dc:creator>
            <pubDate>Mon, 25 May 2020 05:38:32 GMT</pubDate>
            <atom:updated>2020-05-26T11:12:40.476Z</atom:updated>
            <content:encoded><![CDATA[<p>If you have one color or one-color gradient sprites, to decide a color palette or a color of a specific sprite you can use the color property of the SpriteRenderer or Image component of your sprite. This helps to test colors on how they would look in the game and make faster art decisions on the contrary of exporting each iteration from art software.</p><p>Let’s say you have a set of sprites with mono-color elements, whether they are UI or 2d game elements. You could export them pre-colored from the choice of your editing/drawing software. When you need to change some colors you would end up with external software — change colors — export loop. You could also export them fully white. if they have black borders leave them as they are. You can also use gray color to represent shadows. This way you can quickly test colors out for your sprites inside the editor.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1VGqE1kPD52-uTBmQqDaOQ.png" /><figcaption>One sprite many colors</figcaption></figure><p>For my game <a href="https://play.google.com/store/apps/details?id=com.RegaliaGames.VirusBump">Virus Bump</a>, I created a sprite sheet of my UI elements that have black outlines and are filled with white color. This helped me try different color palettes in the game. I could easily change colors and create a new release.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NTY5FB2avqFjoZ1tuauTSQ.png" /><figcaption>Virus Bump, a sprite rich(!) mobile game</figcaption></figure><p>After I import black-white sprite, I start to play with colors. For example in the previous version, the star was green as I was going for a less range of colors for my game. After having feedbacks from a friend, a more colorful approach did not sound so bad. (Yes, this is my colorful approach) I am a bit hesitant to colorize my game in the fear of losing harmony. Now the star is yellow with other changes on the screen. I even had the level end button di-color.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zu-OuuZCTGLoHdDESOCjmQ.png" /><figcaption>These changes were very easy to make on Unity UI</figcaption></figure><h3>Use Case:</h3><p>We start with having 2 2d art elements in our project. Left one is a Sprite has SpriteRenderer and the right one is an Image.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/432/0*zXX9o9YxEwowvR8N" /></figure><p>We start with coloring the Image one, simply setting its color to yellow.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/438/0*NOcDhIafUVKLUCJ3" /></figure><p>We can also set the color property of the SpriteRenderer and test whether green is a better choice.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/433/0*Q-pkUExPNneHFRuG" /></figure><p>Now we can decide which color to use. Sprite one looks bigger because in space it is closer to the perspective camera.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/438/0*IWl1Vwg2ME2FEPD_" /></figure><h3>Proposed step by step approach:</h3><ol><li>Design your sprites in grayscale. Black for the outline, white to black for color gradient, like shadows.</li><li>Export the sprites</li><li>Import them into Unity</li><li>Put the sprites on the scene</li><li>Whichever component you use to start changing colors.</li><li>Test things out, get feedback, and finalize your design.</li><li>Well done.</li></ol><p>Whenever I have simple sprites compatible to apply this approach I choose to use it. This way not only making design decisions fastened but also the wait time of change color-export loop is omitted. If you are also after some practices to fasten your development in Unity, I suggest giving this one a try.</p><p><em>Originally published at </em><a href="https://devsplorer.wordpress.com/2020/05/25/color-prototyping-in-unity/"><em>http://devsplorer.wordpress.com</em></a><em> on May 25, 2020.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=252e67d8e64e" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>