It was a dumb idea to even have a timer in the first place. I mean, how am I supposed to see everything this demo has to offer if I'm kicked back to the title screen in the middle of climbing a ladder?
Sad to see all of these reports...there is an issue with RDNA2 architecture that we are in the trying to solve (sadly we didn't have a tester with a modern AMD card and this was not found earlier), issue that seem "common" on Unreal 4 games, even some from big companies...will keep you posted as soon as a solution is found...
. But not 100% correctly.
This might actually be useful, thanksIt works for me on mine RX6800XT ...on Linux
On character select menu I have 13 FPS on any settings though can get 50 on ultra in game with FSR disabled in 2K resolution. But in game there are some rendering issues - for example base surfaces have strange stripes. This is somehow related to shadows - lowering shadows quality makes that stripes larger and blurrier though object shadows themselves render fine.
View attachment 2596789
Read the changelog on the first post, you'll find your answer.
Oh great... how did i missed that, now I feel stupid... and thanks for answering my quest mk40
seems like the fifth version of this thing, i feel bad for anyone that threw money at these
You do understand that there are usually multiple versions of a game being developed? A dev doesn't just magic up an entire game on demand, there's a working process of adding content and testing that goes into game development.
Yep, in Phase 3 of the development Matto will move from worldbuilding to populating it with enemies and will rework the h-system and that stuff...
So RDNA3 also crashes on DirectX...but Vulkan works, good to know, thank you very much...
