Forums » Windows
Fatal Error?
I keep trying to open up vendetta cause it looks like such a cool game but the window starts to come up and then it says fatal error. It's really annoying. Any suggestions.
What else does the fatal error say?
Do you have the required minimum hardware specs? If so, how much RAM do you have and what video card do you have? What CPU do you have?
Do you have the required minimum hardware specs? If so, how much RAM do you have and what video card do you have? What CPU do you have?
raybondo- all the fatal error says is, fatal error: could not open window. I'm very sure i have the minimum requirements. I Think when you say CPU your talking about the brand and i have a brand new Vaio released in late october or something like that. I dont know how to tell how much ram i have or what kind of video card i have but if you can tell me how i'll find out.
Ok, Go to the Start menu and select "Run..."
Type in dxdiag and then wait for it to get done collecting data. Click on "Save All Information..." to a file and email it to me at ray.ratelis@gmail.com
Type in dxdiag and then wait for it to get done collecting data. Click on "Save All Information..." to a file and email it to me at ray.ratelis@gmail.com
Ok, We figured out what the problem is. Basically this happens when the video card doesn't support antialiasing and the game thinks it can. The config.ini file needs to be edited to disable antialiasing until I fix the problem.
I'm having the same prob...how do i disable anti-aliasing?
set:
aa_type=0
aa_quality=0
in the [directx9] section.
I thought I fixed it and it only affects the DirectX 9 driver.
aa_type=0
aa_quality=0
in the [directx9] section.
I thought I fixed it and it only affects the DirectX 9 driver.
Those set are already there but its still messin up
Do you have AntiAliasing set to off in your system settings?
Reboot windows. Try again.
This problem cropped up in the beta of the new game client, and rebooting almost always fixed it for me (if not, rebooting twice would).
This problem cropped up in the beta of the new game client, and rebooting almost always fixed it for me (if not, rebooting twice would).