VOGONS

Common searches


Ion Fury - A new Build Engine game

Topic actions

Reply 20 of 71, by Srandista

User metadata
Rank Oldbie
Rank
Oldbie
DosFreak wrote:

It's interesting that the build docs for eduke32 state that SDL 1.2 can still be used.....

This isn't so surprising. The same is true for ScummVM and was until recently for Yamagi for example.

dr.zeissler wrote:

This game would be a big deal if it can be played within DOS or Win9x on a P2/3.

Maybe for us, but general public don't care about that.

Socket 775 - ASRock 4CoreDual-VSTA, Pentium E6500K, 4GB RAM, Radeon X800 XT, ESS Solo-1, Win 98/XP
Socket A - ASRock K7S41GX, AMD Athlon XP 3000+, 512MB RAM, GeForce4 Ti4200, SB Live!, Win 98

Reply 21 of 71, by x0zm_

User metadata
Rank Member
Rank
Member

Ran the latest build of eDuke32 on an XP (x86) machine with a Pentium 4 2.4GHz Northwood, 1GB RAM and a Matrox Mystique.

It was... rough, to say the least. 100% pegged CPU usage, eats an additional 1.5GB of HDD space for page file, barely playable framerates. This is with Polymer renderer off.

It may be possible with lots of config tweaking or a more optimised eDuke build for older machines, but playing stock on anything resembling a retro machine seems to be a dream that won't happen easily. Playing in DOS looks like it'd require significant reworks of the maps.

The game is still super fun on my main machine though!

Builder of Unique Retro Things

[Dimension95 - Dream 586 Setup] [TOXIC - PIII on Water] [More Coming Soon]

Reply 22 of 71, by Firtasik

User metadata
Rank Member
Rank
Member

Another major issue is the game's framerate. While it was, say, smooth enough for the overwhelming majority of the game (although never really what you should expect), it tanked to the low 10s at the worst possible times, namely during the boss battles of zones 2, 3 and 7, making the battles a very excruciating experience for all the wrong reasons. Why I'm getting a much better performance out of Rise of the Tomb Raider, a known resource-hog, at high settings is a question worth asking.

https://msdn.duke4.net/revionfury.php

11 1 111 11 1 1 1 1 1 11 1 1 111 1 111 1 1 1 1 111

Reply 23 of 71, by jmarsh

User metadata
Rank Oldbie
Rank
Oldbie
x0zm_ wrote:

It was... rough, to say the least. 100% pegged CPU usage, eats an additional 1.5GB of HDD space for page file, barely playable framerates. This is with Polymer renderer off.

Things must have changed a lot in the last 6 years, in 2013 I used to run eduke at 60fps on a wii (729MHz CPU, 72MB ram)

Reply 24 of 71, by Srandista

User metadata
Rank Oldbie
Rank
Oldbie

I guess that Wii leverage it's GPU to do a HW acceleration. x0zm_ run game in SW rendering. I would expect the best results older HW with Polymost renderer, but I don't know, if it still can be used in latest eDuke32 (and I'm not home to be able to actually test it).

Socket 775 - ASRock 4CoreDual-VSTA, Pentium E6500K, 4GB RAM, Radeon X800 XT, ESS Solo-1, Win 98/XP
Socket A - ASRock K7S41GX, AMD Athlon XP 3000+, 512MB RAM, GeForce4 Ti4200, SB Live!, Win 98

Reply 26 of 71, by VileR

User metadata
Rank Oldbie
Rank
Oldbie

Got it. Suffice to say I'm digging it profusely.

Also, for fans of period references: https://s.put.re/T7dDTynh.png 😉

web  /   blog   /   tube

Reply 27 of 71, by DosFreak

User metadata
Rank l33t++
Rank
l33t++

https://www.gog.com/forum/ion_fury/ion_fury_eduke32

This is a guide on how to get Ion Fury running under EDuke32. You might find that running the game this way runs better on your […]
Show full quote

This is a guide on how to get Ion Fury running under EDuke32. You might find that running the game this way runs better on your system than using the modified version that Ion Fury uses. Though there are 2 issues specific to running it under EDuke that i've found. The in game menu scrolls and save or load pictures are blank. Other than those two things it seems to run fine.

1) Download EDuke32 from here.

