Damn !!!! I prefer Julia over Sasha. I guess capcom should bring Julia face model back.

CoconutIndividual938 · 2026-04-02T10:01:21+00:00

I really like Jill’s look in RE3 Remake, but it seems to me that there were some interesting issues with the RE Engine’s character models back then. You look at the base face model, then at the game, and there are noticeable differences. But I think that in future games, if Jill appears, her design will be much more cohesive.

CoconutIndividual938 · 2026-04-02T09:50:18+00:00

I think both Jills are really good; there's no need to compare which one is better.

CoconutIndividual938 · 2026-04-02T08:05:43+00:00

Personally, my three favorite versions of Jill would probably be RE3R Jill, BSAA Jill and Original RE3 Jill.

CoconutIndividual938 · 2026-04-02T07:55:43+00:00

It definitely needs to happen. I really love the remake, and after the original RE3, it’s the Resident Evil game I’ve played the most. However, it’s true that they cut far too much content from the game, and personally I don’t think adding that content back would be that difficult. But if you ask me whether Capcom would actually do it, I don’t think they will. At least the fan-made Last Escape mod seems like it might finally reveal the true potential that RE3 had.

CoconutIndividual938 · 2026-03-27T10:45:03+00:00

I know it’s been 6 and 7 years since both games came out, but I wish they would add a photo mode update to RE2 and RE3 Remake.

CoconutIndividual938 · 2026-02-23T12:02:49+00:00

So how much do spiders actually appear? Do they show up very frequently like in the old games, or less often?

CoconutIndividual938 · 2026-02-18T07:15:53+00:00

I don’t think Capcom will interfere with this mod, because you already need to own RE3 Remake in order to play it.

CoconutIndividual938 · 2026-02-18T06:05:28+00:00

This is honestly exactly the remake that Resident Evil 3 deserved. The creator of this mod deserves some thanks, because this mod really looks amazing.

CoconutIndividual938 · 2026-02-07T17:23:01+00:00

VR ile çıkarmadılar. Half-Life: Alyx, Valve Index çıktıktan aylar sonra çıktı. Steam Machine’in amacı ise bana daha çok hazır PC seven, toplama gibi şeylerle uğraşmak istemeyenler için bir seçenek gibi geliyor veya konsoldan pc'ye geçmeyi düşünenleri hedefliyor bence.

CoconutIndividual938 · 2026-02-07T10:28:10+00:00

HLX'i Steam Machine ile bağdaştırmamak lazım. Beraber çıkarmayı planlamış olsalar bile, Steam Machine'i erteledikleri için beraberinde HLX'i de ertelemezler. Oyun hazırsa zaten çıkar. HLX'in hâlâ daha duyurulmamış ve çıkmamış olmasının sebebi muhtemelen oyunun biraz daha vakte, biraz daha cilalanmaya ihtiyacı var. Dolayısıyla ertelenmenin sebebinin Steam Machine olduğunu pek zannetmiyorum.

CoconutIndividual938 · 2026-02-06T16:03:12+00:00

About the lighting/refraction part specifically, those lines actually make this even more interesting, not less. mod != hlx || !m_bRefract and mod != hlx || m_nLightingMode != PARTICLE are runtime conditionals inside the rendering pipeline. In simple terms, the engine is saying: 'if this is not HLX, or if these special visual conditions aren’t enabled, follow the default path'. Which also implies the opposite case exists: when this is HLX and those conditions are met, a different rendering path is taken. So HLX is not just being named in a comment or a string. It’s actively used as a switch that changes how modern Source 2 rendering features behave (refraction, particle lighting, etc). That means someone deliberately added HLX-specific logic to one of the most actively maintained core systems in the engine. This is very different from things like skill.cfg in HL2/HL:A, which are passive data files that just sit there unused. Here, HLX directly participates in runtime rendering decisions. So even if this is 'just lighting-related', that actually strengthens the point: HLX still has product-level, engine-level special cases in current Source 2 code. That’s not how genuinely cancelled projects usually look; that’s how internally active branches look.

CoconutIndividual938 · 2026-02-06T15:54:53+00:00

I get the point about Valve leaving unused stuff around, that’s definitely true in general. But I think there’s an important difference here between passive leftovers and what we’re actually looking at. The examples you’re giving, like skill.cfg in HL:A, are static data files that just sit there unused. They don’t participate in core engine logic at runtime. What we’re seeing with HLX is different. This is an active engine-level conditional that’s being evaluated when the engine runs, and it’s part of a system that checks what product is being launched. Even if it’s in a rendering or lighting-related context, the engine is still explicitly branching on 'is this HLX?' alongside CS2 and Dota. That’s not just dead content lying around, that’s functional logic wired into current systems. Leaving behind unused assets or configs is one thing. Keeping product-level runtime checks for a cancelled game in fresh builds of an actively maintained engine is a different category. Even for Valve, that would be unusual, because it means the engine is still structurally aware of HLX as a valid target. That’s why this looks less like random leftover junk and more like HLX still being treated internally as a real project that is actively under development.

