Jump to content

Recommended Posts

Posted (edited)

I figured out how to export the radar display to an MFD in the Phantom, but for some reason in this plane, it's way too bright and washed out. I have a Winwing 3 MFD setup and most of my modules have one to three displays that can be exported to these MFD's. Three of my modules are not included in the Winwing app to export a display. However, one of those modules, the F-1 Mirage, exports its radar display to one of my MFD's on it's own. The app doesn't even need to be active. Curious as to how this happens, I started asking around to try to figure out how this all works. Then I started looking at various .lua files in the Mirage cockpit/scripts directory. I found a file where it references the viewport handling and then it says to "try to find" this viewport or that viewport. So I went to the other two modules that didn't export... the AJS-37 Viggen and the F-4E, and found some similar init.lua files. I added the lines that talked about trying to find this or that viewport to the same init.lua file that talked about viewport handling, and with a bit of trial and error, I got a completely functional radar display on my MFD for the AJS-37 Viggen. So I tried the same thing with the Phantom. At first, I had the added lines in the wrong init.lua file and all I got was a radar overlay on the main gaming screen. I found a file called init_bake.lua and tried that and then I had radar on an MFD as well as the overlay. Ironically, when I had it like this, the radar display on the MFD seemed somewhat normal. When I removed the lines from the first init.lua file, I got rid of the overlay, but then the radar display on the MFD is totaly bloomed and washed out. I have to tweak the displays controls a bunch in the airplane and then tweak the MFD displays with this other mod I have for that, and I can get the MFD radar display somewhat usable. But then the radar display in the airplane is too dim to see. So my obvious question is how can I adjust the brightness and contrast of the radar display going to the MFD without affecting the radar display in the cockpit? I would think there would be some way to do this but it's beyond me at this point. I figured there had to be some .lua file somewhere to adjust this. Everything else in DCS is controlled by a .lua file. I have heard that the Phantom is not yet set up for exporting displays. I obviously figured out how to do it but maybe there's more to it...? Is some secret file that needs to be tweaked for this to work? The Viggen radar display works great on my MFD. When I adjust the display in the cockpit, the MFD display matches it. So come on Haatblur. What am I missing here? How can I make this radar display on my MFD usable?

Edited by brettt777
  • Like 1

AMD Ryzen 9 5900X @ 4.4ghz, 64gb DDR4 @ 3200mhz, GeForce RTX-3060ti 8GB DDR6, Three KTC 32" QHD monitors @ 165hz, Rosewill 80plus Bronze 1000w, Corsair Hydro H100i, 2tb M.2  SSD for OS, Two 3tb HDD, 2tb SSD for DCS, P3D, Star Citizen, Sound Blaster Zx, Thermaltake Overseer RX-I, Winwing Orion 2 HOTAS F-15EX throttle and F-16EX stick, Winwing 3 MFD MIP with FA-18 UFC and F-16 ICP, TrackIR 5, Surround Speakers & Subwoofer, Oculus Quest 2 VR.

:joystick::pilotfly:

Posted
vor 1 Stunde schrieb brettt777:

I figured out how to export the radar display to an MFD in the Phantom, ...

Would you mind sharing how you did that?

Thanks.

DCS: A-10C II Tank Killer, F-4E Phantom II, F/A-18C, F-16C Viper, A-10A Flaming Cliffs, Caucasus, Marianas, Normandy 2.0, The Channel, Kola, Syria, Nevada, Sinai, Persian Gulf, CW Germany, Combined Arms

System: HP Z2 Tower, Win11 24H2, i9-14900K, 64GB RAM, 2TB SSD (M2) + 18TB HDD (Sata), GeForce RTX4070 TI Super 16GB VRAM, Samsung Odyssey 57" curved monitor (main screen) + BenQ 32" UW3270 (secondary screen), VKB Gunfighter Ultimate MK4 + S-TECS Throttle

Posted (edited)

I just modified my init_bake.lua as mentioned in your text and got this (see attached). The MFCD is not useable and I also can't modify intensity, contrast or anything else.

image.jpeg

Edited by TheBiggerBass
  • Like 1

DCS: A-10C II Tank Killer, F-4E Phantom II, F/A-18C, F-16C Viper, A-10A Flaming Cliffs, Caucasus, Marianas, Normandy 2.0, The Channel, Kola, Syria, Nevada, Sinai, Persian Gulf, CW Germany, Combined Arms

