- Jul 21, 2019
- 6
- 3
I'm also having a problem in game where the mouse is offset during menu selections making most dialog choices and menus unusable
It's been a decade since I last saw the classic window style.Here for me, this trial version cannot be played.
I already updated c ++, tried to change dlls, tried to run on another operating system (Win10), but nothing corrects this problem. This has never happened before in any previous version.
I think I'll have to wait for another version or purchase another PC. ( Never ). Very sad.
Customization exists, just possess any of the pre made characters and press I.Does anyone know if character customization is planned?
Choosing a pre-made one sucks.
Temperatures seem ok to me, I'm only getting 66 degrees maximum on my GPU in a very intensive area. The framerate does seem worse though, I'm now getting around 40 fps in a spot where I used to get 50 fps.in the penultimate build the performance was excellent. in this build, in the new oasis, it's horrible. the temperatures are not acceptable in the long run. the graphics with the fog looks fantastic but the temperatures of the graphics card are extremely high. 93 degrees in hotspot is just too high.
Strange, Im getting 40 where I used to get 35. Mine got betterI'm now getting around 40 fps in a spot where I used to get 50 fps.
AMD and Unreal Engine games really don't like eachother (it's better now than it has been, but there is still room for improvement). Try turning down the view distance in game (don't need that anyway for closeup scenes) and turn on Radeon Chill (set your min/max FPS like 60-90). That helped me a lot on my RX 5700 XT @1440p.right. for the first generation of vega64 the temperature would be ok. but i have the second generation. this card makes even in ghost recon wildlands on epic settings in 4K resolution maximum 70 degrees. the performance in WildLife is horrible, everyone who plays on epic will confirm that.
and my case has 16 fans, cpu is water cooled, i have very low temperatures in every other game.
anyone who says the vega64 is an oven has either never had one or is unable to configure it properly. if you undervoltage this card you get more power and the temperatures are fantastic.
you can see on my photo that the vega in idle is only 22 degrees, which is absolutely perfect for cooling.
Fuck, game doesn't run under win 7 anymore! Steve, are you nuts?
1.) Go to C:\Windows\System32\ and copy xinput1_3.dll.
2.) Paste xinput1_3.dll into the same folder as your Wild Life .exe, and rename it to xinput1_4.dll
3.) Launch the game
They where pretty heavily forced to else they would have lost the Consoles completely Epic is a very deep Research Partner of Nvidia.AMD and Unreal Engine games really don't like eachother (it's better now than it has been, but there is still room for improvement). Try turning down the view distance in game (don't need that anyway for closeup scenes) and turn on Radeon Chill (set your min/max FPS like 60-90). That helped me a lot on my RX 5700 XT @1440p.
P.S. Your GPU is only 61°C , it's a hotspot that is 93°C (could be a MOSFET or some other power regulating part.)
Unfortunately not every Indie Dev understands the relation between components and Compilers and the Windows SDKs.Fuck, game doesn't run under win 7 anymore! Steve, are you nuts?
it isn't a critical Dependency it is pretty insane to make it to one, especially if it is for bound Ecosystem convenience.Didn't think to check this myself before I deleted the game but, does anyone else who's experiencing/experienced the xinput***.dll error have a controller plugged in? Unplugging the controller might help.
What I ended up doing was pulling an xinput.dll out of another game's redist folder, renaming it and dropping it into the directory with this game's .exe . Worked like a charm.
Thank you, name change workedHere's a work-around that's been confirmed by a few people: