search

bradharding / doomretro

The classic, refined DOOM source port. For Windows PC.
https://www.doomretro.com
GNU General Public License v3.0
685 stars 86 forks source link

Suggestion - DOOM 4 (Vanilla) #670

Closed SilentMRG closed 3 years ago

SilentMRG commented 3 years ago

Hi... =)

It will be interesting to see DOOM Retro running this demake: https://www.doomworld.com/forum/topic/108725-doom-4-vanilla-v32/

I have nothing against Chocolate Doom or Crispy Doom, but it seems that most people do not remember or care about DOOM Retro, which in my view is a mistake, given the practicality and whimsy that it has. In particular, I see that DOOM Retro works better and is more practical to make things work.

Stay the tip... And thanks very much! =D

VGkav commented 3 years ago

It should work. Doesn't it?

SilentMRG commented 3 years ago

It should work. Doesn't it?

I am not sure. I plan to test tomorrow. However, the PWAD needs the DOOM II IWAD - Hell on Earth, and from what I saw the PWAD works with other PWADs (weapons, maps, sounds and etc ...). It probably won't work. =(

Apparently, this is not an independent IWAD.

bradharding commented 3 years ago

Last time I checked, D4V worked fine in DR. And you're right, D4V.wad is a PWAD. You are meant to play it with DOOM.WAD or DOOM2.WAD, and other PWADs, not by itself.

SilentMRG commented 3 years ago

Hey...

Hehe... I was already coming here to close.

Anyway, just for the record: Doom 4 Vanilla worked after I created some .bat files, and I needed to create a .bat file for each map. XD

On the other hand, the additional weapons did not work, the sprites appeared, but, they did not fire. According to the developer, these weapons do not work in all source ports.

I also tried the 64-bit version of DOOM Retro, but it failed (appcrash) to run. The 32-bit version worked well, however it presents appcrash when closing the DR, and sometimes, the program is not terminated correctly, in this case, I close the program through the Task Manager.

I apologize for the delay in closing the topic, is that I wanted to make sure that everything (or almost everything) was fine.

Thank you for your attention!

bradharding commented 3 years ago

I think I may know what the problem is with the 32-bit build, and it should be fixed in the next version. Unfortunately with the 64-bit build, I'm having a lot of trouble tracking down the issue with that one. It works fine on my system (Windows 10 Home), so that doesn't help.

SilentMRG commented 3 years ago

I don't know anything about programming. But sometimes I think that the Appcrash error has to do with the Visual Studio 2019 version. It's just a suggestion: Maybe... if you re-code in C++ 2017, solve the problem. Hehehe... I must have said a lot of bullshit! XD However, in my ignorance, this is what I think.

I use a Laptop with this configuration:

Windows 7 Ultimate 64 Bit I5 2.67 GHz 4 GB DDR3 Intel HD Graphics 1000

Yes, it is a low performance machine. And that already has 10 years of use! hehe

I don't know if that helps...

See you later!

bradharding commented 3 years ago

Actually, that's an interesting idea. Can you please tell me if the following works for you? It was compiled using the VS 2017 toolset:

https://www.dropbox.com/s/c8ld85oyniitxxr/doomretro-4.0.9beta1-win64.zip?dl=1

SilentMRG commented 3 years ago

Thank you so much for giving me a chance to test! =D

Unfortunately, I don't have time to test it today, so I'm going to test it tomorrow with extreme calm to see if everything works.

Tomorrow, in the afternoon, I say if it worked.

See you tomorrow! \o

SilentMRG commented 3 years ago

Actually, that's an interesting idea. Can you please tell me if the following works for you? It was compiled using the VS 2017 toolset:

https://www.dropbox.com/s/c8ld85oyniitxxr/doomretro-4.0.9beta1-win64.zip?dl=1

Hi...

It didn't work, unfortunately. =(

Perhaps this will help to identify the error...

Problem signature:

Problem Event Name: APPCRASH Application Name: doomretro.exe Application Version: 4.0.9.0 Application Timestamp: 608a4934 Fault Module Name: StackHash_fa72 Fault Module Version: 6.1.7601.24441 Fault Module Timestamp: 5cb9356e Exception Code: c0000374 Exception Offset: 00000000000bf302 Operating system version: 6.1.7601.2.1.0.256.1 Locality ID: 1046 Additional Information 1: fa72 Additional Information 2: fa72542fa41b9a9db5c86c4acc8803e1 Additional Information 3: 4dbd Additional Information 4: 4dbd6ae406167c101e88e262518a6ceb

