eulaced Posted July 23, 2020 Share Posted July 23, 2020 Hi I am having problem with the AMPCD DDI on my Second monitor the below will and LUA file attack for someone help . the problem start after the update July 16, 2020 . Can anyone help me please . This happen only in F/A18 Link to comment Share on other sites More sharing options...
ED Team BIGNEWY Posted July 24, 2020 ED Team Share Posted July 24, 2020 Hi All seems normal for me, have you tried a cleanup and repair? Make sure you backup your monitor.lua first Forum rules - DCS Crashing? Try this first - Cleanup and Repair - Discord BIGNEWY#8703 - Youtube - Patch Status Windows 11, NVIDIA MSI RTX 3090, Intel® i9-10900K 3.70GHz, 5.30GHz Turbo, Corsair Hydro Series H150i Pro, 64GB DDR @3200, ASUS ROG Strix Z490-F Gaming, HP Reverb G2 Link to comment Share on other sites More sharing options...
gunterlund21 Posted July 24, 2020 Share Posted July 24, 2020 (edited) this occurs for me as well with the mfd's. Somehow the values are linked to the HUD so if you make adjustments the MFD's look ok but the HUD disappears because you have to thin out the lines to much. Adjusting MDG_strokesDefs.lua dofile(LockOn_Options.script_path.."config.lua") stroke_thickness = 0.9 this impacts both MFD and HUD stroke_fuzziness = 0.15 this impacts both MFD and HUD if bakeIndicators == true then DMC_stroke_thickness = stroke_thickness DMC_stroke_fuzziness = stroke_fuzziness -- Currently is used for DMC generated fonts black outline --DMC_outline_thickness = stroke_thickness * 3 --DMC_outline_fuzziness = stroke_fuzziness * 0.15 -- valid for cockpit view, but looks overdone at HUD only view DMC_outline_thickness = stroke_thickness * 3.5 DMC_outline_fuzziness = stroke_fuzziness * 1.4 else DMC_stroke_thickness = 1 DMC_stroke_fuzziness = 0.15 -- Currently is used for DMC generated fonts black outline DMC_outline_thickness = stroke_thickness * 3 DMC_outline_fuzziness = stroke_fuzziness * 0.15 end Edited July 24, 2020 by gunterlund21 I was in Art of the Kill D#@ it!!!! Link to comment Share on other sites More sharing options...
eulaced Posted July 24, 2020 Author Share Posted July 24, 2020 Thank You will try that now Link to comment Share on other sites More sharing options...
gunterlund21 Posted July 25, 2020 Share Posted July 25, 2020 (edited) BigNewy this is not what you see when you export? If not send us your setup Edited July 25, 2020 by gunterlund21 I was in Art of the Kill D#@ it!!!! Link to comment Share on other sites More sharing options...
fox2bravo Posted August 16, 2020 Share Posted August 16, 2020 Anyone got this sorted out as I have the same problem Link to comment Share on other sites More sharing options...
Beamscanner Posted August 16, 2020 Share Posted August 16, 2020 This bug has been around for years.. It occurs when you use vertical displays (hence why BIGNEWY didnt get the bug). https://forums.eagle.ru/showthread.php?p=3631456#post3631456 https://forums.eagle.ru/showthread.php?t=226340&page=5&highlight=blurry https://forums.eagle.ru/showthread.php?t=224265&highlight=blurry Link to comment Share on other sites More sharing options...
fox2bravo Posted August 16, 2020 Share Posted August 16, 2020 Yeah, I have the AMPCD on a vertical external display, and it has been working just fine until the last update... Link to comment Share on other sites More sharing options...
arpia47 Posted August 16, 2020 Share Posted August 16, 2020 Hello Same problem here, weeks before it was working perfectly, i was trying changing values like.... shaderLineDefaultThickness = 0.8 shaderLineDefaultFuzziness = 0.5 but nothing works Link to comment Share on other sites More sharing options...
neok Posted August 18, 2020 Share Posted August 18, 2020 I like to bump this. Please can I have some help with this as well? I used these values in the MDG_strokesDefs.lua, but those don't seem to work any more after the update. stroke_thickness = 0.4 stroke_fuzziness = 0.2 -- Currently is used for DMC generated fonts black outline DMC_outline_thickness = stroke_thickness * 3 DMC_outline_fuzziness = stroke_fuzziness * 0.15 DMC_stroke_thickness = 0.4 DMC_stroke_fuzziness = 0.2 Link to comment Share on other sites More sharing options...
Noluck Posted August 20, 2020 Share Posted August 20, 2020 (edited) Just another example of F/A-18 'updates'. Fix one thing, break more things. Why the main and very important displays used, the DDI's, MFCD and HUD keep on getting 'tweaked'? Those displays are something very basic that should have worked from day 1 the pre-release was announced and distributed. I still have a blurry HUD in my main view with my monitor setup. Been like that for months! CANNOT REPRODUCE? There is a problem as shown here. All of those reporting should share their exact monitor setup and monitor config file so ED can better understand our current DCS configuration. --- Edited August 20, 2020 by Noluck PC: Windows 10 Pro X64, AMD FX8120 8 Core @ ~4.0GHz, 32GB DDR3-1600, GTX 1080 8Gb, 1 TB EVO 860 SSD | Displays: 3 Dell HD 1920x1080 @ 5520x1080 windowed ||| Hardware : TM Warthog HOTAS Stick+Throttle | 3x TM Cougar MFD's | WW Combat Panel | WW Landing Panel ||| Mods: F/A-18C | F-16 | P51-D | UH-1H | C130-J | NTTR | Persian Gulf | Syria | Channel | Normandy | WWII Assets | Super Carrier | Combined Arms Link to comment Share on other sites More sharing options...
fox2bravo Posted August 22, 2020 Share Posted August 22, 2020 I found a solution, I changed my F-18 lua.file under Config/Monitor setup from "F-18_AMPCD" to "CENTER_MFD" instead. Link to comment Share on other sites More sharing options...
Beamscanner Posted August 31, 2020 Share Posted August 31, 2020 remove your DDI/AMPCD export mods. ED has added these veiwport exports to the base game. no need to change any font size, etc.. just change your monitor config to say "Center_MFCD" instead of "AMPCD". You still need an export mod if you want the RWR, UFC or IFE on a second monitor. Link to comment Share on other sites More sharing options...
edison_trent Posted November 22, 2020 Share Posted November 22, 2020 I found a solution, I changed my F-18 lua.file under Config/Monitor setup from "F-18_AMPCD" to "CENTER_MFD" instead. i confirm. that worked. Link to comment Share on other sites More sharing options...
Recommended Posts