If on Mac then download it from here.

EDuke32 is only available natively on Windows or Mac. However you can build it yourself if on Linux from following these instructions.

2. Put EDuke32 (unzip it if you downloaded it) into a folder on your system. It doesn't matter where or what the folder is called.

3. Install Ion Fury from wherever you brought the game from.

4. Navigate to Ion Fury's directory and copy fury.def, fury.grp and fury.grpinfo to wherever you put EDuke32.

fury.grp contains all the info about the game, such as maps, sounds etc. fury.grpinfo tells EDuke32 what the grp is and where it is, without this EDuke32 will not detected fury.grp. fury.def contains needed palette information, without this you will get a palette error and the game will not launch.

5. Double click on EDuke32.exe, make sure that Ion Fury is selected in the Game section in the window that pops up. Then click start when ready.

You can now remove Ion Fury if you want to.

So if the above is true then Windows XP 32bit should be good. Need to test eduke32 with kernelex on Windows 98 next and blackwingcat patch on Windows 2000. Anybody have a CRT hooked up?

DOSBox Compilation Guides
DosBox Feature Request Thread
PC Game Compatibility List
How To Ask Questions The Smart Way
Running DRM games offline

Reply 28 of 71, by Srandista

User metadata
Rank Oldbie
Rank
Oldbie

I'll try it on XP tomorrow (not with CRT though).

Socket 775 - ASRock 4CoreDual-VSTA, Pentium E6500K, 4GB RAM, Radeon X800 XT, ESS Solo-1, Win 98/XP
Socket A - ASRock K7S41GX, AMD Athlon XP 3000+, 512MB RAM, GeForce4 Ti4200, SB Live!, Win 98

Reply 29 of 71, by DosFreak

User metadata
Rank l33t++
Rank
l33t++

Here is Ion Fury running on Windows 2000 using BlackWingCat ExtendedCore with eduke32 w/ SDL2 eduke32_win32_20190820-8043.7z

Attachments

  • IonFury2000.PNG
    Filename
    IonFury2000.PNG
    File size
    1.1 MiB
    Views
    1289 views
    File license
    Fair use/fair dealing exception

DOSBox Compilation Guides
DosBox Feature Request Thread
PC Game Compatibility List
How To Ask Questions The Smart Way
Running DRM games offline

Reply 30 of 71, by DosFreak

User metadata
Rank l33t++
Rank
l33t++

Iron Fury on Windows 98 SE using KernelEx 4.5.2016.17 w/ Kernel Extension 22 with eduke32 w/ SDL2 eduke32_win32_20190820-8043.7z
Copy msvcr71.dll to c:\windows\system, Backup old msvcrt.dll in c:\windows\system, delete msvcrt.dll. Rename msvcr71.dll to msvcrt.dll.

Run eduke32 in Windows XP compatibility mode

I'm still wondering if eduke32 can be compiled with SDL 1.2 with the current source. Need to look into that but eduke32 itself likely requires APIs not existing in Windows 98 so wouldn't be that simple but would be nice since then could potentially run on 95 and NT4.

Attachments

  • Filename
    msvcr71.zip
    File size
    173.71 KiB
    Downloads
    32 downloads
    File license
    Fair use/fair dealing exception
  • ionfury98se.PNG
    Filename
    ionfury98se.PNG
    File size
    266.91 KiB
    Views
    1285 views
    File license
    Fair use/fair dealing exception
Last edited by DosFreak on 2020-05-18, 23:42. Edited 1 time in total.

DOSBox Compilation Guides
DosBox Feature Request Thread
PC Game Compatibility List
How To Ask Questions The Smart Way
Running DRM games offline

Reply 31 of 71, by gerwin

User metadata
Rank l33t
Rank
l33t

Interesting results there.
I have less success with this on my Windows XP system, using Radeon 6670 graphics.
eduke32_win32_20190820-8043.7z only runs in software mode with the original Duke3D.grp file. Using fury.grp or OpenGL mode gives a crash.

