Jump to content

Recommended Posts

Posted

...with the F-14 it is unfortunately exactly the same! Both monitors run at 60Hz.

1. Monitor 3840x2160,  2. Monitor 1920x1080

Resolution =.

          x = 0;
          y = 0;
          width = 3840;
          height = 2160;
          viewDx = 0;
          viewDy = 0;
          aspect = 1.77777777778

DCS_MT_Bug.png

BS: Windows 11 Pro 23H2; CPU: Intel(R) Core(TM) i9-14900KS, 3.20 GHz; MB: ASUSTek, ROG STRIX B760-ASUSTek; RAM: Kingstone DDR5 6000MHz; GPU: AORUS GeForce RTX™ 4080 16GB XTREME WATERFORCE.

Thrustmaster HOTAS WARTHOG, Thrustmaster MFD Cougar, MFG Crosswind rudder pedals, TrackIR 5

 

 

 

Posted
23 hours ago, Sadhu said:

Al comparar la configuración de visualización de los módulos que funcionan con ventanas gráficas de exportación utilizando el nuevo subprocesamiento múltiple, tanto correcta como incorrectamente, encontré una solución temporal para mí.

Para
el archivo F-16
\Eagle Dynamics\DCS World OpenBeta\Mods\aircraft\F-16C\Cockpit\Scripts\Displays\MFD\indicator\LCD\page.lua
line

cambiar a


Para el archivo FA-18
\Eagle Dynamics\DCS World OpenBeta\Mods\aircraft\FA-18C\Cockpit\Scripts\Multipurpose_Display_Group\Common\indicator\BAKE\MPD_common_bake_page.lua
línea

cambiar a


Esta no es una solución a la raíz del problema, ya que todavía se notan artefactos alrededor de los bordes. Tampoco se ha probado su integridad en multijugador. Espero que ED encuentre pronto una solución.

It worked for me, Thanks.

Posted
2 hours ago, AnimalMother1775 said:

works for me but just failed integrity check on server . it let me connect but once i left the server i had the fail message. 

 

Yes unfortunately we need ED to fix it properly to get past IC checks.

It fails the "pure scripts" check, but passes pure client.

Servers like Hoggit and DCS Dogfighters will fail.

Praying for hotfix soon..

Pimax Crystal VR & Simpit User | Ryzen CPU & Nvidia RTX GPU | Some of my mods

Posted

Any solution for F-18 IFEI and Harrier?

My Hardware: ROG Strix X570-F Gaming - AMD 5600X @ 4.7 ghz - G.SKILL TRIDENT 32GB DDR4 3200 (14-14-14-34 CL) - GigaByte 3080ti OC 12gb - Corsair MP600 Force 1TB - 2 x EVO Nvme 500GB - Virpil Warbird Base T-50CM2 and TM Throttle + Trackhat + G25 + AOC AG271QG 27"

My Modules: JF-17, F-16C, AV-8N/A, F-18C, ASJ37, MiG-15Bis, MiG-21Bis, Fw-190D, Bf-109K, P-51D, F-86F, Ka-50 III, UH-1H, Mi-8MTV2, NS430, FC3, A-10C, Mirage 2000C, L-39, F-5E-3, SA342, Spitfire, AH-64, Mirage F-1CE.

My Maps: Nevada, Normandy, Persian Gulf, Syria, South Atlantic.

Posted
On 3/10/2023 at 10:30 PM, Sadhu said:

By comparing the display settings of modules that are working with export viewports using the new multi-threading, both correctly and incorrectly, I have found a temporary solution for myself.

For F-16
file
\Eagle Dynamics\DCS World OpenBeta\Mods\aircraft\F-16C\Cockpit\Scripts\Displays\MFD\indicator\LCD\page.lua
line

picture.additive_alpha   = true

change to

picture.additive_alpha   = false

For FA-18
file
\Eagle Dynamics\DCS World OpenBeta\Mods\aircraft\FA-18C\Cockpit\Scripts\Multipurpose_Display_Group\Common\indicator\BAKE\MPD_common_bake_page.lua
line

picture.additive_alpha   = true

change to

picture.additive_alpha   = false


This is not a solution to the root of the problem, as artifacts are still noticeable around the edges. It also hasn't been tested for integrity in multiplayer. I hope that ED will soon find a solution.

This fix has done the trick for me (WinWing MIP) thanks 🙂

Guido

Posted (edited)

It's disappointing, since we were excited about multicore support, but it's a beta version, so not a big deal. More disappointing is actually that we can not export RWR, IFEI (and probably more) without breaking the integrity check anymore. Is there are reason for that? I wouldn't consider exporting the IFEI in any way cheating, especially since exporting the DDI/MPCD is still possible without breaking the integrity check. That does not make any sense to me. Could you please add those two lines to the scripts, so we can still legally export those? Please? All simpit/cockpit builders are having this problem now.

Edited by abikns
Posted
6 hours ago, Mercury_1965 said:

Unfortunately not solve the prob for A10C_2

 

I saw this setting in Mods\aircraft\MIG-21bis\Cockpit\RADAR\Indicator\definitions.lua

object.additive_alpha   = true

Sadly, changing it does not help with my radar export.  Ah well..

 

 


 
Posted
12 hours ago, Mercury_1965 said:

Unfortunately not solve the prob for A10C_2

 

You had the problem with the A10C_2? Mine never had any issue so I wouldn't even know what file to examine to attempt a fix. If you changed something for the A-10C2, I'd say try changing it back.

CPU: 5950x || Memory: 64GB || GPU: RTX 4090

Input: Virpil CM3, TM F/A-18 Grip on Virpil WarBRD base, WW F-16EX grip on TM Warthog base, Virpil CP1 and CP2, Cougar MFD x2 / w CubeSim screens, StreamDeck XL x2, StreamDeck 15-key, TrackIR5

Posted (edited)

Any solutions for the RWR, DED and EHSI of the F-16?

 

Hopefully ED will fix this soon as it breaks most external cockpits.

Edited by PierPaolo
Posted

Tried this solution for the F5 and no joy.  The viewports are tanked.   I could not locate the suspected files in the F5 folder.  Maybe it is such an old module and not developed by Eagle, that these files do not exist in this module. ?????

Trackir4 using the latest Trackir 5 software, Win10 Pro [Creator Update] updated from Win7Pro Pro 64Bit, Intel® Core™ i5-2500 3.30 GHz 6M Intel Smart Cache LGA115 , GigaByte GA-Z68XP-UD4 Intel Z68 Chipset DDR3 16GB Ram, GTX MSI Gaming 1060 [6 GB] Video Card, Main Monitor 1 on left 1920x1080 Touchscreen Monitor 2 on right 1920x1080 .

Guest
This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...