🚀 go-pugleaf

Good, it's like the Quakes then.  Hm.  Also should mean same rules would
apply to the PK4 files that did PK3.   It might be easier to re-skin
models, and create newer ones than I was thinking too.  I wonder if
Nod-Tu Good found his way in here?  Chip?  pF-CF?  Heh!  Heh heh!
Thanks!
--
McGrandpa [AGQx]

pop wrote:
> autoexec.cfg is read after DoomConfig.cfg so entries in the
> autoexec.cfg take precedence.
>
> --
> pop is Mark
> Old age ain't no place for sissies.
> --
> "McGrandpa" <McGrandpaNOT@NOThotmail.com> wrote in message
> news:W7nSc.1589$M8.516@fe2.texas.rr.com...
>> Michael-NC wrote:
>>> "McGrandpa" <McGrandpaNOT@NOThotmail.com> wrote in message
>>> news:higSc.12073$va2.4149@fe1.texas.rr.com...
>>>> Stephen Gordon wrote:
>>>>> JK wrote:
>>>>>
>>>>>> I doubt it will run well. Even a 2.4 ghz P4 doesn't run Doom that
>>>>>> well., An Athlon 64 processor is great for Doom 3.
>>>>>>
>>>>>> http://www.anandtech.com/cpuchipsets/showdoc.aspx?i=2149&p=7
>>>>>>
>>>>>> Dave Bushnell wrote:
>>>>>>
>>>>>
>>>>> The Intel 2.4C is shown in that article to benchmark at 60.5 fps,
>>>>> since actual gameplay is locked at 60 fps max (benchmarks are left
>>>>> 'unlocked' for obvious reasons) it's a bit of a big call to say
>>>>> this is not running doom 3 that well.
>>>>>
>>>>> Also, get a new link.
>>>>>
>>>>> -Steve
>>>>
>>>> I'm quite pleased with my 1024x768 and 57 fps.  Though I do have a
>>>> 3 gHz cpu.
>>>>
>>>> --
>>>> McGrandpa [AGQx]
>>>
>>>
>>>
>>> Tuesday, August 10, 2004 12:53 AM
>>> McGrandpa <McGrandpaNOT@NOThotmail.com>
>>>
>>> "I'm using a GA8-IPE1000-G, P4-3.0E/800/1m L2(HT), 2 x 512m PC3200+
>>> at DDR400 dual channel, PNY FX5900-128 (400 core 850 ram), TB Santa
>>> Cruz. XP Pro, nv 61.77 and DX9.0c  all stock clocked
>>> just one run thru timedemo demo1 got 34.8
>>> in game settings are 1024x768 - High -
>>> in advanced, all on except vsync and aniso (OFF).
>>> McG."
>>>
>>>
>>>
>>> How did you get from 34.8 to 57 FPS?
>>
>> Running the game just with settings in the games menus got me the
>> one-time timedemo of 34.8, after which I learned I needed to run the
>> timedemo two or three times for a more accurate rate.   I will say
>> that I *think* the 34.8 would actually drop a couple of frames if I
>> had with all settings as they were.  Next, I got the links to
>> UpsetChaps and Viper lair guides.  Upset Chaps provided a good tweak
>> section and Inglo posted his autoexec.cfg file.  I tried a number of
>> changes to some of these cvars and found what seem to make the more
>> positive changes in game for me.   I'd made changes that actually
>> reduced image quality enough to be noticeable in game when I got the
>> 57 fps thru 5 runs of timedemo.  Since yesterday morning, I'd made
>> other changes that got image quality back up and with current config
>> I am getting 53.3 fps in timedemo after 5 runs.  In short, I don't
>> remember everything I did change to get the 57 fps consistently.
>> However, the game showed 'jaggies' in small detail areas (mouths,
>> eyes) and in straight lines at angles suggesting no AA or too little
>> AA.
>> In another post I suggested also posting the autoexec.cfg and
>> DoomConfig.cfg as some settings in these won't have an equivalent in
>> the game menus.  I'd stayed up all night till 6:30 am playing and
>> tweaking and was too tired to go thru and note the changes that seem
>> to make the most difference in keeping a good image quality with
>> higher FPS.  So, to that I'll post my .cfg's and what shows in my
>> game menus.
>>
>> Any thoughts, ideas, explanations to all these settings are welcome.
>>
>> Menu settings:
>> High Quality - 1024x768
>> Advanced menu:
>> HQ Special Effects - Yes
>> Enable Shadows - No
>> Enable SPecular - Yes
>> Enable Bump Maps - Yes
>> Vertical Sync - No  (this makes up to 20 fps diff in the timedemo
>> that I've seen)
>> Antialiasing - 2x
>>
>> my autoexec.cfg
>> seta com_allowConsole "1"
>> seta com_showFPS "0"
>> seta com_videoRam "128"
>> seta image_useCache "1"
>> seta image_cacheMegs "512"
>> seta image_cacheMinK "2048"
>> seta image_useCompression "1"
>> seta image_lodbias "0"
>> seta image_anisotropy "0"
>> seta r_lightscale "4"
>> seta r_multiSamples "2"
>> seta r_swapinterval "1"
>> seta r_mode "5"
>>
>> DoomConfig.cfg  (relevant bits)
>> seta r_debugArrowStep "120"
>> seta r_debugLineWidth "1"
>> seta r_debugLineDepthTest "0"
>> seta r_cgFragmentProfile "best"
>> seta r_cgVertexProfile "best"
>> seta r_forceLoadImages "0"
>> seta r_shadows "0"
>> seta r_skipBump "0"
>> seta r_skipSpecular "0"
>> seta r_skipNewAmbient "0"
>> seta r_renderer "best"
>> seta r_brightness "2"
>> seta r_gamma "1.5"
>> seta r_swapInterval "1"
>> seta r_useIndexBuffers "0"
>> seta r_customHeight "486"
>> seta r_customWidth "720"
>> seta r_fullscreen "1"
>> seta r_mode "5"
>> seta r_multiSamples "2"
>> seta image_downSizeLimit "512"
>> seta image_ignoreHighQuality "1"
>> seta image_downSizeBumpLimit "512"
>> seta image_downSizeSpecularLimit "64"
>> seta image_downSizeBump "1"
>> seta image_downSizeSpecular "1"
>> seta image_useCache "1"
>> seta image_cacheMegs "512"
>> seta image_cacheMinK "2048"
>> seta image_usePrecompressedTextures "1"
>> seta image_useNormalCompression "2"
>> seta image_useAllFormats "1"
>> seta image_useCompression "1"
>> seta image_roundDown "1"
>> seta image_forceDownSize "1"
>> seta image_downSize "1"
>> seta image_lodbias "0"
>> seta image_anisotropy "0"
>> seta image_filter "GL_LINEAR_MIPMAP_LINEAR"
>> seta com_showFPS "0"
>> seta com_purgeAll "0"
>> seta com_machineSpec "2"
>>
>> I'm wondering if it would be better to leave the DoomConfig.cfg file
>> alone, let Doom do its changing to it only, and put anything I want
>> to change in my autoexec.cfg?  Would things in the DoomConfig.cfg
>> that are duplicated in my autoexec.cfg be executed as in the
>> autoexec?
>>
>> --
>> McGrandpa [AGQx]  {not a GUru, just a GUy}