--> ISA Soundcard Overview // Doom MBF 2.04 // SetMul

Reply 32 of 71, by DosFreak

User metadata
Rank l33t++
Rank
l33t++

Yeah crashes for me too in XP as well with Ion Fury and Duke 3D just shows a black screen haven't figured that one out yet.

/EDIT

It looks like eduke32 in Windows XP in Vmware 15.1.0 stopped working as of this version:
http://dukeworld.duke4.net/eduke32/synthesis/20180613-6922/

------------------------------------------------------------------------
r6922 | pogokeen | 2018-06-13 12:15:26 -0700 (Wed, 13 Jun 2018) | 1 line

Add glsurface.cpp/h and tilepacker.cpp/h to Visual Studio Project
------------------------------------------------------------------------
r6921 | pogokeen | 2018-06-13 12:15:22 -0700 (Wed, 13 Jun 2018) | 2 lines

Don't allow GL modes if GL Major Version is less than 2.
Additionally, fix build issues for RENDERTYPE=WIN introduced in r6827.
------------------------------------------------------------------------
r6920 | pogokeen | 2018-06-13 12:15:19 -0700 (Wed, 13 Jun 2018) | 1 line

sdlayer.cpp: don't alter desktop composition using win_setvideomode() if we're creating an SDL window for rendering GL
------------------------------------------------------------------------
r6919 | pogokeen | 2018-06-13 12:15:16 -0700 (Wed, 13 Jun 2018) | 1 line

When OpenGL is available, prefer using the new glsurface to blit the classic renderer's 8-bit buffer to the screen.
------------------------------------------------------------------------
r6918 | pogokeen | 2018-06-13 12:15:10 -0700 (Wed, 13 Jun 2018) | 1 line

tilepacker.cpp: instead of maintaining the heap on each insertion, maxheap_buildHeap() on tilepacker_pack()
------------------------------------------------------------------------
See http://svn.eduke32.com/listing.php?repname=eduke32 for more details.

I can see this when comparing the log files since this version (which works) http://dukeworld.duke4.net/eduke32/synthesis/20180612-6917/ shows "Trying SDL_Renderer "direct3d"" in the log whereas the newer versions show OpenGL information even though software mode is selected.

Part of this is likely buggy vmware drivers but the other part is if software mode is selected why is eduke32 still trying to use OpenGL?

/EDIT
Just disabled graphics acceleration for the XP VM and working fine with eduke32_win32_20190820-8043.7z with Duke 3D now in Vmware.

DOSBox Compilation Guides
DosBox Feature Request Thread
PC Game Compatibility List
How To Ask Questions The Smart Way
Running DRM games offline

Reply 33 of 71, by gerwin

User metadata
Rank l33t
Rank
l33t

Bummer...

Before I used this version on two Windows XP systems: EDuke32 r7297 - Built Dec 20 2018 17:16:47, GCC 7.2.0, 32-bit
OpenGL mode works fine with that one. But of course it is not Ion Fury compatible.

--> ISA Soundcard Overview // Doom MBF 2.04 // SetMul

Reply 34 of 71, by DosFreak

User metadata
Rank l33t++
Rank
l33t++

If OpenGL works in older versions and not newer versions try going through each build to identify where it broke and then report it mabye it will get fixed.

DOSBox Compilation Guides
DosBox Feature Request Thread
PC Game Compatibility List
How To Ask Questions The Smart Way
Running DRM games offline

Reply 35 of 71, by DosFreak

User metadata
Rank l33t++
Rank
l33t++

It looks like it crashes when it's going through the files in fury.grp and compiling the scripts.

GOOD

