Mark Theriault founded the startup FITY envisioning a line of clever cooling products: cold drink holders that come with freezable pucks to keep beverages cold for longer without the mess of ice. The entrepreneur started with 3D prints of products in his basement, building one unit at a time, before eventually scaling to mass production. Founding a consumer product company from scratch was a tall order for a single person. Going from preliminary sketches to production-ready designs was a major challenge. To bring his creative vision to life, Theriault relied on AI and his NVIDIA GeForce RTX-equipped system. For him, AI isn’t just a tool — it’s an entire pipeline to help him accomplish his goals. Read more about his workflow below. Plus, GeForce RTX 5050 laptops start arriving today at retailers worldwide, from $999. GeForce RTX 5050 Laptop GPUs feature 2,560 NVIDIA Blackwell CUDA cores, fifth-generation AI Tensor Cores, fourth-generation RT Cores, a ninth-generation NVENC encoder and a sixth-generation NVDEC decoder. In addition, NVIDIA’s Plug and Play: Project G-Assist Plug-In Hackathon — running virtually through Wednesday, July 16 — invites developers to explore AI and build custom G-Assist plug-ins for a chance to win prizes. Save the date for the G-Assist Plug-In webinar on Wednesday, July 9, from 10-11 a.m. PT, to learn more about Project G-Assist capabilities and fundamentals, and to participate in a live Q&A session. From Concept to Completion To create his standout products, Theriault tinkers with potential FITY Flex cooler designs with traditional methods, from sketch to computer-aided design to rapid prototyping, until he finds the right vision. A unique aspect of the FITY Flex design is that it can be customized with fun, popular shoe charms. For packaging design inspiration, Theriault uses his preferred text-to-image generative AI model for prototyping, Stable Diffusion XL — which runs 60% faster with the NVIDIA TensorRT software development kit — using the modular, node-based interface ComfyUI. ComfyUI gives users granular control over every step of the generation process — prompting, sampling, model loading, image conditioning and post-processing. It’s ideal for advanced users like Theriault who want to customize how images are generated. Theriault’s uses of AI result in a complete computer graphics-based ad campaign. Image courtesy of FITY. NVIDIA and GeForce RTX GPUs based on the NVIDIA Blackwell architecture include fifth-generation Tensor Cores designed to accelerate AI and deep learning workloads. These GPUs work with CUDA optimizations in PyTorch to seamlessly accelerate ComfyUI, reducing generation time on FLUX.1-dev, an image generation model from Black Forest Labs, from two minutes per image on the Mac M3 Ultra to about four seconds on the GeForce RTX 5090 desktop GPU. ComfyUI can also add ControlNets — AI models that help control image generation — that Theriault uses for tasks like guiding human poses, setting compositions via depth mapping and converting scribbles to images. Theriault even creates his own fine-tuned models to keep his style consistent. He used low-rank adaptation (LoRA) models — small, efficient adapters into specific layers of the network — enabling hyper-customized generation with minimal compute cost. LoRA models allow Theriault to ideate on visuals quickly. Image courtesy of FITY. “Over the last few months, I’ve been shifting from AI-assisted computer graphics renders to fully AI-generated product imagery using a custom Flux LoRA I trained in house. My RTX 4080 SUPER GPU has been essential for getting the performance I need to train and iterate quickly.” – Mark Theriault, founder of FITY  Theriault also taps into generative AI to create marketing assets like FITY Flex product packaging. He uses FLUX.1, which excels at generating legible text within images, addressing a common challenge in text-to-image models. Though FLUX.1 models can typically consume over 23GB of VRAM, NVIDIA has collaborated with Black Forest Labs to help reduce the size of these models using quantization — a technique that reduces model size while maintaining quality. The models were then accelerated with TensorRT, which provides an up to 2x speedup over PyTorch. To simplify using these models in ComfyUI, NVIDIA created the FLUX.1 NIM microservice, a containerized version of FLUX.1 that can be loaded in ComfyUI and enables FP4 quantization and TensorRT support. Combined, the models come down to just over 11GB of VRAM, and performance improves by 2.5x. Theriault uses the Blender Cycles app to render out final files. For 3D workflows, NVIDIA offers the AI Blueprint for 3D-guided generative AI to ease the positioning and composition of 3D images, so anyone interested in this method can quickly get started. Photorealistic renders. Image courtesy of FITY. Finally, Theriault uses large language models to generate marketing copy — tailored for search engine optimization, tone and storytelling — as well as to complete his patent and provisional applications, work that usually costs thousands of dollars in legal fees and considerable time. Generative AI helps Theriault create promotional materials like the above. Image courtesy of FITY. “As a one-man band with a ton of content to generate, having on-the-fly generation capabilities for my product designs really helps speed things up.” – Mark Theriault, founder of FITY Every texture, every word, every photo, every accessory was a micro-decision, Theriault said. AI helped him survive the “death by a thousand cuts” that can stall solo startup founders, he added. Each week, the RTX AI Garage blog series features community-driven AI innovations and content for those looking to learn more about NVIDIA NIM microservices and AI Blueprints, as well as building AI agents, creative workflows, digital humans, productivity apps and more on AI PCs and workstations.  Plug in to NVIDIA AI PC on Facebook, Instagram, TikTok and X — and stay informed by subscribing to the RTX AI PC newsletter. Follow NVIDIA Workstation on LinkedIn and X.  See notice regarding software product information.

