Fan Mission: Return to the City v2 (01/03/2011)

[Shadowhide]

I finished the mission with TDM 1.03 and it still looked better than T1.

did you enjoy black textures and missing objects ? if you forgot, tdm_update.exe lying somewhere inside darkmod directory

[Mechs Delight]

Well, I don't know what's going on, but I can't get this mission to run. I've tried several of the suggestions in this thread as well.

 

My system:

 

Dell Studio XPS 8000

Intel Core i7 860 @ 280 GHz

8 GB RAM

64-bit Windows 7

Dark Mod 1.05

Edited April 10, 2011 by Mechs Delight

[Bikerdude]

we need either some screenshots or a desription of whats happening.

[Mechs Delight]

we need either some screenshots or a desription of whats happening.

 

I've also tried going in to change the video resolution, and not only does it not help make the mission work, it results in a blurry menu when I try to return to my old resolution.

[Bikerdude]

Ok, sound like your trying to get TDM, rather than this mission to run in a resolution it dosen't like..?

[Mechs Delight]

Ok, sound like your trying to get TDM, rather than this mission to run in a resolution it dosen't like..?

 

No, TDM runs just fine in 1920 * 1080 with other missions. I'm trying to upload the picture of the problem and the message boards won't allow it. I'm getting the Malloc Failure for 2097160 that so many others have gotten earlier with TDM 1.04.

[nbohr1more]

You made sure that your DoomConfig.cfg has these settings then?

 

 

 

 

seta image_usePrecompressedTextures "1" 

seta image_useNormalCompression "2" 

seta image_useAllFormats "1" 

seta image_useCompression "1" 

seta image_preload "1"

Edited April 10, 2011 by nbohr1more

[Mechs Delight]

You made sure that your DoomConfig.cfg has these settings then?

 

 

 

 

seta image_usePrecompressedTextures "1" 

seta image_useNormalCompression "2" 

seta image_useAllFormats "1" 

seta image_useCompression "1" 

seta image_preload "1"

 

Well, this is embarrassing. I think I forgot to change one of the numbers earlier. I tried again, and the mission started right away. Thank you.

[Melan]

Good to read that it works now!

[Baddcog]

I don't know what the deal is, but this mission (v2) just won't load for me.

 

I Dl'ed it. Started, loaded, it crashed with a malloc. (Didn't copy it down because i wasn't through).

 

Same happened with Heart. With Heart I dmapped, replaced in the pk4, it ran fine.

-------

Took a slightly different approach here.

 

I unzipped the map file, dmapped and got a leak right after a few missing tex. I suppose the missing texture can't seal the void because Doom3 doesn't know what properties it would have. Didn't want to 'corrupt' my clean TDM folder by unzipping everything into it (thus miss tex). So deleted the map files.

 

Tried to load again through TDM. Several times however I got the same issue, but never got a malloc again. It would load, then during the 'mission loaded please wait' phase I'd see the fps counter jump around like it's working, then right at about 30 seconds it would stop ticking. I waited a few times for up to 4 minutes. No response. ctrl-alt-del to bring up task manager and I'd get a doom3 stopped working dialog.

 

So system reboot, retry, same results, no malloc but it hangs.

----------

So I unzipped the entire pk4. dmapped. and just ran it through console. Worked fine but was getting late.

Took a screenshot of a closed portal and locked up so quit for the night.

 

Anyway, I took a screenshot, not sure if you're aware of this. But from start for a brief sec you can see a portal open and close, must be a distance check.

Not really that noticable, kindof fits with the typical LOD system in games, it's far away and if you aren't looking right at it...

 

Anyway, in the first vers (i believe with my gts8600 also) I was getting 6 fps. Now it's around 35-40. So pretty good optimization done for sure. If the street was just a biut longer at that T and wrapped around a bit more that portal could have closed and not been seen though.

[Bikerdude]

BC missing textures will cause a leak. But as I know the .pk4 is fine that you must have an FM still insitalled or some other corruption. Can you reset you TDM folder back to vanilla and then try the FM again.

 

regarding the second part of your issues - the low FPS after a dmap/map is normal is doom has been open for a while, deleted the generated files and do the dmap/map on a fresh start pf tdm and you will see better fps.

 

The VP issue, got a screenshot? and lastly re your 8600GT whats rest of the specs of your system hardware/software.

[Baddcog]

There's a pic in my last post of the VP.

 

I said I got low fps with my old card, the 8600gts (6fps-at start point) on the original map. My fps is fine with my new card (5850), TDM 1.05 and the new vers (40 fps - at start point).

 

It's not my system I'm sure. 5850 (1 gig ddr3), Q6600 2.4 quad, 4 gigs ram 800 ddr2, 7200 HD (for games, 10,000 for OS), Win 7 64 Pro.

 

I know the FPS ticks really slow in that after load 'wait period', my point was that at 30 seconds it completely freezes and I'm sure that's when the lock up occours.

 

My folder WAS clean, no missions installed. Until I gave up, unzipped the whole package, dmapped and then it worked from console. I assume same as Heart if I put MY dmapped files into the zip it would load from game just fine.

 

--------------

So I suspect there is something in the way my system dmaps, compared to other systems where the issues lie. As others have had no issues with this OR heart, and yet both wouldn't work on my rig until I dmapped locally.

I have no idea what the difference would be though.

[AluminumHaste]

I'm pretty sure I asked you this already but I can't remember the answer; have you tried flagging doom3.exe as Large Address Aware? Should be fine as long as you have 4 GB in your machine.

[Baddcog]

