Jump to content
The Dark Mod Forums

nbohr1more

Development Role
  • Posts

    12146
  • Joined

  • Last visited

  • Days Won

    200

Everything posted by nbohr1more

  1. From a practical POV a contest that requires the use of the new AI and mantling would be a great promotional tool at Moddb
  2. Did you try to manually copy the gamex86.so to your darkmod directory?
  3. Congratulations! (It's good to reload the OS once in awhile anyway )
  4. FM based on a movie sounds great to me (as long as it's a fun movie... no Sideways theme please .)
  5. Thanks! That does sound similar to the polygon based geometry that Splash Damage alluded to. I do see the issue there. You would need to find four opposite edges of each n-sided plane to calculate the center position so that you could scale outward from the plane center in sync with scaling away from the model origin.
  6. That video discussion reminds me of one thing that new players might get hung-up on: When missions are loading, especially ones without progress bars, there are long idle periods where a new player would not know whether anything was happening or there was a lockup. I calm myself by setting com_showFPS so I can at least see the numbers flicker to life every couple of seconds. Some basic animation other than the optional progress bar would make the mission load process less nerve-wracking.
  7. You're welcome. I hope your new card works out. (An OS reinstall was really the only other option short of changing hardware.)
  8. No, there is no way to tell if the BIOS updater utility depends on some running Windows service. If this were 2004 I'd say yes but who knows these days. (I miss BIOS update floppies...). Good luck. (I've never killed a Motherboard with a BIOS update nor do I know any other PC tech who has done so. The risk is very small. I wouldn't be smug about it though or a power-outage might happen mid-flash... at least that would be my fortune )...
  9. I would look at an ATI 5850 or 5870 as they should have reasonably stable drivers and great price for performance. The new ATI 69xx and 68xx series still have driver toothing issues so you might end-up in the same situation if you pick one up. Really even older cards as far back as an X1600 (or older) series can run this mod, most of the limitation is on the CPU side (where you have reasonable strength). The new HDR-lite mode might be a little heavy on a mid-range cards for some missions so HD3650 or better might be advisable. Approx: $50 ATI 4650 1GB http://www.newegg.com/Product/Product.aspx?Item=N82E16814131360
  10. I hate to bring this idea up again, but that Motherboard was made right during the lawsuit war between Intel and Nvidia. When nForce motherboards were pulling this crap for ATI cards they eventually relented and released BIOS updates that fixed most of those problems. Now that the spat is mostly settled, ASUS may have a better Intel BIOS that is more Nvidia friendly. So... a BIOS update? Before checking that, you could also just try getting the latest ASUS chipset drivers (instead of Intel's version) which may be fixed compatibility with Nvidia cards as well... Or you could get a ATI/AMD card as that is what your motherboard was designed to work with...
  11. Sounds like the Motherboard might have onboard ATI graphics? If your monitor cable connected directly to the Video Card instead of a port built into the Motherboard? Yes, the original drivers might have the correct INF data if the generic nVidia drivers don't... That is a valid option.
  12. No problem. If you want to fiddle with your config you should make an Autoexec.cfg and place your changes there so you can easily see what you've changed and change it back (smaller list to parse). Make sure to leave comments in there too...
  13. If it's allowed in your locality, I recommend you download the Darkmod torrent using a torrent client that allows you to select individual files. Then just download the DoomConfig.cfg. (Make sure to remove any Autoexec.cfg you may have added). Or just download the whole darn thing directly and take the needed file (as soon as Moddb authorizes the v1.03 I uploaded...)
  14. I'd say that is the opinion of a good number of folks here.
  15. Kill Spybot in Normal mode and Install the drivers in Normal Mode. XP SP3 is terrible at driver installs in Safemode. They added something called the "Windows Installer Service" and pretty-much destroyed the utility of Safemode. (It was a horrible decision and I think they did it so XP would be a little worse so folks would jump to Vista or Win7...)
  16. Windows has a habit of leaving processes alive after their Service has been shut-down so anything's possible... You might see an SDbot or TeaTimer process in Task Manager that you can kill... Edit: Oh I see a problem. If you have Spybot set to auto-start with Windows any changes you make to protected areas in Safemode will be regressed by Spybot when Windows starts in Normal mode. It may be best to temporarily uninstall Spybot if you can't disable the file/registry/directory change protections...
  17. Make sure Spybot's "Tea Timer" is not protecting either the Windows\System32 directory or the opengl32.dll. I believe a vendor version replaces this one. Try placing NVOGLNT.DLL in your Doom 3 install directory as a workaround.
  18. Can you copy more of your console error? Also, is the screen you are trying to play from designated as your Primary display? (I would try the 195 WHQL version tried in this thread if you haven't already.) Finally, this may sound strange but some Spyware has been know to hook into the Device Manager registry keys (the symptom is usually a blank white page when opening the Device Manager), you could try running Super Antispyware or some other anti malware then running the driver cleaner then reinstalling the drivers. If it were my system, I would also download the latest BIOS from ASUS in case the card isn't being properly detected but upgrading your BIOS is risky so I will let you make that call.
  19. More curiosity: So if I read this Doom3world article: http://www.doom3world.org/phpbb2/viewtopic.php?p=151225 ...and cross-reference this Splash Damage reference: http://wiki.splashdamage.com/index.php/Collision_Meshes I see that Collision is not really a traditional Model to Doom 3 per se but instead is always treated as BSP. So unlike the Ground Zero style Vertex manipulation you would need to manipulate BSP nodes to scale the Clip Models? If so, have you found the corresponding internal structure for collison BSP node data? Or is there an internal polygonal data structure (confirming Splash Damage's assertion that Collision is rendered as Polygons rather than triangles...) ?
  20. I would go with the latest WHQL drivers for XP. I don't think that the Extension Limit issue affects Doom 3 but WHQL should be known to work with the game.
  21. This is an Nvidia GTX 260? Which add-in partner made it? Did you install their drivers? Please post the specifics from GPU-Z.
  22. Doom 3 itself won't start? I would make sure that nothing is in the "Doom 3\Base" directory other than the files that come with the application. I would also make sure that the "Threaded Optimizations" setting is set to "disabled" (might be invoking the wrong thread to initialize the OpenGL ICD). (Re-installing your Motherboard Chipset drivers can also knock loose Enum registry keys tied to old driver revisions so you could also try that after Rebb's driver cleaner recommendation for extra measure...) Intel Chipset Driver: http://downloadcenter.intel.com/Detail_Desc.aspx?agr=Y&DwnldID=18494&ProdId=816&lang=eng
  23. Did you follow these steps for the Steam specific launcher? http://wiki.thedarkmod.com/index.php?title=FAQ#Does_it_run_with_the_Steam_version_of_Doom_3.3F If not, you should still be able to launch The Dark Mod from within the "Mods" sub-menu after launching the game. Another thing to check is whether you have the latest motherboard Chipset drivers. Just for verification please post the results of these steps: Open Doom 3 and hit Ctrl+Alt+~ (tilde, ^ on German keyboards) to open the console. You'll see the version printed in the lower left corner of the console. It should read 1.3.1.1304. If your version is ending on 1302, you've got the wrong patch installed.
  24. Which version of DirectX do you have installed? Also, is the 1.3.1.1304 patch applied?
×
×
  • Create New...