Odd way to run Freedoom

XCOPY

Well it is possibly a known fact that Freedoom often crashes Doomsday Engine. But uh, suddenly I felt like trying making doom64 work as intended in the latest build, and out of nowhere I came with the "genius" idea of making a folder called "doom64.box" (inside addons folder) and the trying to run it. Suddenly, freedoom maps loaded really well, and seems that most of their maps just uses cosmetic boom features, got amazed and all then, suddenly I decided to make the "doom64.box" folder empty and load it with freedoom, it didn't crash too and the game ran smoothly (when it crashed, it gave an error on msvcr100.dll or something). I dunno if I classify as bug report or what. All I can say is that I'm running windows XP 32 bits.

Since this was a persistent issue I had with freedoom and, after creating such folder and then deleting "fixed" the problem, I ask anyone if it happens to any of you too.

Sorry for the apparently weird topic, but I can't properly explain what was causing the issue of doomsday crashing on freedoom maps.

Gordon

win xp has since been discontinued for official support aka there not supported in the latest releases. but i am glad you got as far as you did.

DaniJ

As far as I'm aware the current version of Freedoom (last I checked, about a year back) makes use of various BOOM features and as such won't work as intended with Doomsday.

I'm not entirely sure what it is you're trying to do wrt DOOM 64, though. Care to explain?

XCOPY

I was trying to put this mod to run in the latest build http://www.doom2.net/~doomdepot/abs-download.html
It's doom 64 Absolution, it uses jdoom (doomsday) to run, but all it's ded and resource files are completely spreaded, right now I'm trying to discover which file is which.

DaniJ

That mod comes with its own executable which the mod requires to work correctly. Its not "simply" a TC in same sense as say Ghostbusters DOOM. I think you'll run into many more issues than merely packaging it up.