EDuke32 r8043
Built Aug 20 2019 20:21:56, GCC 7.2.0, 32-bit
Using D:/Ion Fury/eduke32_win32_20190820-8043/ for game data
Checking for updates...
Connecting to http://www.eduke32.com
Current version is 20120522... no updates available
Running on Windows 10 (build 10.0.18362)
Initializing SDL 2.0.10
Searching for game data...
Checksumming fury.grp... Done
Using "fury.grp" as main game data file.
Compiling: scripts/main.con (50245 bytes)
Including: scripts/tokens.con (27554 bytes)
Including: scripts/names.con (59980 bytes)
Including: scripts/sounds.con (191808 bytes)
Including: scripts/music.con (3666 bytes)
Including: scripts/text.con (12575 bytes)
Including: scripts/levels.con (7633 bytes)
Including: scripts/customize.con (6567 bytes)
Including: scripts/subroutines.con (16878 bytes)
Including: scripts/surfaces.con (110651 bytes)
Including: scripts/draw.con (24750 bytes)
Including: scripts/sectors.con (374828 bytes)
Including: scripts/weapons.con (403793 bytes)
Including: scripts/pickups.con (74629 bytes)
Including: scripts/switches.con (152869 bytes)
Including: scripts/props.con (293032 bytes)
Including: scripts/dialog.con (40999 bytes)
Including: scripts/player.con (340291 bytes)
Including: scripts/screens.con (42167 bytes)
Including: scripts/menu.con (40291 bytes)
Including: scripts/inventory.con (1355 bytes)
Including: scripts/particles.con (292072 bytes)
Including: scripts/enemies.con (598362 bytes)
Compiled 995820 bytes in 146ms

BAD

EDuke32 r8043
Built Aug 20 2019 20:21:56, GCC 7.2.0, 32-bit
Using C:/eduke32_win32_20190820-8043/ for game data
Running on Windows XP Service Pack 3 (build 5.1.2600)
Initializing SDL 2.0.10
Searching for game data...
warning: number 0x007843075dd10030 truncated to 32 bits.
Using "fury.grp" as main game data file.
Compiling: scripts/main.con (50245 bytes)
Including: scripts/tokens.con (27554 bytes)
scripts/tokens.conscripts/tokens.conscripts/tokens.conscripts/tokens.conscripts/tokens.conscripts/tokens.conscripts/tokens.conscripts/tokens.conscripts/tokens.conscripts/tokens.conscripts/tokens.conscripts/tokens.conscripts/tokens.conscripts/tokens.conscripts/tokens.conscripts/tokens.conscripts/tokens.conscripts/tokens.conscripts/tokens.conscripts/tokens.conscripts/tokens.conscripts/tokens.conscripts/tokens.conscripts/tokens.conscripts/tokens.conscripts/tokens.conscripts/tokens.conscripts/tokens.conscripts/tokens.conscripts/tokens.conscripts/tokens.conscripts/tokens.conscripts/tokens.conscripts/tokens.conscripts/tokens.conscripts/tokens.conscripts/tokens.conscripts/tokens.conscripts/tokens.conscripts/tokens.conscripts/tokens.conscripts/tokens.conscripts/tokens.conscripts/tokens.conscripts/tokens.conscripts/tokens.conscripts/tokens.conscripts/tokens.conscripts/tokens.conscripts/tokens.conscripts/tokens.conscripts/tokens.conscripts/tokens.conscripts/tokens.conscripts/tokens.conscripts/tokens.conscripts/tokens.conscripts/tokens.conscripts/tokens.conscripts/tokens.conscripts/tokens.conscripts/tokens.conscripts/tokens.conscripts/tokens.conscripts/tokens.conscripts/tokens.conscripts/tokens.conscripts/tokens.conscripts/tokens.conscripts/tokens.conscripts/tokens.conscripts/tokens.conscripts/tokens.conscripts/tokens.conscripts/tokens.conscripts/tokens.conIncluding: scripts/names.con (59980 bytes)
Including: scripts/sounds.con (191808 bytes)
Including: scripts/music.con (3666 bytes)
Including: scripts/text.con (12575 bytes)
Including: scripts/levels.con (7633 bytes)
Including: scripts/customize.con (6567 bytes)
Including: scripts/subroutines.con (16878 bytes)
Including: scripts/surfaces.con (110651 bytes)
Including: scripts/draw.con (24750 bytes)
Including: scripts/sectors.con (374828 bytes)
scripts/sectors.conscripts/sectors.conscripts/sectors.conscripts/sectors.conIncluding: scripts/weapons.con (403793 bytes)
scripts/weapons.conscripts/weapons.conIncluding: scripts/pickups.con (74629 bytes)
Including: scripts/switches.con (152869 bytes)
Including: scripts/props.con (293032 bytes)
Including: scripts/dialog.con (40999 bytes)
Inclu

