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

[xabbott]

Originally Posted by Elwin

I heard Nvidia said the problem is fixed with newest beta .. cant be sure tough. I am fine with my 191.07

I tried the beta, still had the error.

I went back to 185.85 and the problem seems to be gone. In the end it wasn't too bad because my performance went up across the board and my flat panel scaling options work again. Yay.

Hopefully Nvidia/1C get it all sorted eventually though.

[geldonyetich]

Judging by this thread on the official NVIDIA boards, the same problem exists on King's Bounty: The Legend as well. Same solution, roll back to pre-current NVIDIA drivers.

[idontlikestaem]

I had the exact same error message but have an ATI 4870, so I didn't think it was the drivers.

Fixed it by:
- installing the demo
- tried running the demo and got same error
- went into the demo\game config file and set the screen resolution to my default (x-1920 y-1080).
- the demo started working!
- this created and .ini file for the demo.
- went into the users\yourname\ documents\games\kb demo folder and found the .ini file.
- copied this into the full game's \documents\games\armored princess folder.

The full game started

Hope this helps some people.

[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.

[Breadfan]

As explained in other similar posts, this problem is rooted in the `optional` Windows updates that get installed.
Every time Micro$oft include a driver in these, it plays havoc with the `event handlers` within DirectX (those files with names like FILE.cpp).
The only sure way to fix this, is to download the latest NVidia/ATI drivers from NVidia/ATI, then you have to reinstall DirectX to get things back on track.

Personally, I turn off `optional` Windoze updates, they create too many problems, busting things that already worked.