GerardoM_N
-
Posts
16 -
Joined
-
Last visited
Posts posted by GerardoM_N
-
-
Jerry,
How would people like myself ( who have a non working DU on a secondary system with not a single FS addon installed apart from pfpx and asn) fit into your theory ?
Regards / Dick
=
Well, it's obvious that the airbus cant be the only source of problems since not everyone owns it. But if a font is causing Castle.MicroKernel to stop working I assume (and it's only an assumption) that it makes it easier for the devs to see what's causing the problem.
At any rate, the problem is still there and it needs to be fixed whatever the cause of it may be.
Jerry
-
UPDATE: I have tested EFB on a virtual machine with Windows 10 and the DU stops working after installing Aerosoft's Airbus. I have no idea if this is the only add on that causes trouble with EFB but maybe it narrows down the possible problems. Btw, the Airbus installs and works fine under Windows 10, it only seems to wreck EFB and one system font. After uninstalling the Airbus the problem persists, but then I deleted the fonts that it installs and the DU works again. So it is clear it has something to do with Airbus fonts
Regards,
Jerry
-
Hello to everyone,
As of today something happened that the DU no longer starts. As you remember it had been running fine from a clean W10 install. I have no idea why it ran okay for almost three weeks and now it's dead
Anyway, it's nice to hear its being worked on so hopefully a fix is due soon.
Regards,
Jerry
-
Hi All
Update - all works well after a clean install on W10 Pro x64. I did change the install media to the "RTM-version" that was released after the 29th July.
Previously was on Insider Build 10240 that was released around the 20th July 2015.
Steps taken were as stated by Urs and Jerry-thank you Gents!
Will post pics later (dont know how to do that at the moment ) as well as list steps taken to complete the installation.
I did encounter an issue related to DotNet but this was resolved after I installed Simconnect from the P3D "redist" folder.
Keep well and regards
Pauga
That's really good to hear! I'm glad you got it working.
Regards
Jerry
-
It is interesting, to say the least, that it's working for some people but not for others. Hopefully it will get sorted out soon.
Hi Jerry,
Thanks for this update.
Do i understand correctly you are running everything on one PC?
Because i am running P3d en DP on different machine from DU. DP is giving me no problems. It is starting up properly and then waits for connection to DU.Might be worth the try to deinstall EFB on the support machine and reinstall.
I do not look forward to a clean Win/10 install though
Just a question, do i need something like my licence code to reinstall or will it be saved over a deinstall/install on the same machine?
Hello, and yes, everything is on one PC.
Maybe you could go to Settings, Update & Security, Recovery, Reset this PC and when prompted select keep files and see if that fixes it? It is the closest thing to a reinstall without losing anything.
I started the setup from windows explorer and it forced me to put a key before it continued. It did not let me put it in later. I don't know if running it from the BIOS is any different though.You can get your key using this tool http://janek2012.eu/ultimate-pid-checker/.
Take care
Jerry
-
Hello all,
I am sorry to hear that some of you have not been able to get it working. Here are the steps I followed:
1. Make an upgrade to Windows 10 using the media creation tool
2. Before anything else, I downloaded the 1.5.1 setup.exe (it only let me install the DU). On first run, it prompted for installation of .NET 3.5. No weird letter spacing and everything was normal.
3. I created a bootable USB with the media creation tool and made a clean install from there.
4. Repeated step 2. All good.
5. Uninstalled EFB.
6. Install P3D and simconnect
7. Ran the EFB installer again and this time installed both DP and DU.
I hope this helps
Jerry
-
Hello Pauga,
I have some news (the good kind, I'd hope).
As I'm sure you remember I downgraded Windows 8.1 and EFB was working OK. Since, I've upgraded again to W10 (full version this time) and surprisingly EFB worked as if nothing had gone wrong two weeks earlier.
I think it's worth noting that I used the Media Creation Tool and did an "Upgrade" keeping all my files and settings; instead of doing a "Clean Install" as I had done with the Technical Preview.
However, this last paragraph can be disregarded. I have formatted my SSD and done a clean install of Windows. First thing I did (literally) was download the EFB setup. Because as of right now I have not installed P3D, it only allowed for a Display Unit install. (Also, Windows asked for a .NET install when I first ran it [which is weird because I thought it would be preinstalled on Windows]). Upon running it, I noticed that the symptoms described at the start of the thread no longer seem to appear. I have yet to install P3D and the Data Provider, but, if the Display Unit behavior is any indication I'm sure it will go well.
As for why the DU was not working on the technical preview, I haven't a clue. I will complete my installs tomorrow and report if the functionality remains.
Keep well
Jerry
-
Busy upgrading home PC's to W10.
Hi Pauga,
I actually downgraded to Win 8.1. Mainly because I did not want to be part of the Insider Program forever; as a bonus my EFB now works!
Regards
Jerry
-
hoping one of the current W10 Updates gets to fix the DotNet issues.
Hello,
Honestly if I were Microsoft, I would not rush the fix and resume working on it after the 29th. Specially since we are so close to the release date. Oh well, it is what it is, let's just hope for the best.
Jerry
-
Morning Brian
Thanks and will try that this morning
Thank you
Pauga
Hello Pauga.
Have you had any luck? If not, our best bet is that past July 29th with the official release of W10 the dev can look into it and work on trying to make it compatible (or create some temporary workaround) with W10 and/or .NET 4.6.
Jerry
-
i've got 393295
Weird. I just updated my .net to be on the same version as you and reinstalled but it keeps happening. Honestly, I don't think .net is the problem but rather Castle.Microkernel.dll. I tried updating it but now I don't even get the error screen, it just crashes. Oh well, thanks for your help and hopefully this gets sorted out in the future
-
I'd go with Urs suggestion and check your .net stuff.
What version do you have on both your machines? I have version 4.6 RC build 393292 (from HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\Full\)
-
Hi Jerry,
To be honest, I have no experience yet with Windows 10, especially because it's not yet officially released.
Have a look at the "Turn on or off Windows features" dialog from the "Windows Control Panel - Uninstall a program" dialog (if this is still available in Windows 10) and verify whether the .NET Framework 3.5.1 components are explicitely ticked. You don't need to tick the two WCF options below (see the enclosed image).
I suppose something has change internally in Windows that doesn't play nicely with EFB. I have these settings
Hi Jerry
I am running the data provider on a Windows 7 pc and the display unit on a windows 10 and that works fine so maybe there is an issue with the DP running on windows 10. I don;t think my license will allow me to install on another computer otherwise I'd load it up and try it for you.
That's my guess. I get this weird letters as well .
Thank you for the offer. I have another PC with Windows 7, but because P3D is not installed there, I wont be able to install the DP, right? I might try it the other way around (DU on W7 and DP on W10) and see how that goes.
Regards
Jerry
-
Hello,
I am running both on the same computer; and I am using Windows 10 Pro 64bit.
Jerry
-
Hello, I recently decided to install EFB and opted out for a trial at first. I downloaded the 1.5.1 setup executable and ran it as per the Installation and Configuration pdf.
I started the Data Provider, set it up and was configured with no errors (except some really large letter spacing). I then started the Display Unit, set it up and after the splash screen I immediately get this message
I click OK and then it crashes. Has anyone a clue as to why this happens? I've tried reinstalling it and also reinstalling SimConnect to no avail.
Regards
Jerry M.
Cannot start Display Unit
in EFB v1 (Read only, no longer supported)
Posted
I am glad some of you have been able to fix their problems. I see that some of you had to remove CDU.ttf, or AirbusPFD.ttf, or AirbusPFD2.ttf.
I found that for me, the AirbusDisp and AirbusPFD were the cause of problems. I can have either one installed but not both at the same time.
In my case, AirbusPFD2 was causing text in steam, microsoft edge, and other applications to look weird. A fixed .ttf is found on the aerosoft forums and for my particular case it did not interfere with EFB. Aerosoft are now aware of these problems with fonts and will fix them
Keep well
Jerry