EFB not working

Doc Savage

I have managed to create a new community folder and installed only the Vulcan download and EFB is now working.
As to what mod is conflicting I have know idea as I have 17 mods installed in the community folder i have now disabled.

Martyn

Thanks for confirming that the B78XH mod was the cause of this issue. That has also been confirmed elsewhere.

Doc Savage

@Martyn said in EFB not working:

Thanks for confirming that the B78XH mod was the cause of this issue. That has also been confirmed elsewhere.

But, it was not the cause of my issue, like I said, I've had to disable all 17 of my mods just to get the EFB working

Martyn

@Doc-Savage Unfortunately it sounds like you'll need to add each of those back in to see which is causing the conflict.

Doc Savage

@Martyn said in EFB not working:

@Doc-Savage Unfortunately it sounds like you'll need to add each of those back in to see which is causing the conflict.

I am doing that as we speak....

Doc Savage

@Doc-Savage said in EFB not working:

@Martyn said in EFB not working:

@Doc-Savage Unfortunately it sounds like you'll need to add each of those back in to see which is causing the conflict.

I am doing that as we speak....

My Bad it was the B78XH mod, just never saw it in amongst my mods.

? Offline

Hello,

i never had this mod installed and it did not work either.
So any ideas what else could cause this?
Thank you.

Martyn

@TGS Does it work OK if you remove everything but the Vulcan from your Community folder?

? Offline

Hello,

I removed ALL and then it worked.

But is this the conclusion, I have to remove all my paid add-ons to use the Vulcan?
The panels of the navigator and AEO are still not working!

Sorry, but I think it is your add-on is causing the issues as everything else worked before!
I use PMDG with an EFB, no issues! I use FBWA320 no issues with other paid add-ons.

For me it is inacceptable to remove all my add-ons to use one!

The 787 mod was never an issue because I never used it but I want to use it in the future.

My conclusion is that your add-on is interfering with any other software somehow.

I hope you find the issue shortly because I will not use the Vulcan this way.

If you have no solution I want an immidiate refund.

Regards

Martyn

@TGS No, that wasn't the conclusion, it was just a way of confirming that the issue is being caused by a conflict with another package in the Community folder. We are not able to verify compatibility with the hundreds or thousands of other packages (mods) that are available, so you will need to either reinstall those a few at a time to confirm which one is causing the conflict or contact our support team via our website for an exchange or refund. To be clear though, this isn't a bug in our EFB, but there might be something like a file naming conflict.

As far as we know, based on feedback from the community, the EFB issue is caused by conflicts with other packages, or possibly just the 787 mod, however the AEO and navigator panels not working is a separate issue. If the issue you are having with those is that none of the controls can be operated (no click spots) then you need to change from LOCK to LEGACY interaction mode in the MSFS accessibility settings menu. That will no longer be a requirement though once the Vulcan v1.1 update has been released.

? Offline

Funny that other publisher have no issues.
I want a refund.

Martyn

@TGS We'll have to agree to disagree. Please contact the support team: https://support.justflight.com/

kubar22

I would also like to add that I was having the same problem with the non working of the EFB in the Bae146, but when I moved my B78XH file from the Community folder, the problem was gone and was able to access the EFB.

NickW61

Same problem here on BAE 146-300 v2. Was fine yesterday before the Cities update. I don't have B78XH installed.

NickW61

@NickW61 I took at the Horizons 787-9 and seem to be ok again - why does the 787 seem to conflict?

Mark

We're not sure of the exact reason why the 787 mods are causing a conflict with our products, as well as some other developer's products. Those mods may be using some edits/modifications to core MSFS files that are causing conflicts with other third-party products that call on those files for their own functionality.

Mark - Just Flight

NickW61

@Mark Thanks for the quick reply. Could you try and liaise with them? I will try and let them know but there is less "pressure" on them as their product works. Personally, I haven't found a conflict with any other aircraft.

NickW61

@Mark FYI - Horizons are looking into the issue. This from their discord:
"Hello all,

We're aware of an issue regarding our 789 & causing issues with justflights bae efb & fsreborns efb. At this moment in time the team is currently investigating the issue to see if there's anything we can do. As a temporary workaround. You can use addonlinker to remove 789 if you wish to fly just flights or fsreborns products & vice versa.

Kind regards

David - B787-9 Project Manager,
Horizon Simulations Team"

NickW61

@Mark Horizons report this as fixed at version 1.1.2 and it worked for me this morning. From Discord:
"CPDLC so far has been a huge success! We are aware of the CPDLC update breaking other aircraft, namely JFs BAE146's EFBs and FSReborn's EFBs and a fix is now here after a whole load of load of stress.

Horizon Simulations 787-9 v1.1.2
Changelog
Fixed conflicts with other aircraft"

Mark

@NickW61 Thanks for letting us know. We've passed this info on to our support team so that they can quickly point users in the right direction if they run into this issue.

Mark - Just Flight