#141
|
||||
|
||||
@ zap....
to have the "correct" field of view is a totally different topic... as long as the devs offer different FOVs in the game, and in some of them, contacts totally disappear in mid ranges, it can and should be seen as a bug... try 1024x768 for example, and you will see what im talking about...there is no doubt, that that is a bug....it has nothing to do with distortion, but the game just seems to forget to load one LOD model in that resolution. |
#142
|
|||||
|
|||||
Quote:
Quote:
Quote:
How would plan to achieve your desire and have it also suit everybody else? Quote:
Quote:
__________________
Intel 980x | eVGA X58 FTW | Intel 180Gb 520 SSD x 2 | eVGA GTX 580 | Corsair Vengeance 1600 x 12Gb | Windows 7 Ultimate (SP1) 64 bit | Corsair 550D | Corsair HX 1000 PSU | Eaton 1500va UPS | Warthog HOTAS w/- Saitek rudders | Samsung PX2370 Monitor | Deathadder 3500 mouse | MS X6 Keyboard | TIR4 Stand alone Collector's Edition DCS Series Even duct tape can't fix stupid... but it can muffle the sound. Last edited by Wolf_Rider; 10-30-2012 at 07:19 AM. |
#143
|
||||
|
||||
Quote:
the reason i keep mentioning the need to first set the correct "normal" FoV for your personal monitor size and home viewing setup, is that in any of these "visibility bug" discussions we need to start from a known quantity with most in-game parameters set to represent as closely as possible a similar real life situation. since that "normal FoV" setup is slightly different for most posters here, at least we will then be comparing apples with apples as you could see from the earlier tracks slipball posted, some people claimed to have perfectly good visibility of the aircraft on the ground 1200 meters below, but then it was found they were using the zoomed 35 view which is like strapping on some binoculars. others were still able to see the same distant aircraft in the wide view, yet some couldnt see it with a correctly set "normal FoV" for their monitor size. ie, once we have determined how it behaves under normal visibility conditions then the nest step is to add whatever altered settings can magnify the problem so we can identify its cause more easily Quote:
with you using a non native resolution a couple of things come to mind, for ex you have significantly increased your pixel size, and it is slightly more blurry because the non-native display resolution is not as sharp and crisp. none of that might matter in the bug you mentioned, but we dont know. i just prefer comparing apples with apples, and then progress from there
__________________
President Dwight D. Eisenhower 1953: Every gun that is made, every warship launched, every rocket fired signifies, in the final sense, a theft from those who hunger and are not fed, those who are cold and are not clothed. This world in arms is not spending money alone, it is spending the sweat of its laborers, the genius of its scientists, the hopes of its children Last edited by zapatista; 10-30-2012 at 10:09 AM. |
#144
|
||||
|
||||
looked interesting, i could see a difference in the comparison screenshots
__________________
President Dwight D. Eisenhower 1953: Every gun that is made, every warship launched, every rocket fired signifies, in the final sense, a theft from those who hunger and are not fed, those who are cold and are not clothed. This world in arms is not spending money alone, it is spending the sweat of its laborers, the genius of its scientists, the hopes of its children |
#145
|
||||
|
||||
sorry zapatista, you are wrong, although i appreciate many things you brought up in this thread already...
you said:" the reason i keep mentioning the need to first set the correct "normal" FoV for your personal monitor size and home viewing setup, is that in any of these "visibility bug" discussions we need to start from a known quantity with most in-game parameters set to represent as closely as possible a similar real life situation." and thats where i have to disagree with you, as this bug seems to be dependent on three different settings: resolution FOV model details this bug doesnt give a rats ... about "correct" FOV. you can simply recreate it: use a resolution of 1024x768 + FOV 90° + medium model details |
#146
|
|||
|
|||
Not sure I can use a 'normal' FOV considering I only use the TrackIR 6DOF to change FOV
|
#147
|
||||
|
||||
Quote:
__________________
i7 2600k @ 4.5 | GTX580 1.5GB (latest drivers) | P8Z77-V Pro MB | 8GB DDR3 1600 Mhz | SSD (OS) + Raptor 150 (Games) + 1TB WD (Extra) | X-Fi Fatality Pro (PCI) | Windows 7 x64 | TrackIR 4 | G940 Hotas |
#148
|
||||
|
||||
I HAD THIS PROBLEM REAL BAD BETWEEN 1 AND 2 KM PLAENS WER TOTALLY INVISIBLE
SOLVED IT SETTING TEXTURES TO ORIGINAL AND MODELS TO HIGH WHICH I CAN EVEN RUN IN MY POOR SYSTEM sorry about the caps but this solved it for me so should solve it for the rest
__________________
2.4ghz dual core cpu 3gb ram ASUS Radeon EAH4650 DI - 1 GB GDDR2 I PREFER TO LOVE WITHOUT BEING LOVED THAT NOT LOVE AT ALL |
#149
|
||||
|
||||
i assume you use native resolution?
|
#150
|
||||
|
||||
So... whats the fix now? I run monitor-native resolution 1920*1080, Textures original and Models High and I've got massive problems
|
|
|