Jump to content

Recommended Posts

Posted (edited)
6 hours ago, UTurista said:

 

 

Untitled.png

+1

This same thing happened to a friend of mine (to me it happens in MFD, instead, there's huge mosaic on the right)

Edited by Saruman
Posted (edited)
3 hours ago, 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.

Workaround seems to be working for me in the F-18.  Thanks!

EDIT: this is in F-18 with WinWing MIP.

Edited by rob10
  • Like 1
Posted
5 hours ago, 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.

Thank you so much!!!! This completely fixed the issue for me 

  • Like 1

[sIGPIC][/sIGPIC]

Nvidia GTX Titan Pascal - i7 6700K - 960 Pro 512GB NVMe SSD - 32GB DDR4 Corsair - Corsair PSU - Saitek x52 Pro - Custom FreeTrack IR Setup - iControl for DCS

Posted (edited)

Booted up the new MT version of open beta to see how much improvement there was, and while the increase in FPS was significant (gained ~30-40 FPS), the frames being rendered were somewhat... unusual.

First thing I noticed was that with the 3 monitor (LMFD-Center-RMFD) setup, the MFD's were not cleanly refreshing. The new images were being overlayed in the remnants of the old images, making the MFD displays useless. The separate monitor MFDs were also rendered in the night yellow/orange while the cockpit MFDs were the normal (and desired) green day color. Additionally, the control indicator overlay was displaying a nearly solid red box with the lines and diamond barely visible.

The second thing I noticed was that the labels were displaced from the unit model by a sizeable amount. In the track I'm bombing a docked ship, and the ship label appears at half the screen away. I also switched to the F6 view to watch the bombs, and their labels were displaced as well.

Lastly, I noticed vertical lines/tears in the image of terrain.

I loaded up the same mission in the standard single thread open beta, and everything is normal. 

I've attached screenshots and a track file.

My system is:

Intel i9 12900k, 64GB DDR4 DRAM, RTX 3080 (current drivers and clean install), Samsung 980 Pro 2TB SSD.Screen_230310_234101.jpg

Screen_230310_234003.jpg

Multi-thread Strange Behavior.trk

Screen_230310_234009.jpg

Edited by mvesky
Posted (edited)

I have ampcd viewport for the f-18 on a second monitor.
With MT the view ports are not refreshing but overlaying screens one after the other. 
The text is also yellow not green

here is a video of it happening. Eventually it will go all white.

https://streamable.com/4dp90i

Edited by thekow
added info
Posted

Of course - that's the beauty of a feature rollout behind an optional flag. We can always fall back to the previous behavior easily, but... hopes were high, since on my rig I can't have all the cool graphics and stuff in ST, but MT seems to be able to do it. I am truly excited about it!

Keep up the good work!

As a side note, and I don't know if I should report it or not (it *could* be related, or a different bug) - in F/A-18 exported DFD views are really blurry/bright/yellow. This could be related to them not actually being refreshed, but could be something else totally. 

Posted

Same issue using simapp pro with the topgun mips. Fine in st, broken in mt. No point in switching over until there is a solution, at least for me as I just got these panels a few weeks ago lol

| Callsign - NOMAD | i7-8700K Water Cooled | 32GB DDR4 3200 | Nvidia GTX 1080 TI Water Cooled | VKB Gunfighter Mk.II | Virpil MongoosT-50CM Throttle | Thrustmaster TPR Pedals |TrackIR Pro 5 |

Posted

@markom Yes MT I can up some of the graphics settings and resolutions with MT up from 35fps to 60 stable. Looks promising. Will have to wait until MT can handle viewports.

  • Like 1
  • ED Team
Posted
14 minutes ago, markom said:

Of course - that's the beauty of a feature rollout behind an optional flag. We can always fall back to the previous behavior easily, but... hopes were high, since on my rig I can't have all the cool graphics and stuff in ST, but MT seems to be able to do it. I am truly excited about it!

Keep up the good work!

As a side note, and I don't know if I should report it or not (it *could* be related, or a different bug) - in F/A-18 exported DFD views are really blurry/bright/yellow. This could be related to them not actually being refreshed, but could be something else totally. 

I know its super disappointing to have such an exciting new feature and be blocked by a nasty bug, I will make sure the team is aware this is very breaking for those that use it. 

  • Like 1

64Sig.png
Forum RulesMy YouTube • My Discord - NineLine#0440• **How to Report a Bug**

1146563203_makefg(6).png.82dab0a01be3a361522f3fff75916ba4.png  80141746_makefg(1).png.6fa028f2fe35222644e87c786da1fabb.png  28661714_makefg(2).png.b3816386a8f83b0cceab6cb43ae2477e.png  389390805_makefg(3).png.bca83a238dd2aaf235ea3ce2873b55bc.png  216757889_makefg(4).png.35cb826069cdae5c1a164a94deaff377.png  1359338181_makefg(5).png.e6135dea01fa097e5d841ee5fb3c2dc5.png

Posted

For everyone else, while ED fixes the underlying issue, we could use a workaround that wonderful folks have already figured out: 

 

15 minutes ago, NineLine said:

I know its super disappointing to have such an exciting new feature and be blocked by a nasty bug, I will make sure the team is aware this is very breaking for those that use it. 

 Nah, we good, man. You were very clear this was a preview... in a beta (!!!). We expected things to break. It's super-exciting to even glimpse how much better your product will be once you iron out the kinks. Keep up the good work!

  • Like 1
Posted (edited)

@NineLinethe vertical "tear" reported here is something I've observed consistently. I don't see an dedicated thread to the issue so maybe it should be split out? To my eyeball, the "tear" is more like a delineation where the lighting model on one side are incomplete (hence darker); possibly because the renderer thinks I'm not looking, or not able to look in that direction. It's very noticable and tends to happen when looking at some off plane boresight direction and angle. In the prior post's screenshots, it looks like it's happening in an external view, so I wouldn't suggest it's dependent on plane direction.

Maybe it's a compounding issue with MFD exports? My guesses are probably unhelpful.

I've seen the issue on multiple maps (Syria, Persion Gulf, I think Caucuses) and visually, it looks screenspace/viewport dependent rather than world space. Here are additional screenshots:

image.png

image.png

image.png

My specs are: 5950x; 64GB DDR RAM; RTX 4090 latest GameReady driver (531.26), fxo + metashaders2 folders cleaned post-patch and post-install of latest driver; 2x normal monitors, 2x CUBESIM displays (USB3 connected); Samsung 980 pro drive.

Edited by EbonySeraphim

CPU: 9950X3D || Memory: 64GB 6000 CL26 || GPU: RTX 4090

Input: Virpil CM3, TM F/A-18 Grip on Virpil WarBRD base, WW F-16EX grip on Orion2 base, Virpil CP1 and CP2, 3x WinWing MFD + displays, StreamDeck XL x2, StreamDeck 15-key, TrackIR5

Posted (edited)

Can confirm that my F-16 and F/A-18 MFD/DDI export issues were fixed by changing the picture.additive_alpha = false line of code in the aforementioned files. I have 2xCubeSim screens and a normal secondary monitor that displayed the AMPCD for the F/A-18 which was also corrupted. For those who it didn't work for, be careful because there is a similar line earlier in the file which does not fix anything if you change it. The correct one is pretty close to the bottom.

I can also confirm that I didn't need the fix at all for the A-10C_2 or the Ka-50 (ABRIS + Shkval). Those worked just fine as-is included in the patch.

Edited by EbonySeraphim
Formatting, clarity, and useful information inclusion
  • Like 2

CPU: 9950X3D || Memory: 64GB 6000 CL26 || GPU: RTX 4090

Input: Virpil CM3, TM F/A-18 Grip on Virpil WarBRD base, WW F-16EX grip on Orion2 base, Virpil CP1 and CP2, 3x WinWing MFD + displays, StreamDeck XL x2, StreamDeck 15-key, TrackIR5

Posted (edited)
36 minutes ago, EbonySeraphim said:

 For those who it didn't work for, be careful because there is a similar line earlier in the file which does not fix anything if you change it. The correct one is pretty close to the bottom.

Thanks guys!!

This is now working for me in the F16 and F18. The other non-MFD areas of my extra screens still have the fuzzy background but at least it's workable.

If anyone flys the M2000 and exports the RWR (VCM) screen, this fix also applies to that by changing the picture.additive_alpha = false in the VCM_screen.lua. Thankfully the radar (VTB) export already works with MT similar to how the A10C does.

I've attached the change to the M2000 RWR, along with the changes for the F16 & F18 mentioned by @Sadhu above in a JSGME format mod to save some time for anyone else who needs it.

 

Sad news about the F-14 though, I wasn't able to get anything fixed in that. Doing some digging, this fix will only work for screens that use a background element called "ceTexPoly". The F14 screens use "ceMeshPoly" I believe which seem to have a different data structure. 

Maybe someone who knows the lua better can figure out how to fix ceMeshPoly style screens?

It seems the problem is due to the background bleed through combined with the history of previous screen draws - setting a solid background without alpha works around by covering that up. 

MT export fixes.zip

Edited by TAIPAN_
  • Like 2

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

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

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