Nope, never heard of that. How do I do it, didn't see that in properties.

[AluminumHaste]

You need to manually edit the binary (doom3.exe) with a hex editor or you can use the various tools available on the internet. I can't find the one that I use, but try this one:

 

EDIT: nevermind that's just for X3, I'll keep looking.

 

EDIT 2: Ah, found it: http://www.techpowerup.com/forums/showthread.php?t=112556

 

File Download

[Serpentine]

Try :

image_usePrecompressedTextures 1
image_useAllFormats 1 
image_useCompression 1
image_useNormalCompression 0
image_downSize 0
image_useCache 0

Close doom3 after entering them, make sure that useNormalCompression is 0 on restarting it.

[nbohr1more]

Try :

image_usePrecompressedTextures 1
image_useAllFormats 1 
image_useCompression 1
image_useNormalCompression 0
image_downSize 0
image_useCache 0

Close doom3 after entering them, make sure that useNormalCompression is 0 on restarting it.

 

 

That's odd... others with the Malloc errors needed to set those to:

 

 

seta image_usePrecompressedTextures "1" 

seta image_useNormalCompression "2" 

seta image_useAllFormats "1" 

seta image_useCompression "1" 

seta image_preload "1"

 

I have 2GB of RAM so I don't think this mission pushes the 32bit limit to run but it might push the limit for dmap?

Alternate doom3.exe patch method that Bikerdude (and others have used):

 

http://www.ntcore.com/4gb_patch.php

[Baddcog]

I actually do have all those settings Serp. I changed a few yesterday due to a few posts higher in the thread, but they didn't do anything.

 

normal compression was 2.

 

Again, it was only 2 missions so far.

 

I'll try the Hex edit...

-----------------

 

I went ahead and uninstalled, wiped everything clean, updated, re-DL'ed map. Same thing, hanging after 30 seconds of 'please wait time'. (I even waited 10 minutes before ctrl-alt-del)

 

So I extracted again. Tried to dmap, but this time it hangs when it gets to , ah crap, placing primitives I guess. Waited about 10 minutes, nothing.

[AluminumHaste]

I actually do have all those settings Serp. I changed a few yesterday due to a few posts higher in the thread, but they didn't do anything.

 

normal compression was 2.

 

Again, it was only 2 missions so far.

 

I'll try the Hex edit...

-----------------

 

I went ahead and uninstalled, wiped everything clean, updated, re-DL'ed map. Same thing, hanging after 30 seconds of 'please wait time'. (I even waited 10 minutes before ctrl-alt-del)

 

So I extracted again. Tried to dmap, but this time it hangs when it gets to , ah crap, placing primitives I guess. Waited about 10 minutes, nothing.

 

Well yeah even for me when dmapping large maps sometimes I had to wait 15-20 minutes and Doom3 was "Not Responding" the whole time.

[Baddcog]

edit for AH^ - well, yesterday it took maybe 5-10 minutes to dmap. Then today it's hanging forever. (it was after fresh reboot yesterday, not today though)

--------

OK, after doing the Large Address thing the mission starts after 13 seconds of 'wait time'.

 

So that's good, I get to play the mission Thanks everyone.

----------------------

A little off topic.... Does this say something specific about my system? Is there something I need to worry about, etc... I've never seen most of my Ram being used anyway when watching the performance in task manager. I don't seem to have any problems running most of my games pretty much maxed out on a 1920x1200 res (though usually no higher than 4x AA).

 

I have an Abit IP35 Pro Mobo which is supposed to be (or was at least) a pretty decent gaming board, good bridges, cooling, etc..

 

I don't have many issues with lock-ups or crashes. And when I do it tends to be certain programs that just have those issues (Like TF2 after a bad update).

 

----------

How would I know if doing this to other programs would be beneficial?

[AluminumHaste]

The issue is that Doom3.exe was using over 1.8 gigs of ram when Dmapping and maybe loading large missions, which was causing Malloc errors (in my case anyways). Flagging a 32bit exe as LAA allows that executable to access 3 GB of the memory and leaves only 1 GB for the OS as opposed to 2GB for OS and application(s).

 

Operating systems based on Microsoft Windows NT technologies have always provided applications with a flat 32-bit virtual address space that describes 4 gigabytes (GB) of virtual memory. The address space is usually split so that 2 GB of address space is directly accessible to the application and the other 2 GB is only accessible to the Windows executive software.

 

The 32-bit versions of the Windows 2000 Advanced Server and Windows NT Server 4.0, Enterprise Edition, operating systems were the first versions of Windows to provide applications with a 3-GB flat virtual address space, with the kernel and executive components using only 1 GB. In response to customer requests, Microsoft has expanded the availability of this support to the 32-bit version of Windows XP Professional and all 32-bit versions of Windows Server 2003.

 

 

[Baddcog]

OK, so 7 is capable of using more Ram, but Doom3 doesn't know that.

[AluminumHaste]

OK, so 7 is capable of using more Ram, but Doom3 doesn't know that.

 

Any 32 bit OS has a limit of 4 GB or ram. By default Windows segregates 2 GB for applications and 2 GB for the Kernel. By setting the 3GB switch, you tell the Kernel to limit itself to 1 GB whenever an application with the Large Address Aware flag active, is running. This will allow that application to be able to address up to 3 GB of ram.

[Bikerdude]

BC/AH you need to download the 4Gb .exe file patcher,

 

- http://www.ntcore.com/4gb_patch.php

[AluminumHaste]

Yeah he has 64 bit, the 4GB patch will help for me (I have 6 GB of ram) but he only has 4 GB, not a good idea for him.