Head, legs, arms...dude TITS, TITS is the word we're looking for. You've been a great community ambassador so far, I guess you misspoke. Can't wait to get my creasy fingers on those perky coasts and jackets.
Unreal Engine Project Extermination: Operation GroundZeroes [Phase 2 - 2023-07-16] [MATEYDEV]
- Thread starter Alket
- Start date
lol, this is outfit customization xD. Character customization will be done (leveraging the same subsystem) sometime soon™ as part of the "safe room" system, basically the homebase hub, that is the next big scheduled thing...
- Aug 31, 2021
- 44
- 218
How much fat will we be able to add to dat ass, Alket? You're making sure to advise Matey on these important decisions, yes?
- Jan 27, 2021
- 105
- 169
I really wanna like this, but while menus may not make a game, they can certainly break it and they DO break this one for me...
They are HORRIBLE; and I really mean straight up trash, a weird mix of controller/maus/keyboard stuff and neither works properly on its own.
They are HORRIBLE; and I really mean straight up trash, a weird mix of controller/maus/keyboard stuff and neither works properly on its own.
The game is still in development and things can change. I suggest waiting for another 4 years for some minor UI changes... Development is hard and things like these can take time.
Last edited:
- Oct 15, 2020
- 109
- 97
from last devlogs it seems its getting changed tho, just need for the update to come
Best defer to the T&A scientists in the Lab 3 division, those crazy kooks always making new innovations in the datassilogy field.
Is there an exact release date for the next update?
My gratitude for Your answer!
My gratitude for Your answer!
Next Patreon update? within next week +/- 3 days.
Next playable build? no ETA / when ready.
- Jan 9, 2023
- 184
- 318
Steam demo/early access release I suppose then...
To reach early access state,I think it gonna need another 2 years at least if everything goes well.
- Jan 14, 2021
- 142
- 202
This game does not runs at all on my 6900XT. Latest drivers, turned RVT off as suggested in the "known bugs", tried windowed, fullscreen... nothing.
It runs, shows the menu, I click new game, it starts loading things showing a static screen and text of what it is doing on the bottom righ, then it crashes. Every single time.
Never saw a game more anti-AMD than this demo, not even when AMDs OpenGL drivers were fucked up decades ago when Nvidia paid the entire industry to conform to their unique OpenGL drivers...
Shame, I really wanted to give it a try, screenshots are cool and it seems a game kinda similar to Delta Zone.
It runs, shows the menu, I click new game, it starts loading things showing a static screen and text of what it is doing on the bottom righ, then it crashes. Every single time.
Never saw a game more anti-AMD than this demo, not even when AMDs OpenGL drivers were fucked up decades ago when Nvidia paid the entire industry to conform to their unique OpenGL drivers...
Shame, I really wanted to give it a try, screenshots are cool and it seems a game kinda similar to Delta Zone.
"anti-AMD" lol, bro, it's not like Matto did that on purpose, take your frustration on Epic for making a shitty supported product and to AMD for rendering it incompatible, nevertheless:
Yes, disabling RVT should be the solution, everyone with a RDNA2/3 GPU that I know of was able to play by disabling that component in the menu before starting (obvious is obvious, but you have to save the changes
)...can you please post a screenshot of the error you're getting? Is it the same "D3D device lost" that was seen by others?On a totally different note: do you have Rivatuner installed by chance? can you please confirm the API you're rendering the game with? (if you have no idea how to do this, disregard this.)
You must be registered to see the links
- Jan 14, 2021
- 142
- 202
Not trying to acuse the dev or saying it was done on purpose, but most UE4 and 5 things, even "tech-demos", run perfectly fine with RT and Lumen enabled. So i don't know what was done here, it specificaly fucks up with amd anyway.
I'll give this a try again, and post the screenshot, I don't remember what the UE error reporter said was the problem (access violation? i don't remember will try again and post here when I have time).
And, no, I don't use Afterburner and Rivatuner, amd drivers have all the built-in controls for clock/voltage and fan curves of the GPU and CPU if Ryzen Master installed, plus a OSD to show temps and such. No need for third party programs. And no, they don't hook nor mess up games like Afterburner and Rivatuner does. How? I have no fucking idea, they hook the APIs and windows WDM in a much less aggressive way. And no, I'm not enabling them in this game, to avoid even further bullshit as cause for crashes.
Also the API being used is D3D12 (dxgi.dll).
Last edited:
if I remember correctly dxgi should be the common interface, the game is running D3D11 and, btw, that's the problem, AMD forces DX12, while the game is built in DX11, nvidia runs fine on DX11 but AMD, for some reasons (hide the fact that their newer gpus don't have good compatibility with older directx), forces DX12...and that would be fine, but some native components of UE4 have not been brought up to speed, like RVT, and crashes on DX12.
If you somehow manage to tell AMD drivers to fuck off and us DX11 u should be good...and if you do, please share how, nobody with AMD has ever been willing to test shit...
- Jan 14, 2021
- 142
- 202
well fuck me sideways:
it ran...
Also, yeah not d3d12 my bad, d3d11 (dxgi and d3d11 dlls being invoked by system). I saw dxgi and automatically assumed dx12, but it is indeed calling d3d11 too, which means it's running in dx11 level.
Now ask me what I done differently from when I posted that it crashed multiple times (I tried 5 times changing things around to try to make it run, making clear I saw the "disable RVT" warning in the readme/front page known bugs). I changed NOTHING, it just decided to run... I sometimes hate PCs behaviour.
If it's worth anything: it was crashing in the "Initializing Game" phase of the loading. It loaded everything into RAM/VRAM, and only when done it crashed.
And was strange since the 3D model of the character before the loading screen worked without issue, so the engine somehow was initializing the renderer without issues. Something triggered on map loading was crashing to me apparently.
edit: also, note that on the screenshot I posted, the AMD overlay is running on top left without problems, so it's hooking without causing issues. BUT, and that's kinda strange, if I enable the "show API" it shows "N/A", so it is hooking the window to overlay the overlay (heh), but it is unable to properly detect which API is being used to draw.
edit2: also, I'll try later to use DXVK since this uses dx11 (which is know to be quite bad comparing to 10 and 12). Most games that gives trouble using dx11 work flawlessly with DXVK translating them to Vulkan (which is kinda black magic still to me).
edit3: the DXVK made it worse, went from 60fps locked to 30. There's some fuckery going on with this demo and how something is rendered somewhere, I don't know what, but it's very badly coded.
Last edited:
when there will be a new playable version of this game? anyone knows?
Nope, trust me, it's only one component that's fucking everything up and that's RVT and only for AMD...if u where to find the iteration of the poc before this one you will not have any issue.
You're reading N/A in the api because AMD it's likely doing something strange with directx, that's why I specifically mentioned rivatuner, because I believe that it would hook, as u mentioned, more aggressively and it would likely give better details.
Nevertheless, AMD and UE4 shenanigans aside, I'm glad u managed to play...