11 réponses à ce sujet

[GhostOfGod]

I recently ugraded my computer and updated graphics drivers (Using ATI card). I was having all the same problems that everyone else seemed to be. My first problem was that everytime I would try to run the game from the nwloader or the toolset it would just crash the game. Of all the possible fixes posted the only thing that worked for me was to change the name of the nwmain.exe to something else. I just went with "nwmain_game". And now launch the game via desktop shortcut directly to the main and bybass the loader all together.

The problem now is that nwloader and the toolset can no longer launch the game since the "main" name is changed. I don't care so much about the loader but I used the option in the toolset, "Test Module", to test the game ALL the time.

So is there some way to force the toolset to open the game after the above fix? Can I "point" the toolset in a new direction so to speak?

Any help greatly appreciated.

P.S. My second problem was the invisible character and NPC problem. Unchecking the "Evrionment mapping on creatures" box in the ingame graphics options fixed that problem. Just in case this helps anyone.

Modifié par GhostOfGod, 02 janvier 2013 - 01:39 .

[Just-Me]

Here's how to cover all the bases:

social.bioware.com/forum/1/topic/187/index/3303069

[HipMaestro]

GhostOfGod wrote...
So is there some way to force the toolset to open the game after the above fix? Can I "point" the toolset in a new direction so to speak?

Did you try opening the module to be played in toolset beforehand then closing it and starting the module with the game.exe.  It will load the module name in the ini's recent file list, hopefully at the top.  Whether this works or not... dunno but it's the only idea I had.

BTW, for others (like me ) who may find your experimentation useful, please publish your OS and hardware specs at least so we can make the comparisons in the future... please.  Thanks, bro.

[GhostOfGod]

@ Hip Maestro:

Yep I tried doing that as well. As soon as you click "Test Module" the tool set minimizes like it normally does but then nothing happens..nothing at all. I suspect that when you click that it tries to run nwmain.exe which now has a different name so it can't?

Oh and sorry about not posting specs. Nothing fancy:

Game Version: NWN 1 v1.69 all expansions + kingmaker
Game Language: English
Retail or Digital: Retail Diamond
Processor Manufacturer: AMD
Processor Type: AMD Athlon II X3 450 (Rana)
Processor Speed: 3.2 GHz
Operating System / Service Pack: WindowsXP/SP3
System RAM: 4 gigs DDR3 1333
Video Card Manufacturer: ATI
Video Card Model: Radeon HD 5670
Video Card RAM: 512 megs GDDR5
Video Card Driver Version: Catalyst 12.8 / 6.14.10.7270 / 8.982.0.0 (all kindsa different numbers)
Sound Card Manufacturer: VIA/AMD
Sound Card Model: VIA/AMD High Definition Audio Device (integrated)
Sound Card Driver Version: 5.18.0.5514
CD/ROM Type: ASUS DRW-24b1ST

Modifié par GhostOfGod, 02 janvier 2013 - 07:07 .

[Pearls]

yes it just runs nwmain with the module name, is your nwmain now called nwmain_game.exe precisely?

[GhostOfGod]

@Pearls:

Changed name from "nwmain" to "nwmain_game" precisely.

[Pearls]

pmed

[GhostOfGod]

SOLVED!

Thank you Pearls.

[Nissa_Red]

Alright, in the hopes that it might help someone else from our community in the future, I would like to say that I had the same issues than you on one of my computers (WinXP/SP3, with an ATI Radeon card).

I could not launch the game through "nwmain.exe" : it would almost instantly crash. I could watch the intro videos if I launched the game through "nwn.exe" + "Play", but would crash soon thereafter.

So I renamed the "nwmain.exe" to something else, and could finally launch the game, but would have the same issue with the toolset than you, GhostOfGod. I could no longer hit "F9" to launch and test my modules directly from the toolset.

Today :

• I uninstalled the current ATI drivers on my machine thanks to this tool, provided by ATI themselves. Its usage requires to be advanced in the knowledge of how drivers work (the whole operation here is unfortunately not recommended for novice users!).
• I rebooted into "safe mode", and removed everything related to ATI drivers (leftovers from previous versions) on my machine thanks to "DriverSweeper", a tool you may find here. It's made by the Guru3D community. It is portable, it's free, and comes with no virus or malware.
• I then rebooted into "VGA mode", and installed the latest "Catalyst drivers" (13.1 as we speak).
• I rebooted one last time, and made sure to uncheck "Triple buffering" in the OpenGL settings of the "Catalyst Control Center". Everything else can remain maxed out, even "Catalyst AI" (and Environmental mapping works in game).
• I can now play the game without renaming the "nwmain.exe" file. This implies that I can have normal usage (keeping fingers crossed) of my beloved NWN and its toolset, yay!
• I even tested the latest NWN explorer (1.63), and it works without any modification or addition of dlls.

There you have it, in the hopes that it will work as smoothly for you as it did for me ^.^

Modifié par Nissa_Red, 03 février 2013 - 02:51 .

[GhostOfGod]

Oh wow. I just now saw this reply. Thanks for this info Nissa. I'm afraid to try it since pearls got it working just right for me. But I might just save what pearls made and give this a shot. Thanks again.

[Nissa_Red]

You're welcome ^.^

The ideal would be to test this on a "virtual machine" first, so that if it happens that it won't work for you, you could instantly discard the changes. As I said, unfortunately this manipulation is not meant for everyone (there is alot that could potentially go wrong with uninstalling drivers), and if you're happy enough with just renaming the executable to something else and don't mind losing on the Environmental mapping and toolset connection, it's probably best to just stick to it.

My suggestion is just an alternative that I wanted to share with everyone, since it worked (and continues to work) for me.

Modifié par Nissa_Red, 21 mars 2013 - 09:57 .

[Pstemarie]

Its not uncommon for nVidia or ATI driver updates to break NWN, although it seems to occur more often with ATI.