DOSBox Compilation Guides
DosBox Feature Request Thread
PC Game Compatibility List
How To Ask Questions The Smart Way
Running DRM games offline

Reply 36 of 71, by keenmaster486

User metadata
Rank l33t
Rank
l33t

It's great how this game is released and immediately the VOGONS community says "let's run it with ancient OS's" hahaha!

What goes around comes around - nowadays it is "Very new games on old systems!"

I flermmed the plootash just like you asked.

Reply 37 of 71, by Srandista

User metadata
Rank Oldbie
Rank
Oldbie

Another small tidbit of an information from Discord:

you shouldn't use the eduke32 binary
you should use one compiled with the FURY=1 flag
yes, you can boot it up but it will eventually slow down to a crawl or crash
There are some things that are specific to duke that do not get handled properly in fury and have been fixed in source level

Socket 775 - ASRock 4CoreDual-VSTA, Pentium E6500K, 4GB RAM, Radeon X800 XT, ESS Solo-1, Win 98/XP
Socket A - ASRock K7S41GX, AMD Athlon XP 3000+, 512MB RAM, GeForce4 Ti4200, SB Live!, Win 98

Reply 38 of 71, by DosFreak

User metadata
Rank l33t++
Rank
l33t++

Thanks.

http://svn.eduke32.com/log.php?repname=eduke3 … ath=%2F&isdir=1&

https://forums.duke4.net/topic/8181-ion-fury/ … post__p__327495

Regular builds wont have support for a while since there are manual overrides done on source level for things that we can't do in a modular fashion from CON.
We used eduke32 binaries a lot when testing stuff internally as well between revisions.

It's up to the guys if they want to build a standalone binary alongside regular duke binary (would make sense in a way since other "from scratch" projects could benefit from this)

Found this which does execute on XP 32bit but requires "GetTickCount64" which requires Vista. So Vista+ 32bit OS should work:
http://www.mediafire.com/file/w70bv4yddm2ccos … 0190821.7z/file

This build also works with 98 w/ kernelex and 2000 blackwingcat extended core.

I'll look into SDL 1.2 with the latest source.

DOSBox Compilation Guides
DosBox Feature Request Thread
PC Game Compatibility List
How To Ask Questions The Smart Way
Running DRM games offline

Reply 39 of 71, by IntMD

User metadata
Rank Newbie
Rank
Newbie
DosFreak wrote:

Found this which does execute on XP 32bit but requires "GetTickCount64" which requires Vista. So Vista+ 32bit OS should work:
http://www.mediafire.com/file/w70bv4yddm2ccos … 0190821.7z/file

Assuming GetTickCount64 is the only >NT5 API call, i assume it can be easily mitigated using UncleVasya's "EU4_WinXP_fix" (contrary to the name, it should work for any game too, that will have >NT5 API calls, which this patch has reimplemented, for ex. the program's kernel32 implementation [zernel32.dll] will take care of those function calls: GetTickCount64; K32GetProcessMemoryInfo; InitializeCriticalSectionEx; GetThreadID; QueryFullProcessImageNameA) - https://github.com/UncleVasya/EU4_WinXP_fix

Unpack the latest version's archive contents into the folder with the eduke32 files, open command prompt and navigate to the said folder's path, and assuming the main exes should be patched - input this:

rundll32 zernel32.dll,PatchFile eduke32-if.exe
rundll32 zernel32.dll,PatchFile mapster32-if.exe

Though to be very certain it will patch absolutely everything, just patch every exe and dll in the eduke32 folder. Launch and hope that it will solve things for XP.

I haven't tested this patch on this build in a machine with XP on it, but assuming everything goes perfectly and that it's the only API call that needs to be patched, there are certain chances that it will work.

Last edited by IntMD on 2019-08-26, 06:11. Edited 1 time in total.