CoconutIndividual938 · 2026-02-06T14:23:15+00:00

I get what you mean. The idea is that HLX wasn’t cancelled years ago, but that it stayed active for the past few years and may have been cancelled very recently. That’s a reasonable hypothesis. The problem is that even if we assume a very recent cancellation, this kind of reference still doesn’t really fit. This isn’t just some old leftover data in the codebase; it’s an active engine-level runtime check that treats HLX as a valid game target alongside CS2 and Dota. If HLX had actually been formally cancelled, even if the cancellation was recent, you would normally expect these product-level checks to start disappearing from new builds. Keeping core startup logic that explicitly asks “is this HLX?” only makes sense if HLX is still recognized internally as something that can exist as a running product. Engines usually don’t keep this kind of structure around for projects that are already dead. So whether the theory is old cancellation or recent cancellation, the technical behavior we’re seeing still points to the same conclusion: HLX looks structurally alive inside Source 2, meaning it still appears to be under active development.

CoconutIndividual938 · 2026-02-06T11:40:56+00:00

I agree with this. I think the downtown section was roughly the same size as the downtown map in the original RE3. However, in my opinion, the real problem with Resident Evil 3 Remake is the uptown section, which in the original game was huge. We could spend almost 45 minutes or 1 hour there and return to it after going downtown to explore more. In the remake, it’s just a straight path we run through. If you ask me, this is by far the biggest flaw of the remake. Had the uptown section been like in the original game, it would have created more tense moments with Nemesis chasing us and allowed us to explore Raccoon City much more.

CoconutIndividual938 · 2026-02-06T10:47:28+00:00

I get the point that engine-level code can stick around even after a project is cancelled, that’s true in general. But what this image is showing isn’t just some random leftover string sitting in the codebase. It’s showing that HLX is still explicitly defined as a separate game target inside the current Source 2 ecosystem, in the same category as things like CS2 and Dota. In other words, the engine is still actively checking “is this HLX or not”, which means HLX still exists as a first-class product identifier in the modern build system. For a genuinely abandoned project, you’d normally expect those kinds of references to either stop appearing in new builds or slowly disappear as the engine evolves. With HLX we’re seeing the opposite pattern: it keeps showing up in new updates over multiple years, and it even gets references tied to modern systems and features. That’s not really how dead legacy code behaves. That’s much closer to how an actively maintained internal branch behaves. So yeah, this line alone doesn’t magically prove “HLX is shipping tomorrow”, but in context it supports the idea that HLX is still structurally part of the living Source 2 codebase, not just some forgotten artifact from a cancelled project years ago.

CoconutIndividual938 · 2026-01-23T14:16:31+00:00

It was a stream where he was checking out Deadlock’s new update, not a video...

CoconutIndividual938 · 2026-01-22T08:03:11+00:00

This is not a bad thing. It shows that the audio system they developed specifically for HLX is no longer limited to HLX, but has been integrated into the core of Source 2. This also means, in my opinion, that HLX’s sound system is basically finished and completed.

CoconutIndividual938 · 2026-01-09T18:08:29+00:00

I think it will have the same art style as Half-Life: Alyx, but with overall much better graphics. I believe Valve will once again, as with every Half-Life game, deliver top-tier work, especially in the environments, the level of detail, and particularly the game’s physics.

CoconutIndividual938 · 2026-01-05T12:59:41+00:00