The new design celebrates the team's centennial.

Learn a useful trick with Blender's Pen tool with this new tutorial by John R. Nyquist. For the new Bits of Blender logo (my series of quick tips and tutorials for the Blender community), I used Blender 4.4 to create the 2D art. I began with thumbnai

Les Muppets n’ont pas disparu. Après la fermeture de Muppet Vision 3D aux studios d’Hollywood, […] Cet article Les Muppets reviennent en VR pour leurs sketches les plus fous a été publié sur REALITE-VIRTUELLE.COM.

herramienta de medición, Leica BLK3D, tecnología de medición, mediciones en 3D, telemetría, diseño arquitectónico, innovación tecnológica ## Introducción El **Leica BLK3D**, un dispositivo que se presenta como la panacea para todos nuestros problemas de medición, es simplemente otra herramienta más en un mercado saturado. Nos dicen que es versátil, que permite medir en fotos, que tiene un...

Recommendations straight from the experts.

Six top manga artists reveal the secrets behind their success

Casa Sofia | © Fernando Guerra / FG+SG Located in the historic heart of Lagos, Portugal, Casa Sofia by Mário Martins Atelier is a thoughtful exercise in urban integration and contemporary reinterpretation. Occupying a site once held by a modest two-story house, the project is situated on the corner of a block facing the Church of St Sebastião. With its commanding presence, this national monument set a formidable challenge for the architects: introducing a new residence that respects the weight of history while offering a clear, contemporary expression. Casa Sofia Technical Information Architects1-4: Mário Martins Atelier Location: Lagos, Portugal Project Completion Years: 2023 Photographs: © Fernando Guerra / FG+SG It is therefore important to design a building to fit into and complete the block. A house that is quiet and solid, with rhythmic metrics, whose new design brings an identity, with the weight and scent of the times, to a city that has existed for many centuries. – Mário Martins Atelier Casa Sofia Photographs © Fernando Guerra / FG+SG © Fernando Guerra / FG+SG © Fernando Guerra / FG+SG © Fernando Guerra / FG+SG © Fernando Guerra / FG+SG © Fernando Guerra / FG+SG © Fernando Guerra / FG+SG © Fernando Guerra / FG+SG © Fernando Guerra / FG+SG © Fernando Guerra / FG+SG © Fernando Guerra / FG+SG Spatial Organization and Circulation The design’s ambition is anchored in reconciling modern residential needs with the dense urban fabric that defines the walled city. Rather than imposing a bold or disruptive form, the project embraces the existing rhythms and textures of the surrounding architecture. The result is a building that both defers to and elevates the neighborhood’s character. Its restrained profile and carefully modulated facade echo the massing and articulation of the original house while introducing an identity that is clearly of its time. At the core of Casa Sofia’s spatial organization is a deliberate hierarchy of spaces that transitions seamlessly between public, semi-public, and private domains. Entry from the street occurs through a modest set of steps leading to an exterior atrium. This threshold mediates the relationship between the public realm and the interior, grounding the house in its urban context. Once inside, an open hall reveals the vertical flow of the building, dominated by a staircase that appears to float, linking the house’s various levels while maintaining visual continuity throughout. The ground floor houses three bedrooms, each with an ensuite bathroom, radiating from the central hall. This level also contains a small basement for technical support, reinforcing the discreet layering of functional and domestic spaces. Midway up the staircase, the house opens onto a garage, a laundry room, and an intimate courtyard. These areas, essential for daily life, are seamlessly integrated into the overall composition, contributing to a spatial richness that is both pragmatic and sensorial. On the first floor, an open-plan arrangement accommodates the main living spaces. Around a central void, the living and dining areas, kitchen, and master suite are arranged to encourage visual interplay and shared light. This configuration enhances the spatial porosity, ensuring that despite the density of the historic center, the house retains a sense of openness and fluidity. Above, a recessed roof level recedes from the street, culminating in a panoramic terrace with a swimming pool. Here, the building dissolves into the sky, offering expansive views and light-filled leisure spaces that contrast with the more enclosed lower floors. Materiality and Craftsmanship Materiality plays a decisive role in mediating the building’s relationship with its context. White-painted plaster, a familiar element in the region, is punctuated by deep limestone moldings. These details create a play of light and shadow that emphasizes the facade’s verticality and rhythm. The generous thickness of the walls, carried over from the site’s earlier construction, lends a sense of solidity and permanence to the house, recalling the tactile traditions of the Algarve’s architecture. The interior and exterior detailing is characterized by an economy of means, where each material is selected for its ability to reinforce the house’s quiet presence. Local materials and craftsmanship ground the project in its immediate context while responding to environmental imperatives. High thermal comfort is achieved through careful orientation and passive design strategies, complemented by the integration of solar control and water conservation measures. These considerations underscore the project’s commitment to sustainability without resorting to superficial gestures. Broader Urban and Cultural Implications Beyond its immediate function as a family home, Casa Sofia engages in a broader dialogue with its urban and cultural surroundings. The project exemplifies a measured response to the question of how to build within a historical setting without resorting to nostalgia or pastiche. It demonstrates that contemporary architecture can find resonance within heritage contexts by prioritizing the values of continuity, scale, and material authenticity. In its measured dialogue with the Church of St Sebastião and the centuries-old urban landscape of Lagos, Casa Sofia illustrates the potential for architecture to enrich the experience of place through quiet, rigorous interventions. It is a project that reaffirms architecture’s capacity to negotiate between past and present, crafting spaces that are at once deeply contextual and unambiguously of their moment. Casa Sofia Plans Sketch | © Mário Martins Atelier Ground Level | © Mário Martins Atelier Level 1 | © Mário Martins Atelier Level 2 | © Mário Martins Atelier Roof Plan | © Mário Martins Atelier Section | © Mário Martins Atelier Casa Sofia Image Gallery About Mário Martins Atelier Mário Martins Atelier is a Portuguese architecture and urbanism practice founded in 2000 by architect Mário Martins, who holds a degree from the Faculty of Architecture at the Technical University of Lisbon (1988). Headquartered in Lagos with a secondary office in Lisbon, the firm operates with a dedicated multidisciplinary team. The office has developed a broad spectrum of work, from single-family homes and collective housing to public buildings and urban regeneration, distinguished by technical precision, contextual sensitivity, and sustainable strategies. Credits and Additional Notes Lead Architect: Mário Martins, arq. Project Team: Rita Rocha, Sónia Fialho, Susana Caetano, Susana Jóia, Ana Graça Engineering: Nuno Grave Engenharia Building: Marques Antunes Engenharia Lda

