- Nov 27, 2017
- 1,204
- 1,403
how did we use this ?[Core.System]
Paths=../../../Engine/Content
Paths=%GAMEDIR%Content
Paths=%GAMEDIR%DataTables
Paths=../../../Engine/Plugins/2D/Paper2D/Content
Paths=../../../Engine/Plugins/Animation/ControlRigSpline/Content
Paths=../../../Engine/Plugins/Animation/ControlRig/Content
Paths=../../../Engine/Plugins/Animation/IKRig/Content
Paths=../../../Engine/Plugins/Bridge/Content
Paths=../../../Engine/Plugins/Developer/AnimationSharing/Content
Paths=../../../Engine/Plugins/Editor/BlueprintHeaderView/Content
Paths=../../../Engine/Plugins/Editor/GeometryMode/Content
Paths=../../../Engine/Plugins/Editor/ObjectMixer/LightMixer/Content
Paths=../../../Engine/Plugins/Editor/ObjectMixer/ObjectMixer/Content
Paths=../../../Engine/Plugins/Editor/SpeedTreeImporter/Content
Paths=../../../Engine/Plugins/Enterprise/DatasmithContent/Content
Paths=../../../Engine/Plugins/Enterprise/GLTFExporter/Content
Paths=../../../Engine/Plugins/Experimental/ChaosCaching/Content
Paths=../../../Engine/Plugins/Experimental/ChaosClothEditor/Content
Paths=../../../Engine/Plugins/Experimental/ChaosNiagara/Content
Paths=../../../Engine/Plugins/Experimental/ChaosSolverPlugin/Content
Paths=../../../Engine/Plugins/Experimental/Dataflow/Content
Paths=../../../Engine/Plugins/Experimental/FullBodyIK/Content
Paths=../../../Engine/Plugins/Experimental/GeometryCollectionPlugin/Content
Paths=../../../Engine/Plugins/Experimental/PythonScriptPlugin/Content
Paths=../../../Engine/Plugins/Experimental/UVEditor/Content
Paths=../../../Engine/Plugins/FX/Niagara/Content
Paths=../../../Engine/Plugins/Marketplace/ThumbnailGenerator/Content
Paths=../../../Engine/Plugins/Media/MediaCompositing/Content
Paths=../../../Engine/Plugins/Media/MediaPlate/Content
Paths=../../../Engine/Plugins/MovieScene/SequencerScripting/Content
Paths=../../../Engine/Plugins/Runtime/AudioSynesthesia/Content
Paths=../../../Engine/Plugins/Runtime/AudioWidgets/Content
Paths=../../../Engine/Plugins/Runtime/GeometryProcessing/Content
Paths=../../../Engine/Plugins/Runtime/Metasound/Content
Paths=../../../Engine/Plugins/Runtime/OpenXR/Content
Paths=../../../Engine/Plugins/Runtime/ResonanceAudio/Content
Paths=../../../Engine/Plugins/Runtime/Synthesis/Content
Paths=../../../Engine/Plugins/Runtime/WaveTable/Content
Paths=../../../Engine/Plugins/VirtualProduction/Takes/Content
Paths=../../../WildLifeC/Plugins/AnimGraphExtension/Content
Paths=../../../WildLifeC/Plugins/CVNUtilities/Content
Paths=../../../WildLifeC/Plugins/DragonIK/Content
Paths=../../../WildLifeC/Plugins/GFurPRO/Content
Paths=../../../WildLifeC/Plugins/GameDetailCustomizations/Content
Paths=../../../WildLifeC/Plugins/ImpostorBaker-master/Content
Paths=../../../WildLifeC/Plugins/LoadingScreen/Content
Paths=../../../WildLifeC/Plugins/LovenseIntegration/Content
Paths=../../../WildLifeC/Plugins/Oceanology_Plugin/Content
Paths=../../../WildLifeC/Plugins/Prefabricator/Content
Paths=../../../WildLifeC/Plugins/RuntimeMeshLoader/Content
Paths=../../../WildLifeC/Plugins/Runtime/Substance/Content
Paths=../../../WildLifeC/Plugins/VictoryUMG/Content
Paths=../../../WildLifeC/Plugins/Wwise/Content
Paths=../../../Engine/Plugins/Animation/AnimationLocomotionLibrary/Content
Paths=../../../Engine/Plugins/Animation/AnimationWarping/Content
Paths=../../../Engine/Plugins/Developer/TraceSourceFiltering/Content
Paths=../../../Engine/Plugins/Editor/ModelingToolsEditorMode/Content
Paths=../../../Engine/Plugins/Enterprise/DataprepEditor/Content
Paths=../../../WildLifeC/Plugins/DLSS/Content
Paths=../../../WildLifeC/Plugins/KantanCharts/Content
Paths=../../../WildLifeC/Plugins/PerformanceBenchTest/Content
Paths=../../../Engine/Plugins/Compositing/OpenColorIO/Content
Paths=../../../Engine/Plugins/Marketplace/FSR2MovieRenderPipeline/Content
Paths=../../../Engine/Plugins/Marketplace/FSR2/Content
Paths=../../../Engine/Plugins/MovieScene/MovieRenderPipeline/Content
[/Script/Engine.RendererSettings]
r.Shadow.Virtual.Enable=0
UE5, they are obviously not gonna release new updates for the old engineupdate is out for UE4 or only for UE5
What?the problem of games like this one , is that they started developing 20129301 years ago and when they want to update all to new tec. they have to remake a lot of things, man such a pity, it seems like nobody can make a nice UE porn game
Those spinners in the thread are the Halo fandom and the sonic fandom combined by nowThey literally just released new quests, you people are a broken disc at this point, try to keep up to date before coming here to complain or ask the same question over and over
Welp, I finally tried the UE5 build for the first time, and I have to give it credit for being the first game in four years to lock up my system so badly I had to use the physical reset button on my pc. Guess I'm stuck on the old UE4 builds for the forseeable future
Holy fuck, is the UE5 version that bad? I was going to give a try on the UE5 with my 1050 ti, most of the time I played without problems in the UE4 version, medium-high, in the sandbox to be precise, had my fun but after this I'm kinda worriedFor me, it seems that the UE5 version is more demanding than Elden Ring.
Not surprising. I'm able to run Elden Ring at ~45 fps on high and I was getting well under 10 on high settings in Wild Life's last update. I figured it was temporary and it was going to become less comically bad next update, is that at least the case? I don't want to waste my time with this until they at least make it function for people who don't have absolute top-of-the-line hardwareFor me, it seems that the UE5 version is more demanding than Elden Ring.
I also have a 1050 ti, though my CPU is where things bottleneck (FX-8320, released in 2012). The UE4 version I can run at 60 FPS in the showroom with light to medium amount of props, while still getting around 30 FPS average everywhere else with everything on epic. The UE5 version though... The showroom still ran okay, maybe 45 FPS. The Old Wild Life map is completely gutted, no textures, no caves no props, so I couldn't use that one. The New Map is filled with props and any time I spawned in or went to a prop-heavy area the game just died. Even getting outside of the prop-heavy areas, the map just ran like shit. This was after I made sure that the FPS limit was at 60 (it defaults to enabled at 20 FPS for some reason?).Holy fuck, is the UE5 version that bad? I was going to give a try on the UE5 with my 1050 ti, most of the time I played without problems in the UE4 version, medium-high, in the sandbox to be precise, had my fun but after this I'm kinda worried