VOGONS

Search

Common searches

Search results

Display options

Display options

Re: Ion Fury - A new Build Engine game

Posted on 2023-10-30, 05:36

If HT is part of the cause due to context switches happening, you could also disallow it within user space. On MS Windows, this can be done in Windows Task Manager. Start the game, then Alt+Tab to Task Manager, go to the Details tab, sort by name, then right-click an already running process and pick …

Re: MyPal is dead

Posted on 2022-05-27, 17:06

Actually, why exactly is this a bad thing? Seems Feodor2 managed to backport Rust and is now using FF68 as a base for MyPal. While the GUI may suck depending on your taste, the ability to render and access more modern web sites or use WebExtensions may prove to be a game-changer for XP users, no? …

Re: Best WinXP Video Card

Posted on 2022-02-23, 17:22

Having read a lot about this topic (best XP graphics card and high-res displays) on this forum, I just took a pretty big risk and bought the following monitor: LG 38WN95C-W, 3840×1600 pixels Considering the GeForce GTX Titan Black asthe best XP card, it's what I'm using in my ancient XP x64 …

Re: Running 3dMark 2000 on modern hardware

Posted on 2021-01-30, 18:54

Yeeesss, it works! Thank you so much, I can finally watch that demo again without having to resort to YouTube. :) Funny part: The 6900 XT's fans didn't even bother spinning at all until the "Matrix" parts of the demo started. ;) Love it! Edit: And that was with 8xEQ MSAA+SSTAA and 16xAF in 2048×1536 …

Re: Running 3dMark 2000 on modern hardware

Posted on 2021-01-30, 13:28

Try this https://www.vogons.org/viewtopic.php?p=605361#p605361 Edit: Also attached the file here. There indeed seems to be an issue with Ryzen cpus. Thank you very much teleguy! Results: 3DMark2000mmxchecknegative.exe shows the same MMX error, while 3DMark2000mmxcheckpositive.exe starts up the GUI …

Re: Running 3dMark 2000 on modern hardware

Posted on 2021-01-30, 07:56

I just tried this with patch 4 on two machines, failed on both. The first: XP Pro x64 Edition SP2 Intel Xeon X5690 (think "i7 990X") 48GiB RAM nVidia GeForce GTX Titan Black, 6GiB VRAM, running with driver 368.81 Screen resolution: 2560×1600×32 Error: No visible errors reported. The program appears …

Re: Ion Fury - A new Build Engine game

Posted on 2019-09-11, 07:53

[...] - In Polymost mode the menus are not visible, but I can keep pressing enter and the ingame 3D view then appears. It looks very much like software mode, with unfiltered textures, and is a bit slow. But it actually does use more then 256 colors. Huh, that's interesting. I just tried it, and it …

Re: Ion Fury - A new Build Engine game

Posted on 2019-09-10, 19:45

It should depend on the Visual C++ 2015 redistributable, but nothing other than that. It's been compiled using the v140_xp toolset. @jmarsh: With GNU make, you just do "make FURY=1". When looking at the Makefile, it seems to set a few preprocessor definitions whenever that flag is set to 1, which I …

Re: Ion Fury - A new Build Engine game

Posted on 2019-09-10, 11:54

Interestingly, there are no preprocessor #ifdef, #if defined or #if !defined to be found anywhere in conjunction with "FURY". X:\Build\eDuke32\eduke32\source>grep -r "FURY" . | grep "#" ./duke3d/src/common_game.h:#define GAMEFLAG_FURY 0x00000080 ./duke3d/src/common_game.h:#define FURY (g_gameType & …

Re: Ion Fury - A new Build Engine game

Posted on 2019-09-10, 09:38

Thank you! This seems to be similar to adding /D "FURY=1" to the command line directly. I tried adding FURY=1 to the preprocessor definitions, but the resulting binary seems identical (compared file size, but not checksums). The only difference appears to be that I get lots of warnings and notes …

Re: Ion Fury - A new Build Engine game

Posted on 2019-09-10, 09:02

Alright, thank you. I got it to work with eduke32-IF-win32-r8075-20190906.7z (your version seems to have been replaced by this newer one). In the meantime I have started compiling eDuke32 myself, and I can now produce XP-compatible builds with (I think) no SSE/SSE2 code mixed in. No more …

Re: Ion Fury - A new Build Engine game

Posted on 2019-09-09, 20:58

Can't get that build to work either. When run as-is, it says it's being aborted by Ctrl+C, which seems really bad. Instead, it should complain about GetTickCount64() not being available. So I patched that out (wrapping GetTickCount64() around GetTickCount() using Oleg's Stellaris patch), and after …

Re: Ion Fury - A new Build Engine game

Posted on 2019-09-09, 14:16

I just retried it on 32-bit XP, since XP x64 worked so wonderfully. However, I cannot get it to work with 32-bit eDuke32 like DosFreak managed to do. I tried the eduke32_win32_20190820-8043.7z that DosFreak used, and also the latest version of the eDuke32 engine, that's eduke32_win32_20190908-8090. …

Re: Ion Fury - A new Build Engine game

Posted on 2019-09-09, 06:27

I wonder why the engine is so CPU-hungry though. I mean, this is the Build Engine with eDuke32... So why... Or is eDuke32 itself this slow these days? Because of that new renderer? Been a while since I've been playing Duke Nuk'em 3D with it, which is why I'm asking.

Re: Ion Fury - A new Build Engine game

Posted on 2019-08-29, 06:05

Usually, if it's there, it's right beside the game EXE. For the 3DRealms version, the game consists of just files, no subfolders. The files in the game folder (without the XP fix): fury.def, fury.grp, fury.grpinfo, fury_nodrm.bin, fury_nodrm.exe, gamecontrollerdb.txt, legal.txt. After launch it will …

Re: Ion Fury - A new Build Engine game

Posted on 2019-08-28, 21:17

Interesting. A lot of "non-Galaxy" versions from GOG still come with said DLL, requiring hacking it to make it work. MD5 checksum of unmodified fury_nodrm.exe from the 3DRealms store: Copy code to clipboard 1 a579d0a0c4e3c7eda4209a18e42462ec *fury_nodrm.exe

Page 1 of 2

Go to top of page Go to top of page
Close window
Close window