Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Terrible NVG quality in triple monitor #3540

Open
jonpas opened this issue Mar 5, 2016 · 5 comments
Open

Terrible NVG quality in triple monitor #3540

jonpas opened this issue Mar 5, 2016 · 5 comments
Assignees
Labels
Milestone

Comments

@jonpas
Copy link
Member

jonpas commented Mar 5, 2016

Arma 3 Version: 1.56 (stable)
CBA Version: 2.3.1 (stable)
ACE3 Version: 3.5.0 (stable)

Mods:

  • @CBA_A3
  • @ace

Description:

Steps to reproduce:

  • Start Arma 3 in triple monitor
  • Put on NVGs
  • Observe the difference compared to single monitor

Where did the issue occur?

  • Dedicated

Placed Modules:

  • None

RPT log file:

  • N/A
@jonpas jonpas added the kind/bug label Mar 5, 2016
@jonpas jonpas added this to the 3.5.1 milestone Mar 5, 2016
@nicolasbadano
Copy link
Contributor

Oh, I suspect this might be related to the different amount of black surface in single vs triple monitor configurations. That might affect the "ColorCorrections" ppEffect in case that filters uses an average color value as part of the calculations.

If that's the case I'm not sure we can fix it, but we might be able to either change the parameters of the effect or disable it altogether based on the aspect ratio of the screen.

@nicolasbadano
Copy link
Contributor

BTW, I really love how restrictive the NVG FOV looks in the triple monitor setup.

@jonpas jonpas modified the milestones: 3.5.1, 3.6.0 Mar 16, 2016
@thojkooi thojkooi modified the milestones: 3.6.0, 3.7.0 Jun 19, 2016
@thojkooi thojkooi modified the milestones: 3.7.0, 3.8.0 Sep 4, 2016
@thojkooi thojkooi modified the milestones: 3.8.0, 3.9.0 Oct 8, 2016
@PabstMirror PabstMirror modified the milestones: 3.10.0, 3.9.0 Feb 11, 2017
@PabstMirror PabstMirror self-assigned this Feb 11, 2017
@PabstMirror PabstMirror modified the milestones: Ongoing, 3.10.0 May 31, 2017
@PabstMirror
Copy link
Contributor

Is this still an issue after the rework?

@jonpas
Copy link
Member Author

jonpas commented Sep 18, 2018

I will investigate.

@veteran29
Copy link
Member

Does not look like it was fixed yet.
https://imgur.com/a/07Aojlr

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

5 participants