LaLa Posted April 22, 2020 Share Posted April 22, 2020 I'm modifying my monitor config but cant get the RWR to display. Below my .lua _ = function(p) return p; end; name = _('F16C MCD 3520x1080'); Description = 'f16 setup 2 monitors' --TOTAL DEL VIEWPORT Viewports = { Center = { x = 0; y = 0; width = 1920; height = 1080; viewDx = 0; viewDy = 0; aspect = 16/9; } } --LEFT LEFT_MFCD = { x = 1920+70; y = 99; width = 642; height = 707; } --RIGHT RIGHT_MFCD = { x = 1920+877; y = 99; width = 642; height = 707; } -- RWR F16_RWR = { x = 1920+711; y = 730; width = 180; height = 153; } F16_DED = { x = 1920+1211; y = 0; width = 317; height = 108; } EHSI = { x = 1920+1418; y = 710; width = 120; height = 120; } UIMainView = Viewports.Center The right and left MCDs OK, the EHSI OK, but cant see the DED or RWR. Any help appreciated. Link to comment Share on other sites More sharing options...
LaLa Posted April 22, 2020 Author Share Posted April 22, 2020 Is it possible to export RWR on the F16? I noticed that I have a couple of monitor lua files that dont show up in DCS setup, despite being in the correct folder along with the others...corruption?? Link to comment Share on other sites More sharing options...
questerymj Posted April 22, 2020 Share Posted April 22, 2020 You need to add lines in RWR init lua file of F-16C. I'd success export the RWR, do you need I to post it here? Link to comment Share on other sites More sharing options...
LeCuvier Posted April 22, 2020 Share Posted April 22, 2020 In the F/A-18 you need to add these lines into the device initit .lua file: dofile(LockOn_Options.common_script_path.."ViewportHandling.lua") try_find_assigned_viewport("F18_RWR") You probably have to do something similar in the f-16. The file for the F-16 is "RWR_ALR56_init.lua" and it's located in "\DCS World OpenBeta\Mods\aircraft\F-16C\Cockpit\Scripts\EWS\RWR\indicator". LeCuvier Windows 10 Pro 64Bit | i7-4790 CPU |16 GB RAM|SSD System Disk|SSD Gaming Disk| MSI GTX-1080 Gaming 8 GB| Acer XB270HU | TM Warthog HOTAS | VKB Gladiator Pro | MongoosT-50 | MFG Crosswind Pedals | TrackIR 5 Link to comment Share on other sites More sharing options...
LaLa Posted April 22, 2020 Author Share Posted April 22, 2020 Yes please! Thanks alot! Link to comment Share on other sites More sharing options...
LaLa Posted April 22, 2020 Author Share Posted April 22, 2020 (edited) Thanx LeCuvier! What you said makes perfect sense, but still no joy, I just noticed your path is OpenBeta mine isnt! Hmmmm! In the F/A-18 you need to add these lines into the device initit .lua file: dofile(LockOn_Options.common_script_path.."ViewportHandling.lua") try_find_assigned_viewport("F18_RWR")You probably have to do something similar in the f-16. The file for the F-16 is "RWR_ALR56_init.lua" and it's located in "\DCS World OpenBeta\Mods\aircraft\F-16C\Cockpit\Scripts\EWS\RWR\indicator". Yeah Found the file added: "Dofile(LockOn_Options.common_script_path.."ViewportHandling.lua") try_find_assigned_viewport("F16_RWR")" at the line at the very end of C:\Program Files\Eagle Dynamics\DCS World\Mods\aircraft\F-16C\Cockpit\Scripts\EWS\RWR\indicator\RWR_ALR56_init.lua but no joy! :noexpression: Edited April 22, 2020 by LaLa Link to comment Share on other sites More sharing options...
LaLa Posted April 22, 2020 Author Share Posted April 22, 2020 You need to add lines in RWR init lua file of F-16C. I'd success export the RWR, do you need I to post it here? :) Yeah that would be great! Link to comment Share on other sites More sharing options...
LaLa Posted April 22, 2020 Author Share Posted April 22, 2020 Is OpenBeta version a necessity for RWR on F16? Link to comment Share on other sites More sharing options...
Ddaddy Posted April 25, 2020 Share Posted April 25, 2020 Ok, I am getting the same in F18, right MFCD will not display. F15 the same. Used to work. The other 2 mfcds display and placement works fine. Just blank on any RMFCD... RIGHT_MFCD = { x = 2957; y = 415; width = 327; height = 353; } R5 2600 @4.2 GHZ, 16GB ram @ 3133, 1060 6GB at 2100 and 4400 970 Evo, TM16000M FCS Flight Pack and old eyes. Just an old Hillbilly that does what he wants when he wants...if I can get out of bed! Link to comment Share on other sites More sharing options...
LeCuvier Posted April 26, 2020 Share Posted April 26, 2020 (edited) Works for both planes on my rig in Open Beta. For the F/A-18 I export both DDI's, AMPCD, IFEI and RWR. For the F-16 both MFCD's and RWR. The RWR export on the F/A-18 is fairly useless though. You have to reduce the thickness and fuzziness to 1/10th of the original values, because with the original values the symbols appear as huge green blobs. But with these changes, the symbols in the cockpit RWR become almost invisible. The F-16 RWR exports very nicely. For both RWR's however, the export shows only the dynamic symbols, not the concentric and radial lines. These seem to be part of the indicator glass and not included in the export. I attach screenshots for both planes and the monitor setup file which sits under Saved Games. As you see on the F/A-18 screenshot, I like to put the RWR display on the exported left DDI. Here are the beginnings of the 3 modified indicator init files: For the F/A-18 RWR "RWR_ALR67_init.lua": dofile(LockOn_Options.common_script_path.."devices_defs.lua") indicator_type = indicator_types.COMMON ------------------------ added by Capt Zeen dofile(LockOn_Options.common_script_path.."ViewportHandling.lua") try_find_assigned_viewport("F18_RWR") ------------------------ end of added by Capt Zeen shaderLineParamsUpdatable = true shaderLineDefaultThickness = 0.08 shaderLineDefaultFuzziness = 0.04For the F/A-18 IFEI: "IFEI_init.lua": dofile(LockOn_Options.common_script_path.."devices_defs.lua") indicator_type = indicator_types.COMMON ------------------------ added by HWF dofile(LockOn_Options.common_script_path.."ViewportHandling.lua") try_find_assigned_viewport("F18_IFEI") ------------------------ end of added by HWFFor the F-16 RWR "RWR_ALR56_init.lua": dofile(LockOn_Options.common_script_path.."devices_defs.lua") indicator_type = indicator_types.COMMON -- added HWF based on solution by Captain Zeen dofile(LockOn_Options.common_script_path.."ViewportHandling.lua") try_find_assigned_viewport("F18_RWR") -- End of added by HWFNote that I use the name "F18_RWR" for both planes. This saves me the trouble of adding a "F16_RWR" to the monitor setup file. In fact I could have named both just "RWR". This approach works as long as the 2 RWR have similar geometry and anchor points. I might be able to try this in the stable version later today.Camera+FA-18_AMPCD.lua Edited April 26, 2020 by LeCuvier LeCuvier Windows 10 Pro 64Bit | i7-4790 CPU |16 GB RAM|SSD System Disk|SSD Gaming Disk| MSI GTX-1080 Gaming 8 GB| Acer XB270HU | TM Warthog HOTAS | VKB Gladiator Pro | MongoosT-50 | MFG Crosswind Pedals | TrackIR 5 Link to comment Share on other sites More sharing options...
LeCuvier Posted April 26, 2020 Share Posted April 26, 2020 Export works in Stable Version too I duplicated my setup for F-16 and F/A-18 in the stable version, and everything works the same as in O.B. However, it seems that the exported MFCD's in the F-16 lack brightness. LeCuvier Windows 10 Pro 64Bit | i7-4790 CPU |16 GB RAM|SSD System Disk|SSD Gaming Disk| MSI GTX-1080 Gaming 8 GB| Acer XB270HU | TM Warthog HOTAS | VKB Gladiator Pro | MongoosT-50 | MFG Crosswind Pedals | TrackIR 5 Link to comment Share on other sites More sharing options...
Ddaddy Posted April 26, 2020 Share Posted April 26, 2020 Thanks R5 2600 @4.2 GHZ, 16GB ram @ 3133, 1060 6GB at 2100 and 4400 970 Evo, TM16000M FCS Flight Pack and old eyes. Just an old Hillbilly that does what he wants when he wants...if I can get out of bed! Link to comment Share on other sites More sharing options...
Devrim Posted November 23, 2020 Share Posted November 23, 2020 ...but cant see the DED or RWR. I added; F16_DED = { x = 2725; -- DED start pos. y = 0; -- DED pos from top. width = 600; height = 200; } in my monitorsetup.lua, as you do (this is my monitor setup, of course). And, added; if not USE_DED then --ViewportHandling dofile(LockOn_Options.common_script_path.."ViewportHandling.lua") update_screenspace_diplacement(1, true, 0) try_find_assigned_viewport("F16_DED") end at the end of the DED_init.lua (at "...\Mods\aircraft\F-16C\Cockpit\Scripts\Displays\DED\indicator") It works. DED can be exportable. *** By the way, I have a problem. I modified ViewportHandling.lua file and disabled render_purpose.GENERAL command, but in-game I can see MFDs on in the cockpit. They're not disabled. Is it same for you too? Thanks. Intel i7-14700@5.6GHz | MSI RTX4080 Super SuprimX | Corsair V. 32GB@6400MHz. | Samsung 1TB 990 PRO SSD (Win10Homex64) Samsung G5 32" + Samsung 18" + 2x8"TFT Displays | Saitek X-55 Rhino & Rudder | TM MFD Cougars | Logitech G13, G230, G510, PZ55 & Farming Sim Panel | TIR5 >>MY MODS<< | Discord: Devrim#1068 Link to comment Share on other sites More sharing options...
Coyote_One Posted December 13, 2021 Share Posted December 13, 2021 (edited) On 4/26/2020 at 4:56 AM, LeCuvier said: Works for both planes on my rig in Open Beta. For the F/A-18 I export both DDI's, AMPCD, IFEI and RWR. For the F-16 both MFCD's and RWR. The RWR export on the F/A-18 is fairly useless though. You have to reduce the thickness and fuzziness to 1/10th of the original values, because with the original values the symbols appear as huge green blobs. But with these changes, the symbols in the cockpit RWR become almost invisible. The F-16 RWR exports very nicely. For both RWR's however, the export shows only the dynamic symbols, not the concentric and radial lines. These seem to be part of the indicator glass and not included in the export. I attach screenshots for both planes and the monitor setup file which sits under Saved Games. As you see on the F/A-18 screenshot, I like to put the RWR display on the exported left DDI. Here are the beginnings of the 3 modified indicator init files: For the F/A-18 RWR "RWR_ALR67_init.lua": dofile(LockOn_Options.common_script_path.."devices_defs.lua") indicator_type = indicator_types.COMMON ------------------------ added by Capt Zeen dofile(LockOn_Options.common_script_path.."ViewportHandling.lua") try_find_assigned_viewport("F18_RWR") ------------------------ end of added by Capt Zeen shaderLineParamsUpdatable = true shaderLineDefaultThickness = 0.08 shaderLineDefaultFuzziness = 0.04 For the F/A-18 IFEI: "IFEI_init.lua": dofile(LockOn_Options.common_script_path.."devices_defs.lua") indicator_type = indicator_types.COMMON ------------------------ added by HWF dofile(LockOn_Options.common_script_path.."ViewportHandling.lua") try_find_assigned_viewport("F18_IFEI") ------------------------ end of added by HWF For the F-16 RWR "RWR_ALR56_init.lua": dofile(LockOn_Options.common_script_path.."devices_defs.lua") indicator_type = indicator_types.COMMON -- added HWF based on solution by Captain Zeen dofile(LockOn_Options.common_script_path.."ViewportHandling.lua") try_find_assigned_viewport("F18_RWR") -- End of added by HWF Note that I use the name "F18_RWR" for both planes. This saves me the trouble of adding a "F16_RWR" to the monitor setup file. In fact I could have named both just "RWR". This approach works as long as the 2 RWR have similar geometry and anchor points. I might be able to try this in the stable version later today. Camera+FA-18_AMPCD.lua 1.09 kB · 74 downloads Is this still correct after the whole RWR fiasco recently in that patch a few months ago? I just pasted your F16 line into that ALR56 lua and nothing happened. Im sure its changed by now? Edited December 13, 2021 by Coyote_One Added screenshot Link to comment Share on other sites More sharing options...
LeCuvier Posted December 13, 2021 Share Posted December 13, 2021 I have not used the RWR export recently due to its limited value. But I'm sure ED has made some change in this functionality, because the F/A-18C RWR display in Helios, which used to work ok, produces only blurs since the last update. I do not intend to invest more time into this. LeCuvier Windows 10 Pro 64Bit | i7-4790 CPU |16 GB RAM|SSD System Disk|SSD Gaming Disk| MSI GTX-1080 Gaming 8 GB| Acer XB270HU | TM Warthog HOTAS | VKB Gladiator Pro | MongoosT-50 | MFG Crosswind Pedals | TrackIR 5 Link to comment Share on other sites More sharing options...
scutxd Posted April 18, 2022 Share Posted April 18, 2022 On 12/13/2021 at 11:27 PM, Coyote_One said: Is this still correct after the whole RWR fiasco recently in that patch a few months ago? I just pasted your F16 line into that ALR56 lua and nothing happened. Im sure its changed by now? Thanks very much! I have wasted one whold day for this error. Link to comment Share on other sites More sharing options...
Urgelb Posted June 10, 2022 Share Posted June 10, 2022 Here is my setup to get it working: my monitor file: _ = function(p) return p; end; name = _('Francois'); Description = 'Left MFCD ,Right MFCD, UFC, AMCD, DED, EHSI on the lower monitor' Viewports = { Center = { x = 0; y = 0; width = 5120; height = 1440; viewDx = 0; viewDy = 0; aspect = 5120/1440; } } LEFT_MFCD = { x = 5120; y = 5; width = 482; height = 482; } RIGHT_MFCD = { x = 7198; y = 5; width = 482; height = 482; } CENTER_MFCD = { x = 6080; y = 440; width = 640; height = 640; } DED = { x = 6210; y = 0; width = 380; height = 125; } RWR = { x = 6280; y = 220; width = 240; height = 240; } CDU = { x = 6210; y = 0; width = 380; height = 290; } AN_ALR69V = { x = 6280; y = 300; width = 240; height = 240; } EHSI = { x = 6260; y = 480; width = 280; height = 280; } NS430 = { x = 6080; y = 0; width = 640; height = 300; } UIMainView = Viewports.Center GU_MAIN_VIEWPORT = Viewports.Center Then you have to go to the scripts directory for every plane in my case the A-10CII, F-16, F-18 and NS430 for my L39 and inside the RWR_ALR56_init.LUA file I added the lines: if not USE_LCD_MFD then --ViewportHandling dofile(LockOn_Options.common_script_path.."ViewportHandling.lua") update_screenspace_diplacement(1, true, 0) try_find_assigned_viewport("AN_ALR69V") end I did the same for the DED_init.lua, AN_ALR69V_init.lua, CDU_init.lua, and NS430_init.lua replacing the name with the proper one. The EHSI is already setup by default. Hope this helps you out ! Link to comment Share on other sites More sharing options...
Recommended Posts