- Jun 8, 2020
- 243
- 113
Unreal Engine Wild Life [2024.12.13 Full Build 1] [Adeptus Steve]
- Thread starter Pepé Le Pew
- Start date
- Oct 30, 2019
- 516
- 442
Patreon lasting through next year is a rather dubious proposition. If I was steve I would be getting contingencies, both legal and financial in place now, not later.
- Dec 1, 2018
- 2,169
- 2,089
It can never be something entire different from Nvidias Main architectural path Nvidia just started to add more and more fixed function
And with Ampere they need a much more stable power supply and memory bandwidth modifications on the pcb design level now wich lacked both up to turing
The PCB gets a heavy redesign i compare Ampere to the Introduction of Pascal it is the same huge tock with everything in a improved step to what we saw in Turing.
Maxwell 1/2 = ticks
Pascal = tock
Turing = tick (beta)
Ampere = tock (final)
RDNA 2 = huge tock improving on everything from rasterization to further improving Low Level APIs Async workloads to Raytracing in those Async workloads.
I wait for Sony and AMD presenting their DLSS solution, once that happens DLSS 3.0 wont have that huge Performance benefit anymore on the lower tiers
The upcoming war will be Nvidias Tensor war they will push DLSS 3.0 in the forefront of the Reviews it can save extreme amount of resources per Frame in UHD compared to any current 3rd party studio solution that can then be utilized for other Workloads (more complex physics).
And now that the Power Problems are solved between Rasterizer and Tensor/RT/VPX cores they wont kill each other under full load battling for Power resources anymore like they do on the Turing PCBs.
But therefore you will see Nvidias most Power hungriest design since a while after they improved everything for Tegra after the Fermisaster.
And yeah im on Pascal Turing wasn't impressive at all in it's beta cost reduction maximum profit stage but yeah Ampere or RDNA 2 the next choice to make.
Last edited:
why are such black lines coming out
my system:
AMD Radeon HD 6800 Series
AMD Athlon II x4 630 processor 2.80 GHz
16Gb Ram
Win7Ult
DirectX11
my system:
AMD Radeon HD 6800 Series
AMD Athlon II x4 630 processor 2.80 GHz
16Gb Ram
Win7Ult
DirectX11
Might have something to do with...
The 10 year old card.
The 11 year old processor.
It's a miracle you even got that far and you seriously, seriously need to update that thing.
I was playing previous versions without error, the black lines weren't coming out.
Not every build will be as stable as the last you played, just a simple fact when creating a game. Something they've changed or added is making your setup have a stroke. Be kinda hard to diagnose a fix when the first most obvious issue is simply the age of your hardware.
Just out of curiosity, how many frames do you actually play at even on the lowest setting? I'd be surprised if it went above 15 fps and wasn't constantly choppy.
I'd also finish with simply saying this.
Save up, and buy yourself a decent rig/laptop at least within 2 (edited out 5 as it's still too old imo) years of current year. You will absolutely not be able to play this game when it's fully released. I understand that optimization is obviously a moving target right now, but the games also completely barren. So there will come a time when that rig is no longer able to keep up. You just now hit that threshold by some miracle.
Last edited:
- Jul 27, 2017
- 361
- 277
This version is considerably more demanding, it does look better so it's not for no reason but i'm not surprised if lower end systems can't handle it anymore, it cut my FPS almost in half in the village compared to earlier versions.
I'm noticing more lost frames and stability issues compared to the last even on my hardware. The game sure does look pretty though.
That is interesting, I saw in the discord that some people brought this up and the dev posted a comparison gif showing fps and look of may vs july version. Looks like it has no fps difference for them.
Probably not standing at the start and not moving. I don't notice a steady fps change, but simply lost frames when flying over the town. Whereas before I never dipped outside of the initial startup process.That is interesting, I saw in the discord that some people brought this up and the dev posted a comparison gif showing fps and look of may vs july version. Looks like it has no fps difference for them.
It's fine, not game breaking or anything for me, just a small note to take as their systems are not everyone else's. I won't even pretend my pc is as good as the one they used to do this static test.
Optimization will obviously clean up the small issues some of us are having.
- Dec 1, 2018
- 2,169
- 2,089
It's not the first Report of this problem and before it was AMD also but not as old as Barts VLIW and actually GCN 7000 (GCN) series if im not unsure
But it is the 2nd time now these artifacts come up with AMD Hardware and in Wild-Life running context specifically.
Though in General Unreal will work better on Nvidia Hardware through their older Generations, but for AMD it's not a given to work on anything before GCN.
Epic started first when the Consoles came out to really optimize for AMD Hardware specifically Paragon was the very first more AMD optimized Engine Build for GCN starting to erradicate lot of Nvidias investments out of the Engine into generic agnostic functioning systems.
Everything pre GCN is pretty much not supported by anyone anymore for AMD you either have luck that it works or at the lowest problem level have to live with artifacts.
Also neither the AMD Driver Teams priority lies within anything then PRE GCN to fix specifically.
Tough in this case of the 7000 Series Southern Island is GCNs first iteration away from the VLIW architecture to Nvidias Scalar approach.
This bug is strange but it seems to play specifically out on the Directx Shader Model Layer and the AMD Compiler.
ekomatik
try to test different drivers pre Adrenalin
GCN was a really big step even bigger then RDNA 2 that is upcoming, pre GCN like your HD 6800 Series, if it works be happy if it doesn't it's like it is.
But this is why i like to keep Wild-Life as a very specific stability test case, compared to other indie Unreal projects
In their overall complexity Wild-Life plays on a very high level and Epics ongoing progress to get the Engine Rock stable on the Next Generation Consoles (RDNA 2) with the Unreal 5 big data refactoring which we see continuing.
Best optimized Low level GCN Engine no doubt = IDTech7 and it runs on Nvidia equally amazing (absolute master class hardware optimization work in which direction Unreal 5 is starting to heading)
For everyone Unreal 4.22 was a very important core Performance refactoring release making room for more additional overhead into the Engine.
Last edited:
Nope. Would be a neat feature to add, though. May require some minor touch-ups for some animations.
- Jul 8, 2018
- 6
- 19
- Dec 1, 2018
- 2,169
- 2,089
Different ways to visualize it simplest would be just to brake the camera clipping plane and shade in front of it different
Well, when I said touch-ups, I was thinking about the way the penis enters the body and what happens after that. Steve probably doesn't pay a lot of attention to that when making the animations, since it is normally not visible. It would mainly be a concern with the minotaur and rhino. I remember seeing a stream where he had to fix the penis clipping out of the back of the neck with a blowjob animation with the minotaur.