lxsapper Posted January 27, 2019 Share Posted January 27, 2019 Bones I think what you need to change is in the IFEI_init.lua and add to line to get it to export again. And maybe put the file in your DCS savegames directory so it doesn't get overwriten next time there's an update. Try this (By Capt Zen by the way) : dofile(LockOn_Options.common_script_path.."ViewportHandling.lua") try_find_assigned_viewport("F18_IFEI") I think you can put it almost anywhere in that file, so try at the end of the file. Link to comment Share on other sites More sharing options...
lxsapper Posted January 27, 2019 Share Posted January 27, 2019 Ops.... Sniped :) Link to comment Share on other sites More sharing options...
lxsapper Posted January 27, 2019 Share Posted January 27, 2019 Cap'n Penguin I think it will be easier to try and help if you post your Monitor Config Lua. Link to comment Share on other sites More sharing options...
FZG_Immel Posted January 27, 2019 Share Posted January 27, 2019 Good afternoon all. I need some assistance if anyone is willing.... I have the Cougars and I have the second monitor that was recommended. Created the .lua file and the MFD's export and appear as planned. In Windows 10 I have the second monitor set up and can move the mouse back and forth between the two even when flying DCS. The issue is that I can not get the MFD's to appear on the second screen. I moved them down slowly and have the left MFDat the very bottom on the main cockpit screen but it doesn't show on the secondary monitor. I can put my mouse on it and pull straight down and the mouse appears but the MFD now. My DCS resolution is set at 3840 x 2160 I'm sorry to bother y'all with this but I'm stumped and after 5.5 hours of trying resolution changes and such and I am getting nowhere. Any wisdom is appreciated The easiest way would be to set your second monitor right of you main monitor in windows- side by side, 1 - 2 Can you please tell me what are the resolution of your two monitors ? Also, be aware of something. In windows 10, if your two monitors are running different refresh rates (let's say 144hz for the main and 60hz for the second) you are going to have stuttering- it just happened to me and I had to purchase a second monitor in 144hz. Anyway, tell me you two resolutions and I will help you set this up [sIGPIC]https://forums.eagle.ru/signaturepics/sigpic70550_3.gif[/sIGPIC] Asus Z390-H - SSD M.2 EVO 970 - Intel I9 @5.0ghz - 32gb DDR4 4000 - EVGA 3090 - Cougar FSSB + Virpil WRBRD + Hornet Stick - Thrustmaster TPR Pedal + WinWing MIP + Orion + TO and CO pannels - Track IR5 Link to comment Share on other sites More sharing options...
Bones1775 Posted January 27, 2019 Share Posted January 27, 2019 lxsapper that was it. don't remember modding the IFEI_init.lua file. that fixed it and is now saved in saved games folder. thanks. Link to comment Share on other sites More sharing options...
mikemadmax20 Posted February 28, 2019 Share Posted February 28, 2019 Hi Capt Zeen: Need your input once again. I'm trying to get my FA-18 RWR to export and am having major difficulties doing so. I'm attaching my .lua script below. Would you kindly give it a once over to see if I'm missing something. I've got my monitor setup working well with other exports so I don't believe that's the issue. Your help is appreciated. Anyone else is free to chime in as well. Thanks in advance. Mike dofile(LockOn_Options.common_script_path.."devices_defs.lua") indicator_type = indicator_types.COMMON shaderLineParamsUpdatable = true shaderLineDefaultThickness = 0.8 shaderLineDefaultFuzziness = 0.4 shaderLineDrawAsWire = false shaderLineUseSpecularPass = true opacity_sensitive_materials = { "font_RWR", "RWR_STROKE" } -------PAGE IDs------- id_Page = { PAGE_OFF = 0, PAGE_MAIN = 1, PAGE_BIT = 2 } id_pagesubset = { COMMON = 0, MAIN = 1, BIT = 2 } page_subsets = {} page_subsets[id_pagesubset.COMMON] = LockOn_Options.script_path.."TEWS/indicator/RWR_ALR67_COMMON_page.lua" page_subsets[id_pagesubset.MAIN] = LockOn_Options.script_path.."TEWS/indicator/RWR_ALR67_MAIN_page.lua" page_subsets[id_pagesubset.BIT] = LockOn_Options.script_path.."TEWS/indicator/RWR_ALR67_BIT_page.lua" ---------------------- pages = {} pages[id_Page.PAGE_OFF] = {} pages[id_Page.PAGE_MAIN] = {id_pagesubset.COMMON, id_pagesubset.MAIN} pages[id_Page.PAGE_BIT] = {id_pagesubset.COMMON, id_pagesubset.BIT} init_pageID = id_Page.PAGE_OFF use_parser = false --- master modes RWR_ALR67_OFF = 0 RWR_ALR67_MAIN = 1 RWR_ALR67_BIT = 2 pages_by_mode = {} clear_mode_table(pages_by_mode, 2, 0, 0) function get_page_by_mode(master,L2,L3,L4) return get_page_by_mode_global(pages_by_mode,init_pageID,master,L2,L3,L4) end pages_by_mode[RWR_ALR67_OFF][0][0][0] = id_Page.PAGE_OFF pages_by_mode[RWR_ALR67_MAIN][0][0][0] = id_Page.PAGE_MAIN pages_by_mode[RWR_ALR67_BIT][0][0][0] = id_Page.PAGE_BIT --Capt Zeen mod dofile(LockOn_Options.common_script_path.."ViewportHandling.lua") try_find_assigned_viewport("F18_RWR") -- Link to comment Share on other sites More sharing options...
mikemadmax20 Posted March 2, 2019 Share Posted March 2, 2019 Hi all: Has anyone got a fix on how to export the RWR. Again, see above .lua for your review. All help welcomed. Link to comment Share on other sites More sharing options...
Deezle Posted March 2, 2019 Share Posted March 2, 2019 So, back to the blurry/unreadable exports, it looks like the new SA page symbols are totally unreadable on my exported display, like those symbols are controlled by a different lua file than where everything else was adjusted to be readable, if that makes sense. Anyone figure out a fix? Still don't understand why these F/A-18 displays are handled totally differently than all the other modules. Seems ridiculous that these become unreadable at larger resolutions and on exports without tweaks :doh: Intel 9600K@4.9GHz, Asus Z390, 32GB DDR4, EVGA RTX 3070, Custom Water Cooling, 970 EVO 1TB NVMe 34" UltraWide 3440x1440 Curved Monitor, 21" Touch Screen MFD monitor, TIR5 My Pit Build, VKB Gunfighter Pro w/WH Grip, TMWH Throttle, MFG Crosswinds W/Combat Pedals, Cougar MFDs, Custom A-10C panels, Custom Helo Collective, SimShaker with Transducer Link to comment Share on other sites More sharing options...
USA_Recon Posted March 3, 2019 Share Posted March 3, 2019 are there any step by step instructions for someone that has never done this? Link to comment Share on other sites More sharing options...
Mapi Posted March 3, 2019 Share Posted March 3, 2019 Hi all: Has anyone got a fix on how to export the RWR. Again, see above .lua for your review. All help welcomed. play with this: shaderLineDefaultThickness = 15.0 -- 0.8 shaderLineDefaultFuzziness = 5.0 -- 0.4 ... go there: INPUT / OUTPUT Capt Zeen F/A-18C Beta Helios Profile ! ! ! https://forums.eagle.ru/showthread.php?t=212725&highlight=MDG you will find IMPROVING THE LINES QUALITY IN THE EXPORTED VIEWPORTS https://forums.eagle.ru/showpost.php...&postcount=117 Mapi Link to comment Share on other sites More sharing options...
mikemadmax20 Posted March 15, 2019 Share Posted March 15, 2019 Mapi you're the best. I applied your thickness and fuzziness numeric to my RWR.lua and it popped right up in the exact coordinates I had set in my 2 monitor lua (although I'm missing the threat rings). I now have all five exports working (2xDDI's, AMPCD, IFEI and, RWR). I just completed a trap landing, taxied along side the other two Hornets adjacent to Cat 1, popped the canopy, engaged HUD Only and, just sat there for in my modest pit for about 15 minutes - just taking it all in. This OG got a triple OG. Now I have to continue to find a fix for the text/font blurriness of the AMPCD in Map view. However, my fonts are perfect when I get out of Map view and enter the SA page. Still hoping for a fix of this issue. Been going over so many threads, posts, youtube videos and everything else I can lay my eyes on - that at this point I'm numb. Time for a break. But again, thanks a bunch for your guidance. Mike (Mad Max) Link to comment Share on other sites More sharing options...
CypherS Posted March 15, 2019 Share Posted March 15, 2019 Is the text on the AMPCD SA page messed up for anyone? The threat rings are messed up and the data below the staple doesn't completely show Link to comment Share on other sites More sharing options...
mari8it Posted March 23, 2019 Share Posted March 23, 2019 So, back to the blurry/unreadable exports, it looks like the new SA page symbols are totally unreadable on my exported display, like those symbols are controlled by a different lua file than where everything else was adjusted to be readable, if that makes sense. Anyone figure out a fix? Still don't understand why these F/A-18 displays are handled totally differently than all the other modules. Seems ridiculous that these become unreadable at larger resolutions and on exports without tweaks :doh: I agree Link to comment Share on other sites More sharing options...
Kaufi Posted April 18, 2019 Share Posted April 18, 2019 Can anyone point me if I can make the background of the exported MDIs black and opaque? Has anyone found a solution? [sIGPIC][/sIGPIC] Excuse please my bad English. Write please slowly, so that I can understand you.;) I7-X980Extreme*18GB*Zotac GTX680-4GB*27"+3 10"Touchscreen, TM Warthog Link to comment Share on other sites More sharing options...
mikemadmax20 Posted April 20, 2019 Share Posted April 20, 2019 I don't think anyone's looking. While I've got my AMPCD working, you can't make out the fonts/text/symbols over the map. I use my DD's for SA and other sub-pages and only use the AMPCD to get a Map view of my location. Link to comment Share on other sites More sharing options...
Miasma Posted June 4, 2019 Share Posted June 4, 2019 (edited) A quick question, I am already exporting the left and right DDI's for the hornet And I was wondering if it was possible to modify the lua so I could toggle the AMPCD on and off over one of them so as to not have to buy another screen and another Cougar controller. I only ask because I noticed that the Harrier exports are a toggle button and was wondering if this was possible in the Hornet. Edited June 4, 2019 by Miasma Royal Navy Tomcat skin now live: https://www.digitalcombatsimulator.com/en/files/?CREATED_BY=miasma&set_filter=Y Link to comment Share on other sites More sharing options...
Padonis Posted June 7, 2019 Share Posted June 7, 2019 After the last update, RWR export in F-18 has stopped working properly. All letters are very fuzzy, large green spots. Do colleagues have a similar problem? Link to comment Share on other sites More sharing options...
sobe Posted June 8, 2019 Share Posted June 8, 2019 YEP. Trackir4 using the latest Trackir 5 software, Win10 Pro [Creator Update] updated from Win7Pro Pro 64Bit, Intel® Core™ i5-2500 3.30 GHz 6M Intel Smart Cache LGA115 , GigaByte GA-Z68XP-UD4 Intel Z68 Chipset DDR3 16GB Ram, GTX MSI Gaming 1060 [6 GB] Video Card, Main Monitor 1 on left 1920x1080 Touchscreen Monitor 2 on right 1920x1080 . Link to comment Share on other sites More sharing options...
Dafiew Posted June 11, 2019 Share Posted June 11, 2019 After the last update, RWR export in F-18 has stopped working properly. All letters are very fuzzy, large green spots. Do colleagues have a similar problem? Same here Simflyin' since 1985 :smartass: Link to comment Share on other sites More sharing options...
Padonis Posted June 19, 2019 Share Posted June 19, 2019 Maybe something wrong is stored in the RWR export file to another monitor? What should the file look like? Where and what lines should be added to the file, how to define it? Link to comment Share on other sites More sharing options...
DerTak Posted June 30, 2019 Share Posted June 30, 2019 For the FA/18 I have a blurry RWR, no way to read it. I also have very blurry MDFs. Link to comment Share on other sites More sharing options...
DudleyAz Posted July 21, 2019 Share Posted July 21, 2019 I found that these settings in the RWR init file made my exported RWR readable again. However, it makes the in game cockpit RWR symbols almost invisible. I chose to have my exported one work. D:\Eagle Dynamics\DCS World\Mods\aircraft\FA-18C\Cockpit\Scripts\TEWS\indicator\RWR_ALR67_init.lua shaderLineParamsUpdatable = true shaderLineDefaultThickness = 0.08 shaderLineDefaultFuzziness = 0.03 shaderLineDrawAsWire = false shaderLineUseSpecularPass = true If it worked perfectly... what's the fun in that? :joystick: Link to comment Share on other sites More sharing options...
madeiner Posted July 28, 2019 Share Posted July 28, 2019 Quick question i want to export the MFD within the camera view of the main game. I can do that, but they are transparent. Any way to add a black background? Link to comment Share on other sites More sharing options...
GreatWhiteHype Posted August 21, 2019 Share Posted August 21, 2019 (edited) I am using two TM cougar MFD's with two 8" screens behind them. My DDI exports are working but the DDI's in the cockpit are now black, as if turned off. How do I correct this? Thank you in advance. This only occurs in stable DCS. In open beta, they repeat. Edited August 21, 2019 by GreatWhiteHype Attached pic for clarity Link to comment Share on other sites More sharing options...
Mule Posted August 22, 2019 Share Posted August 22, 2019 Got this working today many thanks. One thing I did get stuck on and that was forgetting to change the resolution of the monitor in game. It was set at 1920x1280 which is my main monitor but with the extra monitor it's 3200x1280. After I changed it the exported mfd's popped up. Cheers! Fighter Pilot Podcast. Link to comment Share on other sites More sharing options...
Recommended Posts