Jump to content

Recommended Posts

Posted

same here (this has been repeated a lot in this post haha)

 

I have something to add tho, it seems to stack, so I ran the f16 free flight 3 times each time the exports got worse, with more overlap, then I decided to try the tomcat and the f16 exports were still displayed, here's the screenshots

Screen_230311_105142.jpg

Screen_230311_105457.jpg

  • Like 1

Tomcat, Tomcat über allen

Posted
2 hours ago, Greg_Mid_TN said:

Same issue here.

The really odd behavior is before the main screen loads (F/A-18 - Ready on the Ramp instant action), the MFDs and AMPCD load correctly (and have active information) on the export monitor (I don't see this on ST - the export monitor is blank until the main display loads) and then the screen repaints and goes all weird. Seems to only affect the export.

Can anyone else replicate?

Not sure if that tidbit helps, but thought I'd post it.

Thanks, Ruddle.

 

Same here. All exports look just fine at the start screen, but as soon as you hit play they go downhill.

Intel i7 13700k, ASUS  rog strix z790A, 64gigs G.Skill Trident DDR5 @6400Mhz, Nvidia  RTX 4080FE, 2x 2TB Samsung M.2 NVME, 2x 1TB Samsung SSD,  Corsair RM1000x, Corsair Titan 360 X AIO cooler, Lian Li LanCool 2, VKB Gunfighter Ultimate, VKB STECS , MFG Crosswinds, Track IR5, 48” LG UltraGear OLED & HP 24” touchscreen for Helios, Streamdeck XL, DCS-UFC App, Corsair Virtuoso RGB Headphones

Posted

Sadhu on the bug thread posted this fix:

 

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.

 

It has worked for me and seems to pass integrity check on multi-player servers.

 

Good Luck!

 

Ruddle.

Posted
6 minutes ago, Greg_Mid_TN said:

Sadhu on the bug thread posted...

Ruddle, what is "the bug thread"? Would you be so kind as to paste a link? Thanks.

I'm Dragon in the Multiplayer servers.

Posted
4 hours ago, RafaPolit said:

As a developer, this actually happens a lot, there is a key less-exposed feature that gets completely overlooked.  What I am surprised with is that this means that no one on the main dev team, nor the big users (Wags for example) or the big houses like Heatblur, use externally exported MFDs.  I would have imagined that, being a group of "really avid flyers", they would be more prone to having this "extras" than the average guy.  Yet no one actually does.  That surprised me in all honesty. 

It surprises me too.

I have been told in the past by an ED partner and developer that apparently people using extraction and viewports are very much in the minority.  Based on the amount of users posting here with this problem so far I tend to think that extracting viewports is more common than they realise and is only going to become a more popular thing to do and be far more mainstream, especially when there are companies making products like MFD bezels and such that require viewport extraction.

Hard to picture someone like Wags having a simple single screen vanilla setup :).

Posted
3 hours ago, RafaPolit said:

Ruddle, what is "the bug thread"? Would you be so kind as to paste a link? Thanks.

Sorry Rafa, should have been clearer. I meant under the 'general' bug thread. I think you found it from the look.

 

Ruddle.

Posted

Same here

| 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
11 hours ago, Greg_Mid_TN said:

Sadhu on the bug thread posted this fix:

 

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.

 

It has worked for me and seems to pass integrity check on multi-player servers.

 

Good Luck!

 

Ruddle.

This does not pass IC, but it does work.

Posted (edited)
54 minutes ago, Padonis said:

Has anyone been able to fix RWR export?

 

The above fixed all exports for me (Hornet)  What's there anything rwr specific?

Edited by Gierasimov

Intel i7-13700KF :: ROG STRIX Z790-A GAMING WIFI D4 :: Corsair Vengeance LPX 64GB ::  MSI RTX 4080  Gaming X Trio  :: VKB Gunfighter MK.III MCG Ultimate :: VPC MongoosT-50 CM3 :: non-VR :: single player :: open beta

Posted
1 hour ago, Padonis said:

Unfortunately, the RWR export does not fix the A-10C II, F-5 and F-18

 

This is what I see with MT and my EW:

If you get different results or having an issue please create a new bug report as otherwise it will be buried here.

EW.jpg

Intel i7-13700KF :: ROG STRIX Z790-A GAMING WIFI D4 :: Corsair Vengeance LPX 64GB ::  MSI RTX 4080  Gaming X Trio  :: VKB Gunfighter MK.III MCG Ultimate :: VPC MongoosT-50 CM3 :: non-VR :: single player :: open beta

Posted
vor 23 Stunden schrieb Greg_Mid_TN:

Sadhu on the bug thread posted this fix:

 

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.

 

It has worked for me and seems to pass integrity check on multi-player servers.

 

Good Luck!

 

Ruddle.

