20 réponses à ce sujet

[Yaniv Balderman]

 hi,
I got a problem with the game, any time I install it, it writes "string ERORR_DX_INSTALL was not found in string table"
now, i can still play the game but every time i reach khelgar's part when i meet him, I cant see well in the game, its all green and weird and I cant play that way, it happens in the area of fort locke too. i cant see in the game.. i tried to make the graphic on high mode, low mode, nothing works... I really want to play that game and last time i played it i never got to see the end because changed computer...

can anyone help me pleaze? 

[CryHavocDogsOfWar]

Have you updated your graphics drivers? Tried getting the latest DirectX? If push comes to shove, a reinstall ma be in order.

[Yaniv Balderman]

yes, I did them both. but i fixed the problem without it, I just didnt make the update on the last time i install the game and it works great.

but thanks for trying to help.

[Sol9o]

i installed the game and the graphic bugs still comes up... only white and black when im meeting khelgar... ive reinstalled it. Updated it, installed mask and updated it as well but it just wont work.. im really out of clues... does anyone know how to fix this?



ive also tried to change the graphic settings to whatever possible, every combination. but still... it just wont work "sigh"

[BioSpirit]

I got exactly the same problem. Looks like the problem is present atleast in patch 1.05 and later. I haven't tried the unpatched version, how many show stopper bugs the 1.00 has ?

NWN2 is only 4 years old and it's no longer working !!! Who is responsible of this ? FIX IT !!

BTW, who ever is responsible about the camera control in NWN2 should never be allowed to touch a computer again.

Modifié par BioSpirit, 01 décembre 2010 - 08:58 .

[mcsupersport]

What are your machine specs, specifically Graphics cards, but all specs might help.



Make sure you have the proper DirectX version specifically 9.0c installed. Later versions will NOT work.

[BioSpirit]

mcsupersport wrote...
What are your machine specs, specifically Graphics cards, but all specs might help.
Make sure you have the proper DirectX version specifically 9.0c installed. Later versions will NOT work.

Core 2 Duo E7400, 4GB RAM, NVIDIA GeForce 9600GT, Windows 7 64-bit, DirectX 11 (8.17.11.9745)

So, you suggest that I should downgrade the DirectX to older 9.0c. Then what about the software that requires a newer version ?  Lets pray that Microsoft will implement a feature to allow an application specific installation of DirectX in their next version of Windows.

I have played some old DirectX 7 games with my current drivers and thay are working well. DirectX is supposed to be backwards compatible. So, if NWN2 got some problems with it. Then I suppose who ever is responsible of the garbage should fix it. Am I the only one loosing nerves with a fraud game products. NWN2 has never worked perfectly well.

[kamalpoe]

BioSpirit wrote...
So, you suggest that I should downgrade the DirectX to older 9.0c. Then what about the software that requires a newer version ?  Lets pray that Microsoft will implement a feature to allow an application specific installation of DirectX in their next version of Windows.

DirectX 9 and later DirectX versions can be installed side by side. There is no "downgrading", only the game using the version of DirectX it was written for. End result: what you pray for is already implemented.

[BioSpirit]

When I force an installation of an older version of DirectX 9.0c I receive error message "Couldn't locate entry point for MakeCriticalSectionGlobal in dynamic link library KERNEL32.dll".



Has anyone got the NWN2 to work under Windows 7 64-bit ?

[kamalpoe]

BioSpirit wrote...
Has anyone got the NWN2 to work under Windows 7 64-bit ?

Yes. Many people. Make sure you are administrator, and run NWN2 in xp mode (it may have to be installed in Admin mode if you did not). A google search will turn up a thread that works for you.

[BioSpirit]

4 years old game shouldn't need any XP modes in order to work. There are a lot older games and they are working perfectly fine. The Elder Scrolls IV: Oblivion is as old as the NWN2 and it doesn't require any hacking nor XP modes to work. It's only the skill of the programmers that will define the quality of the product. Some people just shouldn't be allowed to work with a commercial software products. They don't let just anyone to fly a commercial airplane either.

I have the Windows 7 (Home Premium) and it doesn't have the XP mode available.

But anyway thanks to you kamalpoe and mcsupersport, I'll appreciate the help.
Now, I'll find some other game to play.

Modifié par BioSpirit, 02 décembre 2010 - 10:17 .

[Selene Moonsong]

Here's the deal...



NWN 2 was written for Windows XP 32-bit. However, it will run on a Windows 7 64-bit machine.



Before it will run, however, you need to install the following:



1. DirectX 9.0c (Redistributable). This is the version that software developers include in their games and is available from Microsoft's Download site. Installation of DX 9.0c (Redist) will not overwrite later versions of Dx, and will co-exist on your syste,



2. .NET Frameworks 3.5 (also available from the Microsoft Download Site).



3. Ensure you Video card meets the minimum requirements, and I HIGHLY suggest that that your video card meets or exceeds the Recommended configuration. Note that if you have SoZ that the minimum and recommended requirements are higher than for NWN 2 and MoTB.



4. Follow the instructions for Installation as posted in the Installing NWN 2 topic shown as an announcement at the top of this forum.

[daBear is in]

As suggested, I downloaded the DirectX 9.0c (Redistributable) installer and the .NET 3.5 installer on my my Windows 7 (64 bit) machine. The DirectX 9.0C installer seemed to run but I can't find it on my computer so i don't know if it installed properly.

I ran the .NET 3.5 installer but got no feedback that the installer did anything. My program list does not show .NET 3.5. Since I have .NET 4 do I really need .NET 3.5?

