Jump to content

Recommended Posts

Posted

Got everything working. Sort of. Same problem others have described, a completely washed out LCD screen for the various displays, virtually unreadable. MFCDs are A-okay, but CSMC and RWR, etc are shat. Anyone make it past that point?

Posted
Thanks "Low Blow" works perfectly now. :)

 

 

:thumbup: anytime!

  • Like 1

[sIGPIC][/sIGPIC]

Twitch:

 

My Specs:



 

i7 8700K, 32gig Corsair DDR4 3000Mhz, 2080ti, Obutto R3volution, VKB Gunfighter Mk.III MCG Pro EN, Warthog Throttle, Saitek Combat Pedals, Oculus Rift S

 

 

MMSOBGYTAST!

Posted

I reverted by mfd's back to the old naming convention ie ED_A10C_RIGHT_MFCD back to RIGHT_MFCD. and now it works again. Yea!!! So what is the old CDU name. I tried just CDU but no joy.

 

By my understanding, there are no default viewport mappings defined for most of the instruments, just the MFCDs. I've had to edit each specific instrument's init LUA file (under mods\aircraft\???\Cockpit\Scripts\???\indicator\???_init.lua)

 

Typically, I have to add a bunch of lines like this at the top of each file...

 

--- MB customisation: ---
dofile(LockOn_Options.common_script_path.."ViewportHandling.lua")
render_target_always = false
purposes      = {render_purpose.GENERAL,render_purpose.HUD_ONLY_VIEW}
try_find_assigned_viewport("AN_ALR69V_SCREEN")
--- end customisation ---

However, this still suffers from the "no erase" problem that seems to be plaguing everyone with multi-monitors at the moment.

 

Note also that not every instrument init file is the same. A few already specify a "purpose" line, which needs to be commented out do that the above additions can have effect.

Posted
The Export of the Data is working in generell for the CDU and also for the MFCDs. But there are still some issues that I am not able to solve. As you can see in the pic attached, there is still this Background implemented. But only in my CDU-Screen and not in my MFCD. Further there are some lines in the CDU double-layed.

 

damn, i got that strange overlay on my MFCDs! im using 8' lilliputs and if i turn MFCD in-game cockpit the image on lilliput's display freezes like it some kind of second layer, only still, not moving.

 

and what about background? anyone have managed to produce back background?

 