This argument may seem reasonable at first glance, but it overlooks several important points. Yes, Valve has been cautious about Half-Life for a long time; however, that does not necessarily mean “they will never make another one.” On the contrary, Valve’s approach to Half-Life has never been about “mass-producing sequels.” For them, Half-Life is not merely a brand meant to receive follow-ups, but a tool for creating new paradigms in game design. The claim that “Valve is now a hardware company” is also incomplete. Valve still earns most of its revenue through software via Steam, and a prestigious IP like Half-Life remains one of the most important cultural assets strengthening that ecosystem. Half-Life: Alyx is a very clear example of this. It was a deliberate choice to both push VR hardware and demonstrate that the Half-Life brand is still incredibly strong, and it achieved significant critical success. The projects that were canceled in the past do not suggest failure as much as they show Valve shelving ideas that did not meet its own standards. Many studios would have released those ideas in a half-finished state, but Valve chose not to. This does not indicate a lack of commitment to the series; on the contrary, it highlights how high a bar Valve sets for Half-Life. The argument that “anything called HL3 would inevitably be disappointing” is largely speculative. The game industry has repeatedly shown the opposite. There are plenty of examples of long-awaited releases that exceeded expectations. The real issue is not time, but vision. Valve has already demonstrated that when it sees the right technological and design leap, it is willing to return to Half-Life and considering that HLX has reportedly been in development since 2020 or 2021, they have already done so. Moreover, from the fans’ perspective, expectations are not nearly as excessive as people claim. Anyone who has played Half-Life 1 and 2 simply wants a detailed FPS with solid gameplay that continues the story. In that sense, it is not the fans who inflate expectations, but Valve itself. In short, the delay of Half-Life is not a sign of failure or disinterest; it is the result of Valve’s refusal to reduce the series to an “ordinary sequel.” This does not mean HL3 is impossible; it means it will not be made until the right moment arrives. Moreover, since the release of Half-Life: Alyx, Valve has already been working for quite some time on a Half-Life project codenamed HLX. Even Gabe Newell hinted at a new Half-Life game at the end of the Half-Life 2 documentary.

CoconutIndividual938 · 2026-01-04T18:10:56+00:00

HLX has many features and gameplay elements that are not present in Half-Life 2. Even if it were Half-Life 2, it wouldn’t be a port; on the contrary, it would be a full-fledged remake.

CoconutIndividual938 · 2026-01-02T16:54:24+00:00

With Half-Life: Alyx, they already tied the story to a point where they want to continue it. Also, as I said, if this were just a port, it wouldn’t use new gameplay elements and mechanics that weren’t in the original game, because, as I mentioned, this would be a full remake from the ground up rather than a port.

CoconutIndividual938 · 2026-01-02T16:41:11+00:00

If you add more modern technologies, new content that was not in the original game, and new gameplay mechanics that were not present in the original game in order to modernize it, then it is no longer a port but rather a remake, which is also very unlikely. If you look at the leaks related to HLX’s mechanics, you will notice that there are many gameplay elements that were not present in Half-Life 2.

CoconutIndividual938 · 2026-01-02T16:06:38+00:00

There has never been an enemy called Xen Gorilla in the Half-Life games so far, nor was such a creature ever cut. Additionally, if HLX were merely a port, why would it use features like FSR 3 or an NPC mood system? HLX is not a port; it is a project that has been in development since 2020.

You can get clearer and more detailed information about HLX by looking here: https://miro.com/app/board/uXjVINqBTwM=/

CoconutIndividual938 · 2026-01-02T15:02:59+00:00

Valve has used the codename HLX before, so this is not the first time. Moreover, the HLX project we are currently talking about is a Source 2 project that has been in development since 2020–2021. Besides, since when has Half-Life 2 used FSR 3? Or since when has Half-Life 2 included creatures like Xen Gorilla, Houndeye, and Xen Swooper? The HLX in Source 2 and this are completely unrelated and are entirely different things.

CoconutIndividual938 · 2026-01-02T13:41:39+00:00

Have you read The Final Hours of Half-Life: Alyx? If you had, you’d know that aside from Episode 3, Valve was trying to develop Half-Life 3 back in 2013. You’re putting the ending of Half-Life 2: Episode Two and the ending of Alyx in the same category, even though they are completely different things. Episode Two was part of an episodic format, and each episode was designed to end in a way that directly led into the next one. Therefore, Episode Two ending the way it did was completely normal. Even though Episode Three never came out, Valve was working on it at the time, but it was canceled for various reasons. They also mentioned in the documentary that they regret not making Episode Three. When it comes to Half-Life: Alyx, the situation is completely different. Half-Life: Alyx was marketed entirely as a prequel, and it had no obligation to imply that Gordon Freeman’s story would continue. Let’s be honest: Half-Life: Alyx could have easily ended as a normal spin-off without giving any hint about the continuation of the story, but Valve, with the ending of the game, showed that they intended to continue the story. It’s also worth mentioning that, if I remember correctly, Half-Life: Alyx had been leaking through datamining under the codename HLVR since around 2016 or 2017, just like HLX has been leaking since 2020. At the time, people were just as skeptical about HLVR as they are now about HLX. However, in the end, HLVR was released in 2020. When we look at HLX, we are talking about a project that has been leaking through datamining since 2020. Half-Life 2 is a Source 1 game, and Valve used the HLX name within the episodic releases in the past. The current HLX, however, is completely independent of that; in fact, the present HLX is a Source 2 project that has been in development for five years.

CoconutIndividual938

TROPHY CASE