The Dark Mod released!!

Kin on 18/10/2009 at 15:14

Quote:

Also, any way to actually aim with the bow?

Just put the arrow tip touch what you want to hit (or a millimeter lower). For longer distances it gets vague (but you will not need to shoot that far).

Myagi on 18/10/2009 at 15:16

Quote Posted by Fidcal

I know within a program you can move the local program focus but I'm uncertain if code can seize Windows focus. Maybe it can? Anyone?

WM_ACTIVATE (/ WM_ACTIVATEAPP) / SetActiveWindow is the program/window "focus" stuff.

Bulgarian_Taffer on 18/10/2009 at 15:19

I don't believe it's an error. There is a problem and this should be tracked. Ignoring specific chipset family is a BAD idea.

And yes- if Doom 3 runs fine and it's bought only for the mod - It's a bad idea if the card is unsupported. So respectively - waste of money. I don't care for myself - I found my Doom copy for cheap, but what about the others?

I know it's still beta, anyway... but it's being released as a public beta. My FM practice shows this is a bad idea, but anyway - I tend to accept it, because it's a much bigger project than a FM campaign. Asking for testers in spite of being offered as a finished product in a public thread is better IMO.

So far I'm answering a request from the modders and providing them with screenies.

OK... First screenie I get (IMPORTANT: FAQ is already being followed and config files are OK):

(http://img4.imageshack.us/i/debuggingdarkmodscr1.jpg/)

Inline Image:

http://img4.imageshack.us/img4/6845/debuggingdarkmodscr1.th.jpg

Second screen I get (after hitting ESC):

(http://img4.imageshack.us/i/debuggingdarkmodscr2.jpg/)

Inline Image:

http://img4.imageshack.us/img4/5313/debuggingdarkmodscr2.th.jpg

Springheel on 18/10/2009 at 15:34

Quote:

Ignoring specific chipset family is a BAD idea.

We have plenty of people using that chipset without problems. We'll do what we can for your specific problem, but if Thief's Den worked fine, then it's not very likely that the chipset is the issue.

It's hard to see what's going on in that screenshot. Are you saying all the textures are black except for the torches?

Bulgarian_Taffer on 18/10/2009 at 15:38

Ayeh :)

So you say there are other people with Intel 946Gz Chipset which play the mod fine... Hard to believe that. My Doom 3 installation is fine. Doom 3 has been updated fine.. All darkmod files are being checked and they are ok - so the mod is correctly installed :)

Malleus on 18/10/2009 at 15:39

Is the "lean into doors to hear better what's on the other side" feature (a'la Thief2) in? I couldn't notice anything while leaning into doors, I ended up opening them slightly to hear the other side.

Springheel on 18/10/2009 at 15:41

Quote:

Is the "lean into doors to hear better what's on the other side" feature (a'la Thief2) in?

It's in, but I can't personally vouch for how reliable it is.

Tels on 18/10/2009 at 15:47

Quote Posted by Bulgarian_Taffer

If you see anything as black, except the torches, than that means you do not see compressed textures.

Either, you card does not support them - then you are out of luck without buying a new card. It won't be possible to uncompress the textures as they would not fit into your video memory. You might have luck with uncompressing, then downsizing them. Maybe it is even possible with the right settings in DoomConfig.cfg (meaning the engine does it for you, not you do the uncompress/downsize manually).

Or: your settings are accidentily so that doom does not use the compressed textures.

Here is the FAQ entry, maybe you can see if tweaking the settings will help:

(http://modetwo.net/darkmod/wiki/index.php?title=FAQ#Textures_are_missing.2C_screen_mostly_black)

And yes, posting somewhere that you need a graphic card that can do compressed textures in hardware is a good idea - I know TDM doesn't run on my laptop but so far I thought I am the only one with such a crappy graphic card. Keep in mind that even if it did support compressed textures the power of such cards is so bad that they won't be able to run the mod in a good resoluution, anyway.

Hiatus on 18/10/2009 at 15:50

congrats on the release, guys :)

Q's:

1) does the mod (properly) make use of multi-core CPU's for performance boost?

2) training map loads over 10 minutes on my rig (C2D class CPU, 2GB RAM, Radeon ATI X1950 GPU /w 256MB vRAM, WinXP, latest drivers), which is disappointing. How to speed up the map loading & on what it depends (CPU raw speed, amount of RAM, GPU power, amount of GPU video RAM etc?). AFAIR, it had sth to do with "image_*Compression" variables. How they should be set (what values)?

3) I can confirm that animated skybox in training map is broken on ATI cards (Radeon X1950, Cat 9.3, WinXP).

4) game crashed for me when right clicking the pole in object room in training mission

5) what are recommended (not minimal) hardware reqs to be able to play comfortably with max graphics settings and constant 60 fps in 1680x1050 and 1920x1200 resolutions (with AA and AF on/maxed)? Better to invest in:

a) faster GPU and which one/what class (how much of vid MEM?)
b) faster CPU (how many cores?)
c) more RAM (how much should be enough?

6) my 1st impression is that the mod is mostly ok for 1st beta release, but it's still rough round the edges and need more tweaking/polishing (like movement mechanics etc)

overall: :thumb:

Fidcal on 18/10/2009 at 15:52

Bulgarian Taffer: I know you've looked at the FAQ but exit Dark Mod and check you have those settings from the FAQ both in doom3/darkmod/DoomConfig.cfg and in the FM game folder, eg, doom3/training_mission/DoomConfig/cfg. See (http://modetwo.net/darkmod/wiki/index.php?title=DoomConfig.cfg) for more info about the multiple configs synchronisation.