Lightning's MFDE and 4.33
-
Ok I got a stupid question. How do I get the lightenings panels to show ontop of Falcon while I’m in flight without going into windowed mode? Everytime I start Falcon It takes up the full screen and then I can’t see my gauges.
It is meant to be used on a second monitor
Or was this a trick question ? :munch:
-
SHIFT + / :munch:
-
OK, I’ve got a new one. I’ve been using this for some time and suddenly this evening, Kaspersky is telling me that it has Malware and won’t open it up.
“…Falcon MFD Extractor\Common.InputSupport.dll
Object Name Trojan.MSIL.Agent.abirt
Object type: Trojan”Any thoughts?
Just noticed eagleeyes has the same problem on page 10 of this thread.
Has no one got any ideas about this? Or are Norton and Kaspersky both wrong?
-
I’ m not using MFD ext. currently, my touchscreen broke , but it is 99% false postive by antivirus, depends …
Where did you download it ? Always download from the main site then you can be sure it is the real one soft you’re using.
You see by the module where it was intercepted by antivirus "Common.InputSupport.dll " , that is where antivirus heuristics “believes” it is a trojan keylogger or something , malware.
Because we are using very “fancy” (not so standard) ways of input/output controls for windows.But in our case … , who would do that and why?
Cheers
-
Zonelabs reports a virus too. I downloaded the source from assembla/lightningviper and recompiled it. Still a virus, obviously false positive. I set an exception in Zonelabs antivirus.
-
Have also a virus warning message from G-Data antivirus !
-
Can anyone confirm the virus of this file ?
can not clean the file via antivirus software G-DATA or restore the file back !any ideas?
-
False positiv…
-
Thanks to those who reported it was a false positive.
-
heya, Bitdefender same, “wondering” , set to don’t scan data file! But what is common.dll scaning ?? That’s the problem!
-
It seems I now have lost all functionality with MFDE 0.6.1 and 4.33. At first I only had problems with DE not working in ITO (only MFDEs, other instruments still worked fine), then I tested the new Ikaros version last night and nothing worked.
I then followed the suggestion of uninstalling MFDE completely and deleting the folder found in “Appdata”, then re-installing, but sadly that hasn’t helped. I’ve now also lost all functionality in KTO too, so at least now there’s symmetry
I checked my “Falcon BMS.cfg” for the usual variables concerning Shared Memory and all is looking good. Any ideas what else is there to try?
Thanks, Uwe
-
Do you run BMS in windowed mode? I do, and this is the only way MFDe works fine for me.
-
Yep, windowed mode here too. Funnily enough it seemed to work fine in stock KTO at first but it’s not working now after re-installing version 0.6.1.
Uwe
-
Run as admin made it work in fullscreen mode for me.
-
I’m pretty sure i’m also running it as admin… as I’ve said I didn’t change anything on the system and it worked fine at first with KTO, the first time I noted problems was when trying it in ITO.
Uwe
-
-
Thanks Icarus, I’ll give it a go later.
Uwe
-
Just tried it, still no luck. I’ve got extraction working again though in KTO, however it still doesn’t work in the Ikaros nor the ITO theaters. Very weird.
A giveaway is that the eHSI remains on the default graphics once MFDE starts up, that means that DE won’t work; if the default graphics is replaced by a blank rectangle, DE will work when entering 3d.
Cheers, Uwe
-
Does anyone know where MFDE stores data regarding extracted gauge locations? I’d like to be able to backup this file so that I don’t have to go resize/drag stuff when it decides to go berserk.
-
User name\AppData\Local\MFDExtractor.exe_Uri_1xxxxxxxxxxxetc\0.6.1.1\ user.config