v2.02.76 is out...... Requiem!

gho
2014-05-24
2014-09-08
  • gho
    gho
    2014-05-24

    I'm a bit in a hurry now so more comments and instructions about how to configure will come a bit later, but .....

    update

    Ok, now let me explain a few things about this game (Requiem) and this DxWnd release.
    First of all, Requiem is an almost forgotten wonderful game with a very unique atmosphere! And from the technical point of view, it is one of the early 3D games rendered with 8BPP palette and a fully 2D emulated 3D engine.
    Now, this means that very likely you won't let it go windowed in native mode (a 8BPP desktop is not a real pleasure!), so the best way to enjoy it is running the emulated engine (a dedicated exe file) in surface emulation mode on a 32BPP desktop.
    Trying to do so revealed a bug in the palette handling, the lack of palette import in emulation mode that caused the game to work perfectly, but in a very strange blue world instead of the red you would expect in inferno.
    Another game oddity is the way it checks for DirectX version in the system: it looks for a registry entry and compares the version string with a series of possibilities, but obviously in 1999 nobody dreamt of DirectX 9 and the check fails claiming your software is too old. There would be plenty of possibilities to fix this somehow, but we don't lke easy shortcuts, so I reintroduced in DxWnd the registry handling, with the possibility to set missing registry keys (Emulate registry) or to override existing values (Override registry).
    Requiem requires to override the DirectX version registry entry, and to do so you must leave the dxwnd.reg file in the dxwnd folder. The registry handling is far than complete, but it is easy to understand that possibilities are endless, including the end of the nasty habit to include registry setting scripts in game rips that nobody knows how to eliminate from the registry once inserted.
    So, I would encourage you to suggest further games that may benefit from registry handling, I'll be happy to test them.
    Also, if you never played Requiem, I would suggest you a ry. I must admit that the gameplay might be not such a rich one (first levels pretty linear and simple), but the atmosphere is really unique.
    Have a good trip to hell-
    GHO

     
    Last edit: gho 2014-05-24
    Attachments
  • Matt
    Matt
    2014-05-27

    Ooh, you mean Requiem Avenging Angel! I actually found this ran okay in Windows 7/8 if I applied the latest patch (for DirectX 8 compatibility) and disabled the movies (deleted smacker DLL). Although, having never played it first time around I would not have noticed if the colours were off.

    Regarding the game incorrectly detecting DirectX, I just ignored that and started it anyway.

    I will have a look at this and update my article. Thanks Gho you're a PC retrogaming hero :)

    Edit - My mistake, I got it running in Windows 7, but not at all in Windows 8

     
    Last edit: Matt 2014-05-27
  • Matt
    Matt
    2014-05-27

    Okay I can confirm Requiem now works with Windows 8, but only in software mode which limits us to 640x480. Direct3D mode will now start but just gives a blank screen/window.

    Anyone have any ideas on getting the Direct3D version running? I've got patch 1.3 installed and the game will run on the same hardware under XP but not Windows 8.

     
    • gho
      gho
      2014-05-27

      A black screen could be caused by a wrong emulation mode in the DirectX tab: have you tried "none" or "Locked surface" yet?

       
  • Matt
    Matt
    2014-05-27

    None and Locked Surface both cause the game to crash instantly on startup.

     
    • gho
      gho
      2014-05-28

      With some embarass I must admit the reason of my delay was of the dumbest sort: I didn't figure out that the default Requiem installation DOES NOT install D3D files! Likely, I could share this feeling with the 3DO setup developers, but let's forget about this.....

      Requiem D3D on my PC works in D3D mode, but sets the desktop color depth to 8BPP right until it starts the real D3D part, after the menus. If you set emulation mode, the menus are fine, but the D3D doesn't blit. It's annoying in real windowed mode, but if you play it as fake fullscreen, it shouldn't hurt so much. And, of course, you can set it up to whatever resolution your monitor supports, so there is a big improvement compared with the maximum 640x480 of software emulation.

      May I suggest to reinstall it without any recent patch and, if it crashes again as it is likely, send the logfile to me?

      The screenshot below depicts what you're currently missing: I'd say a big loss!

       
      Last edit: gho 2014-05-28
  • Matt
    Matt
    2014-05-28

    Okay, I will give that a shot either tomorrow or Friday. Also I'm on Windows 8 so I'll first try switching to Windows 7.

    Just to be clear I should be using the existing Requiem export file with no changes?

     
    • gho
      gho
      2014-05-29

      You should use the attached "Requiem Avenging Angel (D3D).dxw" file, of course setting the program path according to your installation.
      But there's nothing too special about this configuration. Just these clues:
      1) the executable is D3D.exe. I saw that it is possible to start the game directly from that file, but if you prefer to use the Requiem.exe frontend, ensure that the game configuration points to the D3D rendering engine.
      2) surface emulation must be avoided, so don't set neither "automatic", nor "surface emulation". I noticed that maybe the first three non-emulated modes seem to work all at low resolutions, but I got a crash setting higher resolutions / window sizes, so my advice is to proceed by steps starting from 800x600 and growing up until possible: maybe there's some limitation I wasn't aware of.
      3) to reduce window movements, I set the lock window position and avoid maximize flags. They seem not necessary, but they could make some difference switching from Win7 to Win8 (who knows?)

       
  • Matt
    Matt
    2014-05-29

    Sorry somehow I didn't notice that export file yesterday.

    Anyway, it's no go on my Windows 7 installation too, instant crash when I start D3D.exe.

    I think my copy of the game might be pre-patched. I've included my copy of D3D.exe see if it is any different to yours.

     
    Last edit: Matt 2014-05-29
    Attachments
    • gho
      gho
      2014-05-29

      Your file is different from mine, but they both work setting the "Primary buffer" flag. Just in case, here's the copy of my file (I guess most of the difference is due to the italian language...).
      To clear other differences out, I just uploaded v2.02.77 that includes a Requiem D3D export file: you could try to start again from that.
      The log shows something very interesting: it seems to point out a recursion in the Palette::QueryInterface method. It is unclear why it should happen on your PC only, but it is an interesting track.....

       
      Attachments
  • Matt
    Matt
    2014-05-29

    Well it seems to be the opening cinematic that causes the crash, although if that is the case I cannot explain why software only mode works.

     
  • Matt
    Matt
    2014-06-16

    Just to report back, I tried the latest DXWnd and the Requiem D3D export file and it's still a no-go for me. Windows 7 crashes instantly, whereas Windows 8 will start, but all the movies and menus are corrupt and in game there is just a black screen. Oh well!

     
    • gho
      gho
      2014-06-16

      I'll have a look at the problem later (likely, not before tomorrow ...) but now it comes to my mind that the recursion problem shown in the last logs you sent me could be triggered (turned on, somehow) by the log "DirectX full trace" flag.
      Would you mind to uncheck this flag (or any other logging flag) and see if by chance at least on Win7 the game starts working?

       
  • Matt
    Matt
    2014-06-20

    Trace was off, doesn't make a difference.

    Oddly, now I'm getting a "Not Enough Memory" error when I try to start the game in Windows 8. This is rapidly becoming as problematic as Star Wars Racer!

     
    • gho
      gho
      2014-06-20

      There is a "Limit available resources" flag in the Compat configuration tab that is meant to fix this kind of problems (16/32 bit integer overflows for hard disk space and memory on modern platforms) though the combination of Win8 and recent DxWnd release doesn't make me confident that it may work.
      In any case, what is necessary is the following:
      o check whether this flag has been set or not (it should be...)
      o if the error persists, a copy of the logfile to check if the patching was triggered or not
      Please, reply, since I don't have the two necessary ingredients for this recepy, that is neither Win8 and nor a powerful PC.... :(

       
      Last edit: gho 2014-06-20
  • KidSpoiler
    KidSpoiler
    2014-09-08

    Sorry to breath life into this thread again...

    Been trying to get this game to work myself.
    still issues with "Not enough memory".
    Also, where does dxwnd save the logs? i can open it, but can't seem to find it O.o

    Here is my specs:
    Asus Gamer computer G75VW-T1399H (Laptop)
    Intel Core i7-3630QM Quad Core processor (2.4 GHz)
    weight: ca. 4,5 kg.
    17,3" Full HD screen (1920 x 1080)
    16 GB DDR3 RAM and 2 x 750 GB hard disks
    (which oddly enough is split into 4 smaller hard disks)
    100/1000 LAN, wireless network card (b/g/n) and Bluetooth 4.0
    NVIDIA GeForce GTX670M with 3 GB GDDR5 RAM and HDMI/mDP
    Blu-Ray-player/DVD-burner
    USB 3.0, HD webcam and cardreader
    Windows 7 [64-bit]

     
    • gho
      gho
      2014-09-08

      Curious: you're having a memory problem that was reported on Win8, but on Win7.
      Likely, it depends on the video card: on my PC the problem never appeared. Have you tried to check the Compatibility ("Compat." tab) "Limit available resources" flag? Please, let us know whether this trick works. If it doesn't, it would be interesting to know...!
      Logs are written only when you check the "Logs" "Enable trace" flag. With this alone, just error messages are written. Or you can check further log options and get more details. Usually, the typical setting is checking just the further three options: "DxWnd hacks", "DirectDraw trace" and "Direct3D trace". Logging tends to be quite verbose, so the more is not always the better!
      And when logs are written, they are within the dxwnd.log file in the game folder. You can simply use the DxWnd Log->View menu command (right clicking on the desired game) to open the current logfile.
      Keep in mind that the quicker way to configure a supported game is to "Import" its exported config file (in the DxWnd exports folder) and adjust the game pathname. Once the game is working in the default mode, you can start to play with all the options.
      There are two exported files, but I suggest NOT to use the D3D configuration. The reason is simple: the game is a 8BPP palettized 3D game (quite an uncommon setting!) so running it in native 3D not emulated mode, your whole desktop would be put on 8BPP color mode! The software version is quite easier to manage.

       
      Last edit: gho 2014-09-08