Pages: [1] :: one page |
|
Author |
Thread Statistics | Show CCP posts - 0 post(s) |

Lun Coldwell
State Protectorate
|
Posted - 2009.03.24 01:16:00 -
[1]
I have a GForce8800 640MB memory card, running the newest drivers (182.08) on a up to date Windows Vista 32-Bit platform.
I run EVE with maximum graphics settings accross the board with good results and using nHance to allow for anti-aliasing+HDR settings together.
When I activate bloom in the graphics settings, ships, gates, stations, effects etc. render without any problems, however the new asteroids in the asteroid fields are blinking in a blinding white fashion. Resulting in the new asteroid belts resembling blinking, blindingly white xmas-light series.
I wanted to bring this to CCPs attention for bug-fixing.
|

Andoran TaVaine
|
Posted - 2009.03.24 06:31:00 -
[2]
You have to hand enter f0000045 in the anti aliasing compatability box in Nhancer for Nvidia cards and it will fix that. I had the same issue.
|

Avizheh
|
Posted - 2009.03.24 08:35:00 -
[3]
I get a similar thing with my ATI HD4850. Big white blobs. What to do?
|

Flinchey
Amarr
|
Posted - 2009.03.24 08:40:00 -
[4]
Originally by: Lun Coldwell I have a GForce8800 640MB memory card, running the newest drivers (182.08) on a up to date Windows Vista 32-Bit platform.
I run EVE with maximum graphics settings accross the board with good results and using nHance to allow for anti-aliasing+HDR settings together.
When I activate bloom in the graphics settings, ships, gates, stations, effects etc. render without any problems, however the new asteroids in the asteroid fields are blinking in a blinding white fashion. Resulting in the new asteroid belts resembling blinking, blindingly white xmas-light series.
I wanted to bring this to CCPs attention for bug-fixing.
you know there's a reason for not having AA in the in game options right? and that is that bloom+AA = no...
one or the other im afraid.
no bug fixing.
|

Lancel Anasazi
|
Posted - 2009.03.24 09:03:00 -
[5]
Originally by: Flinchey
Originally by: Lun Coldwell I have a GForce8800 640MB memory card, running the newest drivers (182.08) on a up to date Windows Vista 32-Bit platform.
I run EVE with maximum graphics settings accross the board with good results and using nHance to allow for anti-aliasing+HDR settings together.
When I activate bloom in the graphics settings, ships, gates, stations, effects etc. render without any problems, however the new asteroids in the asteroid fields are blinking in a blinding white fashion. Resulting in the new asteroid belts resembling blinking, blindingly white xmas-light series.
I wanted to bring this to CCPs attention for bug-fixing.
you know there's a reason for not having AA in the in game options right? and that is that bloom+AA = no...
one or the other im afraid.
no bug fixing.
Actually, it works fine using nhancer and the above HDR+AA compatability setting.
|

Lun Coldwell
State Protectorate
|
Posted - 2009.03.24 16:19:00 -
[6]
Edited by: Lun Coldwell on 24/03/2009 16:19:45
Originally by: Andoran TaVaine You have to hand enter f0000045 in the anti aliasing compatability box in Nhancer for Nvidia cards and it will fix that. I had the same issue.
Fantastic, that did the trick, thank you!
Previously I had it set to the drop down list option of 0000045, apperantly that isn't sufficient, rathyer you actually have to type the in "f" before the digits. In doing so a new option, "0xf0000045", comes in it's place and all the bloom and AA in EVE works in coherence without flaw.
|

Lun Coldwell
State Protectorate
|
Posted - 2009.03.24 16:23:00 -
[7]
CCP it might be good to add this to your http://www.eveonline.com/ingameboard.asp?a=topic&threadID=1006073 thread, as I'm sure I'm not the only one that will come across this issue.
|

Othran
|
Posted - 2009.03.24 16:57:00 -
[8]
As far as CCP is concerned it is NOT an issue. Eve does not support anti-aliasing. End of story.
Yes I know its ridiculous but there you go.
And for all the people saying HDR/bloom and AA is incompatible - bollox it is. It is all part of DX9 and 10.
|

Grez
Minmatar Core Contingency
|
Posted - 2009.03.24 21:19:00 -
[9]
Originally by: Othran As far as CCP is concerned it is NOT an issue. Eve does not support anti-aliasing. End of story.
Yes I know its ridiculous but there you go.
And for all the people saying HDR/bloom and AA is incompatible - bollox it is. It is all part of DX9 and 10.
NVidia cards only supported it after series 7. The 8*00 range supports it, the 7*00's do not. Whereas ATI have supported it since the 9*00 series. It's a reason why some people absolutely hate NVidia now - they haven't followed proper DirectX capability certification procedures. The entire reason DirectX 10.1 was released was because NVidia complained they couldn't get something working in DX10.0, so it was removed, and later supported in 10.1.
HDR + AA does not work on the NVidia 7*00 series and below, nor below the ATI 8*00 series and below. --- Have a rawr on me. |

Othran
|
Posted - 2009.03.24 21:24:00 -
[10]
Thanks for clarifying that Grez. I think we can now say Eve DOES support AA and HDR/Bloom yes... except of course we all know that Eve + AA = fail.
No excuse for it really is there?
|
|

Jobe Pheonix
|
Posted - 2009.03.27 02:00:00 -
[11]
Originally by: Lun Coldwell Edited by: Lun Coldwell on 24/03/2009 16:19:45
Originally by: Andoran TaVaine You have to hand enter f0000045 in the anti aliasing compatability box in Nhancer for Nvidia cards and it will fix that. I had the same issue.
Fantastic, that did the trick, thank you!
Previously I had it set to the drop down list option of 0000045, apperantly that isn't sufficient, rathyer you actually have to type the in "f" before the digits. In doing so a new option, "0xf0000045", comes in it's place and all the bloom and AA in EVE works in coherence without flaw.
I don't know how u guys were able to get that to work?!? I have a similar setup running 2 GeForce 8800 GTXs with nHancer v2.4.5 and was real happy to finally see the jaggies go away but now I have what used to be small asteroids light up in big, bright white christmas lights. So I followed the instructions here. My problem is that entering a f in front of the "00000045: AA & HDR" field under AA compatibility works, when I click on a diff tab, nHancer gives me an error saying "Please enter a hexadecimal value only!". So it will not save it like that. Now I don't know if maybe I'm using a diff version of nHancer (got it today, v 2.4.5) or what but I cannot go past that step.
Please help! Thanks in advance!
|

RiotRick
Black-Sun
|
Posted - 2009.03.27 08:35:00 -
[12]
Is there something similar to get it working on ATI cards? My HD4850 does the same thing in belts. Had to turn AA off to fix it. -- The future is black.
|
|
|
|
Pages: [1] :: one page |
First page | Previous page | Next page | Last page |