You’ve drawn fifty versions of the same screen — and you still hate every one of them. Begrudgingly, you pick three, show them to your product manager, and hear: “Looks cool, but the idea doesn’t work.” Sound familiar? In this article, I’ll unpack why designers fall into detail work at the wrong moment, examining both process pitfalls and the underlying psychological reasons, as understanding these traps is the first step to overcoming them. I’ll also share tactics I use to climb out of that trap. Reason #1 You’re Afraid To Show Rough Work We designers worship detail. We’re taught that true craft equals razor‑sharp typography, perfect grids, and pixel precision. So the minute a task arrives, we pop open Figma and start polishing long before polish is needed. I’ve skipped the sketch phase more times than I care to admit. I told myself it would be faster, yet I always ended up spending hours producing a tidy mock‑up when a scribbled thumbnail would have sparked a five‑minute chat with my product manager. Rough sketches felt “unprofessional,” so I hid them. The cost? Lost time, wasted energy — and, by the third redo, teammates were quietly wondering if I even understood the brief. The real problem here is the habit: we open Figma and start perfecting the UI before we’ve even solved the problem. So why do we hide these rough sketches? It’s not just a bad habit or plain silly. There are solid psychological reasons behind it. We often just call it perfectionism, but it’s deeper than wanting things neat. Digging into the psychology (like the research by Hewitt and Flett) shows there are a couple of flavors driving this: Socially prescribed perfectionismIt’s that nagging feeling that everyone else expects perfect work from you, which makes showing anything rough feel like walking into the lion’s den. Self-oriented perfectionismWhere you’re the one setting impossibly high standards for yourself, leading to brutal self-criticism if anything looks slightly off. Either way, the result’s the same: showing unfinished work feels wrong, and you miss out on that vital early feedback. Back to the design side, remember that clients rarely see architects’ first pencil sketches, but these sketches still exist; they guide structural choices before the 3D render. Treat your thumbnails the same way — artifacts meant to collapse uncertainty, not portfolio pieces. Once stakeholders see the upside, roughness becomes a badge of speed, not sloppiness. So, the key is to consciously make that shift: Treat early sketches as disposable tools for thinking and actively share them to get feedback faster. Reason #2: You Fix The Symptom, Not The Cause Before tackling any task, we need to understand what business outcome we’re aiming for. Product managers might come to us asking to enlarge the payment button in the shopping cart because users aren’t noticing it. The suggested solution itself isn’t necessarily bad, but before redesigning the button, we should ask, “What data suggests they aren’t noticing it?” Don’t get me wrong, I’m not saying you shouldn’t trust your product manager. On the contrary, these questions help ensure you’re on the same page and working with the same data. From my experience, here are several reasons why users might not be clicking that coveted button: Users don’t understand that this step is for payment. They understand it’s about payment but expect order confirmation first. Due to incorrect translation, users don’t understand what the button means. Lack of trust signals (no security icons, unclear seller information). Unexpected additional costs (hidden fees, shipping) that appear at this stage. Technical issues (inactive button, page freezing). Now, imagine you simply did what the manager suggested. Would you have solved the problem? Hardly. Moreover, the responsibility for the unresolved issue would fall on you, as the interface solution lies within the design domain. The product manager actually did their job correctly by identifying a problem: suspiciously, few users are clicking the button. Psychologically, taking on this bigger role isn’t easy. It means overcoming the fear of making mistakes and the discomfort of exploring unclear problems rather than just doing tasks. This shift means seeing ourselves as partners who create value — even if it means fighting a hesitation to question product managers (which might come from a fear of speaking up or a desire to avoid challenging authority) — and understanding that using our product logic expertise proactively is crucial for modern designers. There’s another critical reason why we, designers, need to be a bit like product managers: the rise of AI. I deliberately used a simple example about enlarging a button, but I’m confident that in the near future, AI will easily handle routine design tasks. This worries me, but at the same time, I’m already gladly stepping into the product manager’s territory: understanding product and business metrics, formulating hypotheses, conducting research, and so on. It might sound like I’m taking work away from PMs, but believe me, they undoubtedly have enough on their plates and are usually more than happy to delegate some responsibilities to designers. Reason #3: You’re Solving The Wrong Problem Before solving anything, ask whether the problem even deserves your attention. During a major home‑screen redesign, our goal was to drive more users into paid services. The initial hypothesis — making service buttons bigger and brighter might help returning users — seemed reasonable enough to test. However, even when A/B tests (a method of comparing two versions of a design to determine which performs better) showed minimal impact, we continued to tweak those buttons. Only later did it click: the home screen isn’t the place to sell; visitors open the app to start, not to buy. We removed that promo block, and nothing broke. Contextual entry points deeper into the journey performed brilliantly. Lesson learned: Without the right context, any visual tweak is lipstick on a pig. Why did we get stuck polishing buttons instead of stopping sooner? It’s easy to get tunnel vision. Psychologically, it’s likely the good old sunk cost fallacy kicking in: we’d already invested time in the buttons, so stopping felt like wasting that effort, even though the data wasn’t promising. It’s just easier to keep fiddling with something familiar than to admit we need a new plan. Perhaps the simple question I should have asked myself when results stalled was: “Are we optimizing the right thing or just polishing something that fundamentally doesn’t fit the user’s primary goal here?” That alone might have saved hours. Reason #4: You’re Drowning In Unactionable Feedback We all discuss our work with colleagues. But here’s a crucial point: what kind of question do you pose to kick off that discussion? If your go-to is “What do you think?” well, that question might lead you down a rabbit hole of personal opinions rather than actionable insights. While experienced colleagues will cut through the noise, others, unsure what to evaluate, might comment on anything and everything — fonts, button colors, even when you desperately need to discuss a user flow. What matters here are two things: The question you ask, The context you give. That means clearly stating the problem, what you’ve learned, and how your idea aims to fix it. For instance: “The problem is our payment conversion rate has dropped by X%. I’ve interviewed users and found they abandon payment because they don’t understand how the total amount is calculated. My solution is to show a detailed cost breakdown. Do you think this actually solves the problem for them?” Here, you’ve stated the problem (conversion drop), shared your insight (user confusion), explained your solution (cost breakdown), and asked a direct question. It’s even better if you prepare a list of specific sub-questions. For instance: “Are all items in the cost breakdown clear?” or “Does the placement of this breakdown feel intuitive within the payment flow?” Another good habit is to keep your rough sketches and previous iterations handy. Some of your colleagues’ suggestions might be things you’ve already tried. It’s great if you can discuss them immediately to either revisit those ideas or definitively set them aside. I’m not a psychologist, but experience tells me that, psychologically, the reluctance to be this specific often stems from a fear of our solution being rejected. We tend to internalize feedback: a seemingly innocent comment like, “Have you considered other ways to organize this section?” or “Perhaps explore a different structure for this part?” can instantly morph in our minds into “You completely messed up the structure. You’re a bad designer.” Imposter syndrome, in all its glory. So, to wrap up this point, here are two recommendations: Prepare for every design discussion.A couple of focused questions will yield far more valuable input than a vague “So, what do you think?”. Actively work on separating feedback on your design from your self-worth.If a mistake is pointed out, acknowledge it, learn from it, and you’ll be less likely to repeat it. This is often easier said than done. For me, it took years of working with a psychotherapist. If you struggle with this, I sincerely wish you strength in overcoming it. Reason #5 You’re Just Tired Sometimes, the issue isn’t strategic at all — it’s fatigue. Fussing over icon corners can feel like a cozy bunker when your brain is fried. There’s a name for this: decision fatigue. Basically, your brain’s battery for hard thinking is low, so it hides out in the easy, comfy zone of pixel-pushing. A striking example comes from a New York Times article titled “Do You Suffer From Decision Fatigue?.” It described how judges deciding on release requests were far more likely to grant release early in the day (about 70% of cases) compared to late in the day (less than 10%) simply because their decision-making energy was depleted. Luckily, designers rarely hold someone’s freedom in their hands, but the example dramatically shows how fatigue can impact our judgment and productivity. What helps here: Swap tasks.Trade tickets with another designer; novelty resets your focus. Talk to another designer.If NDA permits, ask peers outside the team for a sanity check. Step away.Even a ten‑minute walk can do more than a double‑shot espresso. By the way, I came up with these ideas while walking around my office. I was lucky to work near a river, and those short walks quickly turned into a helpful habit. And one more trick that helps me snap out of detail mode early: if I catch myself making around 20 little tweaks — changing font weight, color, border radius — I just stop. Over time, it turned into a habit. I have a similar one with Instagram: by the third reel, my brain quietly asks, “Wait, weren’t we working?” Funny how that kind of nudge saves a ton of time. Four Steps I Use to Avoid Drowning In Detail Knowing these potential traps, here’s the practical process I use to stay on track: 1. Define the Core Problem & Business Goal Before anything, dig deep: what’s the actual problem we’re solving, not just the requested task or a surface-level symptom? Ask ‘why’ repeatedly. What user pain or business need are we addressing? Then, state the clear business goal: “What metric am I moving, and do we have data to prove this is the right lever?” If retention is the goal, decide whether push reminders, gamification, or personalised content is the best route. The wrong lever, or tackling a symptom instead of the cause, dooms everything downstream. 2. Choose the Mechanic (Solution Principle) Once the core problem and goal are clear, lock the solution principle or ‘mechanic’ first. Going with a game layer? Decide if it’s leaderboards, streaks, or badges. Write it down. Then move on. No UI yet. This keeps the focus high-level before diving into pixels. 3. Wireframe the Flow & Get Focused Feedback Now open Figma. Map screens, layout, and transitions. Boxes and arrows are enough. Keep the fidelity low so the discussion stays on the flow, not colour. Crucially, when you share these early wires, ask specific questions and provide clear context (as discussed in ‘Reason #4’) to get actionable feedback, not just vague opinions. 4. Polish the Visuals (Mindfully) I only let myself tweak grids, type scales, and shadows after the flow is validated. If progress stalls, or before a major polish effort, I surface the work in a design critique — again using targeted questions and clear context — instead of hiding in version 47. This ensures detailing serves the now-validated solution. Even for something as small as a single button, running these four checkpoints takes about ten minutes and saves hours of decorative dithering. Wrapping Up Next time you feel the pull to vanish into mock‑ups before the problem is nailed down, pause and ask what you might be avoiding. Yes, that can expose an uncomfortable truth. But pausing to ask what you might be avoiding — maybe the fuzzy core problem, or just asking for tough feedback — gives you the power to face the real issue head-on. It keeps the project focused on solving the right problem, not just perfecting a flawed solution. Attention to detail is a superpower when used at the right moment. Obsessing over pixels too soon, though, is a bad habit and a warning light telling us the process needs a rethink.

