Does new GoToDefinition() on blueprint node works for anyone?
For me it’s open new instance of Visual Studio (although I had it already open) and doesn’t even open header file. Not working at all…
Will you be releasing a hotfix relatively soon for 4.18? The engine not only randomly crashes during VR Preview, but also when I compile blueprints. The frequency of the crashes has made it nearly impossible for me to keep building.
from 4.15 to 4.18 you may have a lot more work required then just right click and choose “change engine version”.
Tho, step 1 is “change engine version”. You may find your blueprints fairly broken up and most your 4.15 assets dont work (due to nodes being not used anymore, or whatever). Just be prepared for something like that with such a big jump in versions.
Prior to this morning, I had 4.11.0 installed. I’ve been having quite a time getting 4.18 installed. Apart from a bit of fiddling with it a year or so ago, I have nothing of any importance that would be lost or impacted by a complete uninstall and reinstall, and it sounds like that is the wise choice.
But now here is the wrinkle: I uninstalled using the program manager in windows. There was still an Epic Games directory but I left it. Now that I’ve clicked the install 4.18 link, my launcher is stuck in a snails pace process showing me “Installing UE 4.11.2”
ADDIT: ah I figured out what my problem was: I had VS 2015 installed and everything after 4.15 requires VS 2017.
Should be soon… There are already 33 or so commits of fixes… See here: .com/EpicGames/UnrealEngine/commits/4.18 to see if your is listed.
teak
I second that, while I think static lighting has it’s place, it is indeed really painful to see how neglected dynamic lighting is. And I see nothing that gives me hope of it changing anytime in the near future sadly. 
At this point I am already thinking of switching to CryEngine (or the Amazon version) for the next project, even though it would be a pain to relearn everything.
Can 4.19 be focussed on dynamic lighting please?
Do you mean dynamic shadows (as they are super slow, especially in VR) ?
So dynamic shaders are just slow in general in unreal? And here I thought I was doing something wrong.
Lighting development does tend to cycle between improving static lighting and dynamic lighting. There’s so much to do and so few people.
Earlier this year we made a major push to get dynamic lighting features used in Fortnite running well on consoles and mid spec PC. We made a huge number of optimizations and cross platform fixes. Those dynamic lighting features are: Cascaded Shadow Maps, Cached Whole Scene Shadows (4.13), Distance field AO optimizations (4.16), Ray Traced DF Shadow optimizations (4.16), Volumetric Fog (4.16), LOD for many dynamic lights (r.LightMaxDrawDistanceScale), Capsule Indirect Shadows. That’s a lot! Any UE4 project using dynamic lighting and shadowing benefits hugely from these optimizations.
Right now we’re filling in some holes in the Static lighting and making sure that’s world class. Focus on dynamic lighting will come back around again.
All that’s appreciated.
I think current situation of baked lighting in UE4 already suffice vast majority of projects utilizing baked lighting. But when it comes to those utilizing dynamic lighting, there’s really a big disappointment.
- Sun (directional light) still isn’t physically based. That’s a major block in way of achieving realism and staying “correct”.
- There is no Time of Day editor.
- CSM blocky shadowing still isn’t fixed. See hereand here.
- There’s no proper localized Image Based Lighting support.
- LPVs are neither production ready nor receiving any major improvements.
- For some reason ShadowDepths cost a ton as soon as a dynamic light interacts with a tessellated material.
Etc.
I get that nor Fortnite neither Paragon would’ve benefited from any of this given one is heavily stylized and the other is an arena shooter within an static environment. But majority of projects these days are leaning towards fully dynamic environments and thus while UE4’s baked lighting is pushing to be world class, it’s dynamic lighting features are still way behind 2007.
Not blaming you for anything. Just think there could’ve been more balance between the two.
Well I am quite skeptical with this… because not many projects are actually needing this although it sounds cool. I definitely welcome Epic integrating properly fully dynamic environment lighting but most of the projects can do with static lighting, and therefore make themselves more available to lower end machine…
We can continue using baked lighting and create static environments for another decade however, it’s not a matter of whether we can or cannot. It’s a matter of the direction the entire industry is taking. Most engines these days are going towards fully dynamic lighting regardless of it being possible to use baked lighting.
Just saw this: https://80.lv/articles/ssrtgi-toughe…-real-time-3d/ Food for thought.
You can’t just “not have the dynamic lighting features” and keep claiming most projects wouldn’t need them. Nobody wants to spend an eternity on baking lighting for open world games so they’re forced to not use it, but then dynamic lighting in UE4 even lacks the basics, as mentioned in my previous post. Today UE4 is ~10 years behind regarding dynamic lighting compared to other engines it’s because baked lighting took all the focus and dynamic features weren’t valued much.
I don’t want to continue the debate here because it simply gets us nothing. But as a person who used to work with a 2007 engine and then switched to UE4, I instantly felt the ongoing lack of dynamic lighting features which is still going on year after year.
Thank you for using the native resolution for rendering the UI on Retina display Macs! It’s just such a small detail but the editor is now a lot more enjoyable to work with without that ugly low resolution font rendering. And it feels kinda snappier. Well done! 
That’s Unigine Engine, made by a Russian company who is heavily into all kind of simulators. Thus, they have to have support for massive worlds and photorealistic real-time lighting. Those kind of projects pay their bills and so that’s where their dev focus is. If you want to make a game with that engine, well, good luck with that (I had a license for v1).
While I am in no way oppose fast and good looking real-time lighting (GI in particular), UE4 is a cross platform engine made for games/entertainment first and foremost, and I don’t think consoles can pull real time lighting efficiently. I’d rather have more features added to forward rendering and have high-performance dynamic shadows than real-time GI.
I wonder when hotfix #1 is coming to 4.18…
I think you missed the point. I linked that article to show where advances in real-time lighting are getting at. I didn’t imply Epic should give us dynamic GI right now. -high-performance dynamic shadows- isn’t anything apart from what I said a bit earlier. Let me quote myself:
“6. For some reason ShadowDepths cost a ton as soon as a dynamic light interacts with a tessellated material.”
So I said exactly that. And that’s not going to receive any improvements as long as baked lighting is Epic’s main focus due to their internal projects needing no advances in real-time lighting. Sadly, For some reason Epic doesn’t want to try and get their feet wet on open-world / large-outdoors and that’s the #1 factor why everything is lacking on that end. (be it open world tools or outdoor lighting).
My whole point is that UE4’s baked lighting has got way ahead of it’s dynamic lighting to a point where those who use baked lighting really achieve what they want but those who use dynamic lighting are all tied up by performance issues or lack of features.
So, now that static lighting has achieved world class, you’ll switch back to improving dynamic lighting for the next releases?
Has anyone had any issues with Steam not being able to create sessions? We ungraded today and it appears that sessions are failing to be created, although the create session callback returns true and loads the level.
Note: We found the. We were hard coding the session name with a specified FName, the patch notes mentioned there were changes with a new NAME_GameSession. Changing the Game Session to the #define GameSessionName has solved this. The blueprint Node destroys the game session by NAME_GameSession.
I think the most successful games made with UE4 (Ark and PUBG I would guess, Fortnite BR regarding the amount of players too) use dynamic lighting. People want to have games with huge open worlds, and those have to use dynamic lighting. Also, almost every single game can benefit from a dynamic time of day, even games that are fully indoor with only light coming through the windows. So even games like Paragon or Unreal Tournament would immediately look more dynamic and interesting.
Baked lighting is severely limiting the available gameplay a game can have. For example can’t have dynamic destruction of things like buildings, since its baked. So baked lighting should really be used for almost no games any more. I do see that it makes a lot of sense for architectural visualization and that’s what these world class features that UE4 recently got are mostly used for I think. UE4 is definitely the best engine for any arch viz, because it has this really perfect baked lighting. But almost any existing and future game would be better with dynamic lighting.
Back to lighting.
I personally would like to get some middle-ground. In most games, most of environment is static (even if parts of it are destructible). But lights tends to be dynamic (moving player with light, time of day, etc).
What I’d like to see is some precomputed lighting solution that works with dynamic lights, but with mostly static geometry. Recently there were some interesting papers released about baking light transport in sparse way (so It doesn’t take ■■■■ load of memory and space).
Fully dynamic GI solution is probably out of question (not enough man power, to maintain it), but precomputed one + Scree Space, cloud be nice. (and it cloud eventually replace lightmass).