r/Sourceengine2 • • Dec 16 '20

Half Life Alyx Tutorial - Putting items on Entities

22 Upvotes

r/Sourceengine2 • • Feb 04 '20

Unconfirmed Source 2 is coming to CSGO?

Post image
22 Upvotes

r/Sourceengine2 • • Dec 30 '18

We could be modding Source 2 right now... but there's a catch

22 Upvotes

It is possible to create a makeshift Source 2 SDK by using the SteamVR Performance Test/Aperture Robot Repair Demo as a base, and using a specific version of the Dota 2 SDK to fix compatibility issues. It is possible to gain these specific version of the Dota 2 SDK by using Depot Downloading, however I have issues with this as downloading depots can be unstable for unknown reasons, but fine for others. I cannot seem to download the necessary depots myself, I need help.

Downloading depots can be unstable as even a single error in the download can halt the download completely and have you restart.

The SteamVR Performance Test/Aperture Robot Repair are very identical and both seem to have all/most Half-Life 2 entities ported over.

This server was created 10 months ago and started off strong but has unfortunately died off due to the lack of help and personal interest of my peers. Any help is appreciated.

https://discord.gg/rDPjZMz


r/Sourceengine2 • • Mar 09 '18

Artifact will use Source 2, bringing the engine to iOS and Android

22 Upvotes

https://www.pcgamesn.com/artifact/artifact-source-2-ios-android

https://www.youtube.com/watch?v=Vr9kE7vT1hE

Valve mentioned before that Source 2 SDK will release alongside a fully-developed Source 2 game. Could this, dare I say, be it?


r/Sourceengine2 • • Aug 30 '16

Review of existing engines and why I think Source 2 could fill a certain sweetspot

22 Upvotes

I love talking about game engines.

And since every day is slow news day on this subreddit, I felt like aimlessly talking about current engines and speculating on totally unfounded Source 2 expectations. This thread is meant to be a general place where we share opinions on all that, with no particular goal.

Here's my personal review of current engines:

Unity:

  • Pros: Clean and intuitive API, Very extensible rendering pipeline, huge active community, pleasant and fast to work with (you never really have to spend hours looking up how to do seemingly simple things... or even complex things), ideal for developing advanced/experimental technical features or going crazy with shaders due to how versatile and well-structured it is, has some of the most helpful documentation I have ever seen

  • Cons: Underwhelming tools and features that seem buggy or outdated or perpetually stuck in alpha, no decent networking solution (UNET still too buggy, slow and convoluted), Unity's business model is kinda detrimental to the engine's quality (their focus is on services, asset store sales, and mobile devs), no source code access, performance in general is usually lackluster because Unity tries to support too many things for its own good

UE4:

  • Pros: Extremely rich tools and features, very robust and battle-tested, excellent rendering quality out of the box, best built-in networking solution of all these engines, best community management EVER, source code access, Unlike Unity... Epic uses its engine to develop actual high-quality games instead of realtime movies like Adam so you just know you're not making a mistake by choosing this engine. You've got the solid proof that it works wonderfully well and can handle a lot

  • Cons: Its general design philosophy is to try to fill the engine with every possible tool and feature instead of making it easy and intuitive for devs to make their own solutions for their specific needs (that's one area where I really like Unity more), "Unreal Magic" makes coding incredibly confusing and gives off an impression of convolutedness, obsessive focus on blueprints makes C++ coding treated like a second class citizen with very little documentation/examples, codebase is so huge that it takes forever for intellisense to kick in, the rendering/shader pipeline is very rigid and is a nightmare to extend, editor extensions/plugins are a nightmare too, lots of bloat and game-specific stuff that should be cleaned out, has royalties

Cryengine 5:

  • I messed around in CE5 for a few hours, but I just can't see how it'd be a better choice than UE4. Yes, coding looks much less messy than in UE4, and no-royalties is nice, but feature-wise and workflow-wise it really pales in comparison to UE4. I also really don't like how working in Cryengine pretty much just feels like modding Crysis instead of making your own original project. It does have one of the few great realtime GI solutions in the industry, but I don't think it's worth it. Most people don't have the right hardware for any kind of realtime GI yet, unless you really want your game to run at a sluggish 30fps.

Lumberyard:

  • Lumberyard is a branch of Cryengine 3 maintained and built-upon by Amazon, so most of what I said about Cryengine applies to this too. The main differences are that Lumberyard is built around Amazon's web services compatibility, and that it feels a bit more clean than CryEngine (in the sense that it doesn't just look like a Crysis modding tool). Its community/support also seems to be completely dead and barren, which is never a good thing. And also, the few posts it has on its forums complain about lots of unnecessary complications and obvious missing features. It doesn't even have a proper FBX importer, because their original plan was to cater to AAAs who only use Max/Maya, and their plan backfired. It definitely looks like it has some pretty powerful rendering capabilities, but overall; not looking too great right now. I'm still keeping an eye on it, though, because it's still very new and might become way better with time. Amazon's Lumberyard team seems to be working on plenty of nice things atm.