Again I thank you for giving me the opportunity to test! :-)

bradharding commented 3 years ago

Hi @SilentMRG, I hope you're well! Could I please trouble you again to test the following 64-bit build?

https://www.dropbox.com/s/plntbq7fdwtc5fu/doomretro-test-x64.zip?dl=1

SilentMRG commented 3 years ago

Hi @SilentMRG, I hope you're well! Could I please trouble you again to test the following 64-bit build?

https://www.dropbox.com/s/plntbq7fdwtc5fu/doomretro-test-x64.zip?dl=1

Hello... =)

Brad,

I'm be fine! And I also hope that you are well. =D

I just tested it ... And unfortunately, it didn't work. =(

Again, the same mistake... =/

Problem signature:

Problem Event Name: APPCRASH Application Name: doomretro.exe Application Version: 4.0.9.0 Application Timestamp: 6094e1f9 Fault Module Name: StackHash_4795 Fault Module Version: 6.1.7601.24441 Fault Module Timestamp: 5cb9356e Exception Code: c0000374 Exception Offset: 00000000000bf302 Operating system version: 6.1.7601.2.1.0.256.1 Locality ID: 1046 Additional Information 1: 4795 Additional Information 2: 4795e403dee78f68ceee18934a3aaee4 Additional Information 3: e3ad Additional Information 4: e3adea1c15b39dd8b1409cf8cea72461

I hope this helps! I tested it on the C drive (operating system location), and I also tested it on the D drive. I also tested it with the gamepad connected and the gamepad disconnected, and in any case it presents the aforementioned error before even starting the DR.

Which API Doom Retro use: OpenGL or DirectX? The integrated video card I have here, supports only DirectX 10.1 and OpenGL 3.0.

Perhaps... The source of the problem is the API used. Or the root of the problem must be in the SDL version (SDL2-2.0.14).

Just a layman's opinion on the matter, hehehe. XD

See you later! \o

bradharding commented 3 years ago

Oh well. Thanks anyway. I'll keep looking.

DR can use either DirectX or OpenGL. The vid_scaleapi CVAR can be direct3d, opengl and software.

SilentMRG commented 3 years ago

You're welcome! =)

If you need help... Just let me know. :-)

bradharding commented 3 years ago

Me again! Can you please confirm if that test build creates a doomretro.cfg file before crashing? This will help me further narrow down where in the code the crash occurs.

SilentMRG commented 3 years ago

Unfortunately it does not create any ".cfg" file, because the Doom Retro displays the "AppCrash" error, even before starting, that is, I double-click on the shortcut or click directly in the ".exe", and the error occurs immediately.

In short, the DR window doesn't even open! =(

SilentMRG commented 3 years ago

I feel sorry that I can't help effectively. =/

Anyway, needing help... Just let me know! :)

bradharding commented 3 years ago

You're help is greatly appreciated @SilentMRG! Knowing that the .cfg is not created does help me.

bradharding commented 3 years ago

This is a big ask, and may be tedious for you, but I could really use your further help. Below are 6 zip files each containing a different doomretro.exe. Could you please unzip each of them, one at a time, test1.zip to test6.zip, into the folder that contains all the other files, run doomretro.exe and let me know if you get a specific error messagebox? It's possible that there will be no error whatsoever in even test1.zip, but I'm running blind here and even that result will help me narrow things down even further. 😁

test1.zip test2.zip test3.zip test4.zip test5.zip test6.zip

SilentMRG commented 3 years ago

Test 1 gave the famous appcrash error. From test 2 onwards... All browsers, as well as Malwarebytes and Windows Defender, accused Agent Tesla-type Trojans and one Wacatac, which I researched is Ransomware. It is likely to be a false positive, but, my computer is shared with other people, so I will not be able to risk it.

I'm sorry... Brad... but this time, I won't be able to help.

bradharding commented 3 years ago

Thanks for trying. I can assure you I wasn't sending you ransomeware. Each test set a breakpoint at different parts at the code. The fact that test1 gave you the appcrash error, which had the earliest breakpoint indicates the problem proceeds that.

SilentMRG commented 3 years ago

Brad, I trust your words. I believe it is just a false positive. However, as I said, I share my device with other people ... They have data here, if something happens in their hands, or in my hands, that is, if there is a loss of data, even if it is without the intention for that, it will be my fault anyway.

So, I prefer not to risk it.

Perhaps there is an error in the code that is causing the antivirus to alert these pests, and perhaps this is the point of the code that should be investigated.

Again, the opinion of a complete layman on the subject.