Lightning's MFDE and 4.33
-
bump
Is there any way to contact the developer(s) directly? It’d be great if somebody could take a look at the issue with 3rd party theaters described here
https://www.benchmarksims.org/forum/showthread.php?25693-IKAROS_v3&p=368241&viewfull=1#post368241
as I suspect I may not be the only one affected by it.
Thanks in advance & all the best, Uwe
-
Just wanted to report since it was discussed previously, I too am getting what I believe to be a false positive AVG hit today with MFDe 0.6.1.1. It says it is a Pakes_c trojan in the common.inputsupport.dll
-
Just wanted to report since it was discussed previously, I too am getting what I believe to be a false positive AVG hit today with MFDe 0.6.1.1. It says it is a Pakes_c trojan in the common.inputsupport.dll
You mean its not safe to try these files?
-
I believe the AVG warning is a false positive. I have used Lightning’s MFDE extraction for years with no issues.
-
Just wanted to report since it was discussed previously, I too am getting what I believe to be a false positive AVG hit today with MFDe 0.6.1.1. It says it is a Pakes_c trojan in the common.inputsupport.dll
I believe the AVG warning is a false positive. I have used Lightning’s MFDE extraction for years with no issues.
Agreed.
-
It does seem to be a false positive. Solution: I downloaded the source and recompiled it. No problems since.
-
It does seem to be a false positive. Solution: I downloaded the source and recompiled it. No problems since.
Bikeman, can you elaborate on the kind of dev environment needed in order to recompile the source successfully? Maybe we could take a look at the “invalid path component” problem I outlined above and here:
https://www.benchmarksims.org/forum/showthread.php?25693-IKAROS_v3&p=368241&viewfull=1#post368241
I’d love to get MFDE working again in non KTO theaters, let me know what I can do to help.
Thanks Uwe
-
I think I solved the issue by using only relative pathnames in my theaterdefinition.lst file, for details see this post:
https://www.benchmarksims.org/forum/showthread.php?25693-IKAROS_v3&p=369945&viewfull=1#post369945
It might be worth either fixing the issue in the next MFDE release or putting a note in the README file to illustrate the issue.
All the best, Uwe
-
AMVI_Muplex
What does “doesn’t work mean?” MFD’s don’t work in fullscreen, but work in windowed mode or nothing works at all?
yes, correct, but i doesnt’ like windowed for several reasons
-
@hoover: I used Visual Studio Community 2015
-
yes, correct, but i doesnt’ like windowed for several reasons
Have you tried running MFDE as admin? That did it for me.
-
Have you tried running MFDE as admin? That did it for me.
Guys I have a new very big problem with mfde v 6.1.1 and also 6.1.0.
Now the program, after opening, does not work at all.
The icon appear on the windows taskbar but nothing happends.
I try to click on program options after a mouse right-click on the icon, but nothing happends.PLEASE can some one HELP me ? =(
-
Guys I have a new very big problem with mfde v 6.1.1 and also 6.1.0.
Now the program, after opening, does not work at all.
The icon appear on the windows taskbar but nothing happends.
I try to click on program options after a mouse right-click on the icon, but nothing happends.PLEASE can some one HELP me ? =(
I had the same issue if AVG notified me as false positive for a trojan horse.
You need to kill the exe process, open AVG, add the MFDE folder to the exceptions of AVG scanning, then restart MFDE and it should work fine -
I had the same issue if AVG notified me as false positive for a trojan horse.
You need to kill the exe process, open AVG, add the MFDE folder to the exceptions of AVG scanning, then restart MFDE and it should work fineThank you very much !!! you’re right…
Now also AVIRA detect these false positive, before notThanks again… ^^
have you any info about HOW works MFDE with falcon bms in fullscreen mode ? -
Flawless.
Just do not forget to place the additonal gauge monitors over the main monitor in the windows display settings.
-
Thank you very much !!! you’re right…
Now also AVIRA detect these false positive, before notThanks again… ^^
have you any info about HOW works MFDE with falcon bms in fullscreen mode ?no idea, with me that worked in 4.32. Haven’t tried it in 4.33 because the MFD’s of MFDE are way too laggy in the latest 2 versions and I’m in windowed mode because I’m currently back to using BMS extraction for DED/RWR/MFDs and only use MFDE for the other stuff.
-
Works great for me in fullscreen. Some have issues with the instruments changing position when the UI goes 1024 x 768 in FS. To fix that just make the monitor with the instruments position in the first position in screen resolution.
-
Works great for me in fullscreen. Some have issues with the instruments changing position when the UI goes 1024 x 768 in FS. To fix that just make the monitor with the instruments position in the first position in screen resolution.
Sorry iceburg, what you means exactly ?
If my configuration is :
Main: Philips monitor 226V4 1920x1080 res
2x Usb Samsung U70 with displaylink drivers 7.7.60366.0 version 800x480 reswhen i go to screen resolution options obviuosly the main is 1 and the other mini-monitors are recognised as 2 and 3….
What I have to do to solve?
-
When you are in display properties you can rearrange the displays. Move the two small screens ABOVE the main screen and to the left edge.
So the small screens will be anytime on the 0,0 coordinates and won’t be affected by the resolution switching.
-
When you are in display properties you can rearrange the displays. Move the two small screens ABOVE the main screen and to the left edge.
So the small screens will be anytime on the 0,0 coordinates and won’t be affected by the resolution switching.
ah, undestand, but my problem is the small resolution of the instrument monitors.
I cant work with such that small screen as main =(