IntroductionHello! My name is Denys. I was born and raised in Nigeria, where I'm currently based. I began my journey into 3D art in March 2022, teaching myself through online resources, starting, of course, with the iconic donut tutorial on YouTube. Since then, I've continued to grow my skills independently, and now I'm working toward a career in 3D generalism, with a particular interest in environment art.I originally got into Blender because SketchUp wasn't free, and I could not keep up with the subscriptions. While searching for alternatives, I came across Blender. That's when I realized I had installed it once years ago, but back then, the interface completely intimidated me, and I gave up on it. This time, though, I decided to stick with it – and I'm glad I did.I started out creating simple models. One of my first big projects was modeling the entire SpongeBob crew. That led to my first animation, and eventually, the first four episodes of a short animated series (though it's still incomplete). As I grew more confident, I began participating in online 3D competitions, like cgandwe, where I focused on designing realistic environments. Those experiences have played a huge role in getting me to where I am today.Getting Started Before starting any scene, I always look for references. It might not be the most original approach, but it's what works best for me. One piece that inspired me was a beautiful artwork by Calder Moore. I bookmarked it as soon as I saw it back in 2023, and luckily, I finally found the time to bring it to life last month.BlockoutThe goal was to match the original camera angle and roughly model the main frame of the structures. It wasn't perfect, but modeling and placing the lower docks helped me get the perspective right. Then I moved on to modeling and positioning the major structures in the scene.I gave myself two weeks to complete this project. And as much as I enjoy modeling, I also enjoy not modeling, so I turned to asset kits and free models to help speed things up. I came across an awesome paid kit by Bigmediumsmall and instantly knew it would fit perfectly into my scene.I also downloaded a few models from Sketchfab, including a lamp, desk console, freighter controls, and a robotic arm, which I later took apart to add extra detail. Another incredibly helpful tool was the Random Flow add-on by BlenderGuppy, which made adding sci-fi elements much easier. Lastly, I pulled in some models from my older sci-fi and cyberpunk projects to round things out.Kitbashing Once I had the overall shape I was aiming for, I moved on to kitbashing to pack in as much detail as possible. There wasn't any strict method to the madness; I simply picked assets I liked, whether it was a set of pipes, vents, or even a random shape that just worked in the sci-fi context. I focused first on kitbashing the front structure, and used the Random Flow add-on to fill in areas where I didn't kitbash manually. Then I moved on to the other collections, following the same process.The freighter was the final piece of the puzzle, and I knew it was going to be a challenge. Part of me wanted to model it entirely from scratch, but the more practical side knew I could save a lot of time by sticking with my usual method. So I modeled the main shapes myself, then kitbashed the details to bring it to life. I also grabbed some crates from Sketchfab to fill out the scene.Texturing This part was easily my favorite, and there was no shortcut here. I had to meticulously create each material myself. Well, I did use PBR materials downloaded from CGAmbient as a base, but I spent a lot of time tweaking and editing them to get everything just right.Texturing has always been my favorite stage when building scenes like this. Many artists prefer external tools like Substance 3D Painter (which I did use for some of the models), but I've learned so much about procedural texturing, especially from RyanKingArt, that I couldn't let it go. It's such a flexible and rewarding approach, and I love pushing it as far as I can.I wanted most of the colors in the scene to be dark, but I did keep the original color of the pipes and the pillars, just to add a little bit of vibrance to the scene. I also wanted the overall texture to be very rough and grungy. One of the biggest helps in achieving this was using the Grunge Maps from Substance 3D Painter. I found a way to extract them into Blender, and it helped.A major tool during the texturing phase was Jsplacement, which I used to procedurally generate sci-fi grids and plates. This was the icing on the cake for adding intricate details. Whenever an area felt too flat, I applied bump maps with these grids and panels to bring the materials to life. For example, both the lamp pole and the entire black metal material feature these Jsplacement Maps.Lighting For this, I didn't do anything fancy. I knew the scene was in a high altitude, so I looked for HDRI with a cloudless sky, and I boosted the saturation up a little to give it that high altitude look.Post-Production The rendering phase was challenging since I was working on a low-end laptop. I couldn't render the entire scene all at once, so I broke it down by collections and rendered them as separate layers. Then, I composited the layers together in post-production. I'm not big on heavy post-work, so I kept it simple, mostly tweaking brightness and saturation on my phone. That's about it for the post-production process.Conclusion The entire project took me 10 days to complete, working at least four hours each day. Although I've expressed my love for texturing, my favorite part of this project was the detailing and kitbashing. I really enjoyed piecing all the small details together. The most challenging part was deciding which assets to use and where to place them. I had a lot of greebles to choose from, but I'm happy with the ones I selected; they felt like a perfect fit for the scene.I know kitbashing sometimes gets a negative reputation in the 3D community, but I found it incredibly relieving. Honestly, this project wouldn't have come together without it, so I fully embraced the process.I'm excited to keep making projects like this. The world of 3D art is truly an endless and vast realm, and I encourage every artist like me to keep exploring it, one project at a time.Denys Molokwu, 3D Artist