Stingray:

  • Even though it failed to gain any real traction ever since it was released, Stingray is actually a pretty nice engine. It's very clean, well-structured, powerful and made to be extensible easily. The tech leads of the engine maintain a fascinating dev blog (bitsquid.blogspot.com) that proves they are on the right track in terms of general design philosophy and goals for Stingray. It's just really unfortunate that it is in Autodesk's hands. They seem to manage this product very poorly so far, almost like they don't pay attention to it at all, and they refuse to get with the times in terms of business model. It also lacks a proper networking system. Another problem is that I can't really imagine a bright future for this engine and that's sort of off-putting. It doesn't have much of a dev community, and Autodesk even downsized and fired tons of people recently, which isn't too encouraging. I'd rather invest in learning a game engine that will have a great dev community and stay supported for a very long time. But.... were it not for Autodesk's very poor product/community management, this could've potentially been my favorite engine out there

Xenko:

  • This one is a promising newcomer. C# engine with extensible rendering pipeline. However, it is very unproven and most likely lacking in features/tools. I wouldn't feel too comfortable starting a project on this without spending a few months with it beforehand.

Godot:

  • A free, open-source game engine that is surprisingly good for what it is... but considering all the other alternatives available to us, I see no good reason to choose this engine over the others, unless you're really hell-bent on not paying anything for the engine and doing anything you want with it.


In my mind, there's only 2 main contenders right now. Unity and UE4. Basically Unity is great because it's clean, fast and versatile, and UE4 is great because it's a powerful engine. But they both have their problems. None of those problems are complete dealbreakers, but it still makes me wish for an engine that gets these things right from the start, so that instead of wasting a year trying to fix it, I can fully focus on making a good game. And this is the reason why I'm excited for Source 2. When I look at what I want and don't want in an engine, it actually seems pretty realistic for Source 2 to get most of it right.

Source 2:

Here's what we know for sure Source 2 will get right:

  • Full source code

  • No royalties, fees, or constraints except releasing at least on Steam (which is what everyone would do anyway)

  • C++ and lua, which is probably the ideal combination for coding

  • Great Vulkan integration (Valve has played a meaningful role in the development of Vulkan)

  • Backed by a company with tons of resources and that knows what it's doing

  • A healthy dev community (not a fact, I know, but it's almost unavoidable)

Here's what I'm fairly confident Source 2 will get right:

  • Have a suite of professional tools that at the very least out-matches Unity's. Gabe mentioned that making efficient dev-friendly tools was their goal with Source 2.

  • Have a powerful built-in networking system beautifully integrated with Steam. Can't go wrong in that department with the engine behind CSGO, TF2 and Dota2

Here's where I think Source 2 might be in trouble:

  • Communication. This is Valve's ultimate weakness. Frequent blog updates, public roadmaps, weekly twitch training sessions, good dev presence in the forums, etc... are a very large part of Unity and UE4's success. And I think Valve is highly at risk to be terrible at this

  • Modern workflow. Source was infamous among game devs for bieng a little archaic, even back when it was still new. If Source 2 is just stuff added on top of Source 1 without rewriting much of the engine, chances are this won't change

  • Gabe has been pretty vocal about user-generated content being one of the focuses of Source 2. Let's hope it can really stand on its own as a proper game engine and not just as a cool modding tool for Valve's existing games


r/Sourceengine2 • • Nov 22 '19

A source 2 Gmod would be epic

21 Upvotes

r/Sourceengine2 • • Oct 21 '19

The #1 Thing I Miss Working With Source

21 Upvotes

So, I’ve had a few game ideas I’ve wanted to create for... years. Like, a lot of years. I could prototype in Source and Gmod and was generally really quick and fun.

I still can do that, but I sort of got sick of how broken Source is and the fact that it can’t actually do most of the things I want it to. It’s just showing its age and lacks the tools needed to really dig in deep.

I’ve been learning UE4 off and on for a few years and realized I miss how fast and elegant working in Hammer can be. But one feature, out of everything I really feel the loss of.

The IO system.

The IO system was/is such a fast and intuitive way to create pretty much anything. From something as simple as opening a door, to some really complex systems like having a camera network that actively tracks a target and switches cameras based on trigger volumes. It’s actually amazing how powerful the IO system is.

The craziest thing I realized switching to UE was just how much time something simple, like opening a door , can take a LONG time to make work. Yes, it gives you a ton of control over everything, but sometimes you just want a quick and easy way to prototype ideas.

I waited years for a proper Source2 SDK but realized it wasn’t coming. Or that Valve just do not care about releasing it, which is why I moved on. But damn, I miss the IO system in the Source SDK.

Although, with Epic being so dirty in how they’re playing the market I feel a little gross working with their engine. Gives me a glimmer of hope that MAYBE Valve will step up and actually put out a full Source 2 engine and provide some financial incentives to release games on Steam again. Their no licensing fee for using Source was a joke since no one uses it for making games, but we need more options.

Sadly, it’s clear Valve don’t see Epic as a threat and don’t appear to be doing anything about their new competitor. :(


r/Sourceengine2 • • Apr 13 '17

Can someone who speaks chinese confirm the translations for these slides concerning source 2?

Thumbnail
imgur.com
21 Upvotes

r/Sourceengine2 • • Jan 17 '17

Gabe on Source 2

21 Upvotes

We are continuing to use Source 2 as our primary game development environment. Aside from moving Dota 2 to the engine recently, we are are using it as the foundation of some unannounced products. We would like to have everyone working on games here at Valve to eventually be using the same engine. We also intend to continue to make the Source 2 engine work available to the broad developer community as we go, and to make it available free of charge.

https://www.reddit.com/r/The_Gaben/comments/5olhj4/hi_im_gabe_newell_ama/dck7yd7/


r/Sourceengine2 • • Nov 21 '20

Tutorial How to Transition to Source 2: Advanced Mapping Concepts

Thumbnail
youtube.com
19 Upvotes

r/Sourceengine2 • • Jun 02 '20

Showcase "An Evening With Source Engine 2"

Thumbnail
twitter.com
19 Upvotes

r/Sourceengine2 • • Apr 23 '20

What would be the main obstacles importing Black Mesa to Source 2?

19 Upvotes

My friends and I were thinking about this so Black Mesa can have actual ambient occlusion and better optimized outdoor lighting in general.


r/Sourceengine2 • • Apr 10 '20

S2FM gave up, help S2FM just gave up on me all of a sudden, everything was working perfectly then this happened, even when tryna make a new folder/addon and making a map with the default assets without my custom stuff

Post image
19 Upvotes

r/Sourceengine2 • • Apr 02 '20

Super Beginner Friendly Tutorial!

Thumbnail
youtu.be
19 Upvotes

r/Sourceengine2 • • Jan 22 '20

NEWS: More in comments "We're not currently planning on shipping a full SDK" -Valve

Thumbnail old.reddit.com
19 Upvotes

r/Sourceengine2 • • May 19 '16

Valve Is Finally Releasing Dota 2 With Vulkan Support Very Soon

Thumbnail
phoronix.com
19 Upvotes

r/Sourceengine2 • • Jun 08 '20

i dont actually have Source 2 but i need to know this

18 Upvotes

is there OBSOLETE in Source 2?


r/Sourceengine2 • • Jun 10 '17

Map Hammer Editor - Sourse 2 «Chinatower»

Thumbnail
youtu.be
18 Upvotes

r/Sourceengine2 • • Dec 18 '16

What games currently use Source 2?

18 Upvotes

I was just curious. I don't know much about source 2.


r/Sourceengine2 • • Mar 18 '15

Podcast interview with Gabe Newell and Erik Johnson, Source 2 plans @ 36:42

Thumbnail
soundcloud.com
18 Upvotes

r/Sourceengine2 • • Mar 22 '23

Map CS2 with Source2 engine and map making tools...

Thumbnail
youtube.com
17 Upvotes

r/Sourceengine2 • • Mar 18 '20

Model imma be making a sonic fan-mod for source 2 when half life alyx is out (ofc in non-vr) cuz i wanna use the engine and its cool shit to its limits

Post image
17 Upvotes

r/Sourceengine2 • • Aug 19 '18

CSGO Source 2 imminent?

17 Upvotes

Purely speculation, but these patch notes caught my attention:

the Scaleform launch option was changed, and now it's only available "for a very limited time"

the .exe was modified enough that it can upset antivirus. perhaps it's in preparation to load new software...


r/Sourceengine2 • • Jul 13 '18

de_dust2 Source 2 engine

17 Upvotes

Apparently nobody has posted this yet but de_dust2 was being developed in source engine 2 based on this screenshots from the contract developer.

Roger, mapper from Turtle Rock Studios:

http://alternateground.com/?project=csgo-de_dust2

Video explanation from Valve News Network:

https://www.youtube.com/watch?v=1xZJ4v2ykdw

Screenshots below:


r/Sourceengine2 • • Aug 01 '17

Source 2 - What we know so far

17 Upvotes

In this post I just wanted to ask you guys what we know so far about Source 2, what games use it, info from interviews, etc. What has actually been told about Source 2?

What I noticed that I haven't seen anywhere else is, with the context that I heard rumors Source Filmmaker will be using Source 2, that now for some reason I fired up SFM where it seems to use the Beta (without the DOTA workshop stuff). Just straight from the Source Filmmaker download. I know that there are not too many updates on SFM lately, but there seems to be something cooking right here.