This works great for the F-16 for exported left and right MFD's but it will not fix the exported RWR Display.

Posted

I managed to fix the ghosting on the F-14, but not the artifacts, so it makes little sense to post it.  If someone has managed to solve the artifacts, maybe we can combine efforts?

I'm Dragon in the Multiplayer servers.

Posted
On 3/10/2023 at 2:52 PM, RafaPolit said:

As a developer, this actually happens a lot, there is a key less-exposed feature that gets completely overlooked.  What I am surprised with is that this means that no one on the main dev team, nor the big users (Wags for example) or the big houses like Heatblur, use externally exported MFDs.  I would have imagined that, being a group of "really avid flyers", they would be more prone to having this "extras" than the average guy.  Yet no one actually does.  That surprised me in all honesty. 

So should they have held the update back until all these bugs were resolved?

Posted
8 hours ago, Gierasimov said:

This is what I see with MT and my EW:

If you get different results or having an issue please create a new bug report as otherwise it will be buried here.

EW.jpg

I'm not talking about the EW you display on the DDI, but about the RWR, which is also the case with the A-10C, F-5 and F-18. It's on the right under DDI.

Posted (edited)
33 minutes ago, pr3sidentspence said:

So should they have held the update back until all these bugs were resolved?

Again, this is difficult to answer.  As an "agile" developer, you ideally want to have developed things "correctly" or "properly" and put your software in the hands of the users.  Unequivocally, they will surface the (hopefully few) bugs you have and you fix them and put the fix quickly in their hands so they can keep on testing.

Obviously, if the software is "too buggy", this will create further frustration and distrust on your users.

In this particular development, I'd say it's almost an "alpha": you even need to launch a different exe than the one that is launched with your "normal process", so I'd say this is an opt-in beta test where you know you are going to get even more rough roads than with using the "normal" beta, which is still the same: a place where you are going to face problems.

So I'd say "No". They did the right thing and we are expecting this to be even rougher roads than usual beta problems. 

I have complaints of things more "obvious": how come they "forgot" to enable SSAA.  Those are the type of bugs that are less "forgivable".  As a tech-lead of a developer's team, that is the sort of thing that makes me pull my hairs off and get into a frenzy: "How the heck did we miss this!".  Other types of neglects like: "Yeah, we forgot to test it on externally exported MFDs" are the kind of scenarios where I go: "pfff... Ok, let's fix this and, in the future, create automated tests for these cases that we are more prone to forget to test".

That's how we do it.

Edited by RafaPolit
  • Like 2

I'm Dragon in the Multiplayer servers.

Posted
4 hours ago, Padonis said:

I'm not talking about the EW you display on the DDI, but about the RWR, which is also the case with the A-10C, F-5 and F-18. It's on the right under DDI.

Ah got you! Now I understand. Well the 'fix' specifically addresses MFDs, since the RWR is not one, hence the lack of fix I guess.

I am sure ED will figure it out soon!

Intel i7-13700KF :: ROG STRIX Z790-A GAMING WIFI D4 :: Corsair Vengeance LPX 64GB ::  MSI RTX 4080  Gaming X Trio  :: VKB Gunfighter MK.III MCG Ultimate :: VPC MongoosT-50 CM3 :: non-VR :: single player :: open beta

Posted

As much of a let down as it was to fire up MT and see all the exports look the way they do, ED did say right away that it is a preview version of MT, bugs to be expected. I’m one of those users that didn’t see mega performance improvements, except in heavy missions which run much more consistently fps wise. Mainly because I cap my fps to monitor refresh rate anyway and use vsync .  The standard version still works as it should, with the exception of the f-18 rwr which has been a bunch of blobs for a while now. MT is huge for DCS unfortunately people exporting displays are most likely a minority in ED’s eyes and I don’t feel like that is part of any internal testing. The ability is there, but the game isn’t designed with that in mind necessarily(personal assumption). With hardware such as MIP coming to market, hopefully ED will start putting a little more time into checking those things during tests 🤷‍♂️Exporting displays/viewports  has been part of dcs for a long time and hopefully they don’t inadvertently push it by the wayside, or just say screw it it’s not part of our design too bad. 

Intel i7 13700k, ASUS  rog strix z790A, 64gigs G.Skill Trident DDR5 @6400Mhz, Nvidia  RTX 4080FE, 2x 2TB Samsung M.2 NVME, 2x 1TB Samsung SSD,  Corsair RM1000x, Corsair Titan 360 X AIO cooler, Lian Li LanCool 2, VKB Gunfighter Ultimate, VKB STECS , MFG Crosswinds, Track IR5, 48” LG UltraGear OLED & HP 24” touchscreen for Helios, Streamdeck XL, DCS-UFC App, Corsair Virtuoso RGB Headphones

  • Recently Browsing   0 members

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