System: HP Z2 Tower, Win11 24H2, i9-14900K, 64GB RAM, 2TB SSD (M2) + 18TB HDD (Sata), GeForce RTX4070 TI Super 16GB VRAM, Samsung Odyssey 57" curved monitor (main screen) + BenQ 32" UW3270 (secondary screen), VKB Gunfighter Ultimate MK4 + S-TECS Throttle

Posted
1 hour ago, TheBiggerBass said:

I just modified my init_bake.lua as mentioned in your text and got this (see attached). The MFCD is not useable and I also can't modify intensity, contarst or anything else.

null

image.jpeg

This is exactly what I get when I "patch" with Helios, and the exported display on the HUD. 

3 hours ago, brettt777 said:

However, one of those modules, the F-1 Mirage, exports its radar display to one of my MFD's on it's own.

That's because Aerges did due diligence and export the radar as with left right  centersomething mdf, and you have the correct settings for those in the monitor.lua

There's no sorcery WW does for you except write the file for you. Helios does it in even better ways, and neither needs to run, only write the file for you once. Helios will also "patch" every module that has MFD exports that needs it. I believe I wrote that in another post. Helios will also help you with exports that are not defined, and you can make profiles, and drag and drop around a lot of stuff that's not included by default. Also, Helios will keep the unpatched files as a backup, so you can open and compare in like Notepad++ etc. To make you have a better understanding of all this. 

Myself, I made exports of everything possible in the MB-339 even if it doesn't have any MFDs. 

Cheers! 

Posted
17 hours ago, Zabuzard said:

Sounds like you did not export the right display, can you share a screenshot or something?

 

17 hours ago, Zabuzard said:

Yes, the Phantom is not setup for exporting yet. So you likely will have to standby.

Well, like I said, I can play around with the brightness and contrast in the cockpit, plus modify the gamma and saturation of the MFD with another mod I have, and I can get it usable (while making the radar display in the cockpit unusable). So it is most definitely the correct display. There's just something else I am missing that needs to be done and it probably won't happen til Heatblur gets around to it.

AMD Ryzen 9 5900X @ 4.4ghz, 64gb DDR4 @ 3200mhz, GeForce RTX-3060ti 8GB DDR6, Three KTC 32" QHD monitors @ 165hz, Rosewill 80plus Bronze 1000w, Corsair Hydro H100i, 2tb M.2  SSD for OS, Two 3tb HDD, 2tb SSD for DCS, P3D, Star Citizen, Sound Blaster Zx, Thermaltake Overseer RX-I, Winwing Orion 2 HOTAS F-15EX throttle and F-16EX stick, Winwing 3 MFD MIP with FA-18 UFC and F-16 ICP, TrackIR 5, Surround Speakers & Subwoofer, Oculus Quest 2 VR.

:joystick::pilotfly:

Posted
16 hours ago, TheBiggerBass said:

I just modified my init_bake.lua as mentioned in your text and got this (see attached). The MFCD is not useable and I also can't modify intensity, contrast or anything else.

image.jpeg

I have been able to play around with the brightness and contrast and the gamma and saturation and get a usable display, but it makes the cockpit display unusable. It has to be something with the Heatblur code because I did this exact same mod to the AJS-37 Viggen radar and it worked perfectly.

AMD Ryzen 9 5900X @ 4.4ghz, 64gb DDR4 @ 3200mhz, GeForce RTX-3060ti 8GB DDR6, Three KTC 32" QHD monitors @ 165hz, Rosewill 80plus Bronze 1000w, Corsair Hydro H100i, 2tb M.2  SSD for OS, Two 3tb HDD, 2tb SSD for DCS, P3D, Star Citizen, Sound Blaster Zx, Thermaltake Overseer RX-I, Winwing Orion 2 HOTAS F-15EX throttle and F-16EX stick, Winwing 3 MFD MIP with FA-18 UFC and F-16 ICP, TrackIR 5, Surround Speakers & Subwoofer, Oculus Quest 2 VR.

:joystick::pilotfly:

Posted
4 hours ago, brettt777 said:

 

Well, like I said, I can play around with the brightness and contrast in the cockpit, plus modify the gamma and saturation of the MFD with another mod I have, and I can get it usable (while making the radar display in the cockpit unusable). So it is most definitely the correct display. There's just something else I am missing that needs to be done and it probably won't happen til Heatblur gets around to it.

You are misunderstanding me. There are like 8 different textures in play when it comes to forging the final picture for the DSCG and you might just have caught the wrong one.

 

But if you dont share anything we can not really help you and possibly tell you how to change your setup so that it finally works.

A screenshot and sharing your "mod" would be highly appreciated and the way forward for assisting you with this 🙂 

  • Recently Browsing   0 members

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