Instalar Steam
iniciar sesión
|
idioma
简体中文 (Chino simplificado)
繁體中文 (Chino tradicional)
日本語 (Japonés)
한국어 (Coreano)
ไทย (Tailandés)
български (Búlgaro)
Čeština (Checo)
Dansk (Danés)
Deutsch (Alemán)
English (Inglés)
Español - España
Ελληνικά (Griego)
Français (Francés)
Italiano
Bahasa Indonesia (indonesio)
Magyar (Húngaro)
Nederlands (Holandés)
Norsk (Noruego)
Polski (Polaco)
Português (Portugués de Portugal)
Português - Brasil (Portugués - Brasil)
Română (Rumano)
Русский (Ruso)
Suomi (Finés)
Svenska (Sueco)
Türkçe (Turco)
Tiếng Việt (Vietnamita)
Українська (Ucraniano)
Informar de un error de traducción
Normas y directrices sobre discusión
1 
Denunciar este mensaje
I'd like to report that I couldn't start the game either. On the common build, the game just stuck at the beginning; at beta, the game stuck at the logo; at debug, the game stuck at the purple screen after the logo (https://imgur.com/a/BxYI3By). Here is my log (https://we.tl/t-S2V9iPSx5z). I'd like to help with further info you need as I have wanted to cover this game since a long time ago...
And as implied on the other thread, here is my dxdiag, if needed. https://we.tl/t-MwTpicfkVx
Thank you, and hopefully you'll be able to fix it, so I could cover this game on my stream :))
Have you tried the game's "test" branch?
The next test will be a debug version of the game that has the endings list and gallery mode present. If that works, we might be able to solve the issue as simply as having a present debug build.
In the meantime, I have a few ideas but they require some larger changes to the way the game loads. I should have a new test build within the next few days.
Hm... No offense, but have you heard of something like... RAM Memory Leak? I have 8GB RAM, and when I stream/recording gameplay, I usually close most of my process. Only this time I don't, and if you saw the screenshot, other processes doesn't take that much ram in my opinion...
Your dxdiag screenshot timed out while I was without power. Can you send that to me again?
The game has a much larger VRAM requirement- and I'm wondering if it's contributing to a bottleneck.
This build has one very notable change. I've VRAM compressed every texture in the game.
Effects:
1. The game is about twice as large
2. The game uses half as much VRAM
3. The image quality is considerably worse.
Otherwise, this is equal to version 1.0.6 (so one patch behind).
If this works, we'll know this is a VRAM issue. At that point, we can explore potential paths forward that don't degrade the image quality in places we want it to look nice (characters for example).
Yoooo 😭😭😭😭 Finally the game ran smoothly on my potato laptop 😭😭😭 Now I can cover the game 😭😭😭
Here's some screenshot: https://imgur.com/a/9Pcow4n. The game starts at 1080p (as I set my desktop resolution to 1080p) and it uses 2GB of Memory. Usually, for gaming streaming and recording, I change my desktop to 720p, and now it uses 1GB of Memory. While I didn't play the game fully (so I won't feel bored/biased to do a first impression), the game seems to be able to run smoothly at 60 FPS 😭😭😭
Finally... 😭😭😭
Also, my dxdiag if needed: https://we.tl/t-dl6BRFO27u
I have updated the test build one more time. This version is the current live build- but the VRAM needs are only 800 MB instead of 4 GB. This means the whole game will comfortably run as long as you have ~1-1.5 GB of available RAM.
This only difference between this version and the version most other players are on is that you'll have some longer in-game loading times. This is because I rewrote the in-game databases for it, so instead of having everything stored and ready it reads them from the disk whenever it needs something. In most cases this should be quick, but there's a couple screens that might leave you hanging.
It still has to load everything once early to retrieve the IDs and supporting information, so the startup time isn't faster unfortunately.
It looks like what's happened is that the VRAM on a lot of machines was being overwhelmed. For cards using integrated graphics there is no dedicated VRAM- meaning everything overflowed into RAM, hit your computer's limitations, and then crashed the device.
This is why the game shows only ~300 MB of RAM when I run it and why it seems hardware specific.
Please give it a try, and let me know if you encounter any issues. Rewriting the databases is a really risky change, but I didn't want you to have to play with the low quality graphics from the other build.
Game Path is F:/SteamLibrary/steamapps/common/Doomsday Paradise/Doomsday Paradise.exe
Retried Filename is: Doomsday Paradise.exe
Setting breakpad minidump AppID = 1603420
SteamInternal_SetMinidumpSteamID: Caching Steam ID: 76561198045535480 [API loaded no]
[STEAM] Did Steam initialize?: {status:1, verbal:Steamworks active.}
[STEAM] authenticated successfully
Title Screen RAM check: 0
1.1.0
Loading Game
File Found! Save file is on Version 5 of 5
Game Loaded
In the previous update, where I was overjoyed that the game worked flawlessly, and I could randomly play for a few minutes; in the latest build, the game stuck at the logo -> then after a few seconds -> Lemonade Flashbang logo appeared -> my desktop turned black/blank, OBS not recording anymore -> game audio can be heard, but the screen turns white and windows pop-up appear saying Doomsday Paradise not working (end the process/wait window). The game just stuck there for a few minutes, and nothing works. On Task Manager, I could see that Doomsday Paradise was stuck at 1.3 MB. I don't know what happens, though.