Saruman Posted March 11, 2023 Posted March 11, 2023 (edited) 6 hours ago, UTurista said: +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 March 11, 2023 by Saruman
rob10 Posted March 11, 2023 Posted March 11, 2023 (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 March 11, 2023 by rob10 1
bones1014 Posted March 11, 2023 Posted March 11, 2023 I also saw it was reported after posting this. Hope they can quick fix itSent from my SM-G781U using Tapatalk
Mercury_1965 Posted March 11, 2023 Posted March 11, 2023 nullTher're some problems about the export. Also concerning both MFD where there are some artfacts on borders
Night Posted March 11, 2023 Posted March 11, 2023 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 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
Night Posted March 11, 2023 Posted March 11, 2023 Try the page.lua solution in this thread, it worked for me [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
Night Posted March 11, 2023 Posted March 11, 2023 Try the page.lua solution in this thread, it worked for me [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
tehaviata Posted March 11, 2023 Posted March 11, 2023 Can confirm. I've got the same issue with how MT projects to my Cubesim displays. Without MT there's no issues.
Mercury_1965 Posted March 11, 2023 Posted March 11, 2023 Thx for suggestion. But I cannot find the analog page.lua for RWR and CDU export
mvesky Posted March 11, 2023 Posted March 11, 2023 (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. Multi-thread Strange Behavior.trk Edited March 11, 2023 by mvesky
thekow Posted March 11, 2023 Posted March 11, 2023 (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 March 11, 2023 by thekow added info
abikns Posted March 11, 2023 Posted March 11, 2023 (edited) I can confirm this problem with the F/A-18C DDI Left, DDI Right, MPCD and IFEI. Edited March 11, 2023 by abikns 1
ED Team NineLine Posted March 11, 2023 ED Team Posted March 11, 2023 MFD exports are currently not working in MT, but its known and reported. Thanks guys. Will leave open if I am missing something else in this report. Forum Rules • My YouTube • My Discord - NineLine#0440• **How to Report a Bug**
markom Posted March 11, 2023 Posted March 11, 2023 As a suggestion, this should've gone into the known issues. I had my hopes really up for MT, but this is a show-stopper :-(. 1
ED Team NineLine Posted March 11, 2023 ED Team Posted March 11, 2023 I totally agree it should have been flagged, not sure if it was a late breaking bug, but the team knows its an important one. I apologize, you can use ST for the time being till it is addressed. 1 Forum Rules • My YouTube • My Discord - NineLine#0440• **How to Report a Bug**
markom Posted March 11, 2023 Posted March 11, 2023 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.
Nomad81 Posted March 11, 2023 Posted March 11, 2023 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 |
ED Team NineLine Posted March 11, 2023 ED Team Posted March 11, 2023 Exported MFDs is known and reported, sorry. Forum Rules • My YouTube • My Discord - NineLine#0440• **How to Report a Bug**
thekow Posted March 11, 2023 Posted March 11, 2023 @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. 1
ED Team NineLine Posted March 11, 2023 ED Team Posted March 11, 2023 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. 1 Forum Rules • My YouTube • My Discord - NineLine#0440• **How to Report a Bug**
markom Posted March 11, 2023 Posted March 11, 2023 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! 1
EbonySeraphim Posted March 11, 2023 Posted March 11, 2023 (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: 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 March 11, 2023 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
EbonySeraphim Posted March 11, 2023 Posted March 11, 2023 (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 March 11, 2023 by EbonySeraphim Formatting, clarity, and useful information inclusion 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
TAIPAN_ Posted March 11, 2023 Posted March 11, 2023 (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 March 11, 2023 by TAIPAN_ 2 Pimax Crystal VR & Simpit User | Ryzen CPU & Nvidia RTX GPU | Some of my mods
ianick Posted March 11, 2023 Posted March 11, 2023 (edited) cf pic ALREADY REPORTED Edited March 11, 2023 by ianick
Recommended Posts