Activity
From 2009-06-07 to 2009-06-20
2009-06-18
- 21:54 Bug #721 (Closed): Paused game while opened menu bug
- If the player is standing on a floor with a height of -40 and you press Escape to get into the menu the game won't pa...
- 21:54 Bug #721: Paused game while opened menu bug
- Doomsday out of Heretic and Doom
*Attachments:*
* http://sourceforge.net/p/deng/bugs/_discuss/thread/c4e1a73e/3e23/a... - 08:45 Bug #720: HEXEN 32BIT Savegames not stored in linux
- did'nt read your first comment.
This is definitely a 32bit build, with the
described problem. - 06:42 Bug #720: HEXEN 32BIT Savegames not stored in linux
- dont know who and why someone changed the "hexen" tag to "64bit"?
its 32bit.
2009-06-17
- 12:14 Bug #720: HEXEN 32BIT Savegames not stored in linux
- This problem is looking likely to be limited to 64bit builds (not currently supported). In order to progress with thi...
- 07:19 Bug #720 (Closed): HEXEN 32BIT Savegames not stored in linux
- seems like the game is "doing" something but no savegames are stored.
and the offset of the selector arrow is wrong....
2009-06-16
- 00:23 Bug #693: Keybord and mouse controlls delayed
- Newer versions of Doomsday simply "play nicer" with the underlying operating system and by that I mean; Doomsday will...
2009-06-14
- 13:43 Bug #691: on screen text error
- Fixed in svn for 1.9.0-beta6.4
- 13:04 Bug #691: on screen text error
- > I have one comment about your commit... ...Since vsnprintf() returns the number of characters without the null, if ...
- 13:02 Bug #691: on screen text error
- Oh, and you should be able to see the HUD log message last character truncation problem now on Windows as well.
- 13:00 Bug #691: on screen text error
- An exported public implementation of dd_vsprintf() sounds fine.
I have one comment about your commit:
#ifdef WI... - 12:51 Bug #691: on screen text error
- There is one final decision to make regarding these; do we want an engine-side, exported, public implementation of dd...
- 12:21 Bug #691: on screen text error
- Ok, will do.
- 12:16 Bug #691: on screen text error
- I think we should go the dd_vsnprintf() route because otherwise the return value thing is a bit ugly and error prone ...
- 12:14 Bug #691: on screen text error
- I think that is going to be our best option. Either that or sort out our headers...
- 12:12 Bug #691: on screen text error
- Well, one option is to make it something like dd_vsnprintf() and use find/replace on all the instances of where it's ...
- 12:08 Bug #691: on screen text error
- That is what I've been trying to do but I'm hitting a brick wall because of the way our headers are setup (there are ...
- 12:04 Bug #691: on screen text error
- How about that earlier suggestion about naming it win32_vsnprintf() and using a #define from vsnprintf to that?
- 11:51 Bug #691: on screen text error
- That sounds OK to me though we will naturally have to ensure we don't use the return value or where we do, we account...
- 11:13 Bug #691: on screen text error
- On the bright side, I don't think the return value is used anywhere in the engine. It is vastly more important that t...
- 11:05 Bug #691: on screen text error
- Clearly I need another coffee. On re-reading the definitions again, yes I agree that the Windows varient is indeed be...
- 10:51 Bug #691: on screen text error
- I disagree. The difference is that the Windows version will return -1 if truncation occurs. The C99 returns -1 only i...
- 10:46 Bug #691: on screen text error
- Here is the definition for vsnprintf from MSDN:
"vsnprintf, _vsnprintf, and _vsnwprintf return the number of chara... - 10:42 Bug #691: on screen text error
- Here's the definition from the C99 (draft) for vsnprintf(): [n is the size of the output buffer]
"The vsnprintf fu... - 10:34 Bug #691: on screen text error
- Well, from that man page I interpret that the C99 standard defines the behavior like that: the return value is the nu...
- 10:19 Bug #691: on screen text error
- Looking at the function header comments you've added for snprintf and vsnprintf in dd_share.h I would like to clarify...
2009-06-13
- 21:37 Bug #691: on screen text error
- Yeah I can finish this (I expect I'll be commiting tomorrow as I don't feel much like coding right now).
- 10:18 Bug #691: on screen text error
- I committed the functions in rev 6668. Danij, I trust you can finish the implementation on Windows?
However, if vs... - 08:55 Bug #691: on screen text error
- Agreed. That sounds like the best course of action to me.
- 08:39 Bug #691: on screen text error
- The problem seems to be that the (nonstandard) snprintf() function is defined a bit differently in Windows and Unix. ...
2009-06-11
- 06:09 Bug #719 (Closed): Windowed resolutions wider than primary monitor do not work
- If Doomsday is launched in windowed mode with a resolution larger than that of the primary monitor, the window shrink...
2009-06-10
- 12:04 Bug #718 (Closed): Heretic: Chicken auto movement
- When the player is turned into a chicken, Dday seems to lack the random movement that occurs when you are stationary....
- 10:14 Bug #717 (Closed): Heretic/HeXen: MF_Ripper Blood
- In the original Heretic and HeXen (i.e powered the up Dragon Claw or Mages wand) individual blood splats caused by mi...
- 09:23 Bug #491: Tiny blood splat editing bug
- I'll also throw in that the Doom players punch and chainsaw actions are similarly affected by this behaviour, except ...
- 00:11 Bug #674: Segmentation violation: semi-transparent wall texture (bars)
- I'm sorry to say this problem persists in version 1.9.0-beta6.3 Jun 8 2009 (DGL).
- 00:10 Bug #674: Segmentation violation: semi-transparent wall texture (bars)
- Output from version 1.9.0-beta6.3 Jun 8 2009 (DGL).
*Attachments:*
* http://sourceforge.net/p/deng/bugs/_discuss/th...
2009-06-08
- 15:31 Bug #716: Compatible Dehacked file not loading
- The problem here is the completely bizarre way in which DeHackED choose to represent Text in its patch format. Rather...
- 14:37 Bug #716 (Closed): Compatible Dehacked file not loading
- I was doing some more testing of Doomsday beta 6.3, and decided to load Alien Vendetta, along with its dehacked file ...
- 01:34 Feature #1496 (Closed): Aspect correct scaling of UI and HUD elements/interfaces
- Game HUDs stretch to the same aspect ratio as the current resolution, resulting in horizontally stretched HUD graphic...
- 01:31 Feature #1495 (Closed): FOV cannot be set higher than 179
- The FOV in Doomsday cannot be set higher than 179, making a proper FOV impossible to obtain on very wide aspect ratio...
Also available in: Atom