Anyway, after trying to install DirectX 9.0c and .NET 3.5 NWN 2 still has major graphics problems.

[Skuggans]

I was considering to buy this again through steam, my original package is gone.



But reading through forums and such it seems there is major issues running the game on W7 64-bit. I dont know if I want to go through all of these problems.

[mosreal]

Skuggans wrote...


I was considering to buy this again through steam, my original package is gone.

But reading through forums and such it seems there is major issues running the game on W7 64-bit. I dont know if I want to go through all of these problems.

I just bought it on steam and I'm having these same issues I'm downloading directx v. 9 which hopefully fix the problem

[Richard Uther]

Double Post, sorry!

Modifié par Richard Uther, 12 janvier 2011 - 12:03 .

[Richard Uther]

I can see that a lot of people are having different graphic issues, so I'll just post a solution to one of them. Mind you, I don't know if any of the people who posted here have this issue in particular, but at least it's a fix for anyone who stumbles on this thread because they have it.
I'm talking about the infamous 1/4 of the screen glitch, as seen in the following link:

http://www.gamebansh...23&d=1272516103

The solution is rather simple, because what causes the bug is the sky: You simply need to deactivate it by accesing the console. The key to do this is usualy the one right above the "Tab" key, but it can change depending on your keyboard's language configuration - In my case, spanish, it's ALT + the key to the right of the Ñ.

Once you have the console, you simply need to type "Debugmode 1", followed by "Sky 0", then "Debugmode 0" so you don't have to see all the text the game throws at you while in debug mode.
The only issue is that you will be playing without being able to see a single star in the sky, but it beats downgrading drivers; and with that I would like to add something to the general population:

Stop treating people as if they were idiots!

The only solution to this problem I've seen was "Downgrade your video drivers" and then fake statements, such as "Downgrading wont be detrimental to your computer's performance" followed by a bunch of nonsense explanations that are not true.

With the latest Nvidia drivers I can be working in the toolset, while I'm playing Civ V under DX10. While if I roll back to previous drivers I have to settle for Civ V under DX9 and no toolset. Face the fact that they changed something in SOZ that creates this glitch with newer Nvidia drivers, because otherwise it makes no sense to see vanilla NWN2 working perfectly, while a fully updated game goes bonkers

Just some productive criticism here, I hope nobody takes it the wrong way.

Rich

Modifié par Richard Uther, 12 janvier 2011 - 12:04 .

[NWN DM]

Richard Uther wrote...

The only solution to this problem I've seen was "Downgrade your video drivers" and then fake statements, such as "Downgrading wont be detrimental to your computer's performance" followed by a bunch of nonsense explanations that are not true.

With the latest Nvidia drivers I can be working in the toolset, while I'm playing Civ V under DX10. While if I roll back to previous drivers I have to settle for Civ V under DX9 and no toolset. Face the fact that they changed something in SOZ that creates this glitch with newer Nvidia drivers, because otherwise it makes no sense to see vanilla NWN2 working perfectly, while a fully updated game goes bonkers

Just some productive criticism here, I hope nobody takes it the wrong way.

Rich

If it we're accurate, I'm sure nobody would.

It is a known fact that Nvidia released a number of successive driver versions in the last 6 months or so of 2010 that caused issues with NWN2.

A few minutes of searching would find this information.  It would also find that Nvidia released a version, (260.99) in October of 2010 just for game compatibility.

Most people who are having graphical issues in exterior areas have found that this driver version addresses them.

[Richard Uther]

Look: I'm not saying the drivers had nothing to do with the issues. Even though now that I re-read my post it might have sounded that way.

I agree, it's a well known fact that the drivers had issues with NWN2, but mostly if you had the second expansion and the latest update! so It's not that they had issues with NWN2, but with something that was changed for SOZ.

Now, I'm not saying "This is all Obsidian's fault", I don't think it is at all. But putting the sole blame on Nvidia as if they were some kind of monster, lying to people by telling them that rolling back their drivers would not only fix the problem, but that their video card will work just as good as with the new ones... that's irresponsible at the least.

And the worst part is seeing how all these people -and I'm not pointing fingers here, just speaking in general - spent hours, and hours repeating the same "fix", when it was just a matter of a simple console command that took me about 10 minutes to figure out.

Why am I posting this today and I didn't when this was a problem? Well, because I lost my internet connection right after the problematic drivers came out and only recently got it back.

All I'm saying, in a nutshell, it's that you shouldn't tell people not to update their software just because it's easier than to actually do some research. I hope that makes sense to you.

Rich
 

Modifié par Richard Uther, 12 janvier 2011 - 03:42 .

[NWN DM]

It seems unreasonable to me to expect any software developer to build in forward compatibility for driver versions not yet released, possibly years down the line.

Changing the drivers works for most people to get NWN2 to display properly.

It is certainly possible that the very same update/roll-back may cause other games to run at sub-optimal levels.

But usually the question we're answering is essentially; "how do I get NWN2 to display properly?", not inclusive of considerations with other games.

But unless you and I are both Doctor Who fans, we should be able to still be able to agree to disagree.

[Richard Uther]

Well... I don't know about Dr Who, but I'm a fan of Al Bundy, so that gives us something to have in common.



I'm also not disagreeing with you, to be honest. I'm just saying that in this case, the fix was easy enough, so that nobody should've had to roll back. In fact, I could say that uninstalling Soz fixed the issue just as easily, and without any detriment to other games.



What bothered me were the blatant lies, more than the less productive fix, if you know what I mean. And by all means, I'm not talking about you. I've been around since the toolset beta stage, so I know you're a very helpful bloke.



Rich