Armored Princess direct 3d error please help me !!! thanks

[seattle82m]

I created the account just to share how to fix the problem

The error that I got was:
C:\work\skyfallen\tbm\BMRender\rmode.cpp(5534): Directx call failed: -1,-1,E_FAIL (an undetermined error occurred inside the direct3D subsystem)

The problem appeared after I updated my nvidia drivers (to the newest 195.62 version). The game would not even start. To fix that I deleted the game.ini file located in
C:\Users\(your user name)\Documents\My Games\Kings Bounty Princess

I was able to start the game but it would crash when rotating camera and give me the DirectX error.

To fix it, simply roll back to the previous drivers or install alternative drivers ( I use a laptop and got mine from http://forums.laptopvideo2go.com )
After installing an old driver (180.43) the game is working witout a problem. I should be done playing with the game in a couple of weeks and I will update the drivers then.

Hope it helps.

PS: oh and don't bother reinstalling DirectX. I did it three times, it will not fix the problem.

[Elwin]

Very nice that you shared this with us

[Seth2208]

Nice solution, but I ask is Anti-Aliasing really wroth all problems... I mean rolling back drivers can cause problems in other games... for example, I can not play Borderlands with older drivers. But if you just turn Anti-Aliasing off, all problems gone... and I can live without Anti-Aliasing. And I use nVidia drivers version 195.62 and Windows 7 x64 combo, works without Anti-Aliasing, no errors, no crashes, playing since my first post.

[xabbott]

I'm using Win7x64, 4GB ram, GTX 275 (1680x1050), driver version: 195.62

C:\work\skyfallen\tbm\BMRender\rmode.cpp(5509): DirectX call failed: -1, -1, E_FAIL (An undetermined error occurred inside the Direct3D subsystem) (img)

So turning off AA didn't seem to help. Only way for Windows 7 users to get this running is driver rollbacks?

[geldonyetich]

I can confirm that it seems that version 195.62 of the NVIDIA Windows 7 32-bit drivers are a cause of the trouble. When I downgraded to 185.85 I was able to run the game fine, but 195.62 crashes before reaching the the main menu but after the initial splash videos with an error message like the one you can see in the original post.

This is when attempting to start the King's Bounty: Armored Princess demo, I can only assume full retail has the same problem.

These previously selected solution of deleting game.ini does not apply because I had no such file. (Probably because I had yet to run the game successfully prior to downgrading my drivers.)

[fengjingyu]

I also use the newest nvidia driver 195.81 and got the problem.
My solusion.
When the anti-aliasing option is off:
find "game directory"\data\dafault.ini文件：
find "antialiasing"
change the following lines to:

##################### antialiasing
# antialiasing enable (0 - none, 2 - hardware)
setf ~r_fsaa 0
# render buffer size factor
setf ~r_fsaa_h_sample 2.0
setf ~r_fsaa_v_sample 2.0

When the anti-aliasing option is on:
change the lines in default.ini to:

##################### antialiasing
# antialiasing enable (0 - none, 2 - hardware)
setf ~r_fsaa 0
# render buffer size factor
setf ~r_fsaa_h_sample 0
setf ~r_fsaa_v_sample 0
Then enter the game, and you may find the screen is black. However, you can see the option.
Then go to option to turn off the antialiasing. Exit the game.
Then go to default.ini and change the lines back to:

##################### antialiasing
# antialiasing enable (0 - none, 2 - hardware)
setf ~r_fsaa 0
# render buffer size factor
setf ~r_fsaa_h_sample 2.0
setf ~r_fsaa_v_sample 2.0

Enter the game again and every thing is OK.

[Akkim]

I will continue to check into my solution - but as of the moment, what I believe appears to be part of the problem is that the various .INI files are not writable with the default permissions provided as part of the Demo Installation package.

After deleting the game.ini file found in c:\users\<username>\my documents\my games\Kings Bounty Princess Demo, I had been attempting to tweak with game.ini in C:\Program Files (x86)\1C Company\King's Bounty. Armored Princess Demo\data.

That's when I found the files were all set to Read Only in Windows. I adjusted that to allow me to modify those files.. after that I was able to adjust the settings and make changes that actually showed up in the USERS game.ini.

So from what I've found, it might be possible this is a problem (since it spans both ATI and nVIDIA users) that is attributed to the Demo's behavior under Windows 7 x64 versions and file permissions not being properly set?

EDIT :: Nevermind, Still Crashing.

Things I have attempted to prevent the Demo from Crashing ::
-- I have uninstalled / reinstalled the demo
-- I have redownloaded the demo from Impulse
-- I have tried BETA Drivers, I have tried CURRENT drivers, I have tried OLDER drivers (I have a nVIDIA GX260).
-- I have been renaming the game.ini in my My Documents location and the game will load up again.

Right now I have it running, will see how long this lasts.. but it's definitely not something I feel is "stable"

Nevermind, as soon as the character creation is complete, the loading screen finishes.. I get sliver of some kind of game display and then it crashed.

As has been posted by many people the text of the error ::

Application aborted!
C:\work\skyfallen\BMRender\rmode.cpp(5509): DirectX call failed: -1, -1, E_FAIL (an undetermined error occurred inside the Direct3D subsystem)

--Micah

[evilbob]

Same boat as you guys. Crashed every few minutes when panning the camera in world view with that annoying direct x error in windows 7. Oddly enough putting the game in windows xp sp3 mode made the game playable with a lot fewer crashes however, i'm now taking the boat to verona and getting the error instantly upon arrival in the first second of the loading video for the island.

Really wish someone would patch this game, even unofficially.

[Kings Bounty Hunter]

I'm having the same problem in KBTL on my mage impossible campaigh, so bloody annoying.

I'm not rolling back my graphic drivers ffs

[bug]

I had the same problem. 195.xx and 196.xx drivers from nvidia are bugged. 191.xx are working fine, seems to be the latest working driver.