with all that sad history around UltraMFCD (http://forums.eagle.ru/showthread.php?t=138924&page=87) it looks like we got to do our exports "old fashioned" way :(

MB: Asus ROG Strix Z390-E \ CPU: i9-9900K NZXT Kraken X52\ DDR4: 3000MHz G.SKILL Trident Z Royal 32Gb RAM \

VID: MSI Nvidia RTX4070 12GB \ MON: Samsung ue49ks8000 49'', Lilliput 8'' x2

CNTRL: Thrustmaster HOTAS Warthog \ Saitek Combat Rudder pedals \ TrackIR 5 \ Thrustmaster MFD Cougar Pack

Posted

I don't think anyone has achieved the black background on exports. A few have managed to get them to appear, but none have made them appear correctly.

 

MFCD's appear to be somewhat reliable but nothing else.

 

Not heard from Developers on this topic, is it being addressed?

476th vFG Alumni

Posted

Just adding to what has already been confirmed.

 

I have created LUA files for the SU-25T, the A-10C, and the KA-50 that successfully export the MFDs, ARBRIS, and SHKVAL to my 8inch Lilliput Monitors. No issues. Works great and now with minimum frame rate loss.

 

However, I have been unable to export any of the various radars. The F-15C, Mig-29, and SU-27 appear either corrupted or as a blank box with terrain graphics behind it.

 

Is this the general consensus and shared experience of the group?

 

Thanks,

 

Stephen

Posted
Just adding to what has already been confirmed.

 

I have created LUA files for the SU-25T, the A-10C, and the KA-50 that successfully export the MFDs, ARBRIS, and SHKVAL to my 8inch Lilliput Monitors. No issues. Works great and now with minimum frame rate loss.

 

However, I have been unable to export any of the various radars. The F-15C, Mig-29, and SU-27 appear either corrupted or as a blank box with terrain graphics behind it.

 

Is this the general consensus and shared experience of the group?

 

Thanks,

 

Stephen

 

you have MFCDs exported with black background? when you turn it off in cockpit, it turns off on display as well? please tell us how you done it

MB: Asus ROG Strix Z390-E \ CPU: i9-9900K NZXT Kraken X52\ DDR4: 3000MHz G.SKILL Trident Z Royal 32Gb RAM \

VID: MSI Nvidia RTX4070 12GB \ MON: Samsung ue49ks8000 49'', Lilliput 8'' x2

CNTRL: Thrustmaster HOTAS Warthog \ Saitek Combat Rudder pedals \ TrackIR 5 \ Thrustmaster MFD Cougar Pack

Posted

Backbone,

 

A10C and the KA-50 ARBRIS export with a black background but I haven't learned the trick to disable the displays in the cockpit.

 

I used to use the Easy Monitor Configurator to address that so I will try when I get home. Required a small registry fix.

Posted

I created a simple batch file to automatically insert my export files. Every time DCS would update I would have to go back in a do all this manually. Been using this system for 6 months now. DCS updates, I click from me and I am back in business. With Win10 you have to give your folders permissions to overwrite.

 

 

@echo off

rem copy c:\games\stuff.txt c:\"Program Files"\ /Y

copy c:\Backups\DCS_BACKUPS\ABRIS_init.lua c:\"Program Files\Eagle Dynamics\DCS World OpenBeta\Mods\aircraft\Ka-50\Cockpit\Scripts\ABRIS"\ /Y

copy c:\Backups\DCS_BACKUPS\Ekran_init.lua c:\"Program Files\Eagle Dynamics\DCS World OpenBeta\Mods\aircraft\Ka-50\Cockpit\Scripts\EKRAN\Indicator"\ /Y

copy c:\Backups\DCS_BACKUPS\PVI_init.lua c:\"Program Files\Eagle Dynamics\DCS World OpenBeta\Mods\aircraft\Ka-50\Cockpit\Scripts\PVI"\ /Y

copy c:\Backups\DCS_BACKUPS\UV_26_init.lua c:\"Program Files\Eagle Dynamics\DCS World OpenBeta\Mods\aircraft\Ka-50\Cockpit\Scripts\UV_26"\ /Y

copy c:\Backups\DCS_BACKUPS\AN_ALR69V_init.lua c:\"Program Files\Eagle Dynamics\DCS World OpenBeta\Mods\aircraft\A-10C\Cockpit\Scripts\AN_ALR69V\Indicator"\ /Y

copy c:\Backups\DCS_BACKUPS\CDU_init.lua c:\"Program Files\Eagle Dynamics\DCS World OpenBeta\Mods\aircraft\A-10C\Cockpit\Scripts\CDU\Indicator"\ /Y

copy c:\Backups\DCS_BACKUPS\CMSC_init.lua c:\"Program Files\Eagle Dynamics\DCS World OpenBeta\Mods\aircraft\A-10C\Cockpit\Scripts\CMSC\Indicator"\ /Y

copy c:\Backups\DCS_BACKUPS\CMSP_init.lua c:\"Program Files\Eagle Dynamics\DCS World OpenBeta\Mods\aircraft\A-10C\Cockpit\Scripts\CMSP\Indicator"\ /Y

copy c:\Backups\DCS_BACKUPS\DIGIT_CLK_init.lua c:\"Program Files\Eagle Dynamics\DCS World OpenBeta\Mods\aircraft\A-10C\Cockpit\Scripts\DigitalClock\Indicator"\ /Y

copy c:\Backups\DCS_BACKUPS\freq_status_init.lua c:\"Program Files\Eagle Dynamics\DCS World OpenBeta\Mods\aircraft\A-10C\Cockpit\Scripts\UHF_Radio\Indicator"\ /Y

copy c:\Backups\DCS_BACKUPS\preset_channel_init.lua c:\"Program Files\Eagle Dynamics\DCS World OpenBeta\Mods\aircraft\A-10C\Cockpit\Scripts\UHF_Radio\Indicator"\ /Y

copy c:\Backups\DCS_BACKUPS\repeater_init.lua c:\"Program Files\Eagle Dynamics\DCS World OpenBeta\Mods\aircraft\A-10C\Cockpit\Scripts\UHF_Radio\Indicator"\ /Y

copy c:\Backups\DCS_BACKUPS\focus.png c:\"Program Files\Eagle Dynamics\DCS World OpenBeta\Bazar\Effects\PostEffects"\ /Y

copy c:\Backups\DCS_BACKUPS\Export Backups\Export.lua c:\"Program Files\Eagle Dynamics\DCS World OpenBeta\Config\Export"\ /Y

copy c:\Backups\DCS_BACKUPS\Export Backups\Export.lua c:\"Program Files\Eagle Dynamics\DCS World OpenBeta\Scripts"\ /Y

copy c:\Backups\DCS_BACKUPS\Export Backups\Export.lua c:\"Users\XXXXXXXXXXXXXXXX\Saved Games\DCS.openbeta\Scripts"\ /Y

copy c:\Backups\DCS_BACKUPS\ViewportHandling.lua c:\"Program Files\Eagle Dynamics\DCS World\Scripts\Aircrafts\_Common\Cockpit"\ /Y

 

Posted

This issue is now resolved.

 

Both the overlaying and repeating displays and the stuck terrain view.

 

Thanks ED for getting this fix out the door!

476th vFG Alumni

Posted
This issue is now resolved.

 

Both the overlaying and repeating displays and the stuck terrain view.

 

Thanks ED for getting this fix out the door!

 

 

confirmed! thank you very much, ED! :thumbup:

MB: Asus ROG Strix Z390-E \ CPU: i9-9900K NZXT Kraken X52\ DDR4: 3000MHz G.SKILL Trident Z Royal 32Gb RAM \

VID: MSI Nvidia RTX4070 12GB \ MON: Samsung ue49ks8000 49'', Lilliput 8'' x2

CNTRL: Thrustmaster HOTAS Warthog \ Saitek Combat Rudder pedals \ TrackIR 5 \ Thrustmaster MFD Cougar Pack

Posted
This morning I was thinking about just going back to 1.2.16 until it was resolved. Such a great thing and on a Friday!

 

I was in the same boat. I was ready to install 1.2.16 on my rebuilt rig, so i was pretty chuffed to come off a late shift and see this update had fixed the issue! Nice one devs!

 

 

 

Intel i5 4690k

MSI GTX 970 4g gaming edition

Asus Z97k Mobo

8Gb Corsair vengeance 1866mhz

120GB Samsung 840 evo

Samsung 1TB Spinpoint hdd

Windows 10

4 channel surround

Hotas Cougar w/ 120mm machined steel extension and elite rudder pedals

DIY collective via bu0836x plus some random buttons and knobs

Cougar MFDs

Running 1920*2104 over 3 screens

 

 

Posted

Mine is still not reading the CDU on my 4th screen. I see the two MFD's no problem. In KA50 I see the Shkval and the abris no problem. I can move the abris so I see it on the fourth screen. So I have to believe Im not naming the function right for the CDU. Ive tried CDU,CDU_EXPORT,ED_A10C_CDU. What should it be called.

This is what I have in my file

--***DO NOT MODIFY THESE COMMENT LINES***

--A10CVirtualCockpitServer v0.0.0.0

--LOCATION Config\MonitorSetup

--HOOKTO

--Monitor lua

 

_ = function(p) return p; end;

name = _('A-10C Virtual Cockpit Server');

Description = 'Setup for A-10C Virtual Cockpit Server MFCD and CDU Exports.'

Viewports =

{

Center =

{

x = 0;

y = 0;

width = 1920;

height = 1200;

viewDx = 0;

viewDy = 0;

aspect = 1.717171717;

}

}

 

 

 

Shkval =

{

x = 1920;

y = 0;

width = 800;

height = 600;

}

 

ABRIS =

{

x = 3630;

y = 00;

width = 650;

height = 800;

}

 

LEFT_MFCD =

{

x = 2010;

y = 70;

width = 625;

height = 455;

}

 

RIGHT_MFCD =

{

x = 2809;

y = 70;

width = 625;

height = 455;

}

 

ED_A10C_CDU =

{

x = 3630;

y = 40;

width = 390;

height = 295;

}

 

GUI =

{

x = 0;

y = 0;

width = 1920;

height = 1200;

}

 

 

UIMainView = GUI

I was in Art of the Kill D#@ it!!!!

Posted

Kudos to Low Blow!!

 

He helped me through the A10C Virtual Server software and it works perfect for exporting the MFCD's.

Win 10 64bit; 32 GB DDR4 3200 Ram; ASUS MoBo; 1TB SSD;Intel i7 8700K; GTX 1080ti 11GB; Thrustmaster Warthog;Odyssey + VR

Posted
Mine is still not reading the CDU on my 4th screen. I see the two MFD's no problem. In KA50 I see the Shkval and the abris no problem. I can move the abris so I see it on the fourth screen. So I have to believe Im not naming the function right for the CDU. Ive tried CDU,CDU_EXPORT,ED_A10C_CDU. What should it be called.

This is what I have in my file

 

I believe it should be called whatever the reference is in the file:

 

"\DCS World\Mods\aircraft\A-10C\Cockpit\Scripts\CDU\indicator\CDU_init.lua"

 

In my installation it's in the line "vp = env.ED_A10C_CDU"

 

so I use ED_A10C_CDU

 

You might want to look at my earlier post (in this thread) to see where I got versions of the *init.lua files from, they all work for me.

 

I can also confirm that the latest update has resolved this issue for me - many thanks ED.

System spec: Intel i7 12700k @ stock, ASUS TUF Gaming GeForce RTX 3080 Ti 12GB GDDR6X, Gigabyte Z690 UD DDR4, Corsair Vengeance LPX 32GB (2 x 16GB) DDR4 3200MHz C16, Samsung 980 EVO 500 GB NVME M.2 SSD (system drive), WD Black SN 850X 2TB NVME M.2 SSD (games drive), Thermalright Assassin Spirit 120 Evo Cooler, Asus XG43UQ Monitor, Oculus Quest Pro, Thrustmaster Warthog HOTAS

Prev System spec (leaving here because I often reference it in my posts): Intel i9 13900KF @ stock,  Gigabyte GeForce RTX 4090 Gaming OC 24GB GDDR6X, Gigabyte Z690 UD DDR4, Corsair Vengeance RGB PRO SL 32GB (2 x 16GB) DDR4 3600MHz C18, Samsung 980 EVO 500 GB NVME M.2 SSD (system drive), Samsung 970 EVO 1 TB NVME M.2 SSD (games drive), Cooler Master ML360 Illusion CPU Cooler, Asus XG43UQ Monitor, Oculus Quest Pro, Thrustmaster Warthog HOTAS, MFG Crosswind Rudder Pedals

Posted

Hippo

That was the trick. The cdu_init.lua files were completely different between the beta and the 1.2 version. There is alot of stuff missing in the beta version. I copied and paste all of the lines from the production version to the beta and now it works using the ED_A10C_CDU.

There was no reference to vp in the beta version at all.

 

 

I believe it should be called whatever the reference is in the file:

 

"\DCS World\Mods\aircraft\A-10C\Cockpit\Scripts\CDU\indicator\CDU_init.lua"

 

In my installation it's in the line "vp = env.ED_A10C_CDU"

 

so I use ED_A10C_CDU

 

You might want to look at my earlier post (in this thread) to see where I got versions of the *init.lua files from, they all work for me.

 

I can also confirm that the latest update has resolved this issue for me - many thanks ED.

I was in Art of the Kill D#@ it!!!!

Posted

After yesterdays update everything works for me now. The background of the "export" displays is black again, the fonts aren't blurry anymore and now I can read the FPS.

Problem solved, at least for me. Thanks ED for the quick fix.

Xoxen

AMD Ryzen 7 5800X3D, MSI MPG X570 Gaming Plus, 64GB Crucial Ballistix DDR4-3600 CL16, Asus TUF Gaming RTX 4080 OC, Windows 11 64bit Home Premium, TrackIR 5 with TrackClip: Pro!, Virpil MongoosT-50CM3 Base + TM Warthog Stick + 7cm extension + WINWING Orion 2 with F-15EX grips, Cougar MFDs with 8" displays, Saitek Rudder Pedals, Samsung Odyssey G9 49" 5120x1440 @120 Hz

Posted
After yesterdays update everything works for me now. The background of the "export" displays is black again, the fonts aren't blurry anymore and now I can read the FPS.

Problem solved, at least for me. Thanks ED for the quick fix.

Xoxen

 

 

The same for me. Thanks ED for the fix!

[sIGPIC][/sIGPIC]

  • 3 weeks later...
Posted

What is the name to use to export the Su-25T Shkval to a viewport? I'm using a square "RIGHT_MFCD" (for the various FC3 aircraft & A-10C), and want a 4:3 aspect ratio Shkval for the Su-25T.

 

If in addition to letting me know what name to use for the Su-25T Shkval, the steps to how to find the name would be greatly appreciated!

 

Thanks for any help on this!

Posted
What is the name to use to export the Su-25T Shkval to a viewport? I'm using a square "RIGHT_MFCD" (for the various FC3 aircraft & A-10C), and want a 4:3 aspect ratio Shkval for the Su-25T.

 

If in addition to letting me know what name to use for the Su-25T Shkval, the steps to how to find the name would be greatly appreciated!

 

Thanks for any help on this!

 

I got it sorted out by filtering by aircraft, and changing settings for each one. It gives better results.

  • Recently Browsing   0 members

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