Home › Bob Hoskins › Comments
Bob Hoskins
About
- Username
- Bob Hoskins
- Joined
- 2009 Jun 9
- Visits
- 135
- Last Active
- Apr 14, 10:05
- Roles
- Registered
Comments
-
I have no idea what you're saying but I'll try to help. You have downloaded Doomsday which is an engine only - and it works very well. You still need to have the WAD files from the original games (Doom, Heretic, HeXen) in order to play them. T…
-
It isn't possible to crouch in vanilla Hexen and is considered a cheat.
-
You could try pressing the '+' key on the keyboard (not the keypad) to increased the size of the viewable area. I recall that once you hit a certain size, the HUD elements automatically go to the corners of the screen. [Edited to fix incorrect ke…
-
Perhaps a Google search on "how do I find the model of my notebook"...
-
You're less likely to get help by shouting "I NEED HELP NOW!!!!!!!!!" However, seeing as it's the season of good will - I'll try to assist. - Are you running Doomsday on a laptop or a desktop machine? - Please ZIP up and attach your full doom…
-
Hi Morpheus666. The first thing to do is to post your doomsday.out log file for the devs to have a look at. You can find details here: https://manual.dengine.net/guide/doomsday.out
-
It also looks like you're standing in a different place in each of those screenshots.
-
skyjake wrote: » Bob Hoskins wrote: » If there's anything else that you need then just give me a shout. Please see if the next unstable build (2399) still crashes at launch. I have fixed a bug in the new code that loads package icons, lik…
-
If there's anything else that you need then just give me a shout.
-
skyjake wrote: » Do you have a doomsday.out log file showing messages before the crash? Could you also try starting doomsday.exe with the "-vvv" option? (I suppose the easiest way to do that is via the Windows Command Prompt.) Sure - doomsd…
-
I'm getting the same crash on startup too. Everything was working fine with build 2381. Let me know if there's any more information that you need.
-
That looks awesome! Nice work as always veirdo.
-
Where is DaniJ lately, is he still contributing to the project or has RealLife taken over?
-
Google is your friend...
-
You're using a very old version there. You may want to have a look at the more recent versions on the Builds page, unless you're using that version for a specific reason.
-
So I downloaded build #2295 and the problem seems to have been solved so it's a mystery to me! Thanks for looking into it with me.
-
It's running dual GTX-670s in SLI and drivers are up to date. I tried disabling SLI too as a couple of games I've played recently don't like that but no change. I'll try rolling my drivers back to a previous version as there was an update recently.
-
I renamed the runtime folder and launched Doomsday with the same result. I've attached the verbose (-vvv) doomsday.out file here. Out of interest, I haven't checked the source code but do the log entries get flushed to disk as soon as they're wri…
-
Something else I forgot to mention - I uninstalled Doomsday, cleared out the contents of the installation folder and then reinstalled it. This had no effect. [Edit: I also have a CrashDump file that is generated if that would be of use; I've atta…
-
I have a small update on this. I went back through the versions individually getting to #2282 and they all exhibit the same crash. I know for definite that #2283 was working so something must have changed at my end but I'm not sure what as I don'…
-
I'm running Windows 10 Pro 64-bit too. The update for #2287 was downloaded via the auto-updater. #2288 was downloaded and installed via the MSI package. I haven't gone back to check #2286 yet so I'll do that when I have a little more time. I only…
-
Just to add my 2 cents, I'm a big fan of the interface being within Doomsday itself. From a design perspective, it's much more consistent with most other commercial offerings. If there are settings missing that were previously passed in from Snowber…
-
Yep - that did the trick! Thanks Skyjake.
-
Unfortunately I'm still getting the same error. I'm running 2.1 #2271 and the error log is below. Application path: C:\Games\Doomsday\bin\Doomsday.exe Build: 2.1-Unstable [#2271] Created a new 32.0 MB memory volume. [Config::read] modules/Confi…
-
Will do and thanks for the quick fix Skyjake.
-
Ah! That makes perfect sense - I missed that setting and thought that "Data Files" would cover everything. Thanks for your help, definitely user error. And the new forums are looking good too, nice job.
-
Here you go.
-
I'm still having the same issue in build #2258. I'll try moving the .box folders (both the Hexen and the Doom Resource Packs) into a different folder and will report back the results.
-
@John: Yep, I can get them working as individual packages by removing the .box extension but I'm trying to get them working without the need to do that, thanks. @skyjake: I cleared the cache and restarted DE but neither of the .box add-ons appear…
-
skyjake wrote: That looks like a recent bug. I'll look into it: https://tracker.dengine.net/issues/2206 Hi skyjake. I noticed you submitted a fix for this in the recent build but unfortunately it